Getting Started
What HABICUB Does, in 5 Minutes
The whole model on one page — how a competency becomes a habit, and what the platform actually does between those two points.
Most development tools answer the question what should this person know? HABICUB answers a different one: what should this person do on Thursday, and what happens after they do it?
Here is the whole model.
The chain
Competency → Manifestation → Development Goal → Development Task → MDA → Behavior → HabitRead it left to right and each step gets smaller and more concrete.
A competency is the capability you want — “gives developmental feedback”. Too abstract to practise directly. A manifestation is what that competency looks like when someone has it. A Development Goal is the outcome for this person this quarter. A Development Task is a piece of work that moves them toward it. And an MDA — a Micro Development Action — is one specific thing to do, on one specific day, that takes minutes rather than hours.
Behavior is what happens when the MDA is performed. Habit is what happens when it has been performed enough times that it no longer needs prompting.
Everything the platform does sits between the Development Task and the Habit.
What the platform actually does
It compiles a plan into a calendar. Choose one to three competencies for a person and HABICUB compiles their Development Plan into a Development Journey: fifteen MDAs, ordered, each landing on its own date. Competency is context on an action, not a separate track — a person works one sequence, not three.
It delivers into the working week. Each MDA arrives when its day comes, in a channel the person already uses. Not a course to log into.
It does not stall. A missed action stays open and reportable, and the next one still arrives. A bad week costs one action, not the program.
It closes the loop with a person. A mentor sees what came back and replies to it. That reply is the part that makes the next attempt more likely — and it is the only high-quality evidence in the system, because a qualified human wrote it.
It measures four things, honestly. Received, opened, answered, assessed. Not “completion”.
The two progress numbers
HABICUB reports progress on two axes that legitimately disagree, and never collapses them into one:
- Progress is answered out of total — how much of the work the person has actually done.
- Phase is where the schedule has reached — Awareness, Deliberate Choice, Guided Practice, Habit Formation, Behaviour Integration.
Someone can be in Guided Practice with 40% progress. That is not a contradiction; it means the calendar has moved on and the person has not. Showing one number would have hidden exactly the situation a mentor needs to see.
Who sees what
Three roles, deliberately different views:
| Sees | |
|---|---|
| Leader (participant) | Their own journey, plan and today’s action. Their rhythm and consistency — not the system’s metrics about them. |
| Mentor | Their caseload, each person’s evidence, and the counters. Reviews and replies. |
| Line manager | The same caseload, read-only. Never the mentor’s private notes, never feedback before it is released. |
The boundary is enforced on the wire, not in the interface — a field a role should not see is absent from the response, not hidden in the page.
Where to go next
- Quick Start Guide — get a program running.
- Creating and Managing Development Programs — the design decisions that determine whether it works.
- Book a demo — see it against your own use case.