Where it came from
In 1986, Norman Evans — a Toronto marketing strategist who launched Microsoft in Canada — published a handbook for people who buy creative services. He called it The Creative Marketer’s Handbook, or, with more honesty, The Chicken Tester’s Manual. The chicken test came from aerospace: engineers fire a cannon of dead chickens at a new jet engine to find failure points before committing everything to an outcome that depends on passing it. Rolls-Royce, according to the story Evans tells, spent five years and a quarter-billion dollars developing a powerful new engine. When they finally wheeled in the chicken gun, the blades shattered.
The moral isn’t about chickens. It’s about the order in which you do things.
Buried in that handbook was S.T.A.R. — a tactical method of strategic planning that Evans developed with Philip Bliss and Jonathan Sachs at the Creative Marketing Network. It was built for marketing agencies. I’ve spent the better part of four decades applying it to whatever I was working on: hotels, technology platforms, regulatory governance. A framework that actually works doesn’t care what industry you’re in.
What the framework does
S.T.A.R. answers a specific question: how do you connect a boardroom strategy to actual work on the street? Most organizations can do one or the other. They develop a compelling strategy and implement it randomly. Or they execute tactically with no clear line back to what they were trying to accomplish. S.T.A.R. was designed to bridge that gap.
The global objectives. Not the mission statement framed above reception. The actual answer to “where are we trying to get?” Define the destination before you start moving. Everything else connects back here — or it shouldn’t exist.
Ground-level maneuvers. Specific, attainable, budget-constrained. Each tactic should connect directly back to a strategy. If you can’t draw that line, the tactic shouldn’t exist. That’s not cruelty — it’s focus.
What actually gets done. Who does what, by when, for how much. This is where most plans go to die. They live as slide decks and never become work. Actions is the bridge from intent to execution.
The feedback loop. Did the actions produce the expected outcomes? If not, where did the chain break — strategy, tactics, or execution? The answer changes what you do next. There are reasons and results, and reasons don’t count.
Evans’ original version included two additional elements: Resources and Responsibilities. The operational scaffolding an agency needs when coordinating creative suppliers across a complex production chain. After three-plus decades of applying this framework outside an agency context, I’ve found those elements collapse naturally into Actions. If you’re clear on who does what and by when, you’ve handled both. The cleaner version travels better.
The framework under pressure
I chaired the board of TICO — the Travel Industry Council of Ontario — for five years, ending in early 2026. The mandate was consumer protection for Ontario’s travel industry. The environment was about as stable as a flock of birds near a jet engine: a global pandemic, industry insolvencies, regulatory modernization, and ongoing government relations. New problems arrived before the old ones were resolved.
S.T.A.R. doesn’t make that easier. What it does is prevent the most common governance failure: confusing activity with progress.
The strategy was clear and didn’t change: protect Ontario consumers and maintain the integrity of the regulated travel industry. Everything else — every committee mandate, every policy initiative, every staff priority — had to connect back to that. When it couldn’t, we stopped doing it.
That sounds obvious until you’re three years into a governance mandate and someone proposes something that feels important but can’t be traced back to the core strategy. The framework gives you a question to ask instead of an argument to have: where does this connect?
The results were measured mostly in what didn’t happen. The consumer compensation fund held. The industry survived circumstances nobody had planned for. Consumers were protected. Five years of genuine turbulence, zero governance theatre.
What Norman knew in 1986
Norman would point out, accurately, that he built S.T.A.R. for marketing agencies. He’s not wrong about what he built it for. But that’s the thing about a framework that actually works: it doesn’t care what industry you’re in.
The chicken test is the part I think about most. The principle isn’t really about jet engines or even about testing early. It’s about sequencing. Do the critical test before you’ve committed everything to an outcome that depends on passing it.
Most strategy fails in the gap between planning and execution. Not because the strategy was wrong. Because nobody built a bridge between where the plan ended and where the work began.
That’s what S.T.A.R. does. It’s not complicated. Norman knew that in 1986.
Some things age better than chickens.
What is the S.T.A.R. methodology?
The S.T.A.R. methodology is a business strategy framework built on four stages: Strategies, Tactics, Actions, and Results. It closes the gap between idea generation and execution, using a feedback loop to trace outcomes back to the point where the chain broke.
Who created the S.T.A.R. methodology?
S.T.A.R. was created by Norman Evans, Philip Bliss, and Jonathan Sachs at the Creative Marketing Network (CMN) in Toronto in 1986. Evans, a marketing strategist who launched Microsoft in Canada, introduced it in The Creative Marketer’s Handbook as a method for bridging strategic planning and operational execution.
What does S.T.A.R. stand for in business strategy?
Strategies (global objectives — where are you trying to get?), Tactics (specific, budget-constrained ground-level maneuvers that connect back to the strategy), Actions (who does what, by when, for how much), and Results (the feedback loop that traces outcomes back to the point where the chain broke).
How is S.T.A.R. different from other strategy frameworks?
Most strategy frameworks stop at the plan. S.T.A.R. was built specifically to bridge the gap between strategic intent and operational execution. The Results stage functions as a diagnostic: when outcomes don’t match expectations, you trace the failure back through the chain — strategy, tactics, or execution. That answer changes what you do next.
What is the chicken test in business strategy?
The chicken test comes from aerospace engineering: fire dead chickens at a jet engine early in development to find failure points before committing full resources. Applied to strategy, it means testing critical assumptions at the concept stage rather than after full investment. Norman Evans used it as the organizing metaphor for S.T.A.R. — the feedback loop built into the Results stage is the chicken gun, designed in from the start.
Can S.T.A.R. be applied outside of marketing?
Yes. Evans designed it for marketing agencies. It’s been applied across hotel operations, technology platform development, and regulatory governance. A framework that actually works doesn’t care what industry you’re in. The core question is always the same: can you draw a clear line from this action back to the strategy it’s supposed to serve?
