Which processes should a founder-led company map first?
Map the six to ten core processes that produce the outcomes on your function map, and write first the ones whose failure would hurt the company most. Give each process one owner and record its documented and followed statuses separately. Then trace one recent customer order through them to draw your first map.
In the Founder Blueprint, this work comes after the founder has set the vision and the leadership team has built this year's milestones and the function map. Core processes are built in a later working session, after the people decisions, so each process belongs to a function that already has an owner. A coach facilitates the session and the team builds the processes.
The function map itself is covered in how a founder maps the company's critical functions. Use it to decide which outcomes need a repeatable process.
Keep the first list at company level. A founder who starts by listing every action someone performs ends up with a documentation project before the team has agreed which work the company depends on.
What counts as a core process, and what is only a task or a checklist?
A core process is a repeating sequence with a trigger and an end point. It produces an outcome a function answers for, and it usually passes between several people. "Customer order fulfillment" describes a sequence the team can follow from an accepted order to a completed delivery.
A task is a single piece of work with a finish line, such as confirming a delivery address. A procedure gives detailed instructions for one part of the work, and a checklist records the checks to complete, such as those required before an order is released. Several procedures can support the same core process.
The Blueprint holds the company-level list to six to ten core processes. Each process owner can add supporting procedures later, where the team needs more detailed instructions. Begin by agreeing where each core process starts and ends.
A sequence that only one person knows leaves the company when that person does. The owner writes it down so the next person can use it, and the team follows the written version.
How do you find the six to ten core processes?
Work through the responsibilities on the function map and ask which repeating sequence produces each one. Name each process for what happens, such as billing and collection. A department name on its own leaves the sequence undefined.
Then check the list against one customer order from first contact to cash collected. Identify which process handles each part of that order and where responsibility passes to the next process. A step that fits nowhere shows the list has left out part of the work.
Check separately for the work that continues in a week with no new orders. People still have to be paid and the books still have to be closed, and a list built only around winning and serving customers tends to leave those obligations out.
The example below is illustrative and describes no client: an invented company that supplies and installs commercial equipment.
| Core process | Owner | Starts when | Ends when |
|---|---|---|---|
| Inquiry to accepted order | Sales manager | A prospective customer makes an inquiry | An order is accepted or the inquiry is closed |
| Order fulfillment | Operations manager | An accepted order reaches operations | The customer accepts the installation and completion is recorded |
| Purchasing and supplier payment | Purchasing manager | An approved purchasing need is received | Receipt is confirmed and the supplier is paid |
| Billing and collection | Finance manager | An agreed billing milestone is reached | Payment is received and matched to the invoice |
| Service request resolution | Service manager | A customer reports a service issue | The customer confirms the fix and the request is closed |
| Hiring and onboarding | Office manager | A hiring need is approved | The new employee completes the agreed onboarding |
| Payroll | Finance manager | A pay period closes | Pay is issued and payroll records are complete |
| Monthly close | Finance manager | The accounting month ends | Reconciled accounts are reviewed and the month is closed |
Use your own work to set the boundaries. One person can own several processes, and a process can involve people from different functions. The owner is the person who answers for the complete sequence.
If your list falls outside six to ten, check whether a broad label such as "operations" combines separate processes, or whether detailed entries belong inside another process. Test a doubtful entry by stating its trigger and the outcome it produces before you change the count.
Which process do you write first?
Write first the process whose failure tomorrow would cause the most damage. Weigh a customer being let down, cash arriving late, legal or safety exposure, and work that would pull the founder back into daily decisions.
Describe the consequence for each process in one sentence. "Completed work could go unbilled" gives the leadership team something concrete to compare with a late internal report. Settle disagreements about priority by asking what would happen if the process stopped.
The Blueprint records documented and followed separately because a document on its own does not show whether people use it. A team can also follow a consistent sequence that has never been written down. Mark a process followed only when the team can describe the sequence and recent work shows it.
Each combination of the two statuses calls for a different first job.
| Status | What it usually means | First job |
|---|---|---|
| Documented and followed | A usable process exists. | Check that it still produces the required outcome, and keep it current. |
| Documented, not followed | The written version may be impractical or out of date, or people may need help using it. | Compare recent work with the document and find out why they differ. |
| Followed, not documented | The team repeats an agreed sequence from memory. | Have the owner write the sequence down and confirm it with the people who use it. |
| Neither | The work changes depending on who does it. | Agree the essential steps, write them down, and use them on the next suitable piece of work. |
Our guide to handing off work so it does not come back explains why the owner writes the process and where a mistake costs the most. Write the processes one at a time.
How do you draw the first map?
Trace one customer order from the last month with the people who handled it. Choose an order that shows how the work went, delays and corrections included, and draw it on paper or a whiteboard.
Start at the customer's first contact and continue until the cash was collected. For every step, record who did it and what started it, then what the step produced and where that work went next.
Write each step so that someone who touched the order would recognize it. "Sales emailed the accepted order to operations" gives the map an action and a recipient. If people disagree about a step, check the order's records or ask the person who did it.
Mark every point where the work passed between people or functions, including work sent back for correction. Mark where it waited and every time someone asked the founder for a decision. Include calls and conversations that changed what happened next, even when nobody recorded them in a system.
Then mark the steps that differed from the way people would normally describe the process. An order may have moved ahead before an approval, or someone may have supplied information the standard request leaves out. Record those differences before deciding which ones should change.
Finally, label the core processes the order passed through. The map shows how they connect and often points to the one that needs attention first. Keep it to hand while the owner writes that process, so the draft can be checked against work the team remembers.
If the process you will write first is internal, such as payroll, reconstruct a recent example of it the same way: a completed pay run, from its trigger to its end point, with the people who handled it.
How much should a written process say?
A written process should say enough for the team to follow it, and a short outline is a useful starting point. Include its name and owner, what starts it and what finishes it, the main steps in order, the standard that marks it done right, the handoffs, and who decides exceptions.
Use the words employees use when they do the work. "Send the completed installation record to finance" tells someone what to do. "Complete the required administration" leaves the next person to decide what that includes.
An illustrative outline for the invented company's billing and collection process:
- Owner: Finance manager.
- Starts when: The agreed billing milestone has been reached.
- Ends when: Payment is received and matched to the invoice.
- Main steps: Confirm the billing evidence. Prepare and send the invoice. Follow up according to the agreed payment terms. Record and match the receipt.
- Done right: The invoice matches the accepted order and the billing milestone, and the payment is recorded against the correct customer.
- Handoffs: Operations sends completion evidence to finance. Finance sends any delivery dispute to the operations manager.
- Exceptions: Missing evidence goes back to whoever was due to supply it. A request to change payment terms goes to the finance manager.
Stop once the team can perform the process consistently. A separate procedure can explain a difficult step for whoever needs that detail, which keeps instructions for a software screen out of the core process.
Use the draft on the next suitable order and note every point where someone had to ask what it meant. Fix those points with the owner. The Blueprint counts a process as in place only when the team follows it.
Do you need a consultant or process mining software for the first map?
For a first process map in a founder-led company, start with your own team: the people who do the work can usually reconstruct it from a recent example. A consultant helps when the team needs a facilitator or specialist knowledge, and process mining helps when the event data your systems record can answer a defined question about repeated work. The two can be combined.
Process mining software reconstructs work from the event logs that business systems record, such as an ERP or a CRM. It shows the steps those systems recorded and when they happened. A decision made by phone or agreed over email stays outside its view unless that activity is captured in the logs being analyzed.
Consider process mining when you have a specific question about repeated work and your systems record usable event data for the steps involved. It can then examine flows that would be slow to reconstruct one example at a time. Before buying, find out which steps your systems record, and weigh the work of preparing that data and interpreting the results against the question you want answered.
A consultant is useful when the team needs an independent facilitator to settle conflicting accounts of the work. Specialist knowledge may also be needed for regulated processes or work with safety requirements. Define the help you need before you choose someone.
Outside help should leave each process owner able to explain and maintain the work. A consultant can draft the documentation from interviews and observation, with each owner checking the draft against recent work. Agree before the engagement starts who will test the instructions and who will maintain them afterwards. For the broader choice between a consultant and an installed operating system, see Founder Blueprint or a consultant.
How do you keep processes current?
Each owner keeps their written process current, and the leadership team checks the documented and followed statuses at the quarterly review. In the Blueprint, the core processes sit on the same quarterly review page as the function map, so both are reviewed together.
Update a process when the work changes or its owner changes, or when a repeated mistake shows the written version is wrong. Make the correction as soon as the need is clear, because waiting for the quarterly review leaves people using instructions the team already knows are wrong.
At the review, compare each document with recent work and ask the people using it where they departed from the steps. Correct the wording or deal with the reason people cannot follow it, then check its use again.
Choosing measures for the processes belongs to the weekly scorecard, which comes after the processes in the Blueprint sequence.
Where should we start this week?
Book an hour with the people who handled one customer order last month and trace it from first contact to cash collected. Bring the function map, and finish by choosing one core process for its owner to write or correct first.
When the team is ready to build all six to ten, the Founder Blueprint is where we run that working session with a coach.
Frequently asked
Document first the process whose failure would cause the most damage. Start from the outcomes on the function map, then weigh customer harm, delayed cash, legal or safety exposure, and work that would return to the founder. The Founder Blueprint uses six to ten core processes, each with one owner, and writes them one at a time.
The Founder Blueprint uses six to ten core processes at company level, and each company defines its own. If your list is much shorter, check for a broad label that combines separate sequences. For a much longer list, check whether some entries are tasks or supporting procedures that belong inside a core process.
A core process runs from a trigger to an outcome that a function answers for, and it usually passes between several people. A checklist records the actions or checks to complete within that sequence, such as the checks required before dispatch. Agree the company-level process first, then let its owner add supporting checklists where the people doing the work need them.
Yes. A team can repeat a consistent sequence it has never written down. The Founder Blueprint records documented and followed separately so that case is visible. Confirm the sequence with the people doing it and check recent work before marking it followed. The owner then writes it down, so the company keeps the knowledge when someone is absent or leaves.
For a first map, usually no. Process mining analyzes the event data that business systems record, so calls, emails and decisions made in conversation are included only when that data captures them. Start by tracing a recent order with the people who handled it. Consider software later, when you have a specific question about repeated work and your systems record the steps it involves.
Write to the level the team will follow. A short outline is a useful start: the owner, where the process starts and ends, the main steps, the completion standard, the handoffs, and who decides exceptions. Use it on the next suitable piece of work, fix whatever someone had to ask about, and add a separate procedure only where one step needs more explanation.
Next step
To see which parts of the company still depend on you, take the Leadership Scorecard, a ten-minute self-assessment across twelve leadership dimensions and the six drivers of founder-led growth. Your leadership team can discuss the results alongside the first process map.