How does a founder map the company's critical functions?
Start from this year's plan, list the recurring work the company needs, and group it into five to eight critical functions. Write three key responsibilities for each function before putting one person's name against it, then review the map every quarter.
We build in that order so the functions describe the work the company needs before anyone discusses who will own it. A function map records continuing work and the person who answers for it. Our guide to how a founder hands off work so it does not come back covers how that differs from an org chart and why it matters for delegation.
Who should build the function map?
The leadership team builds it, with a coach facilitating, after the founder has set the direction. The founder takes part in the discussion like the other leaders, and once the functions are defined, answers for any function assigned to them.
In the Founder Blueprint, the founder first works alone with the coach to set the vision. The leadership team then spends a full working day turning the three-year view into this year's milestones and drawing the function map from that plan. Our guide to whether a founder should set the vision alone explains that split.
The order matters when a milestone changes what the company must be able to do. A plan to serve customers in a second location, for example, may create continuing work that nobody on the current team is responsible for.
We want the owners to write their own lines, so each owner has agreed the wording they will answer for. The team discusses what each responsibility includes and where another function takes over, and in that discussion an owner can challenge an assumption before accepting the outcome.
Keep the owner column blank while the team identifies the functions and writes the responsibilities. Starting from current job titles encourages the team to fit the work around the existing allocation and carry its gaps onto the map. Once the work is defined, assign the owners before the session ends. People decisions, core processes and the weekly scorecard follow in a later session, once ownership is clear.
How do you find the five to eight functions?
Compare this year's milestones with the recurring work it takes to serve a customer and collect payment. Then look at the support work that keeps that activity running.
Take one customer order through the company from first contact. Describe how the company agrees the work and prepares for delivery, then follow it through completion and invoicing until the cash has been collected. Note any work the customer needs after delivery.
Use the work your company does. If a customer needs approval before delivery can begin, include the work of securing that approval. If the company must buy materials before it can fulfill an order, include purchasing.
Then check the work around the customer order. Include the financial work the business needs even in a week when no new order arrives, and the work of giving employees what they need to do their jobs. Compare this inventory with the year's milestones to find requirements that today's work does not yet cover.
We use a practical test for a proposed function: it needs continuing ownership, its outcome can be measured, and it fails visibly when nobody owns it. Some of the work may fall due monthly, and someone still has to be responsible between deadlines.
A project with an end date belongs under the function responsible for the continuing outcome. Launching a new website may support customer acquisition, and the launch itself does not create a permanent function.
Group related work by the outcome one owner can answer for. If two proposed functions contain the same responsibility, decide where that outcome belongs and write down what the other function contributes.
Fewer than five functions usually means separate areas of work have been merged, so no single owner is visible. Look inside a broad label such as "operations" for outcomes that need separate owners. More than eight usually means tasks, projects or departments have been listed as functions, and the map stops being useful for decisions.
The example below is illustrative and describes no client: an invented maintenance business with six functions, two of them held by the founder.
| Function | Owner | Three key responsibilities |
|---|---|---|
| Customer acquisition | Founder | Qualified inquiries meet the agreed target. Acquisition spending stays within the approved budget. New opportunities match the agreed customer criteria. |
| Sales | Sales lead | Accepted orders meet the sales target. Sold work meets the agreed margin. Accepted orders carry complete customer requirements. |
| Service delivery | Operations lead | Jobs finish by the agreed dates. Completed work meets the agreed acceptance requirements. Delivery costs stay within the approved job budgets. |
| Purchasing and supplies | Purchasing lead | Required materials are available by scheduled job dates. Purchases stay within approved costs. Received materials meet the agreed specifications. |
| Finance | Founder | Completed work is invoiced by the agreed deadlines. Customer payments arrive within agreed terms. Financial records are complete by each reporting deadline. |
| Employee support | Office manager | Employees have access and equipment by their start dates. Payroll information is complete by each cutoff. Required training is completed by its due dates. |
Your year's plan and your recurring work decide which functions belong on your map, so use the example to judge the level of detail. Role titles keep the illustration generic. On a working map, each line carries the name of the person who answers for that function.
How do you write three responsibilities an owner can answer for?
Write each responsibility as an outcome, with enough detail to check whether it happened. Keep three per function so the owner can hold all of them and answer for each one.
"Manage delivery" leaves the expected result open to interpretation. "Jobs finish by the agreed dates" gives the owner and the team a shared basis for review. The wording states what must happen without listing every activity it takes.
At the quarterly review, the team should be able to establish whether each responsibility was met and which figure shows it. For delivery dates, that means comparing completed jobs with their agreed deadlines. A claim that delivery was "better" cannot be checked.
Use a target or deadline the company has agreed. If a responsibility depends on a standard nobody has defined, flag that decision while writing the map. An owner cannot answer for "acceptable quality" when everyone holds a different definition of acceptable.
| Weak responsibility | Answerable responsibility | Reason |
|---|---|---|
| Help with sales | Accepted orders meet the agreed sales target. | The result can be compared with a stated target. |
| Manage projects | Customer work finishes by the agreed delivery dates. | Completed work can be checked against its deadlines. |
| Look after cash collection | Customer invoices are paid within agreed terms. | Overdue invoices show where the outcome was missed. |
| Support purchasing | Required materials are available by scheduled job dates. | Availability can be checked against the delivery schedule. |
| Handle employee training | Required training is completed by each employee's due date. | Completion records show whether the obligation was met. |
The three responsibilities should cover the function's main outcomes. If the team keeps finding more, check whether the function combines separate areas of work, or whether the additions describe activities the existing three already cover.
Avoid fitting several unrelated outcomes into one long sentence. A line that covers sales results alongside employee administration conceals an ownership decision the map needs to make.
Check the wording with the proposed owner before accepting it. They should understand the result they are taking on and be able to explain where they depend on another function. Resolve overlapping commitments while the team is together. Each function later gets its metric on the weekly scorecard.
Who owns a function that two partners share?
One partner owns it, even when both contribute to the work. With two names on one line, nobody is the single person who answers for the outcome.
The other partner can contribute expertise, approve specific decisions agreed in advance, or own a neighboring function. Write the arrangement down so the owner knows which decisions they can make alone and when the other partner's approval is required.
Suppose both partners help win customer work. One can own sales while the other owns delivery and approves the delivery dates offered to customers. The sales owner still answers for the sales responsibilities, including getting that approval before committing to a customer.
Without that record, "we both handle it" lets each partner work from a different assumption about who acts when an outcome is missed.
If two equal owners both want the same function, they settle that between themselves before the leadership team session. A disagreement between the company's owners is theirs to settle, and asking managers to choose would put them in the position of taking a partner's side.
Equal co-founders split the functions between them, and the map shows the allocation they have agreed. If that agreement is still open on the day, name one partner as interim owner and set a date by which the two of them will decide.
What should you do with unowned functions and the functions the founder keeps?
Give every unassigned function an interim owner and a review date before the session ends. The founder's name against several functions shows how the company allocates responsibility today, and the map should record it accurately.
In the companies we work with, the founder's name often appears several times on a first map. Early on, one person can hold two or three functions. Removing the repeated name without transferring ownership would make the record wrong.
Keep each function on its own line even when the owner is the same person. The founder still answers for three responsibilities under each one, and folding them into a single "founder" line would hide the separate outcomes the company depends on.
For a gap, record who owns it now and the date the leadership team will revisit the arrangement. The rest of the team then knows whom to approach in the meantime. A blank owner column leaves the decision to whoever meets the next problem.
A function the company cannot yet afford to staff can stay with the founder as a deliberate choice, with a stated trigger for reconsidering it. Record the trigger beside the review date. Our delegation guide covers that deliberate hold and which function to hand off first, and our guide to a founder's front-line hours measures how much operating work still reaches the founder.
How often should the map change?
The leadership team reviews the function map every quarter, as part of reviewing the rest of the year's execution plan. Change it when the plan changes or when an owner can no longer carry the function.
Start with each owner. Confirm that the person can still answer for the function's responsibilities, given the other functions they hold. Confirm the owner of every function at each review, including the ones that do not change.
Then compare the three responsibilities with next quarter's priorities. Keep a responsibility that still applies. Rewrite a line when the required outcome has changed enough that the old wording would point the owner at the wrong result.
Check whether a change in the plan has created or removed a function. Ending a service may remove work, and adding one may bring a continuing requirement that nobody owns yet. Follow the change through the map before assigning it.
If an owner becomes unable to carry a function between reviews, bring the decision forward. Record the replacement and tell everyone whose work depends on it, so no function waits for the next quarter without an owner.
When someone dislikes their line, discuss the concern. A change still has to rest on the work or on the owner's capacity to carry it, with the new owner agreed.
Where should we start this week?
Put this year's milestones in a shared document and ask each member of the leadership team to list the recurring work those milestones require. Add the work of taking one customer order through to payment, then the support work around it.
Leave the owner column blank. Bring the list to a full working session once the founder has set the direction, and build the map there. The Founder Blueprint is where we run that session with a coach.
Frequently asked
The Founder Blueprint uses five to eight critical functions, each with one owner and three key responsibilities. Fewer than five usually means separate areas of work have been merged, so no single owner is visible. Above eight, check whether tasks or projects have been listed as functions. One person can own several functions, and each stays on its own line.
Three per function, so the owner can hold all of them and answer for each one. Write them as outcomes the leadership team can check at the quarterly review. The limit applies to each function, so a person who owns two functions has both sets on the map and their full load stays visible.
Each function needs one owner, including in a company with equal partners. The other partner can contribute, approve particular decisions agreed in advance, or own a neighboring function. If both partners want the same function, they settle it between themselves before the team session, because a disagreement between the owners is theirs to settle.
Define the functions and their three responsibilities first, then assign people. Starting from this year's plan makes the map describe the work the company needs to run, including work that no current job title covers. Put one name against every function before the working session ends.
Assign an interim owner and a review date before the session ends. The founder may keep a function the company cannot yet afford to staff, as a deliberate decision with a recorded trigger for revisiting it. The function keeps its own line on the map so its responsibilities stay visible during the interim arrangement.
Every quarter. Check whether each owner can still carry the function and whether its three responsibilities fit next quarter's priorities, and look for functions the plan has created or removed. If an owner becomes unable to carry a function between reviews, agree a replacement then and record the change.
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. Discuss the results with your leadership team before you build the map.