Definition
What is process guidance software?
Process guidance software tells a person the next step of their team's documented process for the specific piece of work in front of them — a ticket, an issue, a request, a release, a new hire, a purchase — using its real context, and cites the document it followed. It is not specific to teams that work with tickets.
The problem it solves
Most teams have their processes written down: a triage runbook in Confluence, a release checklist in a Google Doc, an escalation policy in a wiki. The document is far from the work. The ticket is in Freshdesk, the engineering issue is in Jira, the decision was made in a Slack thread. Nobody has time to join them, so new and busy people guess. Escalations bounce, customers are told the wrong thing, releases skip a check, and the senior people spend their day answering "what do I do with this?".
How process guidance works
- Gather the context. The ticket and its conversation, the linked Jira issue and its history, the Slack threads about it, the meeting notes where a decision was made.
- Pick the process. From the processes the team documents, the one that applies to this item, read live from where it lives, with its version.
- Work out where the item is. From what has actually happened — comments, notes, calls — not from the status field, which is often stale.
- Say the next step. One step, with an owner, what it means in one to three bullets, and the sentence of the document that makes it the next step. If a fact that would change the step is missing (which environment was it tested on? did the customer confirm?), ask instead of assuming.
- Learn from corrections. When someone marks an answer wrong, the correction applies to similar items from then on and becomes a suggested edit to the document.
Compared with what teams already have
| Knowledge base / wiki | Helpdesk AI copilot | LMS | Process guidance | |
|---|---|---|---|---|
| Scope | Stores the document | The ticket in one tool | Courses and completions | The process across the tools |
| Output | A page to read | A draft reply, a snippet | A certificate | The next step, cited; a course from the same document; edits back to it |
| When the document is wrong | Nobody notices | Drafts the wrong reply well | Teaches the wrong thing | Corrections become suggested edits |
What to measure
- Bounced escalations — items sent to the wrong team or without the required evidence.
- Senior interruptions — questions in Slack answered by people who should be doing something else.
- Time to first unaided ticket — how long a new hire needs before working an item without help.
Agree the three numbers before a pilot; report them after 90 days.
Ovenbird
Ovenbird is process guidance software built on this loop: Design (the process as a graph), Learn (scenario-based training with mastery per stage and refreshers at 2, 7, 30 and 90 days), Ask (the next step on the real item, in Slack or on the web), Improve (corrections, unanswered questions and failed scenarios become suggested edits). It also simulates where a process will bottleneck on your own numbers, keeps every version of a document with a plain-words summary of what changed, and works across Freshdesk, Jira, Confluence, Slack and Google Docs.