Your strategy is in last quarter’s board deck, a planning memo, an OKR sheet. Import it and the goals, outcomes and initiatives arrive structured, for you to confirm. Or write the direction in a sentence and start from there.
Every decision already links to its tracker work in Decision records. Strategy Alignment rolls those decisions up to the goal that motivated them.
Live coverage shows which goals are actually being executed against. Drift surfaces before the quarter closes.
It is in last quarter’s board deck, a planning memo, an OKR spreadsheet, a Confluence space. Point Traceway at it and the goals, outcomes, initiatives and principles arrive structured as drafts, with a link back to the page they came from, for you to confirm.
Flip the view to Strategies and Trace rolls coverage up from the decision chain, with the healthy goals and the one going dark in the same list.
Product preview · drawn to match the shipping surface · fictional demo data
Follow this decision · where records begin · Decide →Every goal carries a live coverage meter (how many decisions and initiatives actually point at it). The gaps glow before they become a missed quarter.
Strategy Alignment sits on top of your decisions. The tracker link lives in Decision records; Strategy Alignment reads that existing decision-to-execution chain and ties it up to the objectives, so the thread runs board mandate → goal → decision → work without you wiring anything new.
In this fictional example, a team approved a one-year vendor renewal to protect a committed customer-onboarding release. That decision created work: renew the contract, maintain the integration and prepare for the next review. Now a new service requirement has changed the case for keeping the provider. Before the work changes, the team needs to review what the replacement decision would mean for those commitments.
Use the example to check what a product can show before you commit to it.
| Part of the record | Current approved decision: D-214 | Proposed replacement: D-215 |
|---|---|---|
| The call | Renew the current provider for one year. | Replace the provider and revise the related delivery plan. |
| Reason | Migrating before the onboarding release would put its agreed date at risk. | The current provider cannot meet the new service requirement. |
| Alternative considered | Switch providers before the release; rejected because of migration risk. | Keep the renewal and seek an exception; the proposal must explain whether that remains acceptable. |
| Authority | Preserve who approved D-214, when and on which basis. | Name the person authorised to approve this kind of change and the reviews required by your policy. |
| Status | D-214 remains the approved record while the replacement is being considered. | D-215 is a proposal. It becomes the current decision only through the required approval process. |
Follow the records to the work. Ask Procurement whether the renewal commitment can still be changed. Ask the delivery owner which onboarding milestones and integration tasks need a new plan. Ask Operations what a provider change means for the service handover. Record each owner's conclusion, including the work that can continue as agreed.
A list of related work starts that review. The owners still need to confirm what is affected, what evidence is missing and which scope or dates they can commit to. Work that has no dependency on this decision should remain outside the change.
An impact preview is not approval or confirmation that tracker work has changed. Confirm which updates the connection performs and which the delivery owner must make.
When the replacement is approved, keep D-214 and its original reasoning available. Link it to the approved replacement, the version that received sign-off and the work whose commitments changed. Someone joining later should be able to recover both the earlier choice and the reason it was revisited.
Run this exercise in the tools you are considering, with your real approval policy and intended permissions. Start at the goal, open the decision, follow it to the delivery work, then change an assumption and ask the responsible people to complete the review. Check which steps the product enforces, which require configuration and which rely on a maintained handoff. Your existing goal and project systems can remain part of that process.
Use the decision record template to prepare the rationale, alternatives and roles. The audit-evidence guide sets out what to retrieve when you need to show who approved the decision and on what basis. Bring a decision like this to a Traceway demo and follow the same path through rationale, human approval and links to strategy and delivery work.
Strategy primitives stay fixed; the vocabulary is yours. Pick a built-in pack or define your own labels, and the chain works the same underneath.
Most tools stop at the decision. Traceway carries it into the work and tracks the work back to the decision, so nothing drifts from what you actually decided.
A governed decision, signed and on the record.
Tracker creation and state read-back depend on the connected adapter. Azure Boards is built and requires deployment setup. Created work is not edited afterwards.
Delivery rolls back up to the decision; drift is flagged before it costs you.
See Traceway on your kind of decisions, with a direct line to the team building it. Booking a demo never adds you to an automatic email sequence. Tick the box only if you'd like occasional product news.
Data is held in the United States, or in the European Union for a workspace set up there. Book a demo from anywhere.