Verified against ChatGPT · 2026-08-12
Compress a strategy plan into a one-pager an executive will actually finish reading
Distills a strategic plan into a single readable page organized around the actual decision requested, cutting anything that doesn't serve that decision.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Compress this into a strategy one-pager built to actually get read in full by a busy executive, not a shortened version of a longer deck.
STRATEGIC QUESTION BEING ANSWERED
Should we expand into the SMB segment or double down on enterprise for the next two years?
TIME HORIZON
Next 18 months, with a check-in at the 9-month mark.
REAL RESOURCING SITUATION
One dedicated product manager and a 4-person engineering pod that would need to be pulled off the enterprise roadmap.
COMPETING PRIORITY
Would delay the planned enterprise SSO integration by one quarter.
DECISION REQUESTED
Approval to reallocate the 4-person engineering pod to an SMB pilot for two quarters.
Everything on this page has to earn its place against one test: does it change how the reader thinks about the decision requested. Cut anything that's context for its own sake. Open with the decision requested stated as a single sentence, before any background — an executive reading this should know within five seconds what they're being asked to approve or weigh in on. Follow with the strategic recommendation itself, stated plainly, then the two or three reasons behind it, each backed by something concrete from the resourcing reality or competing priority given — not abstract strategic language that could apply to any plan. Address the competing priority head-on rather than ignoring it: state explicitly what this strategy would take resources away from, since an executive weighing a recommendation is implicitly weighing it against what else that resourcing could do, and a one-pager that pretends there's no trade-off reads as either naive or dishonest. State the time horizon plainly and tie the recommendation's urgency to it — why does this decision need to happen on this timeline rather than later.
WHAT NOT TO DO
Do not open with mission-statement-style framing ('as we look to the future...') — get to the decision immediately. Do not list more than three supporting reasons; a one-pager that tries to be comprehensive stops being a one-pager in substance even if it fits on one physical page.
OUTPUT FORMAT
A single page: decision requested (one sentence), recommendation (one paragraph), three or fewer supporting reasons (each tied to something concrete), the competing-priority trade-off stated plainly, and the time-horizon urgency in one closing sentence.Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Strategy documents that fail to get read in full almost always front-load context and save the actual ask for the end, which works against how executives actually triage reading material — they decide within the first few seconds whether something requires their full attention, and a document that makes them read background before reaching the decision gets skimmed or deferred; opening with the decision requested as a single sentence is a direct fix for that triage behavior rather than a stylistic preference. GPT-5.1 tends toward comprehensive, mission-framed openings on strategy documents by default because that's the register most strategy-writing training data uses, so explicitly forbidding the 'as we look to the future' framing and capping supporting reasons at three is necessary to override that default toward something that actually reads as a one-pager in substance, not just in page count. Requiring the competing-priority trade-off to be stated plainly, rather than omitted, targets a specific credibility problem: any real resource allocation decision has an opportunity cost, and an executive evaluating a recommendation is implicitly comparing it against what else those resources could do — a one-pager that omits the trade-off either looks naive about how resourcing actually works or looks like it's deliberately hiding the cost, and either read undermines the recommendation's credibility more than stating the trade-off honestly would. Tying urgency explicitly to the stated time horizon prevents the common failure of strategy documents that argue a course of action is correct without ever establishing why it needs deciding now rather than next quarter, which is often the first question a resourcing-constrained executive actually asks.
What you get back
Decision requested: Approve reallocating the 4-person engineering pod to a two-quarter SMB pilot. Recommendation: Pursue the SMB pilot now rather than waiting, because the competitive window in that segment is narrowing faster than our enterprise roadmap slip would cost us. Trade-off: this delays the enterprise SSO integration by one quarter — a real cost, but a recoverable one against a 9-month check-in.
Verified against
ChatGPT GPT-5.1 · 2026-08-12
Changelog
- 2026-08-12 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — custom software, built and maintained for you — that's Scult's day job.
EXPLORE CUSTOM SOFTWARE
