IBM Design Thinking

I still like that phrase because it sounds smaller than it is. Packaging sounds like surface. It sounds like layout, naming, a better diagram, maybe a friendlier website. And yes, it was partly all of that. But packaging is also how an idea survives contact with people who didn’t help make it.

We found three problems underneath it.

That sentence was a gift. Slightly painful, but useful. The useful ones often are.

That sounds impossibly broad. It almost sounds like the kind of thing you write before reality has had its say. But I don’t think we meant it as a slogan. I think we meant it as a correction.

Design thinking gets mushy when people talk about empathy as if the goal is to feel good about themselves. The point wasn’t to make teams nicer. The point was to help them make better decisions because they understood the people those decisions would affect.

My title was Design Principal and Project Director, but the role was less tidy than that. I was trying to keep the idea intact while it moved through writing, design, code, animation, stakeholder review, publishing constraints, and the natural entropy of a large organization. That’s where intent usually gets lost.

A sentence gets softened. A visual decision becomes decoration. A developer gets handed a design that can’t be built cleanly. Everyone makes a reasonable compromise, and somehow the thing that ships no longer resembles the thing you meant.

I directed the content tone so the reader could focus on intent instead of parsing the writing. I directed Perception, a fifteen-second animation that had to explain the heart of the concept quickly. Fifteen seconds is a rude constraint. Useful, though. You can’t hide a muddy idea inside fifteen seconds.

I co-created the Loop. And I pushed for the larger story behind the framework, because IBM Design Thinking couldn’t survive as a collection of activities. If people were going to carry it, they needed a storyline they could retell.

I still believe visual design is at its best when it changes what someone can understand. Beauty matters, but beauty without usefulness is a very expensive fog machine.

The site was part of the method, too. A framework about continuous improvement couldn’t arrive as a static PDF or a brittle website built through a long chain of handoffs; we would have contradicted ourselves before anyone read a word. So we built our own content system on GitHub and Gulp, kept designers and developers close enough that the visual system could be expressed in code, and delivered the first Bluemix app running inside the ibm.com framework. A method about better work should arrive as better work.

The sentence we wrote was simple: IBM Design Thinking is what happens between the problem and the solution. That became the handle.

The Loop looks obvious now. Observe. Reflect. Make. Three words. A continuous line. A way of moving from the world, into sensemaking, into action, and back again. It didn’t feel obvious while we were making it.

We sketched hundreds of versions. Probably thousands, if I’m being honest about the walls and tables and notebooks involved. We tested the model with people all over the studio, with sponsor users, with stakeholders, with people seeing it for the first time. The question was always the same: do they get it fast enough to use it? Not admire it. Not decode it. Use it.

The previous mental model had too much phase energy in it. It made the work feel like something you moved through and completed. We wanted a model that made learning feel continuous. Observe meant staying open to what people actually do, not what the team wishes they did. Reflect meant making sense before rushing toward certainty. Make meant giving the idea a form early enough that reality could push back. Then around again.

The first major loop of the work was a twelve-week collaboration with the Dun Laoghaire Institute of Art, Design and Technology in Dublin: four of their strongest interns, their advisory professors, and one of my best young designers. Large organizations develop private dialects. Sometimes you need people close enough to understand the assignment and far enough away to tell you when your words have started folding in on themselves.

The Loop also made “fail fast, learn well” feel less like a poster and more like a way of working. Most organizations say they like early failure. Many quietly punish it. The Loop gave us a way to make learning feel less like an admission of weakness and more like the motion of the work itself. That was the behavior change we were after.

The response was strong, internally and externally. People noticed that IBM had opened up its design thinking practice. They noticed the clarity. They noticed that IBM was treating design as a business driver, not a craft service parked at the edge of the process.

Teams using the practice cut initial design time by 75%, development and testing by 33%, and design defects in half. Products reached market twice as fast.

Those responses mattered. But the thing I cared about most was quieter. The method became easier to carry. Easier to remember. Easier to teach. Easier to use when no one from the original team was in the room.

The Loop gave people a mental model they could remember. The scope expanded beyond software product teams. The website gave the method a home that could actually evolve. I don’t think of that work as making design thinking simpler. That sells it short. I think of it as making the intent more durable.

This work is older now, but I trust the lesson more than I did when we made it.

AI has made the distance between an idea and an artifact almost uncomfortably short. A screen can show up before the team understands the behavior it’s trying to support. A strategy can sound finished before anyone has agreed on the problem. A prototype can feel real enough to stop the harder conversation from happening. That is useful, obviously. I use it every day. It’s also a very efficient way to get lost.

The Loop still matters because it slows down the part that shouldn’t be automated away. Look at what’s actually happening. Make sense of it. Give the idea form. Put it back in front of the world and see what it does there.

The tools changed. The responsibility didn’t. Someone still has to know what the work means.