Creating a Business Plan Blueprint: What Goes in It and What to Leave Out

Last November, the COO of a manufacturer of custom products told me they were going to budget for a flat year.

On purpose.

They were doing about $7.5 million in revenue with enough production capacity for $10 to $12 million, so the shop floor wasn’t what was holding them back. What was holding them back was everything underneath it: an ERP upgrade still in progress, an e-commerce launch on deck, and handoffs between departments that needed real work. He’d watched the company bounce back and forth between building systems and chasing growth, and he put it better than I could: “it’s very difficult to build systems while you’re trying to grow the business that’s going to break the systems.”

So the 2026 plan was built around the systems, with the growth push saved for 2027. “We’re going to budget for flat,” he told me, “but we’re going to push for a little incremental growth.”

By the end of the first quarter, net operating income was running at 21% against a goal of 15%. The year before, it had finished at 11%. He was straight with the room that some of that came from working through inventory they’d bought in earlier months, which is exactly what you want your COO saying out loud. Through June it was still sitting around 21.5%, on revenue tracking right where the plan said it would be.

Then in July he told me, “We bit off more than we can chew in terms of trying to improve too many things at once.”

Both of those things are true about the same plan, and that’s why I rewrote this article.

I wrote the first version a few years ago, and it read like most business plan advice: do your market analysis, write your mission and vision, set your goals, remember it’s a living document. None of that is wrong. Very little of it would have helped this team last November. What helped was a plan short enough to hold every new idea up against, which turns out to be the hardest thing about a plan to protect once the year starts.

What Is a Business Blueprint?

A business blueprint is the plan behind the plan. It’s a short document that says where the business is going, how it wins, and what it will and won’t work on this year, and the budget and project plans hang off of it rather than the other way around.

It’s a different document from the business plan you write for a bank. That one exists to convince somebody outside the business. The blueprint exists so the people inside the business can make decisions without walking every one of them into the owner’s office.

For years I built these from a long template. It opens with the basics: what stage of life the business is in, the problem you solve in two sentences or less, your solution in two sentences, your ideal customer in one, your competitors, how you price, and a SWOT. From there it works through sales and marketing, operations, finance and admin, goal setting, and an action plan for each goal.

That template still earns its place, especially for a business that hasn’t answered those basic questions yet, and more established companies fall into that group than you’d think. A note I wrote into it years ago still holds: in my experience, most businesses have a very hard time saying exactly what problem they solve for their customers. If your leadership team can’t get it into two sentences and agree on them, that’s your first planning session, and nothing you build on top of it will hold until you’ve had it.

Most manufacturers that have been around a while can answer the basics, even if nobody ever wrote them down. What they’re usually missing is direction. That’s the part the work with this team was built around, and it’s the version I’d build with any established manufacturer this fall.

What Goes in a Business Blueprint

The backbone of the plan came from a book a colleague recommended to me, Patrick Lencioni’s The Advantage. Lencioni builds it around six questions a leadership team has to answer the same way: why do we exist, how do we behave, what do we do, how will we succeed, what is most important right now, and who must do what. That book, and one more I’ll mention below, helped me put language to the framework I used with this team.

Their final plan fit in a handful of pages. Top to bottom, here’s what was in it:

• Why we exist. One sentence, written about the customer’s outcome rather than the product.
• What we do. One sentence. Theirs was six words.
• Core behaviors. Three, written as things people actually do. One of theirs was sharing information openly and working across teams so problems surface early.
• Strategic anchors. Three statements of how the company wins. One was being the best at the complex custom work other suppliers can’t or won’t take on.
• One thematic goal for the year. Their answer to “what is most important right now?” was smoother end-to-end workflows, inside the company and for the customers they serve.
• Three objectives that exist only to serve that theme: better communication and handoffs, standardized key processes, and a smoother customer experience, each with a named owner and a support team.
• Two initiatives. Finish the ERP upgrade. Launch the e-commerce platform.
• Supporting strategies. Long-term direction that shapes decisions but is explicitly not a priority this year.
• A parked list. Good ideas with a date to come back to them.
• Five KPIs, with net operating income at the top.
• An operating rhythm. What gets reviewed weekly, what gets reviewed monthly, and what gets reset every quarter.

The financial targets and the budget were in there too, one table each, with the budget written as percentages of revenue.

What’s missing matters as much as what’s there. There are no task lists, no due dates and no forty pages of market analysis. When I’m building one of these with a leadership team, most of my job is keeping things out.

Projects Don’t Belong on the Objectives List

The first draft had five objectives. Two of them were “complete the ERP uplift” and “launch the e-commerce platform.” Two weeks later, in the final version, those two had moved into their own section as initiatives and three objectives were left.

That can look like rearranging furniture, but the ERP upgrade was going to happen no matter what. As I said when we reviewed the plan, “it’s got to get done no matter if it’s effective or not, because they’re sunsetting the version.” The software company had already set the deadline. Sitting on the objectives list, it looked like a strategic choice competing with the others, and a project with a vendor and a go-live date wins that competition every single week. Nobody calls you about “improve communication and handoffs.”

I’m not fussy about the labels. I told the COO a couple of weeks later that it doesn’t really matter whether you call something an objective, an initiative, a project or a task, “as long as we’re all talking about the same thing.” What matters is that the outcomes you’re trying to move sit apart from the projects you’re required to finish, so you can tell whether the projects are moving the outcomes at all.

Leave the Dates Out of the Blueprint

This is the part people push back on.

Partway through building the plan, the COO wanted to add an estimated quarter to each objective, so that if anyone asked, they’d have an answer ready. It’s a reasonable instinct. Most planning systems put a due date on everything, and plenty of leadership teams read a missing date as a missing commitment.

I argued against it. My question to him was which one matters more: that we’re actually hitting the numbers we said we’d hit and that we have a regular cadence to talk about our progress, or that we wrote down “we’re going to do this by X” and now have to decide what happens when we miss it. “Who cares what the date is, is my point.”

Later in that same working session I said the bigger version of it: “you can’t make this detailed. This document has to live as the guiding light” for the next 12, 18, 24 months. The same went for budget tracking. The monthly and quarterly reviews were where they’d see how they were tracking against budget, and adding all of that into the plan itself was, in my words that day, overkill.

The dates still exist. They live one level down. Every initiative gets an action plan with its tasks, milestones, owners and due dates, which is the same action planning section that closes out my old template. The blueprint tells you which work matters. The action plan tells you when it’s due. Mix those two layers and the blueprint becomes a project schedule, and a project schedule goes stale the first time a vendor misses a ship date.

The Parked List Is the Most Important Page

When we reviewed the plan in December, there was an easy temptation sitting right in front of us: a custom product builder and an instant quote engine, both genuinely good ideas. I said at the time, “It would be very easy to say, hey, let’s do the configurator, and put that into 2026.” We didn’t. They went on the parked list along with new markets and a deeper analysis of customer buying patterns, to be revisited during 2027 planning. My default is to under promise and over deliver, and putting the configurator in year one would have set an expectation the team had no room to meet.

Parking something doesn’t kill it. The parked list is what lets a leadership team say “not yet” without having the same argument every week, and it only works if somebody actually opens it. This team built that into the rhythm. The agenda for their first quarterly meeting went from the dashboard, to what worked and what didn’t, and then straight into the parked initiatives: what’s ready to activate, what isn’t, and what kind of timeline they could put on it.

That’s also how new ideas get handled between quarters. Someone raises something in the weekly meeting, and the question isn’t whether it’s a good idea. The question is where it fits against the plan. When we were finishing the plan I warned them that “more is not better,” because it becomes easy to get lost trying to be all things to all people. The parked list is where “more” goes to wait its turn.

What Happened When They Ran It

The numbers held. The discipline was harder.

The profit plan worked. Revenue came in right where the flat budget said it would, which also meant it fell short of the extra push they’d hoped for on top of it. That’s an honest result, and it’s what budgeting for flat looks like when you mean it.

In May, the leadership team admitted the plan had never really made it out to the rest of the company. “How are we going to deliver this? What’s the cadence? We didn’t really discuss any of that in the beginning. It was just like, ‘Oh, yeah, we’ll keep you updated.’ That didn’t happen.” The reason it didn’t happen was simple: nobody had decided what they were comfortable sharing with the team, so they shared nothing.

By July, the list of things being worked on had grown well past what was written down, which is when the COO told me they’d bitten off more than they could chew. I told him what that feels like from the inside: “It feels great ’cause you’re really busy and there’s lots of activity, but you know, if you’re not careful, you’re headed towards disaster quickly.”

In September we had the same conversation again, this time about marketing, and I found myself saying what I’d said almost a year earlier. We had too many things on the board, so we had to strip it back to the strategic objectives “and then start filling in the gaps as those things start to move off the board.”

Three objectives and two initiatives was already a lean plan, and it still got crowded. A plan controls what goes on the page. It does nothing about the work that walks in the door every Monday, and that work doesn’t ask permission before it takes your people’s time. What the plan gives you is something to measure that work against, and the quarterly reset is where you take your focus back.

How to Build Yours This Quarter

Before you write a word of next year’s plan, do one thing. List everything your leadership team is working on right now: every project, every initiative, every “we should really…” that has somebody’s time attached to it. Next to each one, write which part of this year’s plan it serves. Anything that serves nothing goes on a parked list with a date to revisit it.

The length of that list will tell you more about next year’s plan than a SWOT will. If it’s long, you don’t have an ideas problem, and the new plan needs to be shorter than you think.

Then build it in this order:

1. Get the problem you solve into two sentences and get the leadership team to agree on them. If you can’t, stop and have that conversation first.
2. Write the North Star: why you exist and what you do, one sentence each, plus three core behaviors and three ways you win.
3. Pick one theme for 2027, then three objectives that exist only to serve it and no more than two initiatives. Anything you’re required to finish, like a software migration, is an initiative.
4. Park everything else with a revisit date, and put the parked list on every quarterly agenda.
5. Set the rhythm before you roll it out. Weekly against the objectives, monthly against the North Star, quarterly to reset. Decide what you’ll share with the whole company, and how often, before the kickoff meeting rather than after it.

Two books helped me put language to this, and both are worth reading before you sit down to build yours:

• The Advantage by Patrick Lencioni. The six questions, and where the terms strategic anchors and thematic goal come from. Read it for the structure.
• It’s Not What You Sell, It’s What You Stand For by Roy Spence and Haley Rushing. A whole book on the first question, why you exist. It’s the hardest sentence in the plan to write, and every other line has to answer to it.

Leave the dates for the action plans underneath. If you’d like a deeper look at turning the vision into day-to-day priorities, I wrote about that here: How to Translate Company Vision Into Operational Priorities.

Final Thoughts

The plan that worked for this team wasn’t detailed. It was short enough that they could hold every new idea up against it in a weekly meeting, and honest enough that when they drifted, they could see it happening.

That’s the whole test for a business blueprint. Not whether it looks thorough in December, but whether you’re still using it in July.

That’s it for today.

See you all again next week!

Dave