Public sector

Structuring delivery in a complex programme

Procurement completed on schedule with a scope the organisation could actually deliver.

The procurement could not restart, but the scope no longer matched reality. The work was to recover room to move without pretending the timeline could change.

Client
Public sector organisation
Role
Embedded advisor and product lead
Duration
12 months

The situation

[3–4 sentences, compressed. Set the scene: what was the organisation trying to do, and what had gone wrong. Name the stakes — what would it cost them if nothing changed. The reader should understand the gravity before the problem is formally named.]

How I read this

[The diagnostic insight — what Fredrik identified as the actual problem beneath the presenting symptoms. Not a list of issues, but a single reframe that made the path forward visible. This is the differentiator: most advisors would have named the same symptoms; the value is in how the problem was reframed.]

[A sharper restatement of the diagnostic frame — the kind of sentence that makes a reader think "yes, that is exactly the problem we have." Authorial voice, not client voice. Should be quotable and direct.]

What I did

  • [Specific activity — framed as a judgment or decision, not just a task. What did Fredrik choose to do, and why was that the right move at that moment?]
  • [Another activity — ideally one that signals how he works with people, not just systems or documents]
  • [Another activity — something that shows the bridge between strategy and day-to-day delivery]
  • [Another activity — something that shows what was left behind after the engagement: capability, clarity, or structure the organisation now owns]

Outcome

[One sentence baseline: what was true before, so the results read as a transformation rather than a list of improvements.] [Then name the primary outcome directly — the thing the teaserOutcome line already stated, but with enough context that it lands with full weight.]

  • [Specific result — with a qualifier that gives it scale or context. Avoid generic language like "improved alignment."]
  • [Specific result — one that a potential client could map directly onto their own situation]
  • [Specific result — the lasting structural change, not just the immediate fix]

[Client quote — direct speech, attributed. The most persuasive single element on the page. Should be a real quote if available; if not, hold this slot open rather than filling it with authorial voice. The quote should speak to the value of the engagement, not just the outcome.]

[Name, Title, Organisation]

Why this pattern matters

[1–2 sentences: the broader insight this engagement reveals about this class of problem. Not a summary of what happened — a claim about why the approach matters beyond this specific case. This is Fredrik's thinking made visible for readers who want depth.]

Working through something similar?

If any of this sounds familiar, I'm happy to think it through with you. No pitch, just a conversation.

Start a conversation →