Notes

Little notes from the training room.

One short, practical idea every two weeks, for business owners and their teams. Each one comes from something that happened in a class.

All notes, newest first

  • People14 Nov 2026

    The seven levels of using AI at work

    AI use at work grows through seven levels: ask, think, produce, systemize, replicate, govern, evolve. The first three are things you do, the next four are things you build, and most teams are on the first three. The useful next step is moving one task that worked from level 3 to level 4, so it runs again next month without being rebuilt.

    Read it →
  • Technology02 Nov 2026

    AI can read the screenshots your customers send

    Feedback that arrives as phone screenshots can go to AI exactly as it is. AI reads the images, sorts faults from suggestions, and a person decides what changes. In one real round, three fixes were running on a test copy the same morning.

    Read it →
  • Process12 Oct 2026

    Fix it before you automate it

    Automation runs whatever version of the task it is given. A quick test tells you whether a task is ready — and getting it ready is usually smaller work than people expect.

    Read it →
  • People02 Oct 2026

    It guessed because you didn't say

    When AI gives you a generic answer, it has usually filled the details you left out with its best guess. Telling it the details you care about changes the answer.

    Read it →
  • People26 Sep 2026

    When AI tools change, your team's skills stay

    AI tools keep changing. The skills a team builds, such as breaking work into steps, briefing AI clearly and checking what comes back, carry over to every new tool, which makes them the investment that lasts.

    Read it →
  • Process19 Sep 2026

    Hand AI the boring task first

    The best first task for AI is a routine one: it comes back every week, you could write its steps down, and you can check the answer. The impressive one can come later.

    Read it →
  • People09 Sep 2026

    Five skills for getting good results from AI

    Getting good results from AI comes down to five skills: break the task down, give it the context, set the limits, refine the draft, and judge the result. When an answer disappoints, the missing skill tells you what to fix.

    Read it →
  • Process02 Sep 2026

    Keep your AI instructions in a file

    The instructions you give AI for a repeated task are worth keeping in a plain document. Use the file every time, update it whenever you correct a result, and the task gets better with every run, whoever on the team runs it.

    Read it →
  • Process19 Aug 2026

    Split AI work into asking, doing and checking

    AI work goes better with three roles kept apart: you decide and write down what good looks like, a fresh AI session does the work from that instruction alone, and someone with no stake in the result checks it against your description.

    Read it →
  • Technology05 Aug 2026

    AI can be confidently wrong

    AI writes by predicting what fits, so it can give an answer that is specific, fluent and wrong. Treat every AI answer as a draft, and check the parts that carry weight, such as numbers, references and names, before you rely on it.

    Read it →
  • People15 Jul 2026

    Brief AI the way you'd brief a person

    Search engines taught us to type a few keywords. AI works from meaning, so it gives better answers when you describe the situation and what the result is for, in plain sentences, the way you would brief a person.

    Read it →
  • People01 Jul 2026

    Build what only you can build

    AI now lets almost anyone build software, senior leaders included. For a leader, the most valuable hours usually still go into direction: deciding what should be built, and why.

    Read it →
  • People24 Jun 2026

    Three permissions your team needs to use AI

    Teams take up AI when they feel free to use it the way it works best: to ask basic questions, to hand it the effort, and to keep asking for a better answer. A manager can grant all three in one sentence.

    Read it →