Why AI-written strategy docs read like consulting homework

What makes this hard

Ask for a strategy document and this often comes back: SWOT, 3C, PESTLE in the table of contents; three strategic options with pros-and-cons tables; and a conclusion of 'choose depending on circumstances.' The form is all there, yet after reading you don't know what it's proposing to do.

Two causes. Use frameworks as the outline and filling the framework becomes the goal — the conclusion disappears; frameworks are thinking tools, not a document's skeleton. And don't demand a decision and AI takes the safest path: listing. The decision gets shipped, whole, to the reader.

What to add to the request

1. Use the frameworks, delete them from headings

Specifying frameworks is good — 'analyze' without one just makes longer lists. But add: don't put framework names in headings; make each heading the question that section answers. Not 'VRIO analysis' but 'what we have and what we lack.'

2. Demand a decision with its basis

Don't stop at options — commit to one, and justify it by impact, risk, and difficulty. In the execution plan's responsibility table, exactly one final approver per row — with two approvers, nobody approves.

3. Don't let solutions stop at a name

'Build an integrated dashboard' plus one line is something no recipient can build. Demand five things: what is being built · what the user sees and does · what goes in and what comes out · which step of the current workflow it replaces · what done looks like — and a name becomes a plan.

Checklist for writing it yourself

1. 1Did you specify frameworks and also say 'not as headings'
2. 2Did you demand a committed choice with basis, not a list of options
3. 3Did you demand the five elements per solution
4. 4Did you make it mark unknown figures, org names, budgets for verification instead of inventing them
5. 5Did you keep undecided items out of the document's opening — a document that opens with an undecided list reads as a confirmation request, not a plan