Outcome Overview

• What is the Business Goal/Objective of this outcome?

Timeline

Timeline put in place for when this outcome will be achieved with the information at hand. E.g Target release date at a high level (Quarter/Year) for milestones (e.g. Developer Preview, Tech Preview, Generally Available)] (Subject to change).
All features required to deliver on this outcome to be linked to the outcome and discussion with teams to be had before the timeline is set. Review of timeline to take place regularly - any changes to be communicated.

Assumptions

List any assumptions you have about your users, technical constraints, or business goals.

Dependencies

List any internal and external dependencies.

All known teams that have a dependency on this Outcome should be listed in the description or notified. They can link to this Outcome or add themselves as a watcher to track risks.
Other dependent Outcomes should also be linked.

Customer Needs

Specific customer needs (external/internal) that this outcome will solve.

Success Criteria

What is the success criteria for this strategic outcome? Avoid listing Features or Initiatives and instead describe "what must be true" for the outcome to be considered delivered.

Use Success Metrics if possible (See Metrics).

Expected Results (what, how, when)

What incremental impact do you expect to create toward the company's Strategic Goals by delivering this outcome? (possible examples: unblocking sales, shifts in product metrics, etc. + provide links to metrics that will be used post-completion for review & pivot decisions). {}For each expected result, list what you will measure and when you will measure it (ex. provide links to existing information or metrics that will be used post-completion for review and specify when you will review the measurement such as 60 days after the work is complete)

Metrics

Possible Measurements / Observable Results: Detailed overview of what will be measured to identify progress on that outcome.
Explicit KPIs and Metrics tied to goals/outcomes