Skip to content
For Department Leads

You're running the AI pilot that exposed the governance gap.

Your team has Pylon tickets piling up faster than you can triage. You've stood up a Claude or ChatGPT workflow to help. It works. Until somebody upstairs asks who approved it, what it cost last month, and what happens when it gets one wrong. Then it stops being a pilot and starts being a problem.

WorkReef is the platform your AI Change Leader is evaluating. This page is what's in it for you.

What a Department Lead does in WorkReef

Three jobs the platform makes possible.

Approve or reject AI takeover for your team's tasks.

Your AI Change Leader does not make per-task decisions inside your department. WorkReef scopes the transformation queue to just your team's work. Each candidate arrives quorum-vetted, with the cost, service, and risk impact named, the shadow-run agreement rate visible, and a one-click approve, reject, or edit with your name on the audit row.

Watch shadow-mode results before you commit.

The agent runs alongside the human baseline for thirty runs at eighty-five-percent agreement before the promotion gate proposes moving to live. You see the agreement rate climb. You see which calls the AI disagrees with humans on. You see the recent runs in your department's view, not a global firehose. You decide when shadow is enough.

Add the context the AI doesn't have.

"This customer pays us $4M/yr. Never autonomous on their tickets." "Anything mentioning OR-day logistics is priority-bumped to a human." These are the things the AI can't infer from the data. WorkReef gives you an "I want to weigh in" channel that lands as an Observation in the analysis queue before the change leader sees the takeover proposal.

Monday morning at Sarah's desk

What this looks like for one VP of Customer Support.

Sarah is the VP of Customer Support at one of our beta companies. Monday morning, 7:48am. Coffee. She opens WorkReef on her laptop.

Three cards waiting in her view. The first is a quorum-vetted recommendation: AI handling the tier-1 password-reset tickets her team currently spends an hour a day on. Cost impact: medium. Service impact: medium. Risk impact: low. The audit-feasibility numbers (2,847 tickets in 90 days, uniform handler pattern) are visible on the card. Sarah taps approve. The agent enters shadow phase.

The second card is an "I want to weigh in" prompt the Architect surfaced. "This candidate touches Aetna account tickets, which your team has previously flagged as priority-bumped. Should the AI route Aetna tickets to a human regardless of recurrence numbers?" Sarah types yes, paragraph of context. The Observation lands in the analysis queue. The Architect will re-run with the context attached.

The third card is Maria's shadow-phase update. Maria is Sarah's AI Supervisor (a former tier-2 IC retrained for the role). Last week's shadow runs: 234 total, 89% agreement, eighteen disagreements landed in Maria's queue. The promotion gate has not yet proposed advancing. Sarah leaves it. Backward moves are always allowed. The gate will propose advancement when it's ready.

Total elapsed time: nine minutes. Sarah closes her laptop and walks to standup. Her AI program is governed. She has not been to a takeover-review meeting in three weeks.

Your workspace, scoped

Only what's relevant to your team. Not the buyer's portfolio dashboard.

What you see

  • Your department's workforce, humans and AI both, as positions with capacity and cost
  • Capacity surface scoped to your team. Who's pressed. Where the slack is. Rebalance proposals before any AI takeover gets considered.
  • Takeover candidates ranked do_now, pilot, consider, skip, for your tasks only
  • Shadow runs in flight. Agreement rate. Recent disagreements with the human baseline.
  • Your team roster with each person's persona (IC augmented, IC overseeing, IC replaced) visible so you can have honest conversations.

What you don't see (by design)

  • Other departments' candidates, decisions, or rollups
  • Platform admin. Billing. Tenant-wide settings.
  • Connector setup, handled by the AI Change Leader and IT
  • Names of ICs at your level in other departments
  • Aggregate org-wide spend numbers, which land with the change leader and the CFO

Why this matters for you specifically.

Half the dept leads we talk to are running an AI pilot upstairs doesn't fully know about. Most of them are losing sleep over it. The four points below are the actual conversations we keep having.

The pilot stops being your problem alone.

Right now, if your AI workflow gets one wrong, it lands on your desk. With WorkReef, the rollout is governed at the platform layer: spend caps, kill criteria, audit trail. Your name is on the approvals. The platform owns the guardrails.

You stop being asked the same questions in every leadership meeting.

"What's your team's AI doing? What's it costing? How do you know it's working?" The Steward agent answers all three weekly. You walk into the meeting with the chart already built.

Your team isn't surprised by the change.

The IC-being-replaced workspace is built around honesty, voice, career path, and exit dignity. No automation-viability score shown to your team members about themselves, ever. The conversation you've been dreading becomes a structured handoff with resources attached.

The decision authority that's actually yours stays yours.

The AI Change Leader sets policy. The CISO signs off on architecture. You, the dept lead, decide what AI takes over in your department, and when. The platform gives you the seat at the table you're already entitled to.

Forward this

Send this page to your AI Change Leader.

If your company is mid-evaluation on WorkReef, the strongest thing you can do is forward this page with one line: "This is what's in it for my team. I want a scoped workspace when we sign."

If your company hasn't started evaluating yet, forward the home page with the same line and a link to the four moves. The platform is in private beta. The path in is short.

Suggested message
Hey, read the WorkReef For Department Leads page. It maps to exactly what we've been doing with the team's AI pilot, but governed. The shadow-mode plus scoped-view setup is what we need before we put anything else into production. Can we get on their beta list?