The Company Still Depends on Your Hours

The company still depends on your hours when a full week still waits on you. Stop one task, name who absorbs it, and protect the critical client flow.

Your week is full and the company still depends on your hours: a person dropping a stack of tasks and holding one card, with rings for stop, who, keep, and flow.

Last updated: 13 November 2026
Reviewed by: The Growth Reads editorial team
Read time: 18 minutes
Sources: 3 checked sources
Books referenced: 1
The short answer

The company still depends on your hours when a full week still stops if you step out of it. Stop one task, name the person who already does that work, and protect the critical client flow. Jenyns says the owner is the wrong person to write the system. If the only name is yours, you have not made the cut.

Key takeaways

  • The company still depends on your hours when the week is full and the work still stops unless you touch it.
  • David Jenyns’s framework page for SYSTEMology (the 2020 book) says to start with a Critical Client Flow of 10 to 15 systems, not hundreds.
  • That same page says the owner is usually the worst person to document a process, and that the owner stays out while the person doing the work records it.
  • The Critical Client Flow page on systemology.com says to map 7 to 12 steps for one client and one product, and, if you are solo, to build a small team first.
  • This week’s cut is one task you stop, one name who absorbs it, and the one flow you protect. A list of intentions with your name still on them is the same full week.

What it means when the company still depends on your hours

The company still depends on your hours when a full calendar has not moved a single recurring task off you. You are a solo founder, so the week is calls, delivery, invoices, and the fix that only you know how to make. You are a new manager, so the week is the team’s questions, the redo, and the approval that waits in your inbox. Either way you can point at a packed week and still be the reason the work stops. Busy is not the same as a company that can run a day without your hands.

The cut for this week is narrower than a new operating system. One task leaves your week. One person absorbs it. One flow stays protected, which means you do not spend the freed hours opening a second offer or a wall of documents. If you cannot name the person, you have not made the cut. You have renamed the same hours.

Your week is full and the company still depends on your hours: a capacity cut that names one task to stop, who absorbs it, and the critical client flow you protect.
One task leaves the week. One name takes it. The critical flow is the only manual you open.

Why a full week does not fix it

A full week is how the dependency hides. Every hour looks necessary because you are the one doing it. David Jenyns, on his framework page for the book SYSTEMology, describes his own digital agency in those terms. He writes that he was working 60-plus hours a week and that the business could not function without him. He writes that in 2016 he hired a CEO, stepped back from daily operations, and the business kept growing. That is his account of his company, on his site. It is not a study, and this article does not treat it as one.

The same page is where he states the method he says the 2020 book walks through. He names three myths. You do not need hundreds of systems. You need a Critical Client Flow, which he puts at 10 to 15 systems that touch the client journey, and everything else can wait. The owner is usually the worst person to document a process, because the owner is too close, too busy, and too likely to overcomplicate it. The person who should capture a system is the person already doing that work well. He calls that person the knowledgeable worker. And a rough, usable document beats a perfect system that never gets written. He calls the rough one a minimum viable system.

A second page, the Critical Client Flow page on systemology.com, gives a tighter count and a shorter exercise. It says a Critical Client Flow is 7 to 12 essential steps, about twenty minutes, for one target client and one primary product. The steps are what you do now, in two or three words, not what you wish you did. If you have more than 12, combine steps that the same person handles. Show it to someone outside the daily work. If they can follow it without a long explanation, it is done. The two pages do not agree on the number. His framework page says 10 to 15. The Critical Client Flow page says 7 to 12. We did not read a numbered page of the book, so this article will not pick a page and call it the real count. The part they agree on is the part you can use this week: not hundreds, one client, one product, and not a manual of the whole company.

The cut: one task off your week, one name on it, one client flow protected. The owner does not spend tonight writing the system.
Your week is full and the company still depends on your hours: two people at a table, one folder changing hands and one card kept, then the capacity cut for the critical client flow.

The capacity cut: stop, who, protect

Stop one task. Name who absorbs it. Protect the critical flow, and nothing else. Jenyns’s stage 2, on the framework page, is the who. For each system in the flow, name the knowledgeable worker, the person who already does that task well, and assign them as the owner of that system. Also name a Systems Champion, someone detail-oriented inside the business who drives the project. Stage 3 is the extract. The worker records themselves doing the task, by screen recording, video, or audio. No writing is required at that stage. The Systems Champion watches the recording and turns it into steps. His line for the owner is that the owner stays out of it entirely.

That is a stronger stop than “try to delegate more.” The task leaves your hands, and the document is not your evening job. The Google Books description of the 2020 book lists, among the things a reader will discover, why business owners are typically the worst people to document systems. That line is the description, not a page we read. It matches the framework page. It does not add a number, and we are not going to invent one.

Where you are The one thing you stop Who absorbs it What you protect
A new manager, and the team already does the work One task you still redo or still approve on habit The person who already does it well. They record it. Someone else writes the steps. The one decision that must come back, inside one client flow
A founder with one other person One recurring hour-sink that person can carry That person. If the only name is yours, the cut has not happened. One target client and one product. No second offer this week.
A founder with nobody else yet The task comes off the week. You do not write the manual for it. Nobody yet. The Critical Client Flow page says to build a small team first. One client and one product. Nothing else gets a system.
A plan to document the whole company Nothing. You added a project to a full week. You, at night. The framework page says that is the myth that stalls it. Nothing. A wall of systems replaces the work.

The later stages on his framework page are organise, integrate, scale, and optimise. They are real parts of the method he describes. They are not this week’s job. Organise means a consistent shape and one place to put the steps. Integrate means the steps get used, not filed. Scale means other departments, after the critical flow is actually running. Optimise means a review later. Opening all four on Monday is how the full week learns a new name.

The sentence you send

Say the handoff once, in writing, with one task and one name. The pages we read do not print this email. The wording is this article’s. Leave the shape. Replace the brackets. Do not add a second task in the same note.

When someone already does the work

Starting [day], I am stopping [the one task]. [Name] owns it. Please record yourself doing it once. [Champion, or the same name] will write the steps. Bring me [the one exception] only. I am keeping [one client and one product], and I am not opening a second system this week.

When you are the only person

I am taking [the one task] off this week. I will not write the manual for it myself. The next person I add absorbs that task, or the task stays off. I am protecting [one client and one product]. Nothing else gets a system until that person exists.

Then stop typing. A second paragraph that says “and I’ll stay across the rest of the list” puts your hours back on every item. The decision you still keep is the one exception in the first script, or it is the promise inside the flow you named. It is not a standing right to redo the task. If you and they would both “just keep an eye on it,” it is not owned. That is the same failure as a meeting that ends with no name, which is a different cut, the one in the call you do not hand off.

How to make the cut this week

Do this before you add another block to the calendar, including if the week is already full. Six moves. None of them is a new tool.

  1. Write one target client and one primary product, in the sense the Critical Client Flow page uses: the client you already serve, and the offer you already deliver. If you cannot name them, that is the work, not a documentation project.
  2. List the recurring tasks inside that flow that stop when you stop. Circle one. Not the most interesting. The one that fills the week and that another person could already do.
  3. Name that person. The framework page calls them the knowledgeable worker. If the only name is yours, go to the solo rule below. Do not spend tonight writing the steps yourself.
  4. They record the doing once. Screen, video, or audio. Someone who is not you writes the steps. His stage 3 says the owner stays out entirely. A rough document is enough. His page calls that a minimum viable system.
  5. Send the sentence. Put the task on their week. Take it off yours. The one exception you still want to see is named in the sentence. Everything else does not come back for a look.
  6. Do not open a second flow, a second product, or a folder of every process in the company. His framework page says everything outside the critical flow can wait. The Critical Client Flow page says one client, one product, one journey.

If you are a new manager, the person in step 3 is already on the team. You are not hiring a department to make this cut. You are stopping the redo. The first hire’s week one is a different problem, about what you give a new person. This cut is about a task the company already waits on you to touch.

When you are the only person

If nobody else works with you, do not pretend you can extract a system from yourself tonight. The Critical Client Flow page answers this directly. It says the flow still works for a one-person business, and that the method provides the most value when you have at least a few team members. Its line for the solo case is to focus first on building a small team. The framework page’s extract assumes a knowledgeable worker and a Systems Champion. Both of those are people who are not the owner.

So the solo cut is still a cut. Take one recurring task off this week. Do not move it to Sunday and call Sunday a colleague. Do not write the manual as a substitute for a person. Either the next person you add, a contractor or a first hire, absorbs that task, or the task stays off until they do. Protect one client and one product while you wait. A client who wants more than the price is not this problem. That is a scope sentence, in what the price covers. A week where every item is marked urgent is a different cut, the one in a week where everything is marked urgent. Do not use either of those as a reason to spend the night documenting the company.

Common mistakes

  • You write the system because you are faster. The framework page says the owner is usually the worst person to document the process. Speed tonight is how the company still depends on your hours next month.
  • You stop five things and name nobody. A list of intentions is not a handoff. One task, one name, or the task comes off the week entirely.
  • You document hundreds of systems. His framework page calls that the first myth. The Critical Client Flow page describes an owner who put a wall of systems up and watched it fail because people could not use it. Start with one flow.
  • You protect nothing. The hours you free will fill with a second offer. Name the one client and the one product, and leave the rest for later.
  • Sunday is the absorber. Moving the task to your own weekend keeps your name on it. The Critical Client Flow page tells a solo owner to build a small team, not to become a second shift.
  • You treat a client ask as this cut. More work than the price covers is a scope decision, in the sentence you send a client. It is not a systems project.
  • You sort the week and call that a handoff. A priority list can order Monday. It does not name who owns the task when you are not in the room. The owner is the point.

What the sources do and do not say

The framework page gives the seven stages and the rule that the owner stays out. The Critical Client Flow page gives the one-client exercise and the solo limit. Neither page gives this article’s one-task sentence. We read both pages. We checked the edition on Google Books and on Booktopia. We did not read a numbered page of the book, and we did not turn a case story on those sites into a result.

Source What it is What we took What it does not show
David Jenyns, framework page, “What Is SYSTEMology? The 7-Stage Framework,” davidjenyns.com/systemology-book-summary/. Read 13 November 2026. His account of the method, not a page of the book. The author’s own stage list for the book: define, assign, extract, organise, integrate, scale, optimise. Critical Client Flow of 10 to 15, not hundreds. The owner is usually the worst person to document. The knowledgeable worker records the work. A Systems Champion writes the steps. The owner stays out entirely. A rough document beats a perfect one that is never written. His account of 60-plus hour weeks at his agency, and of hiring a CEO in 2016. A measured success rate. The “5 million readers” line on that page, which we did not use. The one-task email. Any page number.
SYSTEMology, “Critical Client Flow,” systemology.com/critical-client-flow/. Read 13 November 2026. The current exercise for the one-page map: one client, one product, the steps you do now. 7 to 12 steps, about twenty minutes, two or three words, only current work. Combine steps one person handles. Someone outside the work should be able to follow it. If you are solo, build a small team first. The method is described as most useful with at least a few team members. Agreement with the 10-to-15 count. A study behind the page’s Pareto sentence about efficiency wins. We saw that sentence and did not use it. The case stories on the page. The 90-day claim on the other page. Those are not this week’s plan.
David Jenyns, SYSTEMology, publisher SYSTEMology, 18 November 2020, 212 pages, ISBN 9780648871033, as listed by Google Books (record vYANzgEACAAJ) and by Booktopia. A separate listing uses ISBN 9780648871002 and an August 2020 date. No page numbers. The book those listings describe. We used the listings for the edition, and the Google Books description for one promise the blurb makes. The description says the book is a step-by-step system for owner-dependent businesses, and it lists, among the things a reader will discover, why business owners are typically the worst people to document systems. The chapter text. A page for the 10-to-15 count or the 7-to-12 count. Any statistic. The wording of the handoff sentence, which is this article.

Limit: the two method pages disagree on whether the flow is 10 to 15 or 7 to 12. Use the overlap: one client, one product, far fewer than a wall of systems. The solo page tells you to build a small team before the extract is the point. A new manager who already has people can name one of them this week. A founder with nobody cannot borrow a person from a paragraph. The one-task sentence will not tell you which of those you are. You still have to look at the room before you send it.

Frequently asked questions

What do you do when the company still depends on your hours?

The company still depends on your hours when a full week still stops if you step out of it. Name one recurring task that waits on you, and name the person who already does that work. They record themselves doing it once. Someone else writes the steps. You stay out of both. David Jenyns’s framework page calls that person the knowledgeable worker and says the owner stays out of the extract. Protect one critical client flow, one client and one product, and do not open a second system this week. If the only name on the task is still yours, you have not made the cut.

What is a critical client flow?

A critical client flow is the short map of how one client receives one product, not a manual of the whole company. Jenyns’s framework page puts it at 10 to 15 systems that touch the client journey, and says everything else can wait. The Critical Client Flow page on systemology.com puts it at 7 to 12 steps, and only the work you do now. The two pages do not match on the number. We did not read a page of the book that settles it. The usable part is the overlap: one client, one product, and not hundreds of documents.

Who should write the system down?

Not you, if you are the owner. Jenyns’s framework page says the owner is usually the worst person to document a process, because the owner is too close and too likely to overcomplicate it. The person who already does the work well records it, by screen, video, or audio. A Systems Champion watches that recording and writes the steps. His stage 3 says the owner stays out entirely. The 2020 book’s Google Books description lists the same promise. That is the blurb. We did not read the chapter.

What if you are a solo founder with no team?

Do not write the manual tonight and call that a handoff. The Critical Client Flow page says the map can still be drawn alone, and that the method is most useful with at least a few team members. Its instruction is to build a small team first. Until that person exists, take one recurring task off this week and leave it off. Do not move it to Sunday. The next person you add absorbs that task, or the task stays stopped. Protect one client and one product while you wait.

What should you say when you hand the task off?

One task, one name, one exception, and then stop. Say you are stopping the task on a named day, that the named person owns it, that they will record themselves doing it once, and that someone who is not you will write the steps. Name the single exception they should still bring you. Say which client and product you are keeping, and that nothing else gets a system this week. The pages we checked do not print this note. The wording is this article’s. A second paragraph that keeps you across the rest puts your hours back on the list.

How many systems should you document this week?

One task inside one flow, not the company. Jenyns’s framework page says you do not need hundreds of systems. You start with the critical flow and let the rest wait. The Critical Client Flow page says one target client and one primary product, and only the work you do now. His later stages are on that framework page. They are not Monday’s job. A rough note is what he calls a minimum viable system. Do not open a second flow to feel thorough.

What do you protect, and what do you stop?

You stop one recurring task the company waits on you to touch, and that another person can already do. You protect one client and one product, including the one decision inside that flow that still has to be yours. You do not protect the whole week. If the only step you will release is one nobody else can do, you have not found the task. Look at the redo and the approval you give from habit. The task you stop and the thing you protect are different. Keeping both under your name is the full week you already have.

Is this the same as delegating everything?

No. This cut is one task, one name, and one flow you still protect. It is not handing the company to a stranger on Monday. Jenyns’s pages describe a worker who already does the task and a champion who writes the steps, with the owner out of the writing. The Critical Client Flow page says a solo owner should build a small team before expecting the method to pay. A new manager uses the person who is already good at the task. If the handoff has three names, or no name, the company still depends on your hours, because the task comes back to you.

Sources

  1. Jenyns, D. “What Is SYSTEMology? The 7-Stage Framework.” Author’s framework page, davidjenyns.com/systemology-book-summary/. Read 13 November 2026. States the seven stages, the 10-to-15 Critical Client Flow, the claim that the owner is usually the worst person to document a process, the knowledgeable worker, the Systems Champion, and the line that the owner stays out of the extract. Also his own account of 60-plus hour weeks and of hiring a CEO in 2016. Not a study. No page numbers. Jenyns, SYSTEMology framework.
  2. SYSTEMology. “Critical Client Flow: How to Map Your Entire Business on One Page.” systemology.com/critical-client-flow/. Read 13 November 2026. States 7 to 12 steps, about twenty minutes, one target client, one primary product, two or three words, current work only, and the solo note to build a small team first. Not a study. The page’s Pareto sentence and its case stories were not used as findings. Critical Client Flow.
  3. Jenyns, D. (2020). SYSTEMology: Create Time, Reduce Errors and Scale Your Profits with Proven Business Systems. Publisher SYSTEMology, 18 November 2020, 212 pages, ISBN 9780648871033, as listed by Google Books (record vYANzgEACAAJ) and by Booktopia. A separate listing uses ISBN 9780648871002 and an August 2020 date. The Google Books description lists, among the book’s promises, why business owners are typically the worst people to document systems. No page of the book was read. Google Books record.

The decision next to this one

Where this sits

How this article was researched

The seven stages, the 10-to-15 flow, the knowledgeable worker, and the line that the owner stays out are David Jenyns’s framework page for SYSTEMology, read on 13 November 2026. The 7-to-12 exercise, the twenty minutes, the one client and one product, and the solo note are the Critical Client Flow page on systemology.com, read the same day. The edition is the paperback Google Books and Booktopia both list: publisher SYSTEMology, 18 November 2020, 212 pages, ISBN 9780648871033. We did not read a numbered page. We did not use the “5 million” line, the page’s Pareto sentence, the 90-day claim, or the case stories as findings. The one-task sentence, and the rule that Sunday is not a colleague, are our application for a solo founder or a new manager.

Limit: the two method pages disagree on 10 to 15 versus 7 to 12. A founder with no one else cannot run the extract stage the framework page describes. The book’s chapter text was not in front of us, so it is not in this article.

How we work: every article on The Growth Reads is built from sources we can check, and it is date-stamped when those sources change. Read our methodology.