The M-1 Room

Bring the problem into the Room.

An AI-guided first read shaped by senior direction, delivery and build experience. Behind it, M-1 forms the delivery cell around the problem.

Prefer a person? Email the team directly →

The method · in one minute

See how the Room sharpens a problem.

Choose a problem close to yours. Watch the Room turn a messy brief into a testable first read: one question back, one working hypothesis, and the evidence that would prove or break it.

Choose a representative problem
M-1 Room · worked exampleWorked read
YouEvery week, two people rebuild the delivery report by hand from five systems. Leadership still doesn’t quite trust the number.
The roomOne question back: Which one question does leadership most need answered on demand — the completion date, the forecast cost, or what changed this week?
Working hypothesis
The position lives in five places and is reassembled by hand, so no one owns a single current version.
What we would check
The five sources and who reconciles them, and where their numbers actually diverge.
First read

Likely first build: one cited weekly position, assembled from your own systems, with every figure traceable to its source instead of rebuilt by hand.

M-1 Room · worked exampleWorked read
YouCommercial and delivery quote different numbers for the same package, and both have a spreadsheet to prove it.
The roomOne question back: Do the two numbers disagree on scope, on the baseline, or on what has actually been committed?
Working hypothesis
Cost and schedule are keyed to different breakdowns (CBS vs WBS), so they never reconcile on the same object.
What we would check
The breakdown structures in the ERP and the schedule, and the point where their keys stop matching.
First read

Likely first build: a reconciled view keyed to one structure, so commitments, actuals and forecast line up against the same package.

M-1 Room · worked exampleWorked read
YouNobody can say what’s actually in the next release without three people checking Jira, GitHub and a roadmap.
The roomOne question back: What decision is the scattered status actually blocking — the go/no-go, the client update, or the next sprint’s scope?
Working hypothesis
Release truth is spread across tools with no single owner, so every status is a manual reconstruction.
What we would check
How work moves across Jira and GitHub, and where the roadmap has drifted from the code.
First read

Likely first build: one release position drawn from the tools you already use, each item traceable to its ticket or commit.

M-1 Room · worked exampleWorked read
YouMaintenance history, the engineering record and live sensor data for the same asset sit in three systems, and none of them agrees on its current condition.
The roomOne question back: For the decision in front of you, does “condition” mean overdue maintenance, a design limit reached, or what the live signal is showing right now?
Working hypothesis
The asset is keyed differently across the EAM, the GIS and the historian, so its maintenance, engineering and operational records never line up on one identity.
What we would check
How the asset is identified in EAM/CMMS, GIS and the engineering record, and whether the historian’s signal is ever reconciled against work history.
First read

Likely first build: the asset register, its engineering record and its operational history joined to one identity, so condition and work can be read together.

A first read names the likely break, the evidence to test, and the smallest useful build.

The Room is an AI-guided first conversation shaped by M-1’s direction, delivery and build experience. When the problem is worth pursuing, the brief moves with you to our delivery team.

Bring your problem into the Room