Docs menu

Method guide / Goal

Write the outcome before defining the work.

A Goal gives the software change an accountable result, a reason to exist, and a direction for measuring success.

Start with the business change

A useful Goal describes what should become materially better for the organization. It gives business and technical owners one outcome to evaluate before anyone commits to a solution.

  • Identify the outcome and accountable owner
  • Explain why the change matters now
  • Make important constraints visible
  • Describe what credible progress would look like

Keep the Goal independent of a preferred implementation

A Goal can include a real business, regulatory, or technology constraint. It should not turn an early preference into the solution before the relevant Context and tradeoffs are understood.