Why our clients get the same task board we do.
Not a client-facing dashboard. Not a filtered view. The same board, with the same cards, including the ones that are late.
The standard arrangement in software services is that the client gets a status report and the team gets the truth. The report is assembled the night before the call, the percentages are generous, and everyone leaves the meeting feeling roughly informed. Then at some point near the end of the project the two versions collide, and the conversation becomes difficult in a way it did not need to be.
We gave up on that arrangement. Every engagement runs on a live board the client can open whenever they like, showing exactly what our engineers see.
What people expect to go wrong
When we describe this, the first reaction is usually some version of: won't they panic? Won't they micromanage? Won't they see a card sitting in review for four days and assume the worst?
In practice, no — and the reason is worth understanding. Anxiety in a client relationship is almost never caused by bad news. It is caused by the gap between updates, which the client fills with speculation. A board that says “this is stuck, here is why” produces less worry than a silence that says nothing at all.
Clients do not lose confidence because something went wrong. They lose it because they found out late.
What actually changes
- Scope conversations stop being arguments. When a new request arrives, we do not debate whether it fits — we put the card on the board and everyone can see what it displaces.
- Status meetings shrink or disappear. There is nothing to report that is not already visible, so the time goes to decisions instead.
- Blockers get resolved in hours instead of weeks. A card marked “waiting on client content” that the client can see is a card that gets unblocked.
- Estimates get better, on both sides. Watching cards move gives a client a real feel for the pace of the work, which is the only cure for the belief that everything should take three days.
What it demands of us
This only works if the board is honest, and an honest board is uncomfortable. It shows the ticket that has been reopened twice. It shows the week where velocity dropped because two people were sick. It shows, in writing, the thing we underestimated.
So the discipline is not technical, it is cultural: nobody gets to quietly rename a card to make a week look better. The moment the board becomes a performance, it is worth less than the status report it replaced, because now it is a lie that updates in real time.
The underlying bet
We think the reason most software relationships go bad is not incompetence. It is asymmetry — one side knows what is happening and the other is guessing. Removing the asymmetry costs us the comfort of managing the narrative. What we get back is a client who trusts the good news, because they have seen us report the bad news first.