dax says cheap builds make it easier to reject work

dax posted a small observation about how his team works now. One of the best details of working these days, he says, is that you do not have to feel as bad about rejecting something someone built.

dax

@thdxr

X

feels like our team is able to be more honest with each other

His reasoning is the part worth sitting with. Before, you would feel bad because they worked hard on it, and that added friction. Now the friction is lower, and in his words the team is able to be more honest with each other.

Why that lands

This is one founder's read on his own team, not a study. But it names something most people who have run a code review have felt and never said out loud. When a teammate spends three days on an approach, the honest answer and the kind answer stop being the same answer. You soften it. You merge it with notes. You tell yourself it is close enough, and the thing ships because somebody suffered for it, not because it was right.

Take the suffering out and the calculation changes. If the work was cheap to produce, saying no costs nothing but a rerun. Nobody has to absorb the rejection personally, because the hours that would have been wounded were never spent.

The business read

The story here is not faster building, it is that the standard you apply to the output can go up. Teams quietly carry a lot of mediocre work that survived because rejecting it would have been socially expensive. That protection is gone when the cost of the attempt approaches zero.

dax does not claim the quality of the work improved, only the honesty of the conversation around it. Those are different things, and it is worth keeping them apart. A team that rejects more freely could also churn through more half-finished attempts and call it progress.

Still, if you run a team of any size, it is a cheap thing to test. Watch the next review where the answer should be no and see whether anyone says it.