“We trained forty people. I cannot tell you what changed.”
The rule it became
Competence is proven on a real problem, not in a classroom.
What the system does
Competency is assessed against a published standard, not by attendance.
For CI teams
Improvement, run as a system.
Every idea, every gate, every saving — one witnessed record.
Idea raisedSalma Al Habsi, Warehouse. 3 March
Charter approvedSponsor: Badar Al Siyabi. 12 March
Improvement signedCoach: Eman Al Kindi. 2 June
Measured, with the sponsorWaiting for a signature since 28 September
Verified by financeOMR 3,100 counts from this signature, not before
What the system does
- Every step signed and dated
- Arabic is not a translation layer
- Savings count only when finance signs
- Your data stays where you are
- No AI decides for you
- You set the roles and approvals
- Evidence over activity
- Built in Muscat
Founding clients
We are onboarding our first organisations now. Ask about joining as a founding client.
Ask about joiningAccredited
Tahseen is an LCS Accredited Certifier, and its Lean programs are delivered by an LCS Approved Trainer.
About the Lean Competency System ↗The continuous improvement platform for CI teams in Gulf private, government and semi-governmental organisations and entities
Every rule began as something that went wrong.
The platform holds the people, the delivery and the behaviours in one record — and lets nothing count as a benefit until a named person in finance has accepted it.
Each rule below was learned in a real program before it was written into the software. The system now holds the line that people and spreadsheets could not.
“Every project reports a saving. Finance recognises none of them.”
The rule it became
Nothing is a benefit until a named person in finance accepts it.
What the system does
Committed and verified sit side by side, and only a named verifier moves a saving across. By standard, the person who claimed it cannot verify it; if your rules allow it, the record marks it self-verified.
“The ideas come in. Nobody knows who is holding them.”
The rule it became
Every idea has an owner, and a status the person who raised it can see.
What the system does
The QR form gives the submitter a status link. No saving or amount is ever shown on it.
“The dashboard is green and the gate was never passed.”
The rule it became
A gate is passed only when a named person signs it, in order.
What the system does
Each step is signed by the people your organisation names for it, coach then sponsor by standard. A step you set to need no signature says so on the record.
“The last audit found the same problem we closed last year.”
The rule it became
A project is not closed until its result is shared.
What the system does
The standard project road ends at Close, celebrate and share, so the next team starts from what was learned.
No client or employer is named here. The lessons are the author’s; the programs stay confidential.
Develop the people · govern the delivery · embed the beliefs
So improvement does not depend on us being in the room.
01
Improvement projects
Capable practitioners, developed on real problems rather than in a classroom, with competency assessed against a published standard.
Read about this cycle: Improvement projects02
Project management
Charter to close on one road: method-driven milestones, coach-then-sponsor approvals, and a saving that is never self-certified without the record saying so.
Read about this cycle: Project management03
Change management
Belief, thought, feeling, behaviour (BTFA). Change is easy; sustaining it is the real task, and the system is built for the second part.
Read about this cycle: Change managementThe record, as your staff see it.
The same screens in Arabic and English, on a desk or on a phone. Choose a screen to look closer.
Committed against verified, by department. The gap between the two is the whole reason the system exists.
Every idea from the floor, scored on the same questions, with the person holding it named.
Screens from the sample organisation. Every name and figure in them is invented.
Set it to how you work. The record still tells the truth.
Every organisation runs improvement its own way. Switch on the parts you use, choose who signs each step, and decide how strict to be. Whatever you choose, the record shows what actually happened.
- The parts you use
- Switch a module off and it leaves the menus. Its records are kept, and switching it back on brings everything back.
- Your road for projects
- Offer Lean, Lean Six Sigma or both. For each step, decide whether a file must be attached and who must approve before the project moves on.
- Who may also act
- Keep leader, coach, sponsor and verifier apart, or loosen a rule where you must. A saving verified by the person who claimed it is marked for everyone to see.
- Written reasons
- Choose which acts need a written reason and how long it must be. The button waits until the rule is met.
- Reminders
- The person whose turn it is gets a reminder after the working days you set, three times at most.
- Recognition
- Points, awards and certificates of appreciation printed on your own design. All of it can stay off.
Four commitments
Your data stays where you are
One installation for one organisation, on your own servers or in-country hosting you choose. It sends only the e-mails you switch on, through your organisation's own mail account.
Arabic is not a translation layer
Every screen and every refusal sentence is written in Arabic and English in the same release, right-to-left by design.
Evidence over activity
A benefit is what a named verifier accepted, with the calculation attached. Everything else is still a claim.
No AI decides for you
People score, verify and sign off. No data is sent to any outside AI service, and nothing counts because a machine suggested it.
Who answers when something breaks
Your IT team
The system runs on your own servers, so your IT team is the first line. They see the server before anyone else does.
Us, directly
Your IT team reaches us directly. No call centre, no ticket passed between strangers.
The fix, on record
Every fix ships as a numbered, tested release with an install guide your team can follow.
See it with your own portfolio
Forty-five minutes in the real system, using your gates, your departments and one of your live projects.
Ask for 45 minutes- Built in
- Muscat, Sultanate of Oman
- By
- A CI practitioner of twenty-eight years, not a software house
- Who builds it
Continuous improvement is better than delayed perfection