In the previous article, we looked at organizing related work around a business outcome. The next step is to make that outcome specific enough for people to plan, act, and learn together.
A program does not become strategic because its project list is long. It becomes useful when people can explain the problem, the change they want to see, and how their work contributes.
Begin with evidence
Consider an illustrative organization where clients repeatedly complain about missed follow-ups. The complaints establish a service problem. They do not, by themselves, prove how many clients will leave or how much revenue will be lost.
Write a problem statement that separates what you know from what you still need to investigate: “Agreed client follow-ups are being missed, and responsibility for resolving overdue commitments is unclear.” Record the evidence, the affected groups, and the limits of the data.
Define the outcome and the measure
The desired outcome might be that clients receive the follow-up they were promised, or a timely explanation when that promise needs to change.
An illustrative primary measure is the percentage of agreed follow-ups completed by their due date. Define what counts as a follow-up, where completion is recorded, and who checks the information. Establish a baseline before agreeing a target and review period.
Review supporting measures too: the quality of the response, unresolved complaints, team workload, and respect for client contact preferences. A faster response is not an improvement if it is inaccurate or creates unreasonable work elsewhere.
Give the work clear ownership
Name an accountable program owner who can coordinate across teams and resolve competing priorities. Identify owners for the main areas of work, such as clarifying the follow-up process, improving information quality, and helping people adopt the agreed approach.
Use a work breakdown pyramid to show how those areas connect. Supporting plans should record requirements, dependencies, decisions, and the evidence needed to demonstrate completion. The diagram helps people find the right conversation; it does not replace those conversations.
Compare responses before selecting a tool
A shared task list, a daily review of overdue commitments, changes to an existing system, and new software are possible responses. Compare them against the same requirements before deciding what to implement.
Start with a manageable test where practical. Agree the scope, who participates, what support they need, and what would make you continue, change direction, or stop. Preserve essential controls and service commitments throughout the test.
Review outcomes as well as delivery
At each review, ask what has changed for clients and the people doing the work. Look at the primary measure and supporting evidence together. Investigate whether an apparent improvement reflects better service or simply a change in recording practices.
Completed tasks tell you whether work was delivered. Outcome measures help you understand whether it helped. Use both to decide the next step.
A useful program keeps that connection visible: evidence of a problem, a shared outcome, accountable owners, and regular decisions informed by learning.
Use the accompanying problem-to-program worksheet to structure that first conversation. Leave unknowns visible and assign someone to investigate them rather than filling the gaps with assumptions.