The brief

Articulate IGNITE as a framework people can actually use. Not a slogan, not a campaign, not a pitch deck that ends up in someone's downloads folder. Something that reads like an operating manual and works like one.

The decision

Reject the deck format entirely. A slide deck is an artefact built around a single live presentation moment. Its shelf life is the duration of the meeting. A structured working document, organised well, becomes a reference that gets reopened, forked, and adapted by the people actually doing the work. That's a different product with a different information architecture.

What got built

A structured document organised around the real sequence a program like this goes through, written in plain English and stripped of the usual consulting furniture. The language was rewritten pass by pass to remove the hedges and intensifiers that creep into strategy writing by default. The document was scoped to be readable in fifteen minutes and usable in five.

The broader point

Format is strategy Choosing a document over a deck is not a tooling decision. It's a decision about what you expect the output to do after you leave the room. Most strategy work fails because it was designed for the meeting rather than for the quarter that follows it.

What the work taught me

The clients who get the most value out of strategy work are the ones who can pull the document back up two months later and still follow the logic. That's an editorial problem, not a strategic one. It means writing for the reader who wasn't in the room, because that reader is almost always the one who has to execute.

IGNITE is the framework I'll now reach for any time a team asks for a strategy around internal acceleration, onboarding a cohort, or scaling operator capability. The generic form is more valuable than any single instance of it.