Your first year as a founder-CEO: what to actually focus on
By Brendan Levin. 20+ years scaling businesses, from teams of 8 to 600 and budgets from startup to $100m.
Key takeaways
- The job changes from doing the work to building the structure that does it.
- Three pillars, in order: Direction, Decisions, Delivery. Direction is first.
- Doing more of the founding work quietly makes you the ceiling.
- The Operating Audit installs the Direction pillar first, standalone.
The first-year trap: doing more of what built it
In the founding phase you were the machine. You made the product, closed the customers, and made every call, and it worked because at a handful of people one person can hold all of it. So when you become CEO, the instinct is to do more of that same work, harder and faster. It feels like progress. It is the trap. The founding-era work is exactly what caps the business, because every hour of it makes you more central, not less. The business grows to the edge of what you personally can carry, and then it stops. The problem is rarely effort. It is that the business has no structure of its own, so all of it still runs through you.
What to focus on instead: build the operating system
The real first-year job is a change of role. You stop being the thing the business runs on and start building the thing it runs on. That structure is the operating system: how the business actually runs, separate from the product it sells and the boxes on its org chart. In this practice the model is called the Momentum Engine, and its three pillars are the parts every business runs on whether or not anyone has named them.
Direction first, then Decisions, then Delivery
You do not build all three pillars at once, and the order is not a preference. Direction comes first, because the other two have nothing to organise around until the outcome is named.
- Direction. The single outcome the business exists to deliver this year, and the path to it. Until it is named, every priority looks equally urgent and everything routes to you to rank.
- Decisions. Explicit decision rights, so the team knows what is theirs to call and what genuinely needs you. Without them, everything escalates to be safe, and it all lands on your desk.
- Delivery. The operating rhythm that moves work through the team on a cadence, so progress does not depend on you pushing it. Once the outcome is named and the calls are owned, the rhythm has something to run on.
Named outcome, then owned decisions, then a rhythm that carries the work. Skip Direction and the other two have nothing to point at, which is why the first year starts there.
What to stop doing
Building the operating system is only half the job. The other half is handing off the founding-era work that only you did because there was no one else. In the first year you stop being the default owner of every decision, the person every question routes to, and the one who personally moves each piece of work forward. That work made the business and now it caps it. The hard part is that it still feels like the job, because it is what you have always done. It is not the CEO job any more. The CEO job is to make sure that work has an owner who is not you, starting with a single clear outcome to run at.
The one focus that makes the rest possible: the first domino
If you do one thing in your first year, name the one outcome the business exists to deliver and hand the first move toward it to an owner who is not you. That is the first domino. It is the smallest piece of Direction that, once it is owned by someone else, makes everything after it possible: the decisions have something to serve, the rhythm has something to carry, and you get the first proof that the business can move without you in the room. The Operating Audit installs that Direction pillar standalone in four weeks: a one-page Operating Compass, the first domino handed to an owner who is not you, and an alignment framework the team runs. Decisions and Delivery are built on that foundation, not before it.
Not sure which pillar to focus on first? The free Operating Diagnostic maps where your week goes and names the gap.
Take the free diagnosticCommon questions
What should a founder-CEO focus on in the first year?
Building the operating system the business runs on, so it stops depending entirely on you. That means three things, in order. First, Direction, naming the one outcome the business exists to deliver this year. Second, Decisions, making who decides what explicit so calls stop routing back to you. Third, Delivery, setting a rhythm that moves work through the team without you in the room. Direction comes first, because the other two have nothing to organise around until the outcome is named.
What is the biggest first-year mistake founders make?
Doing more of the work that built the business. In the founding phase you were the product, the salesperson, and the person who made every call, and that worked. As CEO, doing more of that same work feels like progress and quietly makes you the ceiling. The business grows to the edge of what one person can hold, then stops. The first-year job is not to do more of the founding work, it is to build the structure that does it without you.
Should I focus on growth or structure first?
Structure, because growth on top of no structure just means more of everything routing through you. When the business has no named outcome and no clear decision rights, every new customer, hire, and project adds load to the founder rather than to the business. Naming the one outcome and installing decision rights first is what lets growth land on the team instead of on your calendar.
What do I stop doing in the first year?
The founding-era work that only you did because there was no one else: being the default owner of every decision, the person every question routes to, and the one who personally pushes each piece of work forward. That work made the business, and now it caps it. You stop being the operating system so the business can have one. The first thing to hand off is a single clear outcome, the first domino, given to an owner who is not you.
How do I start building the operating system?
Start with Direction, because the other two pillars have nothing to organise around until the outcome is named. The Operating Audit installs the Direction pillar standalone in four weeks: a one-page Operating Compass, the first domino handed to an owner who is not you, and an alignment framework the team runs. Decisions and Delivery are built on that foundation, scoped after Direction is in place.