Rapid engagements

A useful technical outcome can start with one focused week.

Short engagements are not smaller versions of long consulting projects. They are designed around one important question, one bounded problem and one meaningful outcome.

Scope determines the actual duration.

Long discovery phases can be appropriate, but they should not be the default. Sometimes the best next step is to spend a week answering the hardest question first.

How it works

How a timebox works.

  1. Before the timebox

    A short qualification conversation defines the question and outcome, confirms access and dependencies, and agrees what is explicitly out of scope.

  2. During the timebox

    Work is prioritised by whatever most reduces uncertainty or risk, with short checkpoints where useful and decisions and assumptions documented as they are made.

  3. End of the timebox

    You leave with at least one concrete result: a working artefact, a technical decision, a prioritised review, a recovery plan, a prototype/POC or an architecture design.

Example one-week engagements

Four ways a focused week can be used.

Ready when you are

Scope determines how far one week takes you.

From one week does not mean every project is a one-week project. It means Moka Inspire structures work so you can reach useful milestones without overcommitting before the next decision is clear.