erpkaizen

About

Why this exists

The writing on erpkaizen.com exists to argue one thing: an enterprise system is where a company stores its own understanding of itself, and the value of improving it is something you can measure.

Most arguments about ERP stop at adjectives: easier, cleaner, more modern. None of those survive a budget meeting. This site goes the other way — every piece has to say what was measured, how, and against which baseline.

The problem

On go-live day the process freezes into the shape imagined by people who sat in a meeting room months earlier. The business keeps learning every day after that — the season shifts, customers ask for something different, somebody finds a faster way — and the software learns nothing.

That gap gets filled with spreadsheets outside the system, with conventions passed around by word of mouth, and with users quietly adapting to a screen that makes them work in the wrong order. Nobody files a bug, because nothing reports one.

A static system and a compounding one

Static system

  • Configuration frozen at implementation
  • Adding a product type means editing source
  • Users adapt to the software
  • Knowledge lives in the heads of long-timers
  • Success measured as "it went live"

Compounding system

  • Business rules are data, editable in the app
  • Adding a product type is adding a catalogue row
  • The software adapts to how work is really done
  • Knowledge lives in the system and survives departures
  • Success measured as a measured improvement

What is a UI improvement worth?

This is the question most places avoid, because it sounds unmeasurable. It is measurable — as long as you measure before you change anything. A real example of the shape, with illustrative numbers:

TaskCreating a delivery note
Times per day40 notes
Time before the change95 seconds / note
Time after the change38 seconds / note
Per day40 × 57 = 38 minutes
Per year (250 working days)158 hours
In person-days≈ 19.8 days
What makes this number mean anything:a baseline taken before the change, on the same group of users and in the same season. Without a baseline, every number after it is just a story.

Time on task is only the easiest measure. The others are usually worth more: the share of entries keyed wrong and redone, documents abandoned half-finished, the number of times somebody has to ask a colleague before they can continue, and the lag from something happening to it appearing in a report.

Four strands

  1. Concrete improvements. Real cases: how one screen, one field or one flow changed, and what that changed for the person using it.
  2. Measuring the value. What to measure, how to baseline it, and how to separate the improvement caused by the change from the one caused by the season. The hard half, and the reason this site exists.
  3. ERP that is usable. Against the assumption that enterprise software has to be hostile, and that users owe it their patience.
  4. Improvement as the operating model. How the software absorbs what the business learns, release after release, instead of freezing the process on acceptance day.

Three rules

  1. A piece without a measurement is an opinion piece.
  2. Numbers taken from a client system are always anonymised. No company name, no absolute revenue. A ratio carries the argument; the client's tonnage does not.
  3. The articles sell nothing. No article ends in a book-a-demo button; the services are described separately, in Vietnamese.

Who writes this

The articles are written by Nguyễn Hoàng Long, a senior ERP and business-management consultant with more than 20 years of experience. Figures come either from clients' live systems (anonymised) or are illustrative; the label at the top of each piece says which.

What is here comes out of real work implementing and improving ERP for Vietnamese companies. The practices behind this publication are NextStar and DigiNext. The writing keeps its own rule: if an idea here is useful, it is useful even if you never contact anybody.