Why Does It Take So Long to Produce a Quotation?
Why manufacturing quotations take days when the work takes hours, and a practical way to investigate queues, missing information and decisions before investing in AI.
Read articleTopic
Improving Work
Designing better organisational systems by removing friction, reducing waste and improving the flow of information and decisions.
The Information Factory: Why Manufacturing Improvement Shouldn't Stop at Production
The hidden information work behind quotations, approvals and orders may be limiting manufacturing performance. Learn how to investigate it.
Read articleWhy manufacturing businesses spend so much time moving information between systems
Why do manufacturing teams spend so much time checking, re-entering and chasing information? A closer look at workflows, systems and the work between them.
Read articleBefore you introduce Microsoft Copilot, get your information in order
Preparing for Microsoft 365 Copilot? Understand why information quality, SharePoint, permissions and working practices matter before adoption.
Read articleWhere human judgement belongs in an AI workflow
Why manufacturing businesses need to identify consequential decisions, evidence and authority before introducing AI into operational work.
Read articleWhy Copilot does not fix broken processes
Why Microsoft 365 Copilot often disappoints manufacturing SMEs whose information remains on network drives, and what that reveals about how their work is organised.
Read articleWhat the Workflow AI Readiness Sprint actually produces
A proposed short diagnostic engagement that examines one business workflow and identifies evidence-led improvements before committing to AI implementation.
Read articleNon-conformance triage: a worked manufacturing example
An illustrative manufacturing workflow showing how AI might assemble evidence for a quality decision without taking responsibility for disposition.
Read articleHow to find the AI-ready workflows in your business
A practical way to investigate how work happens in a manufacturing SME and decide where AI, automation or simpler changes might help.
Read articleStop looking for AI use cases
Searching for AI use cases starts with the technology. A better approach is to find valuable work that causes problems, understand what is really happening, and use AI to help investigate before deciding what should change.
Read articleDesign the work before you divide it
Once you understand how work actually happens, do not simply allocate the existing tasks between people and technology. Redesign from the outcome, decide what work is genuinely necessary, and only then determine where people, conventional automation and AI belong.
Read articleThe process map is not the work
The documented process is only part of how work gets done. Employees often compensate for gaps through checking, chasing, correcting and judgement — activity managers need to understand before deciding what to improve or automate.
Read articleAI can make bad work harder to see
AI can remove visible friction while making unnecessary or poorly designed work less likely to be questioned.
Before You Automate, Understand the Work
Automation works best when it follows a clear understanding of how work really happens, including the judgement, exceptions and friction hidden by the formal process.
Read articleWho manages the AI workers?
As businesses adopt AI agents, who manages their work? Explore agentic AI governance, delegation, human oversight and organisational accountability.
Read articleAutomation should not be the first question
Understanding real work—including exceptions, waiting and judgement—must precede decisions about what to automate.
Faster does not necessarily mean better
Automation should be assessed by its effect on organisational outcomes, not only by time saved or tasks completed.
Make judgement visible before you automate it
Making judgement visible reveals where AI can support decisions, where authority can be delegated and where humans must remain accountable.
A better sequence for automation
A disciplined automation sequence starts with observing work and defining outcomes before choosing technology or measuring system-wide effects.
Did the process work, or did the people make it work?
Successful outcomes can conceal the checking, correcting and judgement people use to compensate for weaknesses in formal processes.
What would stop working if people stopped quietly fixing things?
Invisible employee compensation can make weak processes appear healthy and must be understood before AI or automation removes it.
The five-minute check that costs 1,400 hours
Small repeated checks can consume substantial capacity, but their accumulated cost should prompt investigation rather than automatic removal.
Don’t automate the workaround
Workarounds are evidence of underlying weaknesses or legitimate needs that must be understood before their compensating work is automated.
Come back with three processes that give you grief
Prioritising valuable organisational problems keeps the intervention space wider than a portfolio framed around AI use cases.
AI should be a conclusion, not a premise
Starting with the work allows AI to emerge as an appropriate conclusion of diagnosis rather than a predetermined solution.
Tool literacy is not improvement capability
Using AI tools effectively is different from knowing what organisational work is worth improving and whether change made it better.
Reveal how your work
really works.
A first conversation is free. Start with a defined project, or discuss whether an optional diagnostic or review would help clarify the right next step.