Every Noettic engagement runs on a four-week cadence. Week one is intake. Week two is build. Week three is install. Week four is handover. Then the cycle repeats, or it ends, or it grows.
The cadence was not an accident. It was the third version of how we ran engagements, and it solved a specific problem that the first two versions did not.
Why four weeks
Two weeks is too short. There is no room for the iteration loop that distinguishes a working system from one that compiles. Six weeks is too long. The client loses the thread, the original problem definition drifts, and the energy of the engagement dissipates.
Four weeks is the smallest unit that has room for one full build-test-revise cycle and the largest unit that maintains its own momentum. We arrived at it by trying both ends and watching what happened.
Why Tuesday
The calendar starts on a Tuesday and ends on a Tuesday. Every kickoff, every milestone, every handover. This is the part most people find strange.
The reason is honest: Mondays are not real days. Half the team is catching up on weekend backlog. Decisions made on Monday morning are routinely revised by Wednesday because nobody had the bandwidth to think about them carefully. We learned this by losing two engagements that were, in retrospect, scoped on Mondays.
Friday is no better. Friday meetings do not produce decisions; they produce next-week-we-will-decide. Tuesday through Thursday is the only window in a five-day week where the team is fully present and the runway after the meeting is long enough to act on what was decided.
The four weeks
Week 1 — Intake
We sit with the team for two days. We do not bring a deck. We bring questions. By the end of week one, we have written a one-page brief naming the smallest version of the highest-leverage problem we could find. Nothing is built yet.
Week 2 — Build
We build the smallest working version. It does not have to be elegant. It has to be honest — a real system processing real data, even if narrow.
Week 3 — Install
The system goes into the actual workflow. The team uses it for a week. We sit nearby and watch where it breaks, where it surprises, where it asks questions we had not anticipated.
Week 4 — Handover
We document, we train, we hand it over. By the end of week four, the team is operating it without us.
What the cadence enforces
The four-week structure does one thing that no longer engagement structure can: it forces honesty about scope. If the smallest version of the problem cannot be solved in four weeks, we have defined the problem wrong, and we restart. Long engagements absorb scope creep silently. Four-week engagements punish it loudly.
The Tuesday-to-Tuesday rhythm exists for the same reason. It removes the easy excuses that ambiguous calendars allow. The work happens, or it does not, and either way you find out fast.
