Why I think you should talk to users before a rewrite

White-roofed houses and moored boats around a shallow turquoise harbour in Bermuda under drifting clouds

Every rewrite I have seen started with the team's understanding of the old system, what it does, which parts matter, which parts can go. The team is usually right about most of it. The part it is wrong about hurts, because a rewrite reproduces what the team understands and silently drops the rest.

What the users know

The people who use a system every day carry a model of it that no document has. They know the export pasted into a spreadsheet every Friday that drives a decision nobody in engineering has heard of. They know the fields have to be in that order because the form is filled in while someone is on the phone, reading from a card.

None of that reads as a requirement in the code. It is there as an accident, a field order someone chose in 2015, a report that was a favor, and the rewrite plan reads those as things to clean up.

Why asking is cheap

A rewrite is the most expensive thing an engineering team does. A conversation with a user is one of the cheapest, and that asymmetry is the whole argument. An hour with five people who use the system will not tell the team everything, but it will almost always turn up the one thing that would otherwise be discovered in production by the person it broke. So the conversations belong before the plan is set, not after the design review.

What I ask

I do not ask what they want, because the answer is a feature list and I cannot tell which items matter. I ask what they do. I ask what they would miss if this screen were gone tomorrow, and the answers are things the new system must do whether or not anyone on the team thought of them. And I ask what they hate, because that is often what the team is about to faithfully reproduce, on the theory that the old behavior is the spec.

What I do with the answers

The answers go into the plan as requirements with the user's name attached, so that when a design review proposes dropping the Friday export, there is a person to talk to rather than a guess to argue about. Some change the order, because a workflow the team thought minor turns out to be the one that cannot be down for a week. And the most valuable kind says the user does not need the thing the team was about to rebuild at all, and a chunk of the rewrite disappears.

The component library version

This applies with force to component libraries, where the users are other engineers. A library rewrite that does not ask the teams using it will discover, after release, every prop they relied on and every escape hatch they quietly built. There is no excuse for not asking.

A rewrite is a bet that the team understands the system well enough to build it again. I think the bet is far safer after an afternoon of listening to the people who already live in it.

Photo source: https://photos.robertstowe.com/bermuda