Leave the workshop with the process map already done
You run current-state sessions on an IT transformation program. Six people from finance operations, ninety minutes, and your job is to come out with an accurate picture of how invoice approval actually works today. Wavelength is a voice to diagram tool that builds that picture while the session is happening, so what you take away has already been corrected by the people who own the process.
The moment that hurts is not the workshop. It is the next morning, when you open Visio with a notebook full of arrows and a transcript you have not read, and start rebuilding a conversation you were only half-recording because you were busy running it.
The demo needs no account. The free plan needs no card.
This is a latency problem, not a drawing problem
Nobody on a transformation program struggles to draw a flowchart. Drawing is the easy part. The problem is the gap between the process being described and a picture of it getting back in front of the people who described it.
In that gap, two things go wrong. You lose most of a day rebuilding the flow from notes, and you rebuild it from your own understanding, so every misunderstanding you had in the room is now a confident-looking box with a confident-looking arrow coming out of it.
So the corrections come back the slow way. One reply on Tuesday saying the credit check happens before the approval, not after. Another on Thursday from someone who was not in the session, contradicting the first. A third the following week reopening a question you thought was closed. None of them happen in front of the other stakeholders, so nobody is reconciled against anybody. You are running consensus by email, one participant at a time, over a two weeks. The map is stale before sign-off, and the signature you get is not agreement, it is fatigue.
The diagram is not the deliverable. Agreement on the diagram is the deliverable, and agreement decays fast once people leave the room.
What the alternatives cost
| What you do today | What it costs |
|---|---|
| Take notes, rebuild the flow afterward | Most of a day of rework per session, and you rebuild from your own understanding, so every error is one you introduced and cannot see. |
| Assign a BA to document it | Adds a handoff and about a week. The BA did not ask the questions, so the first draft comes back with gaps that need another session. |
| Record the call, watch it back later | You will not watch it back. Nobody watches ninety minutes back. It becomes an insurance policy you never claim on. |
| Draw live in Visio while facilitating | You stop facilitating. The room watches you place rectangles and the quiet person who knew about the manual workaround never speaks. |
| Skip the map, rely on the requirements document | Nobody reads a forty page document. Process errors survive review, reach build, and surface in UAT as change requests. |
What the session looks like instead
- Run the session the way you always run it. Ask the process owner to walk you through what happens when an invoice arrives. As they talk, the actors, systems, decisions, and handoffs appear on the canvas.
- Screen-share once there is something worth looking at. Usually two or three minutes in. This is the step that changes the workshop.
- Let the room correct it. People who cannot describe a process accurately will spot an inaccurate picture of it instantly. "That approval goes to the cost center owner first" is a sentence you would not have extracted by asking.
- Mark the inferred connections. Anything Wavelength inferred rather than heard is rendered differently, which gives you a short list of exactly what to confirm out loud before you wrap up.
- Export and attach it to the follow-up. Send the map with the actions before the meeting invite has expired, while everyone still remembers agreeing to it.
Unlike Lucidchart, Miro, and Visio, which require you to draw the process map after the workshop, Wavelength builds it live during the session, so the client validates the as-is process in the room instead of two weeks later in a review cycle.
For the facilitation detail, see how to run a process mapping workshop and how to document a current state process.
Why in-room validation is the whole argument
A picture a business owner corrected in the room is a fundamentally different artifact from a picture you drew and emailed them, even when the two are pixel for pixel identical.
The emailed one carries your authority. Whoever opens it is being asked to review your interpretation of their job, in a format they did not choose, at a moment they did not pick. The polite response is to skim it and reply "looks fine," which is what you usually get, and which is worth almost nothing.
The corrected one carries theirs. They watched it get built, saw a box in the wrong place, said so, and watched it move. That is not review, it is authorship. When a question comes up in design eight weeks later about whether rejected invoices really do go back to the requisitioner, the answer is not "the PM's notes say so." It is that the finance operations lead confirmed it in front of four colleagues. That artifact survives challenge. Notes do not.
It also front-loads disagreements. When two stakeholders hold different models of the same process, and they usually do, a shared picture surfaces the conflict inside the ninety minutes you had already budgeted. Found by email a two weeks later, it costs a re-run session and a slipped milestone.
Where it fits in the program lifecycle
- Discovery and current-state capture. One session, one validated as-is map, no rebuild.
- Requirements workshops. Process first, requirements second. It is easier to judge a requirement when everyone can see where in the flow it lands.
- Design and future-state. Draw the to-be next to the as-is in the same session. The delta is your scope, and it is more defensible than a scope derived from a list of asks.
- Handover to build. The delivery team inherits a map the business already agreed to, rather than a project manager's notes plus a document nobody read.
- Change impact, later. When someone proposes a change in month seven, a genuinely validated as-is map is worth a great deal, because you can point at what it touches instead of reopening discovery.
If you do this work as an external rather than in-house, the client-facing version of the same argument is on the page for IT transformation consultants.
Where this does not fit
Wavelength maps the process. It does not manage the project. No Microsoft Project or Jira integration, no RAID log, no Gantt chart, no resource plan. If you want something to replace your planning stack, this is not it and will not become it.
It also does not do formal notation. No BPMN 2.0 with correct symbology, no UML, no entity relationship diagrams, no C4. If your program's method mandates BPMN, capture the shape of the process in the room, get it agreed, then formalize the notation afterward in whatever tool your standard requires. You still save the rebuild, and you are at least formalizing something true.
And it will not rescue a session with bad room audio. A speakerphone in a large meeting room, three people talking over each other, or a poor dial-in line will all produce poor results. In those conditions, record the session and paste the transcript afterward. See transcript to flowchart for that route.
A reasonable first test
Take one scheduled current-state session, low stakes enough that a tooling experiment cannot damage anything. Run it as normal, share the screen at the ten minute mark, and see whether the room corrects the map. If it does not, you still have your notes.
Common questions
Does this replace Visio or Lucidchart?
No. It covers the capture stage, where nobody yet knows the shape of the process. Once the flow is agreed you can export it and rebuild it to your program's house standard. Most technical project managers keep both. The Lucidchart comparison sets out where each is the better choice.
Can I use a Teams or Zoom transcript instead of running it live?
Yes. Paste the transcript and you get the same editable map. Useful for sessions you did not facilitate, or where live tooling is not yet approved. You lose the in-room correction, which is the main benefit, but you still avoid the rebuild.
What happens to confidential client process data?
Flows are private to your account by default and visible only to collaborators you invite to a specific flow. Nothing is published unless you export it. If your program runs under a client information security policy, check it first, the same way you would for a transcription service.
Can the business owner edit the map themselves?
They can be invited as a collaborator on a specific flow, which helps between sessions. In practice most correction happens verbally while you drive, because a process owner will say what is wrong far faster than they will edit a diagram. Collaborator features and team libraries are on the pricing page.
Does it export to something I can put in a deck?
Yes. Export a PNG for a steering pack or a requirements document, or share a link for people who want the live flow. The usual pattern is to attach the export to the workshop follow-up the same day.