Most consulting engagements in DevOps and digital transformation begin with a tidy set of written goals. Six months in, a surprising number of those goals describe a company that no longer exists: the reorganisation happened, the cloud contract changed, the sponsor moved to another division. The engagement carries on, the team keeps working, and the original aims stay in the kickoff deck, quietly out of date. This post offers an evidence-led checklist for a monthly reread of those goals, so a consulting team and its client can see when an aim has stopped fitting and say so before much more effort is spent on the wrong thing.
The checklist is meant for consultants, internal transformation leads and anyone accountable for a multi-month programme. It is a working audit of the goals themselves, not of the client’s technology.
Why an audit of goals, not just of progress
Progress reports measure movement toward a fixed destination. They rarely ask whether the destination is still right. If a programme goal says “reduce release lead time across all product teams” and one of those teams has been merged into another, the report will keep showing a number for a team that does not exist. The metric stays green while the goal has lost its meaning.
A monthly reread separates the two questions cleanly. Progress asks, “How far have we come?” The reread asks, “Is this still where we ought to be heading?” Teams that only ask the first question accumulate what could be called goal debt: a growing gap between what is written and what matters.
The checklist
Run through these items in order, once a month, with the goal document open and at least one person from the client side in the room. Keep notes in plain sentences.
A. Does the reason still hold?
- Is the business problem that justified this goal still on the client’s priority list?
- Can you name the person who cares most about it today, and is it still the same person?
- Has a change in budget, headcount or vendor contract altered what is feasible?
B. Is the evidence telling us something?
- What did we observe last month that supports or undermines the goal, and where is that observation written down?
- Are we relying on an anecdote from one meeting, or on something repeatable?
- Has any measurement we used to define the goal changed in the way it is collected?
C. Is the scope still sensible?
- Does the goal cover more systems or teams than we can realistically influence?
- Are there parts we are quietly not working on? If so, should the wording reflect that?
- Has an adjacent goal grown to overlap this one?
D. What is the decision?
- Leave it unchanged, with a note on what would trigger a rethink.
- Reword it, naming the specific change in scope, timing or measure.
- Retire it, recording who agreed and what replaces it, if anything.
Write the decision beside each goal with the date. A page of dated decisions is a surprisingly persuasive document in later steering conversations, because it shows that changes were deliberate and not drift.
Reading the evidence honestly
An evidence-led reread demands discipline about what counts. Three kinds of evidence are worth separating. The first is direct observation: a deployment that took less time, an incident handled differently, a form that disappeared. The second is reported experience, such as what engineers say in a retrospective. The third is inference, where you conclude something because a related number moved. All three have a place, but the goal should lean on the first kind wherever possible, and your notes should say which kind each claim is.
It also helps to write down what would count as evidence against the goal. If you cannot describe a result that would make you retire it, the goal is probably too vague to check. For a goal about shortening delivery cycles, you might note that a stable cycle time after two more months would suggest the bottleneck lies elsewhere.
A short example
Consider a mid-sized company that engaged consultants to standardise its deployment process across five product groups. The original goal read: “adopt a single pipeline template in every group by the end of the programme.” At the third monthly reread, three observations stood out. Two groups had adopted the template and reported fewer manual steps. One group was blocked by a regulated release process that the template could not accommodate. One group had been spun off into a separate business unit.
The decision, recorded in a sentence each: keep the goal for the two adopting groups, reword it for the regulated group to “document the exceptions and agree which steps stay manual,” and retire it for the spun-off group. The overall goal shrank from five groups to four, but it became accurate. The next steering meeting was shorter than usual, because there was nothing to defend.
For readers who want more background on how engagements are usually shaped from first assessment to enablement, there is a helpful overview in a blueprint article on running a consulting engagement end to end, which pairs naturally with this checklist.
Keeping the session short and useful
Forty-five minutes is enough if the preparation is done. Ask one person to collect the goal text, the previous month’s decisions and a handful of observations before the meeting, and circulate them a day ahead. Discourage anyone from arriving with new proposals; the reread is for existing goals only, and new ideas can wait for the planning session. When a goal is contested, record both views in a line each and move on, then revisit with extra evidence next month. A disagreement that is written down is far easier to resolve than one that is remembered differently by everyone present.
Adapting the checklist for different roles
- Consultant: reread your engagement goals and your own practice goals separately, since they can drift at different speeds.
- Client sponsor: ask the consulting team which goal they would drop first if forced, then listen carefully to the answer.
- Engineering manager: map each of your team’s goals to the programme goals, and flag any that serve neither.
- Independent practitioner: treat your yearly learning plan as a goal list and reread it on the same monthly rhythm.
On that last point, practitioners often combine several streams of study. One example from a different field is a learning site for aviation professionals called AirCrewU, whose pages describe an independent online platform. Whatever platform or book you use, record the goal, the reason and the date you last confirmed it still fits.
Common failure modes
Three patterns recur. First, the reread becomes a status meeting, and people recite progress without questioning the goals. Prevent this by reading the goal text aloud before anyone speaks about work. Second, the client defers to the consultants and the consultants defer to the client, so nobody proposes retiring anything. Appoint someone, rotating monthly, to argue for dropping at least one goal. Third, the reread happens but is not recorded, so the same debate returns next quarter. A dated list of decisions solves that.
What to bring to the next session
Bring the current goal list, last month’s decision notes and two or three recent observations that bear on the goals. If your organisation is working on broader change, the framing in the article on how consulting support can build enterprise agility may help you test whether each goal still serves the larger direction. Then run the four steps above in about forty-five minutes, and circulate the result the same day.
Goals are working assumptions, and assumptions need regular checking. A monthly reread costs less than a single misdirected sprint, and it keeps the conversation between client and consultant honest about what the work is for.
Best Cardiac Hospitals Near You
Discover top heart hospitals, cardiology centers & cardiac care services by city.
Advanced Heart Care • Trusted Hospitals • Expert Teams
View Best Hospitals