Engagement Kickoff Orbit

Why the first two weeks decide the engagement

The Engagement Kickoff Orbit is a fixed two-week structure for the start of a consulting engagement, built to convert a signed contract into live execution without losing the first month to setup. It treats kickoff as a production with a sequence and owners, rather than a period of ambient warming up while everyone waits for access and alignment. The name comes from the shape of the work: three concentric orbits that must all be established before the engagement can hold a stable path, from the innermost logistics out to the outermost scope and cadence. Like a spacecraft establishing each orbit in turn, an engagement cannot settle its outer commitments until the inner ones are locked.

Kickoff is where engagements quietly succeed or fail, and it usually fails invisibly. The team spends two weeks chasing system access, discovers in week three that a critical stakeholder was never mapped, and reopens scope in week four because the sponsor's expectation was never written down. By then a quarter of a twelve-week engagement is gone and the client is uneasy. The Orbit prevents this by front-loading the setup work into a sequence with checkpoints, so that by the end of week two the engagement is executing on evidence rather than still assembling itself.

The concentric shape is deliberate. The inner orbit is the most concrete and the fastest to close, but nothing else can stabilize until it does, because a team without access or a cadence cannot build a stakeholder map or confirm scope. The middle orbit depends on the inner one, and the outer orbit, where the real commitments live, depends on both. Working the orbits out of order is the classic kickoff mistake: teams jump to scope debates while access is still unresolved, and the conversation founders because there is no evidence base to ground it. The Orbit enforces the sequence so each layer rests on a settled foundation.

Three orbits, one path to execution

The Orbit organizes kickoff into three layers. The inner orbit is fastest and most concrete; the outer orbit is the highest-stakes and depends on the inner ones being settled. Each orbit has a named owner and a checkpoint that must clear before the engagement is considered launched.

The checkpoints are what make the Orbit more than a checklist. A checklist can be half-done and still look complete; a checkpoint is binary, owned, and dated, so at day three someone reports that access is live or that it is not, and if it is not, the engagement lead escalates that morning rather than discovering the gap a week later. This is the difference between a kickoff that is managed and one that is merely hoped for. The owner of each orbit is accountable for a specific outcome by a specific date, and the partner reviews all three checkpoints at the day-10 gate before declaring the engagement launched.

Worked example. A twelve-week operating model review kicks off on a Monday. By Wednesday (day 3) the team has data-room access and a standing Tuesday-Thursday cadence. By the following Monday (day 7) the stakeholder map names nineteen people, six interviews are booked, and the finance and org data sets are in hand. By Wednesday of week two (day 10) scope is confirmed in writing with the COO as decision owner, the cadence is running, and the team ships a first-cut current-state map for review. The client has seen tangible output before the second week closes, and the engagement never entered the drift that swallows the first month.

The day-10 artifact is the pivot of the whole structure. It is not there to impress; it is there to prove. A rough current-state map, shared and discussed, tells the client that the machine is running and gives them something concrete to react to, which surfaces misunderstandings about scope while they are still cheap to fix. An engagement that reaches day ten with access, a stakeholder map, confirmed scope, a live cadence, and a reviewable artifact has effectively de-risked its first quarter, because every later problem now lands on a stable base rather than on a foundation still being poured.

The two-week box is itself a feature. Kickoff work expands to fill whatever time it is given, so an open-ended setup is still organizing itself in week five. Two weeks is long enough to establish the three orbits and short enough to force decisions rather than gold-plating. If a checkpoint genuinely cannot be met in the window, that is important information, usually a sign the client is not ready or scope was misjudged, and far better surfaced in week two than in month two.

Running the two weeks

Running the Orbit well is mostly a matter of parallelism and ownership. The three orbits do not run strictly one after another; the inner orbit starts first and the others begin as soon as their dependencies clear, so by the middle of week one all three are in motion at once. What holds it together is that each orbit has a single accountable owner watching its checkpoint, rather than a team collectively hoping the work gets done. The engagement lead sits above all three, tracking the checkpoints against the calendar, and the partner owns the day-10 gate where the three checkpoints and the first artifact are reviewed together before the engagement is declared launched.

• Start the inner orbit before day one. Access requests and data-room provisioning have client-side lead times, so file them the moment the contract signs, not on the Monday of kickoff.
• Give each orbit a single named owner who is accountable for its checkpoint, so no layer is left to the team collectively and therefore to no one.
• Book the stakeholder interviews in the first week even if the questions are not final. Calendars fill, and a booked slot with a rough guide beats a perfect guide with no slot.
• Write scope down and get the sponsor to confirm it in the outer orbit, so the day-10 checkpoint closes a real agreement rather than a shared assumption.
• Force a reviewable artifact by day ten, and escalate any missed checkpoint the day it slips rather than at the next weekly. The artifact need not be polished; it needs to prove the engagement is producing, which resets client confidence, while a day-3 access gap left until Friday has already cost the engagement most of its first week.

How kickoffs stall

• Treating access as an IT afterthought. It is the longest-lead item and it blocks everything. The fix is to make it the inner orbit's day-3 checkpoint, owned by name.
• Skipping the stakeholder map because the team thinks it knows the players. The unmapped stakeholder surfaces in week four and reopens scope. The fix is a written map by day seven.
• Leaving scope as a verbal understanding. Verbal scope drifts silently until the sponsor and the team discover they meant different things. The fix is written, confirmed scope at day ten.
• Running kickoff with no checkpoints, so setup expands to fill the available time. The fix is the three hard dates, each with an owner who reports the checkpoint cleared or not.
• No first artifact by day ten, so the client's only signal is activity rather than output. The fix is to ship something reviewable, however rough, before week two closes.

Launch the Orbit cleanly

• File all access and data-room requests the day the contract signs.
• Assign one owner to each of the three orbits before kickoff Monday.
• Draft the stakeholder map and book the first-week interviews by day two.
• Get written, sponsor-confirmed scope on the record by day ten.
• Schedule the day-10 review of the first reviewable artifact into the calendar now.