Most people push back on the Steering Guide the easy way: "we already have a mission statement." That's not the real objection. Here are the ones that actually matter, asked the way a smart skeptic would ask them, answered the way I'd answer them to their face.

"Isn't this just mission-vision-values with new labels?"
‍If all you take from the Steering Guide is the three boxes, yes — you've relabeled a whiteboard. The structure isn't the invention. The invention is what's illegal to put inside each box. A mission statement can say anything. A Core Commitment can't — it has to name the customer's pain, the outcome, and be falsifiable in a single interaction. Most mission statements survive because no one can prove them wrong. Most Core Commitments die in the first workshop because someone finally can.

‍"A well-worded commitment doesn't fix misaligned incentives. So what's the framework actually doing?"
‍Correct — it doesn't touch comp plans, doesn't touch KPI conflicts, doesn't touch power dynamics. It was never built to. What it does is remove the most common excuse for drift: "nobody told us what mattered when it got hard." That excuse is real, and it's cheap to fix. Fixing it doesn't fix everything else that's broken. It just removes the one failure mode that leadership could have prevented with a sentence and didn't.

‍"Every case study you use is a company that already failed. Isn't that just retrofitting a narrative onto a failure?"
‍Yes, if that's all I had. It isn't. The test I'd put in front of any skeptic: don't look at the failures — look for the near-miss. A company that had genuine ambiguity at the decision point, watched two people in the same room make opposite calls under the same stated values, and only avoided the failure because someone happened to guess right. That's the tell. The framework doesn't predict failure. It predicts where the coin flip happens.

‍"Doesn't EOS already do this with Rocks and Scorecards?"
‍EOS tells you what to do and how to measure whether you did it. It doesn't tell you what to do when the Rock and the customer are in conflict at the 11th hour and there's no time to convene. That's the gap. Operational cadence answers "are we on track." The Steering Guide answers "what do we do when being on track and doing the right thing stop agreeing with each other." Those are different questions. Most companies only have infrastructure for the first one.

‍"Isn't a rigid decision filter a liability in a fast-moving market?"
‍A filter isn't a rule. A rule tells you the answer. A filter tells you what to weigh. The companies that get hurt by "rigidity" usually didn't have a filter — they had a slogan they were defending past its expiration date. A real Guiding Principle should force a strategy change the moment it stops producing the right calls. If yours never changes, you didn't build a filter. You built a plaque.

‍"Isn't 'it looked great on paper' also true of your own formulas?"
‍This is the one that should keep me honest. Yes — a Core Commitment can be grammatically perfect and organizationally ignored. The formula guarantees clarity. It does not guarantee enforcement. That's why the framework was never meant to end at the sentence. The sentence is the test you can fail fast, in a room, before you've spent six months finding out the hard way. If nobody enforces it, you've learned that in an afternoon instead of a fiscal year. That's the whole value — not that the paper is magic, but that bad paper reveals itself faster than bad culture does.

‍The reality: the Steering Guide doesn't claim to fix organizations. It claims to make the moment they start failing visible weeks earlier than it would otherwise be — and cheap enough to catch.

What is the book about?
Strategy doesn't fail in the boardroom. It fails in the hallway.
‍It Looked Great on Paper is about the gap between what organizations declare and what they actually do. The brilliant plan. And then nothing changes. This book explains why that happens, and what to build so it stops.

Why that title?
Because every failed initiative starts as a good idea.
‍
Nobody approves a strategy they expect to flop. Then it met reality. "It looked great on paper" is the sentence everyone says at the post-mortem and nobody bothers to investigate. This book investigates it.
‍
Who is this book for?
Anyone responsible for making something happen through other people.
‍
Executives, founders, team leads, change agents. If you've ever watched a strategy evaporate somewhere between the announcement and the execution, this is for you. You don't have a planning problem. You have a drift problem. Most leaders can't tell the difference. That's the point of the book.

How is this different from every other strategy book?
Most strategy books help you write a better plan. The plan was never the problem.

This book is about the small structural gap between organizations that execute and organizations that drift—the unglamorous choices that decide whether a strategy survives contact with everyday behavior. It's not about thinking harder or aligning more. It's about building the architecture that makes the right behavior the default, instead of hoping willpower carries it. You already know what you should do. This is about why you don't, and how to fix that on purpose.

What is the Steering Guide?
It's the framework at the heart of the book.

Three parts: A Guiding Principle—what you actually stand for. A set of Core Commitments—what customers can count on you to deliver, every time. And Supporting Actions—the everyday behaviors that make those commitments real. Most organizations have a mission statement. That's wallpaper. The Steering Guide is operational. It tells people what to do different on Monday morning.

Is this theory or practice?
Practice. I'm a consultant, not a theorist.

Everything in the book came from watching real organizations execute and fail to execute—then figuring out what separated the two. No borrowed case studies you've read in ten other books. No academic scaffolding. Just the patterns that actually predict whether a strategy lives or dies.

Do I have to read it cover to cover?
Read it straight through once. Then leave it on your desk.

The diagnosis builds in order, so the first read matters. But the frameworks are designed to be returned to, pulled out the next time an initiative starts to wobble and you need to find out why before it costs you.

Will this work for a small team, or is it only for big companies?
It scales both directions. Corporate, department, team, individual.

Drift isn't a function of size. A two-person team can have a beautiful plan and zero follow-through just as easily as a Fortune 500 can. The Steering Guide works at every level because the underlying problem is the same everywhere: the distance between what's stated and what's done.

What will I actually be able to do after reading it?
Diagnose why your last initiative stalled—precisely, not vaguely. Build a Steering Guide for your team or company. Spot execution drift early, while it's still cheap to fix. The goal isn't to make you nod along. It's to change what you do.

Is there a companion tool?
Yes. It's called The Paper Test. It's a short diagnostic that shows you, fast, where your stated strategy and your real behavior have quietly split apart. Most people are surprised by the result. Then they're motivated by it.

Who is Andrea Belk Olson?
A strategic change expert, organizational consultant, and author. I'm a regular contributor to Harvard Business Review, Inc. Magazine, and Entrepreneur. Founder of The Pragmadik Company and the Steering Guide methodology.

Where can I buy it?
Anywhere where books are sold.
For bulk and corporate orders, or to book a keynote built around the book's frameworks, contact us.

Still deciding?
Think about the last big strategy your organization announced.
Now ask yourself what's actually different because of it.
If you had to think too long, you don't need convincing. You need the book.