Process
Short loops, visible progress.
Nothing here is secret. This is how every NEZ project runs, and you can hold us to it.
The loop
-
Week 1
Scope becomes a written plan
Architecture, milestones, and costs on paper you could take to any other studio.
-
Every day
Progress you can open
Work lands in your repository from day one. You read the commits, not a status report.
-
Every Friday
A demo of working software
Something clickable every week. If a week has nothing to show, we tell you why.
-
Every loop
Feedback becomes the plan
What you say in the demo is on the board Monday morning. Iteration is the process.
In the repo on day one
- 01 A repository you own, with CI and a deploy pipeline
- 02 A staging environment that ships on every merge
- 03 The written scope, visible in the repo, kept current
- 04 A direct channel to the engineers, no relay
Before anything launches
- 01 Migrations rehearsed against production-shaped data
- 02 A rollback path that has been executed, not described
- 03 Alerts wired to user symptoms before launch traffic
- 04 Error paths exercised: timeouts, retries, double submits
- 05 Load assumptions written down and tested
- 06 Accessibility checked against WCAG AA
Work we decline
Saying no is part of the job. We turn down:
- Scopes that need a bigger team than we can honestly staff
- AI features with no fallback for when the model is wrong
- Timelines that only work if the unglamorous parts are skipped