Skills your team sharesCourse 02 · 4 weeks · 10 hours

What one personworks out,everyone gets.

Four weeks for the people who already reach for AI every day. They write down the way a job should be done, hand it to the rest of the team, and point it at the two places the work piles up: the inbox and the browser.

Book this courseSee the four weeks
Four modules

What is in it.

05

Writing your first skill

The way you do it, written down once

06

Sharing it with the team

One person works it out, everyone runs it

07

Letting it use the browser

The click-through you do forty times a month

08

Reading the inbox

Orders, invoices and referrals, sorted on arrival

A skill, sharedThe idea

Written once.Run by everyone.

One person works out the good way to do a job. Everyone else gets it — including whatever the next person sharpens.

How one person's way of doing a job becomes the team'sOne person works out the good way to do a job once. Those steps are written down as a skill. The whole team then runs it — scheduling, quality, purchasing and the office. When anyone sharpens the skill, the improvement goes back into the same shared copy, so everyone gets it.ONE JOB, DONE THE GOOD WAY, ONCEOne person works it outthe way it should be doneA skillthose steps, written down onceThe team runs itsame job, same way, every deskSCHEDULING · QUALITY · PURCHASING · THE OFFICEANYONE SHARPENS IT → EVERYONE GETS THE SHARPER ONEWhat your team builds in week three, and keeps
Two piles of workWhere it goes first

The inbox,and the browser.

The order that arrives every morning, and the portal somebody fills in by hand forty times a month.

Two jobs a shared skill takes overFirst row: an order arrives by email in Gmail or Outlook, the skill reads it and pulls out the parts that matter, and it lands in the schedule, the ledger or the right person's desk. Second row: a portal that is filled in by hand, the skill drives the browser through the same click-through, and the form is filled and filed with the odd one flagged for a person.WHAT ARRIVESWHAT THE SKILL DOESWHAT COMES OUTAn order, by emailthe way it has always arrivedIt reads what came inpulls out the parts that matterInto the schedulethe ledger, or the right person's deskA portal, filled by handthe same fields, forty times a monthIt drives the browserthe click-through, done the same wayFilled and filedand the odd one flagged for a personWHAT IT DOES NOT DODecide anything you would want your own name on. Those it hands back.
Four weeksWhat it takes

Ten hours,and one real job.

Modules watched when it suits, one live hour building on a job your team picks, and a skill running in their hands by the end.

What the four weeks containTen hours of modules run across the month, practical do-it checks start in week one, a one-hour live build session lands in week two, and from week three the team's first shared skill is running on a job they picked.WEEK 1WEEK 2WEEK 3WEEK 4Four modules10 h, watched when it suitsLive build session1 h, on a job your team picksDo-it checkspractical, not examsYour first shared skillon a job they do every weekIN THE TEAM’S HANDSLEGENDWatched or attended on your team’s own scheduleThe deliverable — a skill that keeps running after we leave
Questions

Asked beforeevery cohort.

The steps of a job, written down in plain language so an assistant can follow them the way your best person would. No code. If someone can write a work instruction, they can write one of these.

The rest of the programmeAll courses
Course 01 · 4 weeks · 10 hoursResponsible use of AICheck the answer. Keep private things private.
Train the people you already have

Book a call.

Start with the map of your organization, or with the one job that hurts. Measured in hours and money, and everything we build stays yours.

Loading form…