A goal defines the outcome that makes a project worth doing and the success criteria that mark it complete. It does not, by itself, specify the method or the schedule. Whether a project lasts days or years, start by stating what must be true when it is finished. section 9.1.2
Describe the outcome, not just the implementation
An engineering team might describe a project internally as replacing a Windows XP-dependent customer intake process with Java in a serverless environment. For a CEO or CFO, the useful goal is to modernize intake for greater flexibility and throughput. The second description makes the intended outcome easier to assess without requiring the audience to follow the implementation plan. section 9.1.2
Goals also make team accountability fairer. Agree on meaningful metrics with team leads, then measure and review them together. Finding the right metrics may take weeks, particularly when taking over a team. Once established, they provide a basis for discussing performance and setting new benchmarks instead of relying on subjective judgments. Accountability still needs trust: a problem should be reported openly, not hidden for fear of blame. section 6.4.3 section 6.4.3
The same question applies to a career: what does success in the current role look like? A clear answer makes progress and satisfaction easier to judge. Revisit it as experience changes what you want to pursue next. section 15.6
