DRS Framework / Conversion Scene

The 9:02 AM Meeting

See where you sit

The invite said 9:00.

The meeting started at 9:02 because Doug was losing a quiet fight with his microphone.

He had been COO for eighteen months. Smart. Calm. Good in front of a board. The kind of leader who could make a messy situation sound organized in a slide deck.

He spoke for a full minute before anyone told him he was on mute.

Vince from Sales typed "classic Doug" in the chat. A few people reacted. Doug never checked the chat.

Nobody offered to help. Helping Doug with tech had a way of turning into follow-up work.

When the audio finally kicked in, he smiled like nothing had happened.

"Alright. Thanks for your patience. I'm excited about this one."

Forty-three people were on the call. Finance. Sales. Ops. Marketing. A few cameras on. Most off. Half listening. Half already working.

Doug pulled up the deck.

"We're rolling out a new AI workspace. Forecasting, reporting, approvals. This is going to streamline how we operate across the board."

Same message.

Four very different reactions.


Denise muted herself and kept eating the granola bar she'd been working on since 7:30.

It was stale. She didn't care.

She'd been at the company long enough to know which problems were real and which ones were announcements.

Her screen wasn't on the deck. It was on a spreadsheet labeled "DO NOT DELETE."

Nobody had told her to build it. Nobody outside her team knew how it worked. Everyone knew things broke when she wasn't there.

When Doug said "streamline," Denise's eyes went to one cell.

Q3 inventory override.

Manual. Undocumented. Necessary.

Her first thought wasn't about learning the new system.

It was simple.

Does it know about this?

She already knew the answer.


Jeremy turned his camera off and pulled up a second monitor.

He wasn't watching the slides. He was reading the product documentation.

He had been at the company three years. Long enough to fix things. Not long enough to care who got credit.

He didn't think in features. He thought in logic.

When Doug said "AI-assisted," Jeremy was already scanning for how decisions were being made under the hood.

His first thought:

Where does it break?

If the system was solid, he'd use it.

If it wasn't, he'd build something better and keep it to himself.


Frank didn't switch screens.

He stayed on the meeting, nodded once, and opened his fantasy football app.

Not because he didn't care.

Because nothing in the first three minutes sounded like it would make his day easier.

He handled invoices. A lot of them. The work was predictable. That was the point.

Predictable work meant he could manage everything else. His mom's schedule. His kid's practice. The refinance he hadn't finished.

When Doug said "training rollout," Frank did the math.

Time in training. Time fixing whatever didn't work. Time explaining it to someone else.

His first thought:

What goes away?

He'd learned the answer was usually "nothing."


Tessa leaned forward.

Camera on. Notes open. Already typing.

She'd been there less than a year. Came from a place where new tools meant new leverage.

When Doug said "AI workspace," she didn't hear "standardization."

She heard:

What can I build with this?

She was already sketching a different workflow. One that skipped the monthly cycle entirely. Real-time instead of review meetings.

Faster. Cleaner. No waiting.

She didn't know why the current process existed.

She didn't ask.


Doug clicked to the final slide.

"Ultimately, this is about helping everyone do their best work."

He meant it.

He opened the floor for questions.

Silence.

Then someone unmuted.

"So does this replace anything, or is it in addition?"

Doug paused.

"We'll get into specifics in Phase 2."

A few people nodded. A few people stopped listening entirely.

The meeting ended on time.


Thirty days later

Denise still used her spreadsheet.

She went to the training. Took notes. Asked one question that didn't get answered.

The new system didn't know about the override.

So she kept both.

One official. One real.

Jeremy stopped logging into the tool after week two.

He'd found a flaw in how it handled edge cases. Quietly built a workaround.

Leadership saw his name on the adoption report.

He was counted as a success.

Frank completed the onboarding.

He used the tool exactly as shown in training. Nothing more.

His workload didn't go down.

He now spent an extra half hour a week checking outputs he didn't trust.

No one tracked it.

Tessa rebuilt her team's workflow in three days.

It worked.

Leadership loved it.

What no one noticed was what disappeared.

A check. A step. A piece of logic that had been catching something important for years. Denise's override. The one nobody documented. The one nobody asked about.

That would surface later.

Not in Tessa's metrics.

Doug presented an update to the board.

"Adoption is strong. Teams are engaging. Early indicators are positive."

He wasn't wrong.

From where he sat, the system was working.


Same rollout.

Same training.

Same message.

Four completely different realities.

These aren't personality types.

They're states.

They change with pressure. With time. With what's at stake.

The same person can sit in that meeting on two different weeks and hear two completely different things.

Which one are you right now?

And more importantly... did anyone design for that?

Explore the model.

DRS Framework / Core Model

The Four Psychographic Segments of Workforce AI Adoption

People are not fixed in a segment. They shift under pressure. Click a quadrant to see the integration path and transition triggers.
Identity Source
Mastery (Craft) Output (Result)
Cognitive State (Bandwidth)
Surplus Deficit
Surplus + Mastery
The Operator
They have the energy to learn and they care deeply about the craft. They want a powerful tool... not a simple one.
Path: Expansion — Unlock complexity. If it's too easy, they'll reject it as a toy.
+
You'll recognize them as
The person who already built a better version of your spreadsheet before you asked. The one who reads the documentation for fun. The architect who wants to know why the system made that recommendation... not just what it recommended.
Transition triggers
Exhaustion Slide → Detective Incentive Pivot → Maverick
Cynicism risk
Black Box Authority. If they can't see the logic behind the tool's recommendations, their sign-off becomes varnish on a guess. Years of mastery reduced to a rubber stamp.
Deficit + Mastery
The Detective
Overwhelmed, but they refuse to let quality slip. Often the Old Guard. Protective of the part of the job that makes them... them.
Path: Continuity — Build a bridge. Prove the new respects the old.
+
You'll recognize them as
The person who's been here 15 years and knows where every body is buried. The one who keeps a shadow spreadsheet because the official system can't be trusted. The auditor who catches the error everyone else missed... and resents that nobody noticed.
Transition triggers
Efficiency Dividend → Operator Incentive Pivot → Fixer
Cynicism risk
Liability Node Trap. The system produces a 99% complete output. They verify it. If they catch the error, the system is "efficient." If they miss it, they're "negligent." They're not a governor... they're a legal shield.
Surplus + Output
The Maverick
Energy to burn. They want massive results and aren't wedded to "the way we've always done it."
Path: Modularity — Give them a kit of parts. Let them invent the workflow.
+
You'll recognize them as
The VP who bought the AI tool before IT approved it. The sales rep who built their own CRM in Notion because the official one was too slow. The founder who sees every system as a sandbox.
Transition triggers
Exhaustion Slide → Fixer Audit Shock → Operator
Cynicism risk
Efficiency Squeeze. They save four hours through innovation. The organization immediately fills those hours with grunt work. Being efficient is punished with more work. The path of least resistance becomes a treadmill.
Deficit + Output
The Fixer
Overwhelmed. Zero patience for features. They just want the job done and the desk cleared.
Path: Subtraction — Remove three steps for every one you add. Be invisible.
+
You'll recognize them as
The person with 47 unread Slack messages who just needs the report to go out. The admin who processes 200 tickets a day and has zero capacity for "innovation." The parent-caregiver-employee who just needs one thing to be easy today.
Transition triggers
Efficiency Dividend → Maverick Audit Shock → Detective
Cynicism risk
Performative Agency Paradox. The system asks "How would you like to work today?" but the KPIs stay fixed. If they choose the automated path and get penalized for "low engagement," the choice was an illusion. Dignity as theater.
These are states, not types. A person can be an Operator on Monday and a Fixer by Friday.

Traditional management tries to move everyone into the Operator bucket. This framework recognizes that forcing a segment change is a violation of the human experience. An elegant system meets the human where they currently sit. If someone is a Fixer on Tuesday, you don't lecture them on Mastery... you give them the relief they need to survive the day.