I counted the sections on one page of a workforce dashboard I run. Twenty, stacked top to bottom. The same candidate was drawn more than ten different ways on that one page. Two different modals could edit the same record, and they disagreed about what the record was. The daily loop, the thing staff actually did every morning, was split across three surfaces that were not even next to each other. Everyone knew the page was bad. And I could not take it down to fix it, because people used it to do their jobs.
How a page gets like that
Nobody designs a page with twenty sections. You design a page with three, and then you add one. Each addition is reasonable. Each one is a ten-minute change that solves a real request from a real person. The twentieth section went in for the same good reason as the fourth. That is the trap. A page like this is not the product of bad decisions. It is the product of seventeen good ones.
What broke: That page grew on my watch. I approved most of those sections myself, one at a time, and every one of them looked harmless going in. The mess was not inherited. I built it.
So the page needed a rewrite. But rewriting a live surface is one of the most dangerous things you can do in software. The graveyard is full of v2s that shipped half finished, quietly broke something the old version did, and got rolled back in a panic. Every operator has seen one. So the interesting question is not how to build the new page. It is how to earn the right to ship it.
