Shipping weekly is not a philosophy. It is a set of habits. The philosophy — fast feedback, small batches, continuous improvement — is easy to agree with. The habits are where teams fall apart.
We have shipped production code every week at XenoLabs for the better part of four years. Here is the cadence that makes it possible.
Monday: alignment
Thirty minutes. What shipped last week? What is the single most important thing to ship this week? What might block us? Anything longer than thirty minutes is a symptom that the previous week's work was not properly closed out.
Wednesday: checkpoint
Fifteen minutes. Are we on track? If not, what gets cut? We do not slip the deadline — we reduce scope. This decision point mid-week prevents the Friday panic that is the enemy of quality.
Friday: demo and deploy
We demo to the client every Friday. Not a status update — a working demo. Then we deploy. The demo keeps us honest about what "done" means. The deploy keeps us honest about what "stable" means.
What makes it sustainable
Two things: scope discipline and a genuine deployment pipeline. If merging to main is a ceremony, you will not do it every week. Invest in your pipeline until deploying feels like saving a document.