Early feedback that means to save time is usually the feedback that costs the most of it. On why phases deserve a doorman, and why the leader has to make the pushback cheap to say.
We have a leadership habit where I work, and I put myself in the lineup: injecting build-phase feedback into discovery-phase work. I said so out loud to my design organization in our Monday warm-up this week, because saying things out loud is how I make myself accountable to them. The other half of the habit belongs to the teams, who absorb the feedback politely instead of saying the sentence that would save everyone a month. The sentence is short. We’re in discovery. We’re not ready for build feedback yet.
Almost nobody says it, and I understand why. When a senior executive looks at an early concept and starts asking about edge cases and error states, the room takes notes. Taking notes feels like respect. Pushing back feels like a career decision. So the discovery work mutates into premature build work, the team hardens a direction it hasn’t validated, and everyone wonders later why discovery keeps producing conclusions that feel pre-written.
I want to place the blame carefully, because the easy version of this piece scolds executives for having opinions, and executives are paid to have opinions. The problem is timing, and timing is a leadership discipline.
Build-phase feedback is a gift during build. During discovery it’s a frost, delivered by someone who genuinely believes they’re watering.
I keep calling this a habit rather than a process gap, and the difference matters. Process gaps get fixed with a template. Habits get fixed by people behaving differently in rooms, repeatedly, when it’s awkward, starting with the people who set the price of the pushback. If I want my teams to protect their phases, the protective sentence has to be cheap to say to me. That means when a designer tells me my note belongs to a later phase, I thank them and park it with a timestamp, in that order, with a straight face. Feedback deferred is feedback honored.
Two small proofs from my own week. A mobile designer had an information architecture question buried in a promising prototype, and the temptation was to lock the structure and ride the momentum. We spent one more day in the question instead. Discovery usually asks for a day, and the day is usually worth it. Separately, a team in quarterly planning was drifting toward building a complex capability in-house without anyone having decided to, so we set a build-versus-buy decision point with a date before discovery ends. Sunk-cost drift shouldn’t get to make our calls for us.
The honest risk: phases held too sacred become theater, and a team hiding in discovery is no better than a team rushed out of it. The goal is a permeable membrane with a doorman, and the doorman is the team, backed by leaders who reward the pushback instead of merely tolerating it.
The teachable part
Feedback offered too early hardens a direction before it’s been tested, doing the damage it meant to prevent. Keep phases sacred, park early notes for their right moment, and make the pushback cheap for your team to say.