Feedback Isn’t the Problem. Decisions Are

Most “feedback” is just strategy turning up late. And possibly drunk.

It staggers into a review call, points at your homepage like it’s offended them personally, and says something unhelpful like:

“Can we make it feel more premium?”

Cheers. Really paints a picture. I’ll just pop “premium” into ChatGPT and see what happens.

Here’s the thing: when teams get stuck, it looks like a design or dev problem. The screens are changing. The copy is being rewritten. The tickets are multiplying like mould in a student flat.

But nine times out of ten, the work isn’t blocked by execution. It’s blocked by missing decisions.

And because nobody wants to admit “we haven’t decided what we’re doing”, we call it feedback instead. Which is a bit like calling a fire “ambience”.

The real problem hiding inside “feedback”

The scene is always similar.

You’ve got a decent first pass. Nothing revolutionary, but solid. Sensible structure, clear hierarchy, a story you can actually follow without needing a decoder ring.

On the call, people are nodding:

“Love it.”

Then, a day later, a message lands that feels like it was written mid-panic on a train:

“Sorry—had a chat with the board. Not sure it’s right. Can we explore something totally different?”

And suddenly, the team is back in the swamp. Not because the work was wrong. Because the decision wasn’t real.

The review wasn’t a review. It was a rehearsal for a decision someone else hadn’t made yet.

So you do another round. And another. The product starts to feel stitched together from competing opinions. The website says three different things depending on which paragraph you’re reading. Designers start second-guessing their taste. Developers start quietly resenting everyone. Founders start carrying the whole thing in their nervous system.

And when people are arguing about buttons like it’s a moral issue, it’s not because they care about buttons.

Buttons are just a safe place to have a bigger argument.

So you get comments like:

“Make it pop.” “This doesn’t feel like us.” “Not sure it’s premium enough.” “Can we move it up a bit?”

But what they mean is much harder, and much more important:

Who are we actually building for? What are we promising? What are we refusing to do right now? How are we measuring “good”? And who gets the final call when we can’t agree?

That’s not feedback. That’s strategy arriving late.

And if you keep treating it like a UI problem, you’ll pay for it the boring way: rework, delays, tired teams, and a brand or product that can’t hold a consistent shape.

This is why you’ll see teams “move fast” but never arrive anywhere. They’re sprinting in circles like a dog chasing a laser pointer.

Decision debt: the thing nobody budgets for

Everyone knows tech debt. Everyone nods gravely about it. Everyone pretends they’ll fix it “next sprint”.

But there’s another kind of debt that kills momentum even faster: decision debt.

Decision debt is what happens when the narrative isn’t locked, priorities aren’t explicit, success metrics are fuzzy, and decision-making is political. Nothing is properly decided, so everything gets re-decided. Weekly. In slightly different wording. With slightly different screenshots. With slightly more frustration.

It’s like trying to DJ a set where nobody agrees on the tempo. You can have the best tracks in the world, but if half the room wants 128 BPM and the other half wants “more emotional”, it’s going to sound like a car crash.

Decision debt doesn’t just slow you down. It makes your work feel weird. It turns brand into a costume you put on for the website, and product into a collection of features that don’t quite agree with each other.

The four locks that make shipping feel calm

When I come into teams as Dead Keen—often as a fractional CTO, Brand & Marketing Head, or the slightly unholy combination of both—I’m not there to bring “process for the sake of process”.

I’m there to get you unstuck by making decisions portable and executable.

There are four locks I look for. If even one is missing, “feedback” becomes a bin fire.

First: audience. Who is this actually for? Not “everyone who…”. Not “people who like…”. Not “SMEs and enterprises and start-ups and also my mate Dave”. A specific group of humans with a specific problem. And crucially, who it’s not for.

Second: promise. What are you promising? What change do you create? Not a list of features. Not “powered by”. Not “innovative”. A plain-English outcome someone can repeat in a Slack thread without sounding like they’ve been possessed by a pitch deck.

Third: no’s. What are we not doing? This is where most teams fall apart because they want momentum and optionality. Speed and unlimited exploration. You can’t have both. Boundaries aren’t negativity; they’re what stop delivery becoming a weekly referendum. They give the work something hard to bounce off, which makes everything clearer and faster.

Fourth: decider. Who decides when opinions clash? If the answer is “we all decide together”, congratulations: nobody decides. If the answer is “the loudest person in the meeting”, you’ll get decisions—but they’ll be unstable, expensive, and impossible to build around.

What changed at Voir when we stopped calling it “feedback”

I’m doing fractional CTO/CMO work with Voir, and it’s been a really clean demonstration of the “missing decisions dressed up as feedback” problem.

Not because Voir is chaotic—it’s not.

Because it’s a growing company with big ambitions, lots of moving parts, and the usual modern temptation to chase shiny ideas at 3am.

What helped most wasn’t a new tool. It was locking fundamentals so the team could move as one unit.

The brand stopped being a PDF and became something closer to an operating system. Not because it looked nice, but because it was repeatable. The team could walk the same walk and talk the same talk across sales calls, proposals, internal planning, and delivery. When the brand lives in behaviour—how you talk, how you decide, what you prioritise—feedback gets cleaner because the criteria are shared. Less “does it feel right?”. More “does this match what we’ve chosen to be?”.

We also put in a simple triage system for capturing major initiatives and forcing a genuinely useful question: is this on the critical path, or is it just a good idea that arrived loudly? That one distinction reduces decision debt massively, because it stops every thought becoming a project and every project becoming urgent.

Then there’s culture. Not the foosball-table version. The working version. A collaborative, creative approach across the business—not “make it look pretty”, but “think in the round”. Define the problem before sprinting at a solution. Debate trade-offs instead of defending ego. When a team shares a problem definition, decisions later feel frictionless because people aren’t arguing about taste. They’re agreeing what matters.

And finally, we binned the corporate voice. We speak normally. Honestly. No performative jargon just because the clients sometimes wear nicer shoes. Plain language makes plain decisions. Jargon makes everyone pretend they agree while quietly disagreeing.

The combined effect is boring in the best way: fewer surprise U-turns, less interpretation, more shipping. Not because people became saints. Because decision-making got real.

What Dead Keen actually does when I come in

People sometimes assume all of this is “ops”. It isn’t.

It’s brand, product, and engineering working together instead of taking turns to suffer.

1. I lock the narrative. Not a 90-slide manifesto—something usable. What are you selling, to whom, and why should they care, in words your team can actually say out loud without cringing.
2. Then I turn vibes into a brief with teeth. Decision criteria. Priorities. Non-goals. A shared understanding of what “done” means. This is where CTO brain and CMO brain shake hands without throwing a chair.
3. Then I build the system. Not one pretty screen that collapses when the product grows. A design system and component logic that makes the next six months cheaper, faster, and more consistent.
4. Then we ship the high-leverage surfaces: the homepage, onboarding, conversion flows, key screens—the places where trust is earned or lost. And because I can build as well as design, the loop is tight. Less telephone. More delivery.
5. And I leave a decision trail. Not bureaucracy. Memory. A simple place where decisions live, so you’re not rebuilding context from Slack archaeology and screenshots.

Because the real enemy isn’t complexity.

It’s amnesia.

This is also where the founder bottleneck shows up. If your team can’t move without you, you don’t have a team—you have a founder-shaped bottleneck. Usually because you’re carrying too much invisible translation work: interpreting customers, interpreting internal politics, interpreting what you meant last week, interpreting the board’s mood.

You can’t delegate your way out of that. You decide your way out of that.

Lock the narrative and criteria, and the team stops needing “founder context” for every tiny thing. You get your evenings back, which is an underrated business outcome, frankly.

A 20-minute reset you can steal today

Here’s the quick reset. Twenty minutes. Saves weeks.

Start with one sentence: what are we shipping?

Then pick two priorities you’re optimising for—two, not seven. Speed and clarity. Conversion and trust. Whatever’s true right now.

Then name what you’re not touching. Boundaries are what stop every conversation becoming a debate.

Then name the decider. Not a committee. A person.

When feedback comes in, translate it by asking: what outcome are you worried about? Is this a preference or a priority? What would “good” look like in a measurable way? And if we change this, what are we trading off?

You’ll be amazed how quickly “feedback” becomes buildable when you force it to grow up into a decision.

Calm isn’t a vibe. It’s a capability.

People romanticise chaos. Big swings. Big drama. “High stakes”.

In reality, chaos is just expensive indecision wearing a cool jacket. And the teams that ship consistently aren’t the teams with the most opinions.

They’re the teams with the clearest narrative, the simplest criteria, and the courage to decide—then stick to it.

So if your projects keep dragging, your brand feels inconsistent, and every review call turns into a debate about buttons…

You probably don’t need more feedback.

You need fewer, better decisions.

Which leads to the only question that matters:

Are you stuck because the work is hard… or because the decisions aren’t real?