How to write a one-page AI use policy for your team
A long AI policy nobody reads protects nobody. Here is how to write one page your team will actually follow, section by section, with wording you can adapt today.
5 min read
Articles by topic
Step-by-step guides you can use this week: map a process, write an AI policy, brief a supplier and measure what an automation saves.
A long AI policy nobody reads protects nobody. Here is how to write one page your team will actually follow, section by section, with wording you can adapt today.
5 min read
Most growing businesses pay for software nobody uses, licences nobody needs and two tools doing the same job. Here is a four-hour method to find all of it, with a simple table to fill in and a verdict for every application.
6 min read
Most software buying goes wrong before the first demo, because nobody wrote down what the system actually had to do. Here is how to write a short, testable requirements list and use it to score suppliers fairly.
7 min read
You do not need special software or a consultant to see where a process leaks time. You need the right people, a wall, sticky notes and four hours. Here is the method I use.
5 min read
Three quotes that cannot be compared are worse than one. Here is how to write a short brief that makes suppliers price the same thing, and shows you who actually understood the problem.
5 min read
'It feels quicker' is not a business case. Here is a simple way to set a baseline before you automate, measure honestly afterwards, and report the result your board will believe.
5 min read
Next step
In 30 minutes you'll know whether to fix it, buy it, build it or leave it. No pitch deck.