It starts with one email.
Your champion picks who takes part. Each person gets a short invitation from them: what the diagnostic is, how long it takes, and what happens to their answers. No account to set up in advance.
- Sent in your champion’s name, not a stranger’s.
- Says plainly that it is a conversation, not a test.
- One link, valid for two weeks.


Nobody is asked anything before they know what happens to the answer.
The first screen after the link is consent, in plain language: what is kept, who reads it, and what stays in their control. Iris asks nothing until they agree.
- Phone numbers and email addresses are replaced with codes before anything is saved.
- Colleagues they mention by name are coded in the findings, the map and the report.
- They can pause, stop, skip a question, or ask for their data to be removed.


They choose the time. Nobody has to chase.
Each person books a slot that fits around their work, from the hours your engagement sets. They pick a day and a time, see it said back in words, and only then book it. A confirmation arrives straight away.
- Nothing is booked by accident: a tap selects, a button books.
- Shown in your organisation’s own time zone, with how many times are still open each day.
- Add it to their own calendar in one tap; move or cancel it any time.



The booking email carries the time in their own zone and one button back to the session. If the time stops suiting them, the same page lets them pick another.
A conversation with Iris, and a map that draws itself.
Iris asks one question at a time and follows up on what they actually say. As they mention systems, files and teams, those appear on the left and connect. Every finding is noted as it is made, so nothing is taken without them seeing it.
- Type, or answer by voice; Iris can speak her questions aloud.
- Available in English, French, German, Swiss German, Polish and Philippine English.
- Leave mid-session and pick up where they left off.


Kim from the warehouse, in a first sitting. Iris has picked up the ERP, the pick list, the returns book and two colleagues, and asks about the gap between the paper book and the system.
Your champion sees it come together.
One person on your side runs the engagement: they invite colleagues, add departments and briefs, and upload documents. Their progress page shows who has been heard, what has been covered, and what happened today.
- Progress counted in people heard from, not sessions held.
- Department by department, so gaps are obvious.
- Documents uploaded once and read by Iris before she asks.


How work actually flows, and where it backs up.
Every interview and document feeds one operations map: the systems on top, the people in the middle, the files and paper at the bottom, and every handoff between them. Red is where work backs up. Trace the friction path to see the one chain that does most of the damage.
- Built only from what people said and shared, never templated.
- Filter by department, by person, or by what one system touches.
- The TO-BE view shows what changes, what stays and what is retired.


AS-IS: order to cash at Northbeam today, from ten interviews and seven documents.
Your team confirms the picture before anything is designed on it.
Nobody knows your operation better than you. Your champion confirms each box or flags what is off, then accepts the map as how the business runs, with a note if something matters. Only then is a recommendation designed, and the note goes into it.
- Corrections go straight to the Embiggen team.
- If the map changes later, the acceptance is marked out of date, not carried over.

The options, the recommendation, and what it would take.
Three directions are weighed against each other, from the smallest change to a full rebuild. One is recommended, with the reason, and the work is laid out in waves: an order to do things in, not an invented schedule.
- Every recommendation traces back to something a named person said or shared.
- Read end to end by an Embiggen engagement owner before it reaches you.
- What could not be answered is listed, not hidden.


Scroll inside the window: the recommendation, the three options compared, the roadmap in three waves, and the transformation report in full.
What to build first, and why that order.
Every change the diagnostic recommends is placed on one matrix: how much it would help against how feasible it is with what you already run. The quick wins sit top right, and the priority order beside it is agreed with your Embiggen engagement owner.
- Each item names the capability it needs, so nothing is a black box.
- Every estimate is a range, never a point figure.
- The first three add up to a combined build range you can plan against.


A report your leadership can read in one sitting.
What your people said in their own words, the flow today and the flow recommended, the root causes behind the friction, and a ranked roadmap with honest ranges. Export it as a PDF or a deck.
- Every claim traces to a named conversation or document.
- Released only when an Embiggen engagement owner has signed it off.


