Why your team being stuck is a design problem

There’s a specific kind of stuck that kills startups. Not the dramatic kind where things blow up. The quiet kind where months go by, the team is busy, everyone looks productive, but there’s nothing to show for it.

I walked into exactly that on an insurance project. The team had been at it for months. Smart people, good intentions, real market need. But every conversation circled back to the same debate. How should the ID scan look? What if the user does this instead of that?

The designers were working at full fidelity before anyone had tested a single assumption. Pixel-perfect screens for flows nobody had validated. It looked impressive in Figma. But it was all built on guesswork.

Analysis paralysis is more common than most founders want to admit.

---

When I came in, I didn’t ask to see the designs. I started with a low fidelity approach – total collaboration, focused only on the most important requirements.

The graphic designers were not happy.

We ran a five-day design sprint. No high fidelity, no perfecting, no rabbit holes. We started with paper and finished in Balsamiq – rough boxes, basic interactions, just enough to put in front of a real user and learn something.

By Friday we had our first test. And we got it completely wrong.

The flow made sense to us but confused every single user who tested it. We didn’t even get to the ID scan. The team had assumed users understood industry terms like “third party” – they didn’t. Users got stuck way before the clever stuff, somewhere nobody had thought to question.

That failure cost us a couple of hours in design time. If we’d built it out properly first, it could have cost months – maybe millions if it had carried on for a year.

---

Here’s what most founders miss about failure: a fast failure is not a setback, it’s data. The goal of a sprint isn’t to get it right on the first try. It’s to find out what’s wrong before you’ve committed serious time and money to it.

We went back the following week with a new approach based on what we’d learned. The second prototype tested better. The third better still. A month later, they shipped something real.

The entire project changed not because we had better designers or more budget. It changed because we stopped trying to perfect something nobody had tested yet.

---

If your team has been building for months and you’re not sure what you actually have, that’s a signal worth paying attention to. The problem usually isn’t talent or effort. It’s the sequence. Perfecting before testing, designing before validating, debating before learning.

A design sprint doesn’t solve everything. But it breaks the cycle. It forces a decision, creates something tangible, and puts it in front of real people fast enough to actually change direction before it’s too late.

Speed plus honest feedback beats perfection every time.

---

Pink Cowboy is Wouter Kirstein’s design studio, focused on helping founders move fast, test smart, and build on solid foundations.