Business frameworks you can actually fill in

Nine blocks that hold an entire business on one page: customer segments, value propositions, channels, relationships, revenue, resources, activities, partners, costs. Its real power is that the blocks argue with each other — a channel you cannot afford shows up as a contradiction rather than an opinion.

Not the right tool when you have no customers yet and every block is a guess. Use the Lean Canvas, which replaces the operational half with problem and solution.

Ash Maurya's adaptation for anything that has not been built yet. It swaps key partners, activities and resources — which a startup cannot honestly answer — for problem, solution, key metrics and unfair advantage. Filling the problem box before the solution box is the whole discipline, and it is the box most people skip.

Not the right tool when the business already runs and you need to see cost structure against revenue streams. That is the Business Model Canvas.

A magnifying glass on two blocks of the Business Model Canvas: the customer's jobs, pains and gains on one side, your products, pain relievers and gain creators on the other. It is useful precisely when the two sides refuse to line up — that gap is the finding.

Not the right tool when you do not yet know who the customer is. Do the ideal customer profile first, or you will describe the pains of an average of everybody.

Strengths, weaknesses, opportunities, threats. The most-taught framework on this page, and the one most often filled in badly: the internal/external split is what makes it work, and a SWOT that ends without a decision attached to at least one quadrant was a vocabulary exercise.

Not the right tool when you need to choose between options. SWOT describes a position; it does not rank alternatives.

Allan Dib's nine squares, arranged in three acts — before, during and after the sale — so that the plan covers the part almost everyone drops, which is what happens to a customer after they pay. Its value is the shape: nine squares is small enough that a gap is visible.

Not the right tool when the question is channel mechanics rather than coverage. A retargeting ladder or a campaign brief is finer-grained.

Dave McClure's five stages: acquisition, activation, retention, referral, revenue. Written in that order deliberately — retention sits before referral and revenue because a product people leave cannot be fixed by pouring more traffic into the top. Attach one number to each stage and the leak names itself.

Not the right tool when you have no measurement in place. An AARRR funnel with five blank metrics is a diagram, not an analysis.

Who you sell to, who signs, and the sentences that stop the deal. The objections half is what separates this from a persona poster: writing down the five things people actually say, and the answer to each, is the part that changes a sales call next week.

Not the right tool when you are mapping what a customer does rather than who they are. That is the journey map.

The stages a customer moves through, the touchpoints at each one, and where the friction sits. It earns its place when it is uncomfortable — a journey map that shows a smooth ride end to end has been drawn from the inside of the company rather than from a real customer.

Not the right tool when you want an internal process with handovers between teams. Use a swimlane diagram.

Inventory the candidate tasks, score them on value, risk and data, pick two pilots — not ten — and write the rules everyone follows. One of the frameworks here with a full page of its own, because it is one where the vocabulary is still being set.

Not the right tool when the decision is already made and you need the boundaries written down. That is the AI usage policy.

What may never be pasted into a model, who validates output before it ships, and which tools are approved. Two pages that people read beat forty that they do not, and the test of this one is whether a new joiner could follow it without asking anybody.

Not the right tool when nobody has run anything yet. Write the adoption plan first; a policy for hypothetical use gets ignored.

Objectives with measurable key results underneath. The failure mode is universal and easy to spot: a key result that is a task rather than an outcome. "Ship the new onboarding" is a task; "half of new users finish setup" is a result. This one opens with a progress gauge that moves as results are ticked.

Not the right tool when the work is a fixed scope with a deadline. That is a plan, and it wants a timeline or a kanban board.

The first ninety days of a new hire, split into learn, contribute and own. Useful in both directions: managers write it before someone starts, and candidates bring one to a final interview, which is still one of the few ways to visibly outrank a stronger CV.

Not the right tool when the role has no clear owner or success measure. Fix that first — the plan will just make the vagueness longer.