How it works
Start with one team. Four weeks later, it runs on a system.
You do not need to describe the whole company before Flow is useful. Start where mistakes cost the most, then grow team by team.
- 01
Map the process
Draw how work actually happens, with a lane for every role. Decisions, hand-offs and sub-processes included.
- 02
Connect the know-how
Link each step to the standard that describes it, the role that performs it and the lesson that teaches it.
- 03
Train by role
Tracks assign themselves to the right people — including every new hire, on their first day.
- 04
Check that it stuck
Tests and scheduled re-certification show who really knows the work, and which topics are weak.
A typical first month
- Week 1Pick one team and its three most important processes. Draw them in Flow and attach the standards you already have.
- Week 2Fill the gaps: write missing standards, add the roles, and generate the first training track from a process.
- Week 3Assign the track to the role, add a test, and let the team go through it. Watch the first results.
- Week 4Fix what the results show, set review dates and re-certification, then repeat for the next team.
Timing depends on how much of your work is already written down.
Two ways to start
On your own
Your owner, operations lead or team leads set Flow up with templates and our guides. Most companies start this way.
With our team
We run the first rollout with you: interviews with your best people, the first processes and standards, the first track and test.