For most of the twentieth century, design meant objects. A chair, a lamp, a car, a building. The designer's role was to give form to things, and the quality of the work was judged by the quality of the things produced. This was a coherent framework, and it produced extraordinary work. But it was also incomplete, because it treated the object as the endpoint rather than as one element within a much larger system.

The shift that has defined my practice over twenty-five years is the recognition that the object is never the point. The object is a vehicle. What it carries — meaning, utility, experience, identity — is determined not by the object in isolation but by the context in which it exists. The same chair in a hospital waiting room and in a private residence is not the same chair. The same interface on a trading floor and on a kitchen counter is not the same interface. The context changes everything about how the object is encountered, evaluated, and valued. And yet most design processes still begin and end with the object itself, as if context were someone else's problem.

This is a limitation that becomes visible at the enterprise level. A product company that treats design as the discipline of making things well will make things well. But it will also find that the quality of the individual product does not always translate into market success, because the product exists within an ecosystem of touchpoints, relationships, and expectations that the object-focused approach does not address. The product might be excellent. The packaging might undermine it. The retail environment might contradict it. The customer service experience might erode the trust the product worked to build. Each of these elements lives in the context surrounding the object, and if that context is not designed with the same intention as the object itself, the whole is less than the sum of its parts.

The evolution from object-centered design to context-centered design is not a rejection of craft. The object still matters. Materials still matter. Form still matter. The difference is that these things are now understood as instruments of a larger intent rather than as ends in themselves. The question shifts from "how do we make this product as good as it can be" to "what experience should this product create, and what must be true about everything surrounding it for that experience to be realized."

This is a more demanding question, and it requires a broader kind of expertise. A designer working at the level of context must understand not only form and material but also market dynamics, customer behavior, organizational structure, and competitive positioning. They must be able to hold the relationship between the product and its environment in mind simultaneously, making decisions about one in service of the other. This is not a skill that traditional design education emphasizes, which is why so many organizations struggle to find designers who can operate at this level.

The practical implications for business are significant. When design is understood as an object discipline, it is naturally positioned downstream. The strategy is set. The product is specified. The designer is asked to execute within those parameters. This is a comfortable arrangement for most organizations because it contains the designer's influence within a well-defined scope. It is also a profoundly limiting one, because the most consequential design decisions — what to make, for whom, and why — have already been made by the time the designer enters the process.

When design is understood as a context discipline, its natural position shifts upstream. The designer is involved in the strategic conversation because the strategic conversation is, at its core, a conversation about what experience the company wants to create in the market and what must be true across every function to deliver it. This is a fundamentally different role, and it produces fundamentally different outcomes. The products are not just well-made. They are coherent with everything around them. The customer experiences not a product but a world, one that feels intentional and considered at every point of contact.

I have worked with companies on both sides of this divide. The difference in outcomes is striking and consistent. Companies that treat design as an object discipline produce good products that compete on features and price. Companies that treat design as a context discipline produce products that create categories and command loyalty. The difference is not in the talent of the designers. It is in where design sits in the organization and what questions it is asked to answer.

The evolution of design thinking from objects to context mirrors a broader evolution in how markets work. In an era of abundant choice, the product alone is rarely sufficient to win. The customer is evaluating not just what they are buying but the entire experience of buying it, owning it, and interacting with the company that made it. Every touchpoint is part of the assessment. A product that is excellent in isolation but exists within an incoherent context will lose to a product that is good and exists within a coherent one. This is not a commentary on the unfairness of markets. It is a description of how decisions are actually made.

For leaders, the practical question is whether design is positioned in your organization to address context or only objects. If your designers are involved only after the strategic decisions have been made, you are using design at a fraction of its potential. If your designers are in the room when the questions of what to build, for whom, and why are being discussed, you are using design as a strategic capability. The gap between these two positions is not a matter of design talent. It is a matter of organizational design.

The most important design decision a company makes is not about the product. It is about where design lives in the organization and what it is empowered to influence. Get that decision right, and the products will follow.