When Design Thinks at Enterprise Scale: How Human-Centred Approaches Deliver Real Business Outcomes

I am going to be a little direct here, and I will own that upfront. One thing I have come to believe, through experience rather than theory, is that I tend to see opportunity where others see blockers. I realise how that sounds. It sounds like the kind of thing someone puts on a motivational poster. Hear me out before you decide.

What I mean is something more specific and more earned. Over a career working at the intersection of product, design, and enterprise strategy, I have developed a way of looking at complex, messy, high-stakes problems that consistently surfaces paths forward that were not immediately obvious. And a significant part of that comes from one habit: staying genuinely curious about the people the problem actually belongs to.

This is not innate. It was shaped by specific experiences. One of them started in Austin, Texas, on a hot summer day, in a building that took design very seriously indeed.

Austin, IBM, and a Lobby Full of Executives Doing Role Play

Some years ago I was part of a team working on a new enterprise security product at IBM. The product was ambitious, technically sophisticated, and genuinely aimed at solving a hard problem for large organisations dealing with increasingly complex cyber threats. The potential market was significant. The opportunity was real.

Before we wrote a single line of production code, before we locked down a single feature, we were at IBM Design's headquarters in Austin to put our thinking in front of real scrutiny. IBM Design Thinking was not a casual exercise there. It was the operating model.

What I remember most vividly is the session where our team, a group of executives, product leaders, designers, and engineers, ran a role play exercise to communicate our product concept and demonstrate how it differentiated from everything else in the market. We were not presenting slides. We were inhabiting the problem space. Playing out the scenarios our users would face. Making the abstract concrete in a way that forced us to confront where our thinking was solid and where it was not.

It sounds unconventional for a room full of senior people. It was also one of the most clarifying exercises I have been through. By the end of that session, we knew which parts of our concept genuinely held up and which parts we had been too comfortable about. That clarity was worth more than months of internal review.

The Research That Actually Mattered

Before that session, before any of the formal design and development work began, I spent time directly with the people we were building for. IBM called them Sponsor Users: industry-leading CISOs and security practitioners at organisations that would be potential future customers, engaged under NDA, willing to give us honest and unfiltered feedback on the problems they were actually trying to solve.

This was not a focus group. It was not a survey. It was direct, substantive conversation with highly experienced practitioners about what kept them up at night, what the existing tools were getting wrong, and what a genuinely useful solution would need to do.

What I heard in those conversations shaped the product in ways that no amount of internal analysis could have. The problems they described were real and specific. The workarounds they had built were ingenious and revealing. The gap between what the market was offering and what they actually needed was, in places, substantial.

First-hand insight from the people you are designing for is not a nice-to-have. It is the thing that separates products that resonate from products that get used once and abandoned. I came out of those conversations with a sharper understanding of the problem than I had going in, and that sharpness drove every design decision that followed.

What the Numbers Confirm

McKinsey's research across 300 publicly listed companies over five years found that the top quartile of design-led organisations outperformed peers by 32% in revenue growth and 56% in total shareholder returns. The study covered medical technology, consumer goods, and retail banking, and the pattern held consistently across all three.

What distinguished the leading companies was not design as a separate department. It was design thinking embedded into how decisions get made: continuous iteration with end users, cross-functional integration of design and business teams, and leadership that treated user experience outcomes with the same rigour as financial outcomes.

The product we built in that period went on to win industry recognition. I am careful not to overclaim, because products like that are team efforts and the contributions are many. But I do believe the early research rigour and the design process we applied were foundational to the outcome. Starting with genuine user insight, testing thinking under real scrutiny, and iterating based on evidence rather than assumption, these things matter.

Why This Still Applies in 2026

That experience was some years ago now. The technology has changed. The tools have changed. The pace of product development has changed dramatically. What has not changed is the underlying dynamic: organisations that genuinely understand the people they are designing for build better products than organisations that assume they do.

The frameworks I developed then, around direct user research before solution definition, cross-functional collaboration that brings design and engineering together from day one, and structured testing of concepts before significant investment, have stayed with me through every role since. I apply them whether I am working on a consumer product or an enterprise platform, a new product launch or a large-scale transformation programme.

Speed to innovation and time to value in product development are still fundamentally dependent on making good decisions early. And the best input to early decisions is still genuine insight from the people the product is for. No amount of internal analysis, competitive benchmarking, or executive intuition fully replaces that.

Design thinking has been workshopped to death, used as a corporate box-ticking exercise, and drained of meaning by overuse. Used properly, with genuine intent and real access to users, it remains one of the most powerful approaches available for solving hard problems. The Austin experience taught me that in a way I have not forgotten.