Week 6

Team rollout, one workflow per job type

Every named build lands with its owner this week, on the calendar and in the registry.

Works.

Rollout is change management, not a demo.

A workflow that only works for its builder is a demo. The highest-frequency, lowest-risk work goes first, and the person who already half-built their own fix becomes the flagship, not an import from outside.

This week's handover, part 1

One workflow, one owner, one room

Lachlan: the Proposal Engine, to himself, the sponsor demonstrating his own workflow to the room.
Susan: the reverse brief, to the design team.
Mollie and Grace: the Project Lead Command Centre, to the project leads.
Michael: the QA Console, to Michael and the project leads who share the review.
Kat: her finished cost-code tool, plus the weekly minutes habit, to construction.

This week's handover, part 2

The rest of the room, honestly scoped

Melony (Mel): the Pack Generator, landed last, on purpose, after a team win was already visible.
James: Quote Control, to estimating, the takeoff half stays scope only.
Bruce and Jai: voice to email and task, represented in the room by Kat when the crew is on site.
Steve: the one lane where the locked systems limit what can change, a ten-invoice intake test, not a rollout.
Trent: the image library, small, and last.

No protected time, no adoption, same lever, now at team scale.

A real, calendared weekly slot, roughly two hours, plus a dedicated channel and a Friday usage post: a usage screenshot, one thing shipped, one thing stuck.

Office hours, a skill request inbox, a show and tell, all owned inside the business.

Let the skill request inbox double as a quest board, so a finished build lands in one shared library instead of five people each building a worse copy.

Day 30 / 60 / 90, working estimates

Checked against real work, not a vague timeline

Lachlan's own baseline: about 60 admin days a year. Susan's target: 30 percent of her time on admin, down to 5. Every figure here gets re-confirmed on real jobs, not assumed.

Day 30: the brain is navigable in under a minute, one workflow demonstrably used by its named owner.
Day 60: workflow count checked against what was promised, someone other than the builder runs it unassisted.
Day 90: the team runs it with nobody hovering, and the 25 percent busy work figure is re-checked, not banked.

A new hire gets the same four files everyone else got.

Identity, voice, working preferences, current context, hosted on SharePoint, with a name of their own the way Week 1 gave the first cohort. Onboarding at scale repeats a known pattern, it doesn't reinvent one per person.

The credential ceiling

The login is the boundary. The instruction file is a note taped to the front.

We read from Jack and Databuild once the read-only exports land. We never write into either. Say it once, directly, to everyone new touching the system.

The governance lifecycle

Propose, endorse, approve, register, review, then prune and re-approve.

Register is the box the auditors ask for first. Every agent or automation gets its own credential, never a shared login.

Every handover above gets one line in the registry before it's called done.

Owner, scopes, expiry, next review date, plus a link check, a provenance check, a secret scan. Company data lives in one shared home; identity and personal task lists stay individual.

Lessons flow in. Your operations never flow out.

Held up by two things: credential scoping decides what a login can reach, and the vendor's contract terms decide what happens to the data. Not a promise written into an instructions file.

Before next session

This week's work

Builder + teammate: run a 30-minute walkthrough of one built skill with the right first teammate, a real quick win, not the most hesitant person in the room.
Whoever runs it: capture what the teammate found confusing, that becomes the next iteration.
Whole team: install the three rituals and the dedicated channel's Friday usage post, owned inside the business, not by Works.
Sponsor + Works: stand up the handover dashboard and walk Lachlan through what's shipped, what it's worth, what's next, what needs him.
Rollout owner: write one registry entry, owner, scopes, expiry, next review date.

Exit criteria

You're done when

One workflow from the handover list is running for a named owner outside the person who built it.
Feedback from that first teammate is captured and already shaping the next iteration.
The three rituals and the dedicated channel's Friday usage post are running, owned inside the business.
The handover dashboard is live and has been reviewed with Lachlan.
Every handed-over workflow has a registry entry.
The rule, we never write into Jack or Databuild, has been said once, directly, to everyone new touching the system.