Studio · · 2 min read
How a project week runs at NEZ
NEZ Engineering
Agencies love to describe their process in diagrams with arrows and Greek letters. Ours fits in a week, so we will just describe the week.
Monday is for deciding. We look at what Friday’s demo taught us, what you told us afterward, and what the written plan says comes next. The outcome is small and concrete: the list of things that will demonstrably work by Friday. If something needs a decision from you, Monday is when we ask, in writing, with a recommendation attached.
Tuesday to Thursday is for building, in the open. The work lands in your repository as it happens. Not a fork on our infrastructure, not a zip at the end of the month. Yours. Every commit message is written to be read by a human, and a staging deploy updates on every merge, so if you are curious on Wednesday at 4 p.m., you do not have to ask anyone; you click the link.
That visibility is not a courtesy. It changes behavior on both sides. We cannot hide a slow week behind a status call, and you cannot discover in month three that the architecture was not what you expected. Problems surface when they are a day old, which is when they are cheap.
Friday is for proof. The demo is working software, clicked through live, including the parts that do not work yet. A slide describing progress is not progress. If a week genuinely has nothing to show, which happens in deep infrastructure work, we say exactly that and show the evidence of the digging instead: the migration plan, the load test results, the failed approaches and why.
Then the loop closes. What you say in the demo becomes Monday’s input. Not a ticket in a backlog to be groomed someday. The next Monday, the actual one, three days later.
There are two things deliberately missing from this week. There is no status meeting, because the repository and the staging link answer status questions better than a call. And there is no big reveal, because reveals are where agency projects go to die. By the time anything of ours matters, you have already seen it four Fridays in a row.
None of this is proprietary. Any team could work this way, and the good ones do. We publish it because it is a commitment you can hold us to, starting with the first week.