Home/Mindbreeze/Use cases/Process Guide
Use cases · ProcessesProcess Guide: step by step through processes people rarely do
Onboarding a supplier, requesting an exception, closing a project: processes people do a few times a year. Process Guide walks them through each step from your own procedures, and tells them what comes next.
Discuss this use case All use cases
Illustrative example
In short
Process Guide is a Mindbreeze agent that guides employees step by step through complex or infrequent processes, such as onboarding a supplier, requesting an exception or closing a project. It explains each step from your approved procedures and work instructions, points to the right form or system and says who acts next, with links to the sources. The process owner keeps the procedure; Process Guide helps people follow it. SoftAdvice sets it up with your process owners.
The procedure is written down; following it is the hard part
Processes that people do rarely are the ones where mistakes happen: a step is skipped, the wrong form is used or the request goes to the wrong person. The procedure exists, but it is long, spread over several documents and written for the process owner rather than for the person who has to follow it.
- Procedures and work instructions
- Forms and templates
- Approval rules and roles
- Process descriptions and flowcharts
From “where do I start?” to a completed process
The agent guides; the employee acts and the usual approvals stay in place.
Ask
An employee says what they need to do, in their own words.
Guide step by step
Process Guide explains the current step, the form or system to use and who acts next, with sources.
Act
The employee completes each step in the usual system; approvals follow the normal route.
Improve the process
Questions show where the procedure is unclear, so the process owner can improve it.
A person decides, the sources stay visible
The agent prepares; a person checks and decides. Every answer links to the documents it used, so anyone can see later what it was based on.
Mindbreeze applies the permissions of each source system: what someone cannot open in the source, they do not see in the answer. If access in a source is too broad today, that is fixed in the source; we check it before the start.
- Answers support, people decide
- Permissions of each source respected
- Sources linked in every answer
- Access checked before the start
What we measure on a first use case
We agree the baseline with your team before the start, so the result is measured on your own questions.
Errors and rework
How often requests come back incomplete or go to the wrong person, before and after.
Questions to the process owner
How many “how does this work?” questions still reach the owner.
Answer usefulness
Users rate the guidance against an agreed set of real situations.
Permission tests
Test users confirm that nobody sees what they may not open.
What this use case needs, and what it does not do
Guidance is only as good as the procedures. Before the start we agree which processes are in scope, which procedures are approved and current, and who owns each one. Process Guide explains the steps; it does not skip approvals or act in other systems on its own.
These pages describe how a Mindbreeze agent can be set up for this task. They are not customer references: we describe them without names or figures, and the example answers are illustrative.
- Processes in scope agreed
- An owner per process
- Approvals stay in place
- Procedures kept current
Questions about this use case
What is Process Guide?
Process Guide is one of the pre-built agentic use cases (Insight Touchpoints) in Mindbreeze Insight Workplace. SoftAdvice connects it to your sources, sets it up for your rules and team, and measures the result with you.
Is this the same as a workflow?
No. A workflow in a system such as M-Files enforces the steps; Process Guide explains them to the person. They work well together: the guide explains, the workflow makes sure nothing is skipped.
Do we need to move our documents?
No. The documents stay in the systems where they are today. Mindbreeze connects to them; which systems can be connected is confirmed per system before the start.
How do we start?
With a conversation about one use case: the team, the typical questions and the systems involved. From there we propose a scoped first step.
Would this help your team?
Tell us about the team, the questions and the systems involved. We come back with a proposal for a scoped first step.