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 →For Accounts & Finance
Your team knows every supplier, every payment term and every odd exception. AI takes the matching, the tracking and the first draft of the chasing, so that knowledge goes into the checks.
Every payment has to be tracked by hand against the purchase order it belongs to.
One customer payment clears three invoices, and someone has to work out which three.
The bank statement is a few sen out, and the search runs into the evening.
An assistant accounts manager at an engineering and construction firm was tracking purchase orders and payments by hand, line by line. In coaching, the manager built a register that reads the company's project board and lists every order with its payment status. Tracking used to happen when there was time. Now it runs with one click.
The manager checks every payment trigger, and the financial controller reviews the register. Today it reads the board's own fields; reading the attached documents is the next step.
Participants reconcile card statements against receipts on a practice pack: match each charge, flag the ones that don't fit, and draft the query email for a person to send. Then they save the steps as an instruction file, ready for next month.
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 →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 →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 →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 →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 →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 →Come and watch
Live AI seminar · Friday 27 November, 10am to 12pm, Petaling Jaya.A live two-hour AI seminar in Petaling Jaya. Dates are announced to people who ask.