What counts as front-line work for a founder?
Front-line work is operating work inside a function that someone else owns or should own. Selling an ordinary deal counts. So does doing delivery work, fixing a customer problem a manager should resolve, approving routine items, or answering questions the process should answer. The founder's involvement can be necessary today and still belong in the total.
Leadership work covers the responsibilities that stay with the founder, which our delegation guide's section on what a founder keeps sets out, together with developing the managers who own the functions. Classify by the activity. A calendar entry called "leadership meeting" contains operating work if the founder spends it assigning tomorrow's delivery jobs.
Include functions you hold because the company cannot yet support another owner. Leaving them out would hide the work a future handoff needs to remove. Record each one as it stands today, with a note about why you keep it.
What is the difference between deliberate and pulled-in hours?
Deliberate front-line hours are operating work identified in advance and scheduled with the leadership team's agreement, for a stated purpose. A planned visit to support a strategic account can qualify, and so can temporary delivery cover while a replacement learns the work.
Pulled-in front-line hours are operating work outside the involvement agreed in advance. Most of it reaches the founder because ownership is missing, a process leaves a question unanswered, or a metric cannot tell the responsible manager whether the work is on track. It also includes work you take over yourself when the responsible person could have handled it. These hours interrupt the founder's intended work, and they are the first hours we work to reduce.
A recurring interruption stays pulled-in work even when you expect it. Blocking Friday afternoon for whatever the team sends over gives those hours a slot in the calendar and no agreed purpose. Record the interventions you start yourself too: opening a routine proposal and rewriting it without being asked still consumes operating time.
The label reflects the agreement that existed before the work began. Keep the original label when an interruption turns out to have been useful, so the log continues to show how work reached you.
How should we classify selling, reviews and coaching?
Being the company's best salesperson can be a sound reason to keep a few strategic accounts. Record that selling as front-line time, and label it deliberate when the leadership team agreed its purpose and scheduled your involvement before the work began. The size of the account does not turn selling into leadership, and keeping those hours visible lets the team weigh that choice against other demands on the founder.
When you review work before it ships, setting the company's acceptance standard is leadership work, and checking every routine deliverable against that standard is operating work. If a review becomes a rewrite, split the time at the point where you began doing the delivery team's work.
Coaching a manager stays leadership while the manager keeps the decision. If you take over their staff scheduling during the conversation, count that part as front-line work. Record the activity that took place, including a change of purpose halfway through a meeting.
| Activity | Front-line or leadership? | Why |
|---|---|---|
| Following up an ordinary sales proposal | Front-line, pulled-in unless agreed | You are doing work within the sales function |
| Leading a strategic-account sale agreed with the leadership team in advance | Front-line, deliberate | The team has chosen your involvement in an operating task |
| Speaking with customers to inform company direction | Leadership | The purpose is learning for a decision the founder keeps |
| Reworking a customer deliverable | Front-line | You are producing the delivery team's output |
| Reviewing a sample to set an acceptance standard | Leadership | The work defines the standard the company will apply |
| Approving routine invoices within an agreed budget | Front-line | A finance owner should hold this operating responsibility |
| Coaching a direct report through their reasoning | Leadership | The manager keeps the decision and develops their judgment |
| Taking over a manager's staff scheduling problem | Front-line | You have taken on the manager's operating work |
Deliberate contact with customers and front-line staff should continue. Chris Zook and James Allen identify "frontline obsession" as one dimension of the founder's mentality in their book The Founder's Mentality (Harvard Business Review Press, 2016). We read that as support for purposeful contact: a learning visit can inform leadership while the operating responsibility stays with the function's owner.
How do we keep a two-week time log?
Use 30-minute blocks for two consecutive weeks. Track every working hour, so the front-line total can be checked against the time accounted for elsewhere. Label each block front-line or leadership, and keep personal administration and breaks in a separate category. A calendar or a simple sheet is enough.
For each block, write a short description of the activity and its function. Mark front-line work as deliberate or pulled-in, then record who brought it to you and why your involvement was needed. If you started it yourself, write "self". That entry separates requests from colleagues from work you chose to take over.
An entry such as "Delivery, customer complaint, pulled-in, operations manager, refund authority unclear" gives the team something to examine. "Calls" on its own is too thin to classify. Use the same function names throughout both weeks so similar work adds together.
Log as you go. Update the record when a task changes, and check for gaps at the end of each day. Rebuilding Friday's total from memory favors the meetings you remember and misses the interruptions between them.
When a block holds mixed work, divide its time using your best estimate. Several short operating questions can add up inside one block. Count elapsed time once, even if you answered email during a meeting.
How should travel, email and out-of-hours work count in the log?
Attach travel needed only for a front-line assignment to that function, and tag it as travel, so the team sees the full founder time the assignment consumes. Leave ordinary commuting out of the total, and record travel for leadership work separately. On a mixed trip, split the shared travel by a method agreed before the log begins, and count each travel period once even if you also worked during it.
Email takes the classification of the work it contains. Routine customer replies go to the relevant function as front-line time, while research for a decision the founder keeps goes in the leadership category. Divide a mixed email block by the time spent on each kind of work.
Include work done at night and on weekends in the same reporting week. A delivery problem resolved on Sunday still consumed founder time. Keep the day in the log, so moving operating work outside office hours cannot show up as a reduction.
What should we read from the two-week log?
For each week, add the deliberate and pulled-in hours to get total front-line hours, then average the two weekly totals for the baseline. As illustrative arithmetic, 12 deliberate hours and 8 pulled-in hours give 20 front-line hours in week one, and a week two total of 16 hours gives a baseline of 18 hours a week. These figures show the calculation and imply no target. Keep the individual weeks visible, because a launch or an absence can make one week unusually heavy. Note that context beside the baseline and keep the recorded hours.
Break the total down by function, with deliberate and pulled-in hours shown separately for each. This lets the team tell an agreed sales commitment apart from repeated delivery interventions. The company-wide total alone cannot show which responsibility to address first.
The function with the largest pulled-in total is the first place to look for a missing owner, process or metric, and our guide to handing off work so it does not come back covers what each of those transfers. Read the individual entries before deciding what is missing. An established owner may need the authority to act, or the founder may be stepping into work the owner could already handle.
Check who started each piece of work as well. That field shows how requests travel through the company. A colleague who reports a problem promptly should be able to do so without being blamed for the hours it took to resolve.
What should our weekly and quarterly target be?
The direction we set is downward, quarter by quarter, as functions gain capable owners, with a small deliberate share kept for an agreed purpose. The leadership team picks its own hours figure at the quarterly review, from the measured baseline and the handoffs it plans to complete. Every planned reduction needs an operating change behind it.
In the Founder Blueprint, front-line hours per week is set as the second line of the weekly scorecard, directly after cash, which is locked first. A company can edit or replace it. Leadership teams track cash and front-line hours from the first week of the install.
Once the baseline exists, put the weekly front-line total on the scorecard with the owner, target and on-track rule described in our guide to what a founder's weekly scorecard should track. Keep the deliberate and pulled-in split available behind the total.
After the detailed log, a lighter weekly method works: calendar categories or an end-of-day tally. Correct scheduled blocks for what happened, and add the interruptions that never became calendar entries.
Keep the definition stable when comparing weeks. A lower total produced by leaving out weekend work or relabeling routine approvals tells the team nothing about progress. Note holidays and unusual operating events, so the quarterly figures compare like with like.
What changes reduce pulled-in front-line hours?
Review the function with the largest pulled-in total first. Where someone already owns it, go through the entries with that person to find out why the work still reached you. Choose the responsibility to transfer after weighing its risk and the proposed owner's capacity, and check later logs for the time that responsibility used to consume.
Agree the handoff and its escalation rule as the delegation guide sets out. When a later log shows a change, note any shift in the company's workload that could explain it before crediting the handoff.
Protect leadership time in the calendar under the same agreement. The team needs to know which work can interrupt it and where other requests go. Tie the blocks to leadership responsibilities, so the hours released from operations have an intended use.
Front-line hours can rise for a while when a new owner is learning the work. Scheduled demonstrations and shared operating work count as deliberate front-line time, while coaching that leaves the manager responsible stays leadership. Agree a date to review that temporary involvement, and look for operating tasks the new owner now completes without the founder. A continued rise in pulled-in hours needs investigating, even while the total also includes planned support.
Where should we start this week?
Pick the next two consecutive weeks for the baseline. Agree the classification boundary with the leadership team, including the operating work you intend to keep. Set up the log before the first day and use the same function names throughout.
Book the review with the leadership team before logging begins, and name one person to compile the weekly totals.
Use that review to name the largest source of pulled-in hours and agree who will take responsibility for the work. Keep the baseline, so the first quarterly target has a measured starting point, and continue the lighter weekly tally during the handoff. The Founder Blueprint is where we install this measure.
Frequently asked
Front-line work can serve the company when the leadership team deliberately chooses the founder's involvement. Record interventions outside that prior agreement as pulled-in hours, including work the founder takes over without being asked. Focus the reduction on pulled-in hours and keep purposeful contact with customers and front-line staff.
A founder can keep selected strategic accounts when the leadership team agrees to it. Record that selling as deliberate front-line work and keep it visible in the weekly total. Routine deals that unexpectedly need the founder belong in the pulled-in hours for sales.
Start with two consecutive weeks and record work as it happens. Include evening and weekend work, and note unusual events beside the weekly totals. If an exceptional event dominates those weeks, keep the record and log another period before treating it as representative.
Other leaders can use the same logging method when they need to see how operating work consumes their time. Define the boundary for each role, because a functional manager can rightly carry a lot of operating work. Each leader's target should come from their own baseline and responsibilities, separate from the founder's.
A temporary increase can happen while a new manager learns through shared operating work. Separate that planned support from unplanned interventions, and agree a date to review it. Check whether the manager is taking over the activities that used to need the founder.
The idea is related, and the time log gives it a repeatable measurement. Front-line hours cover operating work inside functions that others own or should own, and the log records leadership work and personal administration separately. Separating deliberate from pulled-in time also records whether the leadership team intended the founder's involvement.
Next step
If the harder question is which parts of the company still depend on you, the Leadership Scorecard is a ten-minute self-assessment across twelve leadership dimensions and the six drivers of founder-led growth. Use its results alongside the time log when deciding which responsibilities to review first.