More Time to Live

The blueprint, step by step.

So many options make it easy to move and groove. A method builds a solid foundation, so what you create actually lasts.

The blueprint at a glance

1Get readySIPOC">2See whereeverything isIPO">3Zoom in onone process4Decidewhat to do5Build theteam6Set routines7MeasureprogressRoom todreamAI lowers the waterknowledge · bots · wow

Each step, up close

1

Get ready for what’s next

Even if your time isn’t full, AI opens room to do far more. Rethink how your time is spent, your true talents, and your potential, not just your capacity. Then look at everything that pours in, and how long it takes.

What the water represents

  • Emails
  • Ad hoc requests
  • Fire drills
  • Teams messages
  • Text messages
  • To-dos
  • Upcoming meetings

Name the pain points

  • What spills over?
  • What waits too long?
  • What wears people down?
  • What takes the longest for the least value?

How to do it

  1. Notice everything coming in: emails, requests, fire drills, messages, to-dos, meetings.
  2. Write down how long each kind takes in a normal week. That is the starting baseline.
  3. Name the pain points: what spills over, what waits too long, what wears people down.
  4. Pick the one or two that hurt most to start with.
2

See where everything is SIPOC

Who supplies, what comes in, the work, what goes out, who receives it. One page that shows where the work comes from, what happens to it, and who it is for.Reference: SIPOC stands for Suppliers, Inputs, Process, Outputs, Customers.

Who suppliesS
  • Customers with requests
  • The team
  • Partners and vendors
  • Tools and data sources
  • AI bots
What comes inI
  • Requests and questions
  • Email and messages
  • Calendar and deadlines
  • Documents and data
  • Ideas and feedback
The workP
  1. Hear the need
  2. Shape it
  3. Make it
  4. Check it
  5. Deliver it
What goes outO
  • Finished work
  • Answers and decisions
  • Updates and reports
  • New ideas tried
Who receives itC
  • Clients
  • The team
  • Leaders and partners
  • Community
  • My future self
Wow measures: on time, right the first time, “they thought of that”

How to do it

  1. List every customer (who receives the work) and every supplier (who feeds it).
  2. List every input that arrives: requests, messages, data, ideas. Know what each one is.
  3. Sketch the work in 5 to 7 big steps, and the outputs each customer gets.
  4. Ask each customer what would wow them, and turn it into 2 or 3 measures.
3

Zoom in on one process IPO

In, work, out: zoom in on the one process that matters most. Example: turning a customer request into finished work.Reference: IPO stands for Input, Process, Output.

Input

  • The request and its goal
  • Past examples of great work
  • The knowledge base
  • Deadline and who it’s for
→

Process

  1. Understand what they really need
  2. Bot drafts from the knowledge base
  3. A specialist checks it before it goes out
  4. Polish and send
→

Output

  • Delivered work the customer can use
  • A note added to the knowledge base
  • The customer’s reaction, written down

How to do it

  1. Pick the one process that matters most to customers and hurts most today.
  2. Write its inputs: what has to be on hand before it starts.
  3. Write its steps and its outputs, and who receives each output.
4

Decide what to do

Take the output of the zoom-in step IPO and break it into three questions: to deliver work the customer can use, what do we need to know, what do we need to do, and who will do it?

Filter inputs down to what matters

Everything that arrives
Tied to a customer on the map? SIPOC
Matters to a customer goal, or the dream?
Needs us, now?
Meaningful inputs

Everything else goes to the archive, a later list, or a bot.

From step 3: the one process, zoomed in IPO

Know

Organize the information.

  • How-we-do-it notes
  • Examples and customer notes
  • Decisions and why
  • In plain text AI can read

Do

Identify your routines.

  • The repeatable actions the bots will run
  • Connectors to email, calendar, docs, notes and sheets

Who

Human or bot.

  • Where a human stays in the loop
  • Where specialists, people or bots, come in

How to do it

  1. Know: organize the information. Put how-we-do-it notes, examples, customer notes and decisions in plain text AI can read.
  2. Do: identify your routines. List the repeatable actions the bots will run, and set up connectors to the tools where the work lives.
  3. Who: human or bot. Decide where a human stays in the loop and where specialists come in.
  4. Filter what comes in so only meaningful inputs get through: tied to a customer on the where-everything-is-today map SIPOC, or to the dream.
5

Build the team RACI

The mixed team of humans and bots comes together and works as one team.

Clear roles

  • People: decide, approve, and take the relationships and judgment calls
  • Bots: sort, draft, check, log, and run the routines
  • Specialists, people or bots: the deep work. Right now we set the system up to handle standard work. Once a specialist is trained and has had enough cycles of learning, it can act on its own on ad hoc work too.

Level up over time

  • Look at what went well and what bounced back
  • Retrain a bot or update what it knows
  • Retire what isn’t pulling its weight
  • Add a member when the work grows

Every output held to a specialist’s bar Skills Matrix

Raw

Fast and broad, like a supercomputer. Needs checking.

Checked

Facts verified, sources shown.

Fitted

In our voice and format, for this customer.

Specialist

What a seasoned expert would sign their name to.

Wow

Answers the next question before it’s asked.

Supercomputer: fast, broad, rawNothing reaches a customer below “Specialist” →SME: specialist, subject-matter expert
6

Set routines Standard Work

Decide what happens every hour, day, week, month, and quarter, and who does it.

Hourly

Decide what the bots check every hour, like new requests and anything urgent.

Daily

Decide what the bots run each morning, and when people check in.

Weekly

Decide when the board gets reviewed and the knowledge base gets updated.

Monthly

Decide when customers get asked and the measures get pulled.

Quarterly

Decide when results get held up to the baseline and the dream.

How to do it

  1. Set the hourly, daily, weekly, monthly and quarterly routines for the team, humans and bots.
  2. Write the key work step by step: who does each step, person or bot, and what done looks like.
7

Measure progress Control Tower

Check how the work is going and whether the transformation is real: first the measures against the baseline, then the board.

How we measure the transformation

Five measures, each read three ways: where we started, where we are, where we’re headed. Bars show the shape, not real numbers yet.

Time given back

Hours a week moved from routine to people, dreams and invention.

Baseline
Now
Target

Right the first time

Share of outputs that pass the specialist bar with no redo.

Baseline
Now
Target

Customer wow

What customers say, and whether they come back and refer others.

Baseline
Now
Target

New things invented

Things we do now that weren’t possible before.

Baseline
Now
Target

Work that runs itself

Share of the work with written steps, readable knowledge and a bot.

Baseline
Now
Target

How to do it

  1. Perform the work, improve the team, and wow the customers, on the routines you set.
  2. Show every piece of work on one board: waiting, doing, checking, delivered.
  3. Measure against the starting baseline: time given back, right the first time, customer wow, new things invented.
  4. Quarterly: hold the measures up to the baseline and the dream, then refresh both.