Blog

  • Blog Retrospective #3

    I have now completed sixty posts.

    The first retrospective examined the writing process. The second examined the emerging theory of product quality assessment. This time, the most interesting development may not be found inside any individual field note. It is found in the relationships between them.

    What Happened?

    During this cycle, the field notes moved across a much wider range of subjects. Some continued the work on product reference models, Product Ownership and assessment. Others explored system continuity, understanding debt, documentation and the preservation of knowledge. Then the notes wandered into watches, clothing, writing, storytelling and AI-assisted thinking.

    At first glance, this might look as though the blog had started losing focus. Instead, something almost opposite happened. The same ideas began appearing in different places. A watch collection became an example of portfolio capability. A suit became an example of how an object can remain unchanged while its environment changes. A watch strap showed how changing a boundary changes what we perceive as the object. Inherited possessions became a way to understand the loss of system context. A comparison between two watches exposed the danger of replacing a reference model with a reference object.

    The subjects changed. The method did not.

    What Surprised Me?

    The biggest surprise was that everyday observations did not merely illustrate ideas already developed in the papers. They generated new ideas.

    The distinction between a reference model and a reference object emerged through a discussion about whether a Seiko could function as a dress watch. A Rolex may be one implementation of a dress watch. It is not the definition of one. Comparing another watch directly with it risks turning its particular design choices into assessment criteria.

    The same mistake appears in transformation projects when the new system is expected to look and work like the old system. The old system becomes the reference object. And not even an obviously good one. It is the system that must be replaced.

    That simple watch example made the software problem easier to see: We call it transformation, but make resemblance to the past the acceptance criterion.

    The field note then produced a refinement that belongs back in the more formal work: A reference model describes required behavior and characteristics. A reference object shows one possible implementation of them. When the reference object replaces the reference model, one implementation quietly becomes the requirement. And QA verifies the implementation rather than the required behavior. The field notes have therefore become more than a way to communicate the theory.

    They have become a way to develop it.

    What Became Clearer?

    Several recurring patterns are becoming visible.

    The first is the separation of purpose from implementation. Requirements should describe required behavior, not merely reproduce an existing solution. Testing should verify behavior, not bind itself unnecessarily to implementation. Capability assessments should assess capabilities, not prescribe particular processes. Reference models should describe characteristics, behaviors and capabilities, not require resemblance to one preferred example.

    The second pattern is continuity of understanding. A system can survive while the reasons behind it disappear. Source code, documents and tickets may remain available, while the organization gradually loses the ability to explain why a business rule exists, why a trade-off was accepted or whether an unusual behavior is deliberate.

    This led to the idea of understanding debt: the accumulated gap between what the product embodies and what the organization can still explain with justified confidence.

    The third pattern concerns communication. Facts do not automatically form an argument. Sentences do not automatically form a thought. Documents do not automatically preserve knowledge. Structure, context and story are not decoration added after the “real work” is complete. They help make meaning reconstructable.

    The Field Notes Are Beginning to Reinforce One Another

    During the previous cycle, I noticed that the product-quality notes formed a chain. This time, the effect became broader. A note about documentation strengthens a note about understanding debt. A note about understanding debt strengthens the case for Product Continuity. A note about reference objects strengthens the distinction between capability and process. A note about storytelling explains why the more conceptual notes become easier to understand when they begin with watches, clothing or inherited possessions.

    Each note can still stand on its own. But later notes increasingly change how earlier ones are understood. The backlog is therefore no longer merely a queue of separate posts. It is becoming a body of work.

    What Changed in the Writing?

    The strongest recent notes often begin with something concrete and apparently insignificant. A watch. A suit. A photograph frame. An inherited object. A paragraph.

    The reader can follow the observation without knowing anything about assessment, Quality Management or transformation. Only after the principle has become visible does the note pivot toward software or organizations. That pivot is often where the note acquires its real meaning.

    Starting with transformation theory would require the reader to accept an abstraction. Starting with a watch allows the reader to discover the abstraction first. The professional problem is then judged by a principle the reader has already understood.

    This may be becoming the characteristic form of these field notes:

    Begin with an object.
    Discover a distinction.
    Follow it into another domain.
    End by revealing that the original subject was never really the subject.

    What Remains Unproven?

    The growing coherence is visible to me because I have followed every conversation and written every note. It is not yet clear whether it is equally visible to a reader encountering the posts individually.

    Several questions remain:

    • Can readers recognize the recurring method without being given a map?
    • Should related field notes be connected through synthesis pages or thematic collections?
    • Can the new concepts be incorporated into the assessment, Product Continuity and transformation papers without making those papers unnecessarily broad?
    • Do the everyday analogies clarify the professional ideas, or will some readers remember only the watches?
    • Do these distinctions improve actual assessment and transformation work?

    The theory is becoming richer. It must still become usable.

    What Comes Next?

    The next phase should probably combine continued exploration with more deliberate consolidation. The field notes can continue to capture new observations. There is no shortage of material.

    But several ideas now deserve to be carried back into the formal papers:

    • the distinction between reference models and reference objects;
    • the danger of confusing required behavior with one existing implementation;
    • understanding debt as the inability to explain what a product embodies;
    • documentation as the preservation of reconstructable meaning;
    • and field observations as a method for testing and refining conceptual models.

    The blog itself may also need stronger thematic routes through the material. The chronological stream shows when the ideas appeared. It does not necessarily show how they belong together.

    Conclusion

    After the first twenty posts, I discovered a writing process. After forty, I could see an emerging theory. After sixty, I am beginning to see the method connecting subjects that initially appeared unrelated.

    I thought I was collecting observations about quality, assessment, software, watches, clothing, writing and memory. Perhaps I was doing something else. Perhaps I was repeatedly asking the same questions:

    • What is this really for?
    • What characteristics matter?
    • What should remain stable when the implementation changes?
    • What knowledge must survive?
    • How can we make the reasoning visible enough for someone else to continue it?

    The individual field notes are becoming stronger. But their real strength may be that they are no longer entirely individual.

    .

  • Practice Note: The Danger of Reference Objects

    Is, let’s say, a Seiko Presage Sharp Edged suitable as a dress watch? One way to answer that question is to find an undisputed dress watch—perhaps a Rolex—and compare the Seiko against it. The Rolex may be thinner. More restrained. Its dial may be simpler, its case less assertive, its overall appearance more traditional. Conclusion: the Seiko is not a dress watch.

    But something has gone wrong. We did not assess whether the Seiko was suitable as a dress watch. We assessed whether it resembled the Rolex.

    The Rolex became a reference object.

    That matters because a Rolex is not the definition of a dress watch. It is one implementation of a dress watch. Its proportions, materials, dial layout and styling are particular design choices through which it realizes certain characteristics. By comparing the Seiko directly with the Rolex, we quietly turn those choices into assessment criteria.

    We are no longer asking:

    Does the Seiko possess the characteristics of a dress watch?

    We are asking:

    Does the Seiko implement those characteristics in the same way as the Rolex?

    A better approach is to define the typical characteristics of a dress watch.

    Perhaps:

    • restrained proportions;
    • an elegant case;
    • a leather strap;
    • limited complications;
    • an appearance that complements rather than dominates formal clothing;
    • and the ability to fit comfortably beneath a shirt cuff.

    Now we have something closer to a reference model.

    Against those characteristics, the answer becomes more interesting. The Seiko may not be the purest or most traditional dress watch. Its case and dial may be more expressive than the classical ideal. But it satisfies enough of the relevant characteristics that it can reasonably function as one. So yes: perhaps it is at least kind of a dress watch.

    The assessment changed because we stopped comparing to a reference object and started measuring against a reference model.

    Now turn to software. What are the requirements for the new system?

    “We don’t really have proper requirements. We don’t have the time, money or capability to define them. But the new system should look and work like the old system.”

    So the old system becomes the reference object. The same old system that must be replaced.

    Now, with considerably more money at stake, we make exactly the same mistake again. The old system is one implementation of the required business behavior. But instead of identifying that behavior, we copy the implementation. Its screens become requirements. Its workflows become requirements. Its terminology and data structures become requirements. Even its limitations, workarounds and historical accidents risk becoming requirements.

    Apparently, the old system is not good enough to keep—but its implementation is good enough to copy. The irony is difficult to miss.

    A transformation project begins because the current system is no longer suitable, then uses that same system as the model for the future. We call it transformation, but make resemblance to the past the acceptance criterion.

    Of course, the old system can still be useful. It may contain valuable examples, business terminology, accumulated knowledge and behaviors that must not be lost. But it should help us discover the reference model, not replace it.

    The real questions remain:

    • What must the new system enable?
    • Which outcomes must it support?
    • Which behaviors must remain possible?
    • Which characteristics must it possess?
    • Which constraints still matter?
    • Which parts of the old system were merely consequences of one particular implementation?

    A reference model describes the required behavior and characteristics.

    A reference object shows one possible implementation of them.

    When the reference object replaces the reference model, one implementation quietly becomes the requirement. And QA verifies the implementation rather than the required behavior.

  • Practice Note: The Story Behind the Facts

    For years I tried to make my reports correct. Then I tried to make them complete. Eventually, I realized I wanted something else: I wanted them to be skön att läsa—enjoyable to read. At first, that sounded almost inappropriate. A report is supposed to be factual, objective and complete. It isn’t supposed to compete with a novel. Or is it?

    Looking back over years of writing reports and giving presentations, I noticed a pattern. Of the many presentations I have delivered, those that received the strongest engagement were rarely the ones in which I tried hardest to explain every fact. They were the ones in which I unintentionally told a story. Not fiction. A real story.

    Those presentations felt different. I was more relaxed. I wasn’t constantly wondering whether I had forgotten a fact or whether someone would misunderstand a definition. I simply invited the audience to walk the same path that had led me to the insight. The audience seemed to enjoy that journey as much as I did.

    Only recently did I realize that the same principle applies to writing. Many technical reports feel like collections of facts. Everything is correct. Everything is complete. Yet reading them feels like climbing a staircase while carrying boxes. Every page asks the reader to do more work. What if the facts themselves are not the problem? What if the problem is that they have no journey to travel on?

    The reader keeps asking:

    “Why are you telling me this?”

    A story answers that question naturally.

    Ironically, storytelling may be one of the most effective ways to communicate technical ideas. Not because it simplifies them. But because it makes understanding feel effortless. A story does not replace facts. It gives the facts somewhere to live.

    Yet storytelling and style are often treated as luxuries for which professional work has no time.

    “Don’t waste my time. Just give me the facts.”

    But facts without a story do not eliminate the work of creating meaning. They merely leave that work to the reader. Making a report skön att läsa takes time. Framing a presentation as a story takes time.

    So does trying to understand a report whose writer decided that readability was a luxury.

    So does trying to make sense of a presentation that is merely a wall of facts.

  • 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.