Category: Practice Notes

  • Practice Note: Choosing a Watch for the Beach

    Yesterday I wanted to spend a few hours at the beach. That should have been one of the simplest decisions of the day. Instead, I found myself choosing between watch configurations. Not watches. Watch configurations. If you’re not interested in watches, you’ve probably just rolled your eyes. Bear with me. This gets worse before it gets better.

    The strange thing about owning more than one watch is that you eventually stop choosing between watches. You start choosing between combinations. First, there are different watch types. Dress watches. Dive watches. Field watches. Pilot watches. GMT watches. Chronographs. Smartwatches. Then there are different case materials. Steel. Titanium. Gold. Ceramic. Carbon. Then come the straps and bracelets. Leather. Steel. Rubber. Silicone. NATO. Milanese. And finally there are the occasions. Business meetings. Client workshops. Traveling. Black tie. Dinner. Walking. Hiking. Swimming. Beach holidays. Working from home.

    Some combinations work beautifully. Others feel completely wrong. A dress watch on a rubber strap. A dive watch with a crocodile leather strap. A smartwatch with a dinner jacket. Technically possible. Practically… questionable.

    Yesterday’s shortlist looked like this:

    • Victorinox on its steel bracelet.
    • Victorinox on the rubber strap that I still intend to buy.
    • Apple Watch Ultra with the titanium Milanese Loop.
    • Apple Watch Ultra with a silicone strap.

    Leather straps never even made the shortlist. Swimming eliminates leather before the discussion begins.

    At this point normal people have probably stopped reading. Or they’re wondering why anyone would willingly complicate something as simple as going to the beach. That is a fair question. I wondered the same thing.

    Then I realized I wasn’t really choosing a watch. I was performing an assessment.

    Hidden beneath the madness

    Without consciously thinking about it, I had already established the context. The occasion was:

    • Swimming.
    • Sunbathing.
    • Casual leisure.
    • Warm weather.
    • Activity tracking would be useful.

    The occasion had quietly defined the reference model. Once that happened, the rest became surprisingly structured. Leather disappeared immediately because it failed a mandatory criterion. The remaining candidates all satisfied the essential requirements. The Victorinox on its steel bracelet would have worked perfectly. The Apple Watch Ultra with the silicone strap would also have worked perfectly.

    In the end I chose the Apple Watch Ultra with the titanium Milanese Loop. Why? Because it already met every important criterion. It works well in the water. It tracks my activity. The Milanese Loop is surprisingly comfortable for swimming. And it was already on the watch.

    Changing to the silicone strap might have produced a tiny improvement. Not enough to justify changing it. The decision wasn’t about finding perfection. It was about recognizing that several options were good enough.

    Then something even stranger happened

    Choosing a watch for today turned out not to be the most interesting assessment. The more interesting question was what this decision said about the collection itself. Suppose I repeatedly discover that no existing watch configuration works well for a certain type of occasion.

    Now I have evidence. Not evidence that I need another watch. Evidence that I may be missing a capability. That is an entirely different conclusion. Buying another dive watch because I like dive watches merely enlarges the collection. Buying a watch that enables a capability I genuinely lack expands the capability of the collection.

    Those are not the same thing. A larger collection is not necessarily a more capable collection. Someone with twelve dive watches may actually have fewer capabilities than someone with four carefully chosen watches covering formal occasions, everyday wear, outdoor activities and sports.

    That distinction only becomes visible once you assess the portfolio rather than admire the individual items.

    From watches to organisations

    At this point you may have forgotten that this story started with a trip to the beach. So had I. Because somewhere along the way I realized that this wasn’t really about watches. It was about assessment. Start with the context. Make the reference model explicit. Identify mandatory criteria. Eliminate unsuitable options. Compare the remaining candidates. Accept that several answers may be equally valid. Observe recurring patterns over time. Identify capability gaps. Invest where capabilities are missing rather than where enthusiasm happens to be highest.

    That is exactly the same reasoning I use when assessing software products, organizational capabilities, consulting practices or transformation initiatives. The domain changes. The thinking does not.

    Method in the madness

    From the outside this probably looked like an enthusiast overthinking a trivial decision. Perhaps it was. But what looked like madness turned out to have a surprisingly coherent method.

    The interesting part is not that I own several watches. The interesting part is that once enough dimensions are involved—watch types, materials, straps, occasions and personal preferences—the number of possible combinations grows remarkably quickly. The world quietly becomes more complicated than our intuition comfortably manages.

    That is the moment when methods become valuable. Not because they make the world more complicated. But because they help us navigate complexity without having to rethink everything from first principles every single time. Yesterday I happened to use that method to choose a watch for the beach. Tomorrow I might use exactly the same method to assess a software product, a wardrobe, an organisation or an investment portfolio.

    The watches were never really the story. They were simply the easiest place to see the method hiding in the madness.

  • Practice Note: The Suit Did Not Become Less Beautiful

    I recently bought a made-to-measure suit. It is not bespoke in the strictest sense. It was adapted from established patterns and standard sizes rather than designed entirely from scratch. Even so, the difference from an ordinary off-the-rack suit is noticeable. The jacket follows my body more closely. The shoulders, sleeves and waist relate properly to one another. The trousers fall cleanly. The outfit appears coherent rather than merely assembled.

    A good suit does something unusual to the male body. It strengthens the shoulders, clarifies the chest, narrows the waist and creates a continuous line through the trousers. The lapels, shirt collar and tie direct attention toward the face. Differences in physique are not removed, but reorganized into a more deliberate silhouette.

    The result is not accidental. The classic suit has been refined over generations to make a man appear balanced, composed and intentional.

    When I wear mine, I look better in it than I do in most ordinary clothes. I also feel better in it. That should be sufficient reason to wear it. Yet if I wore it to the office on an ordinary working day, I would probably have to explain myself. Someone might ask whether I had an important client meeting, a job interview, a wedding or perhaps a funeral. A suit is no longer interpreted simply as clothing. It is evidence that something unusual must be happening.

    The strange part is that I have watched this reversal take place during my own working life.

    Ready to meet the client

    When I began working in the Netherlands around thirty years ago, the professional norm was a suit and tie—or at least a jacket with straight trousers. The clothing communicated readiness.

    In consulting, the assumption was that one should be able to meet a client. The suit was therefore not necessarily a claim of exceptional importance. It was the normal condition of being professionally prepared.

    Casual clothing carried the more specific message. A deliberately casual outfit could indicate that someone expected to remain in the office and would not be meeting clients that day. The deviation from the norm required a reason. Formality did not.

    The tie was part of that system, although it also became the first part to create noticeable friction. On warm days, in particular, it could feel unnecessary and uncomfortable. People began to question why a narrow strip of fabric around the neck should be required to demonstrate professional competence.

    Once the tie became negotiable, the rest of the system gradually became negotiable too. The jacket remained, but increasingly without the tie. Straight trousers gradually lost ground to jeans. Formal leather shoes were replaced by more casual alternatives. The professional uniform did not disappear in one decisive moment. It loosened one element at a time.

    When I moved to Sweden, I encountered a reference model that had already shifted considerably further. The tie was the exception rather than the rule. Jeans had largely replaced tailored trousers. A more restrained and informal style communicated social ease and cultural fit. The same clothing that had signalled professional readiness in the Netherlands could now risk signaling distance, rigidity or excessive formality. I even suspect that wearing a tie may once have contributed to my not surviving an assignment interview. I cannot prove it, and other factors may have been more important. But the possibility itself is revealing.

    A garment that had once demonstrated that I understood professional expectations may have suggested that I did not understand them. The tie had not changed. The reference model around it had.

    The webcam-ready professional

    Then Covid arrived and accelerated changes that were already underway. For many people, work moved into the home. The professional person was reduced to the part visible through a webcam. Clothing no longer needed to present a complete person in a shared physical environment. It needed to produce an acceptable rectangle on a screen.

    The new minimum was something like be sufficiently dressed above the waist, do not appear to have just left bed, look representative enough for a video call. What happened below the camera was largely outside the available evidence.

    Even after offices reopened, much of the old dress logic did not return. The standard became less a matter of being formally prepared and more a matter of avoiding obvious inappropriateness. One should perhaps wear slightly more than shorts and a Hawaiian shirt because clients might visit the office, but the distance between minimum acceptability and considered elegance had become enormous.

    Some managers continued to dress somewhat more formally. So did some people who perhaps wished to become managers. This gave the remaining formal clothing an additional meaning. A jacket or suit could now be interpreted not only as professional preparation, but as a performance of rank, authority or ambition.

    That makes the choice more socially complicated. A man may wear a suit because he likes how it looks and feels. Others may interpret it as an attempt to appear more important than they are. The clothing remains the same. The social explanation changes.

    What makes an outfit good?

    In two earlier field notes, I compared my Apple Watch with my Victorinox I.N.O.X. Automatic. The Apple Watch won on accuracy, functionality, adaptability, information and integration with the digital world. The Victorinox won on physical presence, materials, craftsmanship, visual depth and attachment. The watches occupied the same wrist but represented different ideas of value.

    The comparison depended on the reference model: the set of qualities against which the watches were judged. Change the criteria, or change the weight assigned to them, and the result changes too.

    Clothing reveals a similar conflict, but at a larger scale. A watch occupies a small part of the body. An outfit occupies almost the entire visible person. I can wear only one primary outfit at a time, which means that competing definitions of good clothing must fight for the same physical territory.

    The classic suit performs exceptionally well against one reference model. It provides structure, proportion, visual coherence, dignity and formality. It communicates care and preparation. A well-fitted suit can make an ordinary male body appear more balanced and commanding without becoming overtly decorative.

    Earlier conventions of menswear placed considerable weight on these qualities. Clothing helped distinguish public from private life, work from leisure and formal occasions from ordinary ones. Appearing properly dressed was part of participating in the situation. The wearer accepted a degree of inconvenience in exchange for elegance, ceremony and social clarity.

    The contemporary reference model places greater weight elsewhere. Clothing should be comfortable. It should be easy to wash, easy to combine and suitable for several different situations. It should tolerate changes in body shape and require little specialist knowledge from the wearer. It should work in an office, on public transport, in a café and at home. Ideally, it should not require ironing, polishing, specialist cleaning or careful storage. It should also avoid making the wearer appear overdressed.

    These are not irrational requirements. They represent genuine forms of value. A garment that looks elegant but feels restrictive, requires maintenance and appears inappropriate in most everyday environments may perform poorly against the realities of modern life. The suit can therefore remain aesthetically successful while becoming practically unsuccessful.

    The disappearing weight of elegance

    The change is not simply that comfort became more important. It is that elegance became less decisive. Imagine a reference model for menswear containing several dimensions:

    visual proportion;

    elegance;

    comfort;

    flexibility;

    ease of maintenance;

    affordability;

    social appropriateness;

    personal expression.

    A suit may score very highly on proportion and elegance. Depending on its fabric and construction, it may also perform reasonably well on comfort. But it will usually cost more, require greater care, tolerate fewer sizing errors and carry stronger social meaning than casual clothing.

    A contemporary casual outfit may score less strongly on silhouette and visual coherence, but better on comfort, flexibility, washability and social neutrality.

    Neither assessment requires anyone to deny that the suit looks better. The outcome changes because the dimensions receive different weights.

    Thirty years ago, appearing professionally prepared carried enough weight to justify the inconvenience of a jacket and tie. Today, comfort and ease often dominate the decision before appearance is seriously considered. Elegance remains desirable, but only after the clothing has passed several other tests.

    The suit did not lose because its ability to improve the male silhouette disappeared. Its strongest quality simply became less important to the judgment.

    One body, one choice

    The competition for the wrist is severe because most people wear only one watch at a time. The competition for the body is more severe still. A mechanical watch and a smartwatch compete for one relatively small physical slot. A suit competes with every other possible way of dressing the whole body.

    Each morning becomes a small assessment.

    What will I be doing?

    How warm will it be?

    Will I need to walk or cycle?

    Will I be sitting for long periods?

    How will everyone else be dressed?

    Will the suit communicate confidence, or create distance?

    Will I look elegant, or merely overdressed?

    The answer is rarely determined by appearance alone.

    This makes casualization self-reinforcing. When suits are common, wearing one attracts little attention. When suits become rare, wearing one becomes conspicuous. The same garment that once allowed a man to conform now causes him to stand apart.

    That changes its practical value. A man may admire suits and still avoid wearing one because he does not want to explain the choice. He may not want colleagues to assume he has an interview, an important presentation or some ceremonial obligation. He may not want to look more formal than his manager or appear to be claiming a status that has not been assigned to him.

    The reference model is therefore not entirely personal. It is also social. An outfit must not only satisfy the needs of the wearer. It must interact with the expectations of everyone who sees it. Comfort can be experienced individually. Formality exists between people.

    The coordination problem

    Many men may look better in jackets, tailored trousers and properly fitted shirts. They may even agree that they do. But no individual man controls the dress code of the environment around him. If everyone else dresses casually, the first person to return to formal clothing pays a social cost. He becomes the exception before the potential aesthetic improvement can become normal again.

    The suit once benefited from a shared convention. Men did not need to justify wearing one because the surrounding culture had already justified it for them. When that convention weakened, the suit lost more than popularity. It lost the social infrastructure that made wearing it effortless.

    Casual clothing now benefits from that infrastructure. It is not merely physically comfortable. It is socially comfortable. It rarely requires explanation. It does not imply that the wearer considers the occasion more important than everyone else does. It does not visibly demand that others respond with the same degree of formality.

    Nobody asks a colleague in jeans and trainers:

    Why are you dressed casually today?

    But a colleague wearing a suit may immediately be asked:

    What is the occasion?

    That asymmetry reveals which reference model has become dominant.

    Casual clothing is treated as neutral. Dressing well has become an event.

    Better according to what?

    The suit exposes a recurring problem in assessment. We often speak as though a product, capability or practice is simply good or bad. But every judgment depends on some conception of the required, intended or expected state.

    A classic suit may be better than casual clothing when the objective is to create a structured and elegant male silhouette. Casual clothing may be better when the objective is to maximize comfort, simplify maintenance and move easily between different contexts. The disagreement cannot be resolved by examining the garments more carefully. It originates in the reference model.

    Even the evidence may be accepted by both sides. A person can agree that the suit improves proportion, that knitwear feels more comfortable, that trainers are easier to walk in and that tailored clothing requires more care.

    The dispute begins when those qualities are weighted and combined into a final judgment. This also means that a changing assessment outcome does not necessarily indicate a change in the subject itself. The suit may be much the same garment it was before. Its shoulders still create structure. Its lapels still frame the chest and face. Its trousers still lengthen the visible line of the legs. Its visual logic has not stopped functioning.

    What changed was the required state around it. A garment designed to satisfy an earlier understanding of public appearance now enters a world that expects clothing to satisfy a different combination of needs. The subject remained capable. The environment revised the criteria.

    Progress or exchange?

    It is tempting to describe the change as straightforward progress. Modern clothing is less restrictive. Dress codes are more flexible. People can express themselves more freely and move between professional and private life without changing clothes. Garments are easier to maintain, and formal appearance is less closely tied to respectability or professional legitimacy. Those are real gains.

    But progress in one reference model may conceal losses in another. The average outfit may have become more comfortable while becoming less flattering. It may be easier to maintain while offering less structure and visual coherence. It may allow greater individuality while also making indifference easier.

    Freedom from formal rules does not guarantee that the replacement will be equally considered. Casualization therefore need not be interpreted as either decline or liberation. It is an exchange between qualities. We gained convenience, flexibility and social ease. We gave up some ceremony, visual discipline and shared understanding of what it meant to dress well in public. Whether that exchange represents improvement depends, once again, on the reference model.

    From conformity to choice

    There is one important difference between wearing a suit now and wearing one thirty years ago. Then, the suit was largely conformity. Now, it can be choice.

    When everyone was expected to wear a suit, doing so revealed relatively little about the individual. The garment communicated professional membership more than personal preference.

    Today, wearing one voluntarily may communicate something more personal. It may say that appearance matters. That the wearer enjoys structure, materials and proportion. That comfort is not the only quality worth optimizing. That an ordinary working day can be a sufficient occasion for dressing well.

    The simplest explanation may also be the most honest:

    It looks better, and I feel better wearing it.

    That statement should be unremarkable. Yet in the current environment, it may sound surprisingly assertive. It openly admits that appearance matters and that the wearer has deliberately chosen the more elegant option.

    Modern male dress often permits considerable effort, provided that effort remains disguised. Expensive trainers, carefully selected casual clothing, fitness regimes and subtle status objects may all require attention and money. But saying that one has chosen a suit because it looks better makes the intention explicit.

    The suit no longer needs to justify what it does to the male silhouette. The wearer must justify why he still values it.

    Losing the body

    My made-to-measure suit has not become obsolete in the same way that unsupported software or discontinued hardware becomes obsolete. It still performs the function for which it was designed. It may even perform that function better than most contemporary alternatives. When I put it on, it still improves my proportions. It still creates a unified silhouette. It still makes me appear more deliberate and composed.

    But it must now compete against an expanded definition of what clothing is expected to provide. Comfort matters. Washability matters. Flexibility matters. Social neutrality matters. The ability to dress without thinking too much about clothing may matter most of all.

    The suit can win the aesthetic comparison and still lose the morning decision. That is the extension of the contest between my watches. The Apple Watch and Victorinox compete for one wrist while representing different value systems. Formal and casual clothing compete for the entire body while representing different ideas of everyday life.

    The crucial difference is that clothing is not merely an object I carry. It becomes the visible surface through which I enter a social environment. Choosing an outfit therefore means choosing not only which qualities I value, but which relationship I want to establish with the people around me.

    I began my career in a world where dressing casually required an explanation. Thirty years later, wearing the suit does. The suit did not fall from grace because it ceased to be beautiful.

    It lost because beauty, structure and elegance no longer carry enough weight to defeat comfort, convenience and social neutrality every morning. The better-looking outfit does not lose the assessment. It loses the body—because we are no longer assessing clothing primarily by how good it makes the body look.

  • Practice Note: The Roadmap Should Not Be Part of an Assessment

    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.

  • Practice Note: A Product Reference Model Through the Eyes of an Enterprise Architect

    When I first began thinking about a Product Reference Model, I imagined it as something new. Over time, I have become less convinced that it is.

    Perhaps I have simply been rediscovering ideas that Enterprise Architecture has explored for decades—but applying them at a different scale and with a different objective. Enterprise Architects rarely begin with source code. They think about relationships. Business capabilities support strategic objectives. Applications realize capabilities. Technology supports applications. Information flows between systems. The architecture is not merely a collection of artifacts. It is the set of relationships that makes those artifacts meaningful.

    That sounds surprisingly familiar. My Product Reference Model has gradually evolved into something that also emphasizes relationships. Business objectives relate to capabilities. Capabilities relate to features. Features relate to requirements. Requirements relate to BDD scenarios. BDD scenarios relate to implementation. Implementation relates to architecture. Architecture relates to operational procedures. Assessments relate back to business outcomes. Rather than replacing individual artifacts, the Product Reference Model attempts to make those relationships explicit.

    Perhaps that is exactly what Enterprise Architecture has always tried to achieve—only at enterprise scale. If that is true, then perhaps the Product Reference Model should not be viewed as a competing framework. Instead, it may simply be Enterprise Architecture viewed through the lens of a single product.

    The emphasis is different. Enterprise Architecture asks:

    How does this product fit within the enterprise?

    The Product Reference Model asks:

    How does every important aspect of this product fit together?

    That distinction may appear subtle, but it changes the audience. Enterprise Architects often think across portfolios, organizations and technologies. Product Owners, developers, testers and operations engineers think about one product. The underlying architectural principles remain remarkably similar.

    What also changes is the purpose. Traditional Enterprise Architecture often focuses on describing structure. The Product Reference Model attempts to preserve understanding.

    Every relationship should ultimately help answer one of the questions future teams inevitably ask: Why does this capability exist? Why was this architectural decision made? Why is this business rule still here? Where is the evidence that this requirement is implemented? Which assessment concluded that this capability was fit for purpose? How do all these artifacts relate to one another?

    Perhaps the Product Reference Model is therefore less concerned with documenting a product than with making the product understandable.

    It becomes a navigational model rather than merely a descriptive one. That observation also changes my own perspective. Instead of inventing another framework, perhaps I should learn more from Enterprise Architecture. Architects have already spent decades thinking about repositories, viewpoints, traceability, relationships, stakeholders and governance.

    The Product Reference Model may simply extend those principles into the daily life of a product team. Its contribution would not be another modeling language. Its contribution would be placing product understanding at the center.

    Perhaps the Product Reference Model can therefore be described quite simply:

    The Product Reference Model applies Enterprise Architecture principles to a single product, with particular emphasis on preserving product understanding throughout the product’s lifecycle.

    If Enterprise Architecture asks how an enterprise remains coherent…

    …perhaps the Product Reference Model asks how a product remains understandable.

  • Practice Note: A Product Reference Model Through the Eyes of a Product Owner

    When I first began thinking about a Product Reference Model, I assumed it would become another documentation framework.

    As a Product Owner, that was not particularly attractive. Most Product Owners already spend their days balancing stakeholder expectations, refining the backlog, making priority decisions and answering questions from delivery teams. Another repository sounded like another responsibility.

    But perhaps that is the wrong way to think about it. As Product Owners, we rarely inherit a greenfield product. We inherit decisions. Business rules. Architecture. Operational procedures. Quality concerns. Technical debt. And, perhaps most importantly, we inherit understanding—or the absence of it.

    One of the most common questions a Product Owner asks is remarkably simple:

    Why?

    Why does this capability exist? Why do these customers receive different treatment? Why was this integration introduced? Why is this feature impossible to remove? Why was this architectural decision made? Why is this quality requirement so important?

    Those answers rarely exist in one place. Some are hidden in Jira. Some in architecture documentation. Some in source code. Some in BDD scenarios. Some in assessment reports. Many remain only in the memories of people who happened to be there.

    The Product Reference Model begins to make sense when it is no longer viewed as documentation. Instead, it becomes a map of product understanding. The Product Owner continues owning the backlog. Architects continue owning architecture. Developers continue owning source code. QA continues owning assessments and quality strategy. Operations continues owning operational knowledge.

    Nothing changes. Except that all these pieces become visible to one another. The Product Owner is no longer expected to know everything. The Product Owner is expected to know where the understanding lives.

    That changes the role in an important way. The backlog is no longer the product. It is merely one viewpoint of the product. The Product Reference Model allows the Product Owner to navigate the complete product landscape without becoming responsible for maintaining every artifact personally. Perhaps that is the real value.

    The Product Owner becomes the steward of product understanding rather than merely the owner of the backlog.

    Stewardship is different from ownership. Ownership often implies creating and maintaining artifacts. Stewardship means ensuring that future Product Owners inherit enough understanding to continue making good decisions.

    The Product Reference Model therefore does not make the Product Owner responsible for more documentation. It makes the Product Owner responsible for ensuring that the important answers remain connected. Perhaps continuity is not ultimately about preserving software. Perhaps it is about ensuring that every new Product Owner can understand the product they inherit before deciding how it should evolve.