One of the fastest ways to find operational gaps in a founder-led company is to ask the head of each department to show you their plan. Not a project list, not a budget, not a roadmap — their plan. The document that says: here’s where this function is going over the next 12 months, here’s how we’re going to get there, and here’s how we’ll know if we’re on track.
In most companies under $15M, this document doesn’t exist. Occasionally there’s a version of it for sales or finance, because those functions have the most quantitative accountability. But for operations, marketing, people, product — there’s usually nothing but a collection of projects and a vague directional sense that lives in the department head’s head.
This is a much bigger problem than it looks.
What a DOP is — precisely
A Departmental Operating Plan is a single document, typically 3–5 pages, that captures six things for a given function:
- The mandate. What is this department responsible for? Not a job description — a clear statement of what this function exists to produce for the company.
- The current state. Where does this function stand today? What’s working, what’s not, what’s the baseline?
- The 12-month objective. One clear statement of where this function needs to be in 12 months, in terms of capability or output.
- The key initiatives. The 3–5 specific projects or changes that will produce that objective. Not a task list — strategic bets.
- The metrics. How will we know if we’re on track? What are the leading indicators, not just the lagging ones?
- The dependencies. What does this function need from others to execute? Where are the handoffs?
That’s it. No more, no less. A DOP is not a strategic plan and it’s not a project tracker. It’s the connective tissue between the company’s overall direction and the day-to-day work of a specific function.
Why most founder-led companies don’t have them
The honest answer is that building a DOP requires the department head to have clarity they often don’t have — clarity about where the function is actually going, as opposed to what it’s currently doing.
In a founder-led company, most department heads are excellent at execution. They know what needs to happen this week. They’re responsive, capable, and hardworking. But they haven’t been asked to articulate where their function is going because nobody’s asked them to think a year out. The founder is usually the only person thinking at that horizon, and the implicit expectation is that the founder will tell people what to do when the time comes.
This works at 10 people. It doesn’t work at 30.
What happens when you build them
The first time a leadership team builds DOPs together — which is the right way to do it, in a structured offsite or working session — two things happen.
First, gaps and conflicts surface immediately. The sales DOP assumes marketing is going to deliver a certain kind of lead volume that the marketing DOP has no initiative around. The operations DOP depends on a technology decision that nobody’s made yet. The people DOP has hiring assumptions that don’t match finance’s headcount model. These conflicts existed before the session — you just couldn’t see them.
Second, the leadership team starts to understand each other’s work in a way they didn’t before. When you see someone’s 12-month objective and their key dependencies, you understand where they’re headed and what they need. That understanding changes how the leadership team interacts day-to-day — from a collection of functional leaders to an actual team.
DOPs shouldn't be built by department heads in isolation and then presented to the founder for approval. They should be built in dialogue — department heads with drafts, a working session where the leadership team reviews and aligns, and a final round of revision that reflects the interdependencies. The process is almost as valuable as the output.
How to start
If your company doesn’t have DOPs, don’t try to build them all at once. Start with the two functions that are most under-documented relative to their operational importance. For most companies, that’s either operations or people.
Give the department head a template (the six-section structure above), schedule two weeks for a draft, and then hold a working session to review it. What you learn from that one document about the gaps in your operational clarity will tell you more than a month of one-on-one meetings.
Build the others over the following quarter. By the time you’ve completed the set, you’ll have a leadership team that operates with a qualitatively different level of alignment — not because you changed the people, but because you changed the infrastructure.
