Operational data integrity·Process maturity transformation
Bad data does not announce itself. It just spreads.
We find what is silently broken underneath. Then we build the workflow that runs on top of it.
Chapter 01·The stake
Automation does not fix a broken process. It multiplies it.
A process you have not examined can be automated exactly as it is. The result runs faster. It is also faster at whatever the process already gets wrong.
Two ways inChapter 01·The stake
We establish what is there first, in writing.
There is no patch for this. Somebody reads the file first and writes down what is actually in it. Then you decide what to build. Automating this does not change the number. It changes how quickly you reach it.
Two ways inChapter 02·The evidence
Your ageing report may be a month out, on dates that look correct.
You write day first. Your tool reads month first. The dates compute wrong. Nothing in the value says which convention was typed.
Two ways inChapter 02·The evidence
A file can reconcile cleanly and still be wrong.
This delivery was accepted. Eight of the ten faults were in it. Two of the eight cannot be recovered from this copy. Those need a fresh extract from the source.
Two ways inChapter 03·The result
Every operation runs the same seven stages.
Work arrives, gets made, gets checked, gets approved, gets filed, gets kept, and gets counted. One question per stage.
Two ways inWhat stands behind it
Kudrat Lokman
Bank Negara Malaysia·The Wharton School·COO, building the world's first AI-native takaful operator
- Ten named faults
- A library of broken files
- Three house rules
- Eight controls for letting AI near your data
- Seven stages every operation runs
7 Questions
Where does yours sit
One question per stage. Answer all seven, tell us where to send the result, and it appears here and in your inbox. Apex keeps a copy.
The ladder: every stage sits on it. These seven questions reach L4.
- L1Ad hocDepends on who is on shift. No defined method.
- L2RepeatableA method exists, informally. Results vary by person.
- L3DefinedDocumented, published, actually followed.
- L4InstrumentedThe process emits data about itself.
- L5Self-improvingThat data drives change on a cadence.
- –Intake
- –Making
- –Proofing
- –Authorisation
- –Custody
- –Tracking
- –Scorekeeping
Answer all seven to see an indicative level.
Which door do you want to talk about?
Your address, your seven answers and the door you picked go to Apex Performance, and a copy of the result goes to you. Nothing else is kept, and none of it is passed on.
Sent.
Built on public maturity-model norms: the CMMI level structure and ISO 9001 process discipline. The custody standard is read against published data-protection law: the PDPA 2010 in Malaysia, the GDPR in Europe, and HIPAA where health information is held. It reproduces no vendor's instrument and no client's material. We do not quote peer benchmarks we do not hold.
Two ways in
Find out where you actually stand. And what to move first. Whether or not you do it with us.
-
The AssessmentNinety minutes with whoever actually runs the operation.▸
You leave with a level you can defend. You leave knowing which of the seven stages is weakest, and why it is the one to move first. And where your reporting and your data disagree, if they do. Ninety minutes with whoever actually runs the operation. The seven questions take your word for it. This one does not.
Guided, by invitation. Not self-serve.
build@apexperformance.my -
The BlueprintIt starts with three days inside the operation and two weeks inside the data.▸
The thing you have been meaning to build, designed as if you were starting today. It starts with three days inside the operation and two weeks inside the data. That ends in an implementation plan: what to build, and in what order. Then it gets built, with named human approval points.
Starts with the seven free questions. Either door stands alone.
build@apexperformance.my - 7 QuestionsOne question per stage.▸
- Write to usbuild@apexperformance.my↗