Transcript
A (0:02)
This is an audio version of the brief. The monthly dispatch from DesignBetter Microscopes and Telescopes A friend and former colleague called me recently to catch up and get my perspective on an important question. See, he leads a product team at a major tech company, and the design team had just been moved under him. He's an exceptional product thinker with a sharp grasp of engineering systems and shipping processes. But managing designers? That's definitely new territory. Where should design really fit into our workflow? He asked me. What struck me most was that he asked at all. Too often, when design moves under product in a reorg, it becomes a service function, something to be brought in after the big decisions are made to polish the edges, you know, add the visuals and make things look good. And that, of course, sells the value of design way short. And my friend sensed it. He didn't want design to just support the work of engineers. He wanted it to play a part in shaping the product. That's the way it should work. So I shared what I've seen in organizations where product and design truly thrive together. It starts with recognizing that engineers and designers bring fundamentally different perspectives to the table. Engineers are microscopes, designers are telescopes. Engineers tend to be focused on the here and now. They're driven by efficiency, elegant problem solving, maintaining code and building resilient systems. They often operate on short feedback loops. They're fixing bugs, optimizing performance, closing tickets. It's urgent, high stakes work, especially when you have to stay late on a Friday night to fix something urgent. You need that tight focus when the fire alarm is going off. Designers, on the other hand, are more tuned to experience patterns and consistency. They think about how interfaces feel over time, how a brand holds together across surfaces, how a customer moves through the experience, not just in one moment, but across their whole journey. Their work often lives in ambiguity, requiring exploration and reframing before landing on a solution. These different perspectives aren't in conflict, they're actually quite complementary. I told my friend to think of engineers as microscopes and designers as telescopes. Engineers zoom in to understand near term issues because precision and speed matter when you're shipping to millions of users. Designers, on the other hand, zoom out to see the broader ecosystem because coherence matters when you're building something people want to come back to again and again. There are different time horizons, but here's the catch. Most companies dramatically over index on the microscope. They fixate on short term goals, quarterly okrs, Sprint velocities, shipping the next feature. It's like reading a newspaper through a straw. You get sharp details, but you miss the full story. There's real danger to this singular, myopic approach. We lose our bearings when we stop looking to the horizon, marty Kagan of Silicon Valley Product Group once told us. Most teams are what I call feature teams. They're just there to design and build features that the executives usually are the ones coming up with. We need both instruments, the microscope and the telescope. We need to look down at what's right in front of us, but we also need to look up at what's coming over the horizon. When organizations treat design as a strategic partner, instead of just doing finishing touches, they unlock a different kind of innovation. Design helps you see around corners, imagine new possibilities, and build for the future, not just for the next release. And the data backs this up. McKinsey's business value of Design report found that companies that tightly integrate design into their strategy and operations grow revenues and shareholder returns at nearly twice the rate of their peers. Build the right thing, don't just build the thing right. When design and engineering are integrated early at the problem definition stage, teams are far more likely to build the right thing, not just build the thing right. I encouraged my friend to lean into the superpowers of both sides of the team and make them both aware of how they contribute to celebrate the short term bug squashing brilliance of engineering while also creating space for the long term horizon scanning thinking that design brings. Because a future belongs to leaders who can do both Zoom in and zoom out, microscope and telescope working together. And here's the thing. Even if you're not a design leader, understanding how design and engineering relate and how their perspectives complement one another is still a powerful thing to know. It gives you the language to advocate for design. It helps you bridge disciplines that often operate in silos, and it enables you to guide your team or organization towards better decisions and better products. When you recognize the unique strengths that designers bring, not just as pixel polishers but as systems thinkers, pattern recognizers, and experienced architects, you can start to unlock the full potential of design. That's when design starts driving business outcomes, not just interface outcomes. It's not about where design reports on the org chart. It's about where it shows up in the conversation and who's helping it get there.