How I Used Design to Fix a Broken Product Process

Process is one of those things people either overdo or avoid entirely. Do it right, and you create momentum—clarity, alignment, and breathing room for people to do their best work. Do it wrong, and you’ve built a bureaucracy: meetings for meetings, rituals without meaning, and a to-do list of that no one owns.

In a recent role, we hit that wall. We were fast, technically speaking—deploying features in tight cycles. But progress felt slow. Stakeholders were frustrated. Teams were reactive. Everyone was busy, yet somehow behind. The engineering-first approach was shipping code, but not value.

So I flipped the model: lead with design.

This wasn’t about process theater. It was about creating space. We started working one or more sprints ahead of engineering. That gave design room to explore, test, and clarify—not in a vacuum, but in dialogue with everyone else. We defined the problem before building the solution. Wireframes became the pivot point—not a deliverable, but a conversation tool. Ownership became visible. So did gaps.

I broke the workflow into four flexible stages:

1. Problem Framing – Understand, define, and align.

2. Wireframing – Sketch the system, not just the screen.

3. Feedback – Pull in engineers, PMs, and stakeholders early.

4. Handoff – Deliver clarity, not pretty pictures.

Nothing radical. Just clarity at the right moment.

The end-to-end product and design process—from defining strategy and scope to designing, aligning, and shipping—illustrates how product, design, and engineering collaborate through structured yet fluid hand-offs.

What surprised me most was how personal this work is. Process isn’t a template—it’s a negotiation. You’re not just organizing work; you’re figuring out where people thrive. A few things crystallized for me:

1. Wireframes aren’t placeholders. They’re narrative devices. They let you zoom in on the logic without being distracted by UI polish. Good ones tell a story: what matters, why it matters, and how it might work.

2. Abstraction tolerance varies wildly. Some people can follow a half-formed thought across ten slides. Others need structure on slide one. Good design makes both types feel at home.

3. Most process problems are communication problems. The friction isn’t in the flow—it’s in the ambiguity. And the job of design, more than anything, is to surface what’s unclear so it can be made clear.

Did this fix everything? No. But it gave us a rhythm. It replaced stress with structure. And it reminded everyone—myself included—that when we talk about process, we’re really talking about people.