Why “What’s next?” should begin transformation, not complete assessment
Assessment reports traditionally end with recommendations and a roadmap. The pattern is familiar:
current state → gaps → recommendations → roadmap → implementation
It appears complete and helpful. The assessor identifies what is wrong and then explains how the organization should improve it. The client receives both a diagnosis and a treatment plan. I have worked with that assumption myself.
But the more clearly I distinguish assessment from transformation, the more I think this familiar sequence hides an important change in professional authority and ownership. An assessment can establish what the evidence supports about the current situation. It cannot, by itself, determine which future the organization should choose. The roadmap is therefore not the final assessment deliverable. It is instead one of the first transformation artifacts.
Why the traditional sequence feels so natural
Assessment findings often seem to point directly toward action. If accountability is unclear, clarify accountability. If feedback arrives too late, shorten the feedback loop. If evidence is unreliable, strengthen the evidence process. If a capability dimension is weak, improve it toward the next maturity level.
This appears to create an almost mechanical progression from gap to recommendation and from recommendation to roadmap. This is especially driven by maturity models, where improvement automatically means a higher maturity level.
But a gap does not determine a unique response. An organization may choose to:
- close the gap;
- reduce its consequences;
- accept the risk;
- postpone action;
- gather more evidence;
- change its ambition;
- narrow the scope;
- or stop doing the work that makes the capability necessary.
Even when improvement is chosen, several interventions may be legitimate. A capability weakness might be addressed through leadership, roles, skills, practices, tools, governance, information, incentives, capacity, or organizational structure.
The assessment can reveal the gap and explain its significance. It cannot determine automatically which response is right.
What the assessor can own
The assessor, supported by a domain specialist, can own the professional integrity of the current-state judgment. That includes:
- defining the subject and scope;
- identifying the decision context;
- selecting and applying an appropriate reference model;
- gathering and validating evidence;
- interpreting that evidence;
- identifying strengths, gaps, risks, and uncertainties;
- judging evidence quality and completeness;
- stating the confidence that can be placed in the conclusions;
- determining whether the subject is good enough for its purpose and context;
- explaining which decisions the judgment can support.
This is substantial professional work.
The assessor should be able to explain what was observed, how it was interpreted, which reference was used, and why the resulting judgment is justified. Together, the assessor and domain specialist can responsibly own the statement:
This is what the available evidence supports about the current situation.
They cannot independently own the statement:
This is the future the organization should pursue, and this is how it should get there.
The assessor can explain implications, but not choose the future
The boundary does not mean that an assessment must end with a neutral description of facts. The assessor can explain the implications of the current state. The assessment can state:
- which risks are created by the current capability;
- which ambitions the organization may be unable to support;
- which dependencies or weaknesses constrain future decisions;
- what may happen if nothing changes;
- where evidence is insufficient;
- which matters require leadership attention.
These are consequences of the current-state judgment. They remain within assessment because they explain what the evidence means.
Improvement goals are different. An improvement goal expresses what the organization intends to make possible in the future. It requires choices about ambition, timing, investment, risk tolerance, affected groups, competing priorities, and acceptable disruption. Those choices cannot be derived from assessment evidence alone.
Improvement goals require business ownership
Suppose an assessment concludes that an application delivery capability cannot reliably support the organization’s intended growth.
The assessment may establish the capability gap with high confidence. But the appropriate improvement goal depends on questions such as:
- How important is the growth ambition?
- Which products, customers, or markets matter most?
- How quickly must the organization respond?
- What investment and capacity are available?
- Which other initiatives compete for the same people?
- How much disruption is acceptable?
- Which risks is leadership prepared to carry?
- Which existing strengths must be protected?
- Is the original ambition still realistic?
These are business questions.
The assessor and domain specialist can contribute evidence, challenge assumptions, and explain capability implications. But they do not possess all the knowledge or authority needed to choose the future state alone.
The client must own the improvement goals because the client owns the ambition, consequences, resources, and trade-offs.
Improvement suggestions are already transformation choices
It may be tempting to say that the roadmap belongs to transformation while recommendations or improvement suggestions can remain assessment outputs. But even a suggestion introduces assumptions about the future.
“Introduce clearer governance” assumes that additional governance will improve decisions rather than add reporting and delay.
“Create a dedicated role” assumes that the problem concerns responsibility rather than authority, incentives, or capacity.
“Standardize the process” assumes that consistency is more valuable than local flexibility.
“Implement a new tool” assumes that tooling is an important constraint and that the organization can adopt the tool effectively.
“Provide training” assumes that insufficient knowledge is the cause of weak behavior.
These may all be reasonable intervention hypotheses.
They are not conclusions contained directly in the assessment evidence.
Improvement suggestions should therefore be developed after the organization has decided to intervene and clarified what it wants to achieve.
“What’s next?” is a transition signal
When an assessment has made the current situation visible, the most natural client response is often:
What should we do next?
That question does not reveal a missing assessment deliverable. It shows that the assessment has succeeded in creating enough clarity for the organization to consider change.
Answering “What’s next?” requires a different kind of work:
- clarifying business ambition;
- defining the required future state;
- setting improvement goals;
- involving the people who will own and experience the change;
- developing alternative interventions;
- evaluating feasibility and dependencies;
- making priorities and trade-offs explicit;
- assigning ownership and capacity;
- deciding how progress and learning will be evaluated;
- creating an initial roadmap.
This is not administrative completion of the assessment. It is the substantive beginning of transformation.
The assessment should not end with the assessor’s roadmap. It should end with sufficient shared clarity for the client to decide whether to create one.
Client ownership does not mean client-only work
Moving goals, suggestions, and roadmaps into transformation does not mean that the assessor leaves after presenting the judgment. The assessor and domain specialist may be well positioned to facilitate or lead the next phase. They understand the evidence, reference model, risks, uncertainties, and reasoning behind the current-state judgment.
They can help the organization:
- translate business ambition into capability outcomes;
- define a realistic future state;
- develop and compare intervention options;
- preserve traceability to the assessment evidence;
- identify dependencies and possible unintended consequences;
- distinguish outcomes from activities;
- treat interventions as hypotheses;
- define evidence of adoption and improved capability;
- establish review and reassessment points.
Their role has changed, however.
As assessors, they determine what the evidence supports about the present. As transformation advisors, they help the organization make choices about the future. The distinction is between leading the process and owning the decisions.
The advisor may structure the work, make the reasoning visible, challenge weak assumptions, and contribute expertise. The client must still choose the goals, accept the trade-offs, commit the capacity, and own the roadmap.
A consultant can facilitate the creation of a roadmap. Only the organization can turn it into an organizational commitment.
The roadmap is more than a list of actions
A roadmap is sometimes treated as a prioritized list of assessment recommendations. But a real roadmap does much more.
It chooses which outcomes matter. It commits scarce capacity. It establishes dependencies and ownership. It decides which risks will be addressed and which will remain. It affects teams, budgets, roles, and existing commitments. It creates consequences for people who may not have participated in the assessment. A roadmap therefore contains organizational decisions.
A consultant-created list of actions may be useful input, but without client choice and ownership it remains a proposal. It is not yet a roadmap in the full sense.
From assessment to transformation
Assessment creates clarity about the present. It establishes the current state, the relevant reference state, the evidence, the risks, the uncertainty, and the resulting judgment. The organization then decides whether the current state should be accepted, investigated further, or changed.
When change is authorized, transformation begins. Its initial work includes defining the intended future state, setting improvement goals, developing and comparing intervention options, assigning ownership and capacity, and creating an initial roadmap.
Later transformation work focuses on implementing, adapting, scaling, embedding, and stabilizing the changes that appear to improve the capability. Reassessment then determines whether the subject itself has become more capable, reliable, or fit for purpose.
A stronger service transition
There is also a practical and commercial consequence. When the roadmap is included as an appendix to the assessment, the engagement can end awkwardly:
“Here are our findings, our suggestions, and the roadmap. Good luck implementing it. Would you now like our help with Accelerate?”
That gives away much of the most important transformation reasoning before the necessary business conversations, ownership decisions, and trade-offs have occurred.
A stronger transition is:
“We now have a shared, evidence-based understanding of the current situation. The next question is what future capability you need, which goals matter, which interventions are realistic, and how the organization wants to own and sequence the change.”
The next phase is not created artificially by withholding useful advice. It exists because defining the future and creating an owned roadmap require knowledge, participation, and authority that assessment alone cannot provide. The client’s question—“What’s next?”—naturally opens that phase.
A cleaner professional boundary
Assessment, transformation, and reassessment can remain part of one continuous service. But they are not the same professional act.
Assessment asks:
What does the evidence support about the current state?
Transformation asks:
What does the organization intend to change, why should it change, and how will that change be pursued?
Reassessment asks:
Did the subject actually become more capable, reliable, or fit for purpose?
Separating these responsibilities does not weaken continuity. It makes the continuity more trustworthy. The assessor owns the integrity of the current-state judgment. The client owns the future it chooses to pursue.
The assessor and domain specialist may facilitate or lead the journey between them—but the roadmap becomes real only when the organization makes it its own.