M28BuildTechnology· Module 4
Automation
Skilled staff spend hours re-typing, copying and chasing. The work is routine, but no one has designed it away.
- Grow
- Scale
- Fix
- Technology
- Operations
- ~5 min · Matrix
The business problem
Routine work — re-entering orders, sending reminders, compiling reports, reconciling payments — consumes time and introduces errors. Businesses either ignore automation or try to automate processes that are still unstable, which only makes errors faster.
Why it matters
Well-chosen automation frees capacity, reduces errors and makes processes consistent. The key is choosing stable, high-volume, rule-based work first.
What you will learn
- Identify tasks suitable for automation
- Stabilise and simplify a process before automating it
- Choose appropriate tools: built-in features, integration platforms, scripts
- Measure the value of automation
Core questions
- Which tasks are repeated, rule-based and high-volume?
- Is the process stable enough to automate?
- What happens when the automation fails?
- How much time and error will it save?
Work through the module
CaseWhat is happening?
Property management firm, 12 people · Illustrative teaching case
Staff send hundreds of rent reminders by hand each month and reconcile M-Pesa payments against a spreadsheet. The firm standardises the reminder schedule, then automates reminders and payment matching using features in its existing accounting system. Staff time moves to handling exceptions and tenant issues.
DecisionWhat does the leader need to decide?
Hire another administrator, or standardise and automate the routine work?
FrameworkHow should they think about the problem?
Simplify → standardise → automate
Remove unnecessary steps first. Standardise what remains so it follows rules. Then automate. Keep humans on exceptions and judgement. Always design what happens when the automation fails.
ToolWhat can they use?
Automation opportunity scorecardMatrix
- List routine tasks and hours per month
- Score each: volume, rule-based, stable, error-prone
- Estimate hours saved
- Note the failure plan for each
ApplicationHow does it apply to their business?
Apply it to your own business:
- Ask each team to list their most repetitive tasks
- Score them on the scorecard
- Pick one stable, high-volume task
ImplementationWhat changes?
What should change in the business:
- Simplify and standardise the chosen process
- Automate it with existing tools first
- Monitor exceptions and failures
ReviewDid it work?
How to tell whether the change worked:
- How many hours per month were released?
- Did error rates fall?
- Is the released time being used on higher-value work?
After this module you should be able to decide
Hire another administrator, or standardise and automate the routine work?
And leave with: A prioritised list of automation opportunities.
Sequence · Technology
Related modules
Part of these learning paths