What does operations management mean for an SME?
The term has three meanings. As a discipline, it is planning, running and improving the way a company turns inputs into products and services. As a software category, it is the tools that plan and track that work. For an SME the most useful reading is the third: a knowledge question — who knows how each core process runs, who decides on exceptions, and what happens when they are not there. Methods and tools help, but only once that knowledge is captured and owned.
A short story
The owner of an engineering firm searched for “operations management” and found mostly tool comparisons. The firm chose a work-management tool and set it up in a few weeks. Tasks became visible; deadlines had owners.
The questions did not change. How do we price this variant? Who approves this deviation from the drawing? What did we promise this customer last time? They still went to the same two people, now with a task number attached. The tool made the work visible. It did not make the know-how available. (An illustrative example, not a client case.)
What are the three meanings?
| Meaning | What it covers | What it misses for an SME |
|---|---|---|
| A discipline | Planning, capacity, quality and continuous improvement | It assumes the process knowledge is already available |
| A software category | Task planning, resource tracking, ERP and service tools | It records the work, not the judgement behind it |
| A knowledge question | Core processes, owners, rules, exceptions, data and sources | It takes people's time to capture |
What goes wrong when you start with the tool?
- At set-up: the tool is configured with the tidy version of the processes
- In the first weeks: exceptions are handled outside the tool, by phone and email
- After a few months: the dashboard shows green while customers wait for the one person who knows
- In the end: the tool gets the blame and is replaced by the next one
What does good operations management look like in a small company?
- a short list of core processes, each with one owner;
- the rules and exceptions of the critical steps written down, with their source;
- two or three measures per process that the owner trusts;
- short, regular reviews, plus reviews when something changes;
- a back-up for every critical step.
None of this needs new software to start. It needs the people who know, and a structure to keep what they know.
Where do operational excellence and lean fit in?
Operational excellence and lean are ways to improve how processes run: remove waste, standardise what works, keep improving. They work best on processes that are visible and owned. In many SMEs the first improvement is simply making the know-how visible — then the improvement methods have something to work on.
That is why the approach puts capturing before improving, and improving before automating.
How MentX helps
MentX captures how your company really works: the knowledge of your key people and the processes they run. We offer both a hands-on service approach — mapping your processes and capturing the knowledge behind them, from meetings, workshops and a guided intake — and our own personality-aware knowledge base, with full source attribution, in your own Knowledge Space. We build on the tools you already use and add best-practice solutions where they fit.
In the MentX approach this is steps two to four: map your processes, capture your operations — owners, decision rules, exceptions and data, in one process model — and operational excellence, where the team runs and improves on that knowledge. The tools you run today stay; where automation fits, we work with established solutions.
What to do this quarter
- List your core processes on one page.
- Name one owner per process.
- For the most critical process, write down who decides on exceptions — and who can when that person is away.
- Check which tools already hold part of the process, and which part lives only in people.
- Decide what to capture first.
