Five roles take part in mapping an area with kawaru.app.
| Role | What they do | When | Time |
|---|---|---|---|
| Sponsor | Agrees the scope and the start of the pilot. Nothing hands-on. | At the start and at the readout | about an hour each time |
| Lead | Does all the hands-on work: sets up the value chain and the end-to-end processes, chooses the people and invites them by email, follows up, runs the review. AI agents interview everyone in parallel. | From start to finish | 5–6 days for an area of 150–300 people |
| Invited person | Describes their own work: first the list of what they do, how often, how long it takes and what gets in the way, then their processes step by step for the detailed maps. | After the invitation | about 20 minutes, then 20–40 minutes per detailed map |
| Process owner | Describes one process step by step and confirms its map. | As soon as the process is in the inventory | 1–2 hours per process |
| Reviewer | Decides whether two descriptions of a process are the same process or two different ones. | When people describe a process differently | a few minutes per process |
Sponsor
Agrees the scope at the start and the pilot at the end. Does nothing hands-on: the lead runs everything.
- Agrees the scope. One meeting with the lead settles the business area and the objective: free up time, or handle more volume with the same team.
- Agrees the start of the pilot at the readout, based on the map and the options.
At the readout: the value chain of the area with every process in place, the end-to-end processes across teams, and the options for the first pilot.
Common mistake: widening the scope halfway. New areas go into the next wave, on the same value chain.
Lead
Owns the project from creation to an agreed map, then builds the plan on top of it.
- Creates the project, with an industry template if one fits.
- Runs the company interview.
- Sets up the end-to-end processes and names who does each step.
- Chooses the people: 1–3 per role who do the work every day.
- Invites everyone at once. AI agents interview them in parallel.
- Follows up daily. The pace is set by how fast people answer. Pending invites and the Inventory are checked every day.
- Picks what to map in detail: every step of the end-to-end processes, then the processes with the most hours and pain.
- Runs the review with the Reviewer and the process owners.
- Fills in Setup and reads the Solution step by step.
Done when every step of the end-to-end processes and the top processes are mapped, and nothing is waiting in Review.
Common mistakes:
- Waiting for every inventory before starting detailed maps. The two run in parallel.
- Inviting only managers. Managers describe how work should run; the people doing it describe how it runs.
- Mixing a person's volume with the team's. "9,000 contacts a month across a team of 12" is clear, "40 a day" is not.
Invited person
Describes their own work in two interviews, each at a time that suits them. No preparation is needed, and nobody is assessed.
- Inventory interview, about 20 minutes: everything they do regularly, with rough numbers.
- Process interview, 20 to 40 minutes per process: one process step by step.
Workarounds and exceptions are the most useful part. Customer records and personal data never go in.
Process owner
Answers for one or more processes and confirms their maps.
- Opens the process on the Value Chain and starts the process interview from its card.
- Attaches what exists first: procedures, policies, checklists.
- Walks through the process as it really runs.
- Reads the map back and corrects it.
- Checks how the process fits its chain: what comes in from the previous team and goes out to the next.
- Later, checks the To be map and signs off the spec of their agent.
Common mistake: describing the process as the policy says it should run, instead of what happens on a normal day.
Reviewer
Decides whether differing versions are one process or two. Only this role sees whose version is whose.
- Opens Review in the menu.
- Starts with the most differences.
- Reads the comparison: where steps, order, people, systems or time differ.
- Decides: same process, or different processes.
Common mistake: treating a difference as an error. Two teams may simply work differently, and that is a finding worth keeping.