You formatted the Goal. Now find out if the right people have actually approved it. Strategy built on top of a Goal that leadership has not formally reviewed will produce exactly the kind of strategic misalignment G-STIC is designed to prevent.
Open approval matrixQuick answer
Stakeholder alignment at the Goal layer means the people who must live with the goal have formally reviewed and approved each of its components before strategy begins. This free check runs a Goal Approval Matrix across your stakeholders, then tells you whether the goal is truly signed off or still carries undocumented disagreement that surfaces later as execution failure.
Why this step exists
In the G-STIC sequence, the Goal is the foundation every other layer builds on. Step 8 helps you format it correctly. Step 9 checks whether the people who must live with the consequences have formally reviewed and signed off on each component before the Strategy is written on top of it.
This is not a procedural formality. Undocumented disagreements at the Goal layer become embedded in the Strategy, then become structural conflicts at the Tactics layer, and ultimately surface as execution failures. Getting explicit approval now costs a conversation. Discovering the misalignment after six weeks of Strategy development costs the six weeks.
Click any cell to cycle: not discussed → in review → approved
CEO and CFO are included by default. Toggle any additional role to add a row. Approvals persist across sessions. Return with the same email to continue tracking.
| Stakeholder | Goal ReviewedComplete 4-component doc seen |
Benchmark ApprovedFocus metric and target number |
Demand Source AgreedWhich demand pool we target |
Persuasion Task AgreedBelief change the strategy drives |
Objections ResolvedNo outstanding concerns |
Status |
|---|
Click any cell to begin tracking approvals.
Step 10 authors the strategy your aligned goal will run on.
Save your alignment map
This tool is designed to be updated over time. Save your current state and return with the same email to continue tracking as stakeholder conversations happen.
✓ Your alignment map is saved.
Copy your return link to pick up where you left off from any device.FAQ
Strategy is built on top of the Goal. Every component of the Strategy (Target Customer, Customer Need, Value Proposition, Competitive Advantage) is determined by which Demand Source the Goal specifies and what Persuasion Task it requires. If the Demand Source has not been formally agreed on, then the Target Customer and the GTM motion are both wrong, and the entire Strategy that follows is built on a contested foundation. It costs a conversation to resolve this at Step 9. It costs a month of Strategy rework to resolve it at Step 14.
Formal approval means the stakeholder has seen the complete, formatted Goal document (not just a revenue number or a slide summary) and has explicitly confirmed agreement on each component. An email saying "looks good" in response to a summary is not a formal approval of the Benchmark. A conversation in a meeting where the Goal was shown and the CFO said "yes, that target is right" is. When in doubt, ask yourself: if this stakeholder raises an objection about the Benchmark six weeks from now, will you have a record of them approving it? If not, it has not been formally approved.
Not necessarily. The CFO may have strong opinions on the Benchmark but no particular view on the Persuasion Task. The Sales leader is most important on Demand Source; they own the pipeline the Goal implies. The CEO or Owner needs to see the complete document. You can have stakeholders who are in review on some components and fully approved on others. The tool tracks this granularity so you can see exactly where the remaining conversations need to happen rather than treating alignment as binary.
An unresolvable objection at the Goal layer is useful information: it means the Goal itself may need to be revised before Strategy development begins. This is far less costly than proceeding and discovering six weeks later that the Goal cannot get approved. Use Step 8, the G-STIC Goal Formatter, to revisit the specific component the objection targets and build the case for each component before returning to the approval process.
Yes, but the second time takes much less effort than the first. Once you have established the pattern of formal Goal approval with your stakeholders, subsequent cycles become a review of changes from the prior year rather than a first-time education. Organizations that run this check consistently report that their Strategy reviews go significantly faster because nobody is relitigating the Goal.