One room. One decision.

The meeting that keeps reconvening

Some decisions circle for months because nobody owns them and the discussion restarts from zero every time. The cost isn’t the meeting. It’s the quarter of work parked behind it.

• The same architecture debate, reopened every planning cycle.
• A backlog ranked by whoever spoke last.
• Two teams solving one problem in opposite directions.
• Everyone nods in the room. Nothing changes in the repo.

Facilitated by someone who has built it

We prepare against your real material, run the session with a neutral hand, and push for a decision instead of a discussion. Because we’re engineers, a technical claim gets tested in the room rather than deferred to a call next week.

• A pre-session read of your code, architecture, or roadmap, plus short participant interviews
• An agenda framed around one question, agreed with you before the day
• Exercises built on your actual constraints, not a generic case study
• A decision record — chosen, rejected, why, and who owns it — circulated within two working days
• A prototype, spike, or reference design produced in the room where one settles the argument
• A follow-up call weeks later to check the decision survived contact with reality

1. 01

   Prepare

   We read your material and interview a few participants, so the session opens at the real question instead of discovering it at eleven.

2. 02

   Run

   Short input, long hands-on, and a decision forced before the room empties.

3. 03

   Capture

   Everything decided, written down with the trade-offs and the owners, delivered within two working days.

4. 04

   Follow up

   A check-in weeks later: what shipped, what stalled, and what needs another push.

Sessions are led by practitioners rather than facilitators. The same people designed a multi-tenant legal platform under strict data isolation rules, and an analytics platform that ran 50× faster than BigQuery while cutting infrastructure cost by more than 80%. When a design is called unworkable in the room, that judgment comes from having shipped the alternative.

• How is this different from hiring a facilitator?

  A facilitator manages the conversation. We can also tell you the proposed design won’t scale, and show the arithmetic before lunch.

• Can you run it remotely?

  Yes, in a shorter format with more breaks. On-site is better for contentious decisions; remote is fine for most technical ones.

• What if we don’t reach a decision?

  Then we name the missing information, who gets it, and by when. The ambiguity leaves the room in one form or another.

• Is one day enough?

  For one well-framed question, usually. That’s why the framing happens in preparation rather than in the first two hours.