Five-Day Builds: What to Do When Clients Go Quiet

Résumé

Pixel shares a day-three lesson from a five-day logistics tool build: keep working on independent features while parking decisions that depend on the client’s answer. The example shows how handling an unanswered question about driver reassignment can prevent costly schema rewrites and protect the deadline.

DEV Community

Day three of a five-day build, and the client has gone quiet

A five-day build has one awkward property: it is short enough that a single unanswered question can eat a fifth of the budget, and long enough that nobody thinks of it as urgent when it happens. Last month it happened on day three. The build was an internal tool for a logistics company — a small admin panel where dispatchers replace a spreadsheet that three people were fighting over. Days one and two went fine. Then a question came up that only the client could answer: when a driver is reassigned mid-route, does the old assignment stay in the history or get overwritten? It sounds like a detail. It decides the database schema, the screen, and whether last month's reports still add up. I sent the question at 10 a.m. Seoul time, which is the previous evening for them. No reply that day. No reply the next morning. What I do not do with the silence Two tempting options, both wrong. Guess and keep building. Cheaper in the moment. But a guess in the schema is not a guess you can throw away — by day five it is in the seed data, the reports, and the demo the client clicks through. You end up paying for the rewrite out of a fixed price that assumed no rewrites. Stop and wait. Reversed, but the same bill. The clock on a five-day build is not the studio's clock, it is the calendar the client already told their own team about, and it does not pause because a message went unanswered. So the build keeps moving on everything that does not depend on the answer. On this project that was most of the app: the dispatcher list, the search, the route assignment screen with the field left undecided, permissions, the export. What gets parked is the specific decision and anything downstream of it — in this case one screen and one report. The three-part message I send instead of a reminder Sending "any update?" every six hours is how a builder becomes noise, and noise gets ignored faster each time. What worked, twice now, is one message that does three things: Names the cost of the silence, in their units. Not "I'm blocked", but "this one answer decides whether the monthly report counts a reassigned route once or twice; if it stays open past Thursday, the first version ships with reassignment hidden behind a flag." Now it is a business decision with a date, not a developer waiting. Offers a default I can live with. "If I hear nothing by Thursday noon, I will keep the old assignment in history and add reassignment as a second step." A default turns silence into an answer, and it is reversible if it is written down before it happens. Keeps one alternative alive. "If you would rather drop the reassignment feature entirely for now, say so and I will hand over the rest on Friday." Clients go quiet for two reasons: they are busy, or they are quietly reconsidering the project. Giving the smaller version a name makes the second reason sayable. That message went out on day three at 11 p.m. Seoul time, on purpose — it landed at the start of their working day, at the top of the inbox, instead of during their afternoon. The part that is not about the client Before blaming the silence, check whether the question was answerable. "How should reassignment work?" is not a question, it is homework. "Should the history show both assignments, or only the current one?" can be answered by someone reading a phone in a corridor. That is a scoping job, and it belongs on day one, not day three. A free scope call that ends with a written page — who signs in, who pays, what happens when two people edit the same record, where the data lives, who owns the accounts — is what keeps day three quiet. Not because every question is gone, but because the remaining questions are small enough that a default is honest. Two more things help when the build is this short: One channel, one thread. Not email plus WhatsApp plus a shared doc. The question, the answer, and the default all live in the same place, or day five becomes an archaeology project. A daily two-line note. What moved, what i...
Five-Day Builds: What to Do When Clients Go Quiet
Powered by Readybot.io

Les dernières actus de Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …