ChangeOS Phase 1 by December 31

Find who is falling out. Tell the manager what to do.

Every person's place in the change cycle, daily. A flag when someone falls out. Behind each flag, the questions to ask. Proven first on our own AI tools.

Tap the screens. Everything recomputes from the same sample data.

What Phase 1 proves

Tell a manager who fell out and what to ask, and use comes back.

Three flagsZero use. Plateau. Usage drop.Never tried it. Tried it, never made it a habit. Used it and stopped. Three different conversations.

The playbook behind each flagWhat stopped you trying it? Which step did you drop it on? Who on the team does it well?Placeholders. Kathryn writes the real ones.

One loop closedFlag. Conversation logged. Fourteen days later, did use come back?That number is what the December presentation stands on.

Exit: a measured lift on the pilot, on real usage, with thresholds the team set.

Sources in Phase 1

Real data behind the pilot. A mockup of the Intradiem screens.

Pilot, real dataThe internal AI assistant. Conversations, connected apps, agents used. Export from Jason Dowden, mid-October.
Pilot, real dataMicrosoft 365 Copilot, our own tenant. Daily usage report. One request to the admin away from real rows.
Intradiem, mockupAccept rate and self-cure, per person, per day. Every customer already produces these. Reading them needs Engineering in the room.
Q1 2027Engagement Hub. Once it ships, its signals feed this too. Not required.

Kathryn's readiness assessment runs on the pilot group first and sets the baseline.

Screen 1 · Change cycle

Five stages. Who fell out where, and what to ask.

Tap a person. Stage names are placeholders until Kathryn names them.

Screen 2 · Flags

If adoption drops below X, tell the manager, with the questions.

Open the playbook on a flag. Log the conversation.

Screen 3 · Manager view

Who on my team is struggling, and what do I do next?

Switch manager.

Screen 4 · Executive view

Is adoption working? One screen.

Tap a team to filter.

Inside the product · mockup

Looks like Engagement Hub. Another tab.

Tab 1 · AdoptionAccept rate and self-cure per person, per day.The same change-cycle view as screen 1, on Intradiem's own data. Front office first.

Tab 2 · What to do nextThe flag, the questions, the conversation logged.First find who is not using it and why. Then help the manager close the gap.

Not ProPro is about agent burnout. This is about product adoption.Works without Hub or Pro. Better with both.

No data behind these screens yet. Anonymized rows from one customer would make it a demo. That needs Product and Engineering.

How it is sold

A paid add-on to any Intradiem product. Not free. Not Pro.

The add-onCustomers could do this by hand today. They do not.It makes them more efficient, which means more savings. Intradiem takes a piece of that.

SetupThree flags on by default. Thresholds set once. Nothing to configure.Heavy to set up and they will never use it. The playbook ships with it.

Price is blank until the pilot has a number. Every customer gets the report today and most ignore it. Nobody tells them what to do next. That gap is the product.

ExitA measured lift on the pilot, with thresholds the team set and conversations managers logged.
KathrynThe questions behind each flag, and the plain-word stage names.
JoeyThe assistant's usage export from Jason Dowden, and what customers say gets in the way. Faye, newly hired from a customer, is a first interview.
DallasOur Copilot usage report this week, then real rows on the pilot before November 3.
November 3, 9:00Calibration with Derek.
NextPhase 2: inside the product ›