Proof and possibility

Job titles can be a chicken-and-egg scenario. Sometimes you do the work long enough, consistently enough, and the title follows. A recognition of what now exists. Other times, the title comes first, signaling what needs to happen next. A bet placed on what the future requires.

The creation of a Chief Design Officer at Microsoft encompasses both. It lives at the intersection of proof and possibility, honoring what has been built while making a clear commitment to what must come next for us to meet this moment.

How it started

Twenty years ago, a product manager walked into my office and asked me to pick a color. It was my first week at Microsoft, and I had just finished a master’s degree in human-centered design.

I did not want to pick a color. I wanted to understand what we were building, who it was for, and what problem it solved. It felt like being asked to operate at the surface, and I had plenty of hubris at the time. I thought I needed to turn Microsoft into a design company.

Today, I see that moment very differently. Microsoft has always had a deep desire to build products that people use, rely on, and trust in the flow of their work, at an extraordinary scale. What has evolved is how deeply human-centered thinking is integrated into how those products are imagined, built, and connected.

That shift did not happen by layering design on top. It came from designers operating as builders and leaders, working in step with engineering, product, and research. Over time, a passionate and persistent design community pushed this work forward across products and business cycles.

Leadership is rarely about imposing a point of view or trying to change the nature of a company. It is about understanding it deeply enough to help move it closer to its full potential. That means continuously re-evaluating what we build, how it fits together, and whether it truly serves people. It means disrupting ourselves not for the sake of change, but in service of the people who depend on what we create.

How it’s going

As technology accelerates, the limiting factor is no longer our ability to build. Increasingly, technology can help create itself. The real question is what should be built to serve people. That is a human problem, and design sits at the center of answering it.

We saw what happens when that question is not clearly answered. Early in the Copilot rollout, teams moved quickly to integrate AI across products, but simply, attaching it to existing experiences isn’t enough to create value. At speed and at scale, it led to fragmentation and an experience that wasn’t cohesive. The lesson was not to slow down—it’s that we can now build the wrong things faster than ever before. The real challenge, and the opportunity, is learning to innovate with scale and intentionality.

Customers do not experience Microsoft as a collection of independent inventions. The tools they rely on are used across products, devices, and moments in their day. That experience must feel coherent, but coherence can no longer mean uniform or generic. What we are building now can adapt, reflect context, respond to individual needs, and evolve alongside how people work. That requires shared principles, shared intent, and a level of alignment that enables innovation at scale. Design becomes both more complex and more essential, and that is the work the CDO role exists to drive.

It also raises the bar for craft. The details matter more, not less—how something feels while being used, how intuitive it is, how naturally it fits into a person’s flow. Taste is not decoration. It is how care shows up in the product and how we create moments of quiet delight that build trust over time.

As the practice of design evolves, UX practitioners are becoming more technical, working across the full stack of the experience. From interface and interaction design to the intelligence underneath, human-centered thinking has to be present at every layer.

Where design is headed next

At their best, titles create clarity. They signal what matters and what an organization is committed to.

The Chief Design Officer role exists because of the complexity of the challenge ahead. It spans boundaries, connecting design, engineering, and product to ensure that what we build comes together as a unified, human-centered experience. It exists to reduce fragmentation, increase alignment, and make innovation at scale real across the company.

It also reflects a broader shift in how decisions get made about what to build, for whom, and why it matters. Elevating design leadership ensures those decisions are connected, deliberate, and grounded in real human needs.

Not long ago, Microsoft had no design executives at all. Just as we created the first corporate vice president and partner roles in design, this is the next step. A recognition of the craft, community, and leadership that made it possible, it establishes design as a permanent and essential voice in how Microsoft serves customers and competes in the world.

As we continue this work, we hold two truths. Our feet remain grounded in the realities of today’s products and customers, while we also develop a clear point of view on where things are going. The hardest work sits in between, where uncertainty can easily lead to fragmentation. Our responsibility is to create clarity and move forward deliberately.

I am proud and humbled that years of helping drive Microsoft 365’s business and customer success led to this moment. The work that brought us here was real, but the work ahead is what the title is for. Technology is moving faster than people are ready to move with it. Design helps bridge that gap by living in the space between where customers are today and the richness of what’s possible tomorrow.

That’s the commitment, and I couldn’t be more excited.