Skip to main content

Articles

Ideas worth keeping, not just publishing

Workflows

2 min article

01

Audit a Workflow Before Adding AI

Check how work starts, what counts as finished, and whether every step belongs before adding AI to the process.

Write down every way the workflow starts.

  • Write down every way the workflow starts.
  • Define the result that makes the workflow complete.
Read article

AI

2 min article

02

Four Human Skills Worth Keeping in Your AI Workflow

A thought experiment for recognising the value of your skills, and four responsibilities to keep human when AI does more of the work.

Your existing skills have value even when you struggle to name them

  • Your existing skills have value even when you struggle to name them
  • Keep human judgment, ownership, communication and follow-through in the work
Read article

AI implementation

2 min article

03

Reduce the AI Blast Radius

A practical way to introduce AI without putting too much time, data, or trust at risk all at once.

Start with one small task so the cost of a mistake stays manageable.

  • Start with one small task so the cost of a mistake stays manageable.
  • Put guardrails and policies around what the AI can do.
Read article

AI agents

2 min article

04

Give Every AI Agent a Job, Authority, and Review

Use the JAR framework to define an AI agent's responsibility, boundaries, and review schedule before trusting it with business work.

Define one specific job for the agent.

  • Define one specific job for the agent.
  • Set clear limits on what the agent may discuss and with whom.
Read article

Automation

2 min article

05

Three Tests for a Useful Automation

Check whether an automation saves time, improves decisions, and produces a measurable business result.

Measure the time an automation gives back.

  • Measure the time an automation gives back.
  • Check whether it provides information that improves a real decision.
Read article

Change management

2 min article

06

Rebuild Trust in Technology With Smaller Changes

Acknowledge where past technology projects went wrong, then rebuild confidence through small changes with visible outcomes.

Talk openly about the failed project and the scar tissue it left behind.

  • Talk openly about the failed project and the scar tissue it left behind.
  • Start with a change small enough for the team to absorb and evaluate.
Read article

Operations

2 min article

07

Build Workflows That Buy Back Your Time

Use batching, a repeatable process, and clear format constraints to get more useful work from the same amount of time.

A useful workflow helps the same block of time produce more.

  • A useful workflow helps the same block of time produce more.
  • Batch similar work and put clear constraints around the format.
Read article

Operations

2 min article

08

A Workflow Gives You Something You Can Schedule

Put recurring work on paper so you can schedule it, improve it, delegate it, or hand the right parts to AI.

Turn recurring tasks into visible units of work.

  • Turn recurring tasks into visible units of work.
  • Schedule defined work instead of reacting to every new email.
Read article

Operations

2 min article

09

Workflows Are Easier to Map Than They Look

A practical way to map recurring work, then decide what to schedule, delegate, keep, or stop doing.

Start with one trigger, the steps that follow, and a clear outcome.

  • Start with one trigger, the steps that follow, and a clear outcome.
  • Use the map to question repetitive work instead of accepting it by default.
Read article
Canadian Owned. Canadian Operated.