Product
Four layers, one promise.
Help the individual communicate. Help the organization understand. Do not turn the individual into the data product. The third clause is what makes the first two compatible, and it is the only one that has to hold under pressure.
How it works, end to endWhat HABLA™ does, and what it refuses to do
The four layers
- SPEAK — Recognize what you are carrying in plain language.
- SAY — Get words you can actually use to begin the conversation.
- CONNECT — Choose a human or resource when you are ready.
- LISTEN — Give leadership aggregate signals without an individual behavioral profile.
Three layers for a person, one for an organization.
Three layers for a person, one for an organization
Three of them belong to a person, one belongs to an organization, and the design of the fourth is constrained by the first three rather than the other way round.
The four layers
Recognize, get words, choose a human, and give leadership an aggregate signal.
-
Recognize what you are carrying in plain language. You never have to write your situation out: the statements are offered, not typed.
-
Get words you can actually use to begin the conversation.
-
Choose a human or resource when you are ready. Skipping this step is a complete way to use HABLA.
-
What rises from the lane to this rule is a count. A person’s own path stops wherever they stop it, and what crosses this line is the count rather than the path — the organization receives how often a topic was named, never a route through the layers.
-
Give leadership aggregate signals without an individual behavioral profile. This is the only layer the organization sees.
SPEAK
Recognize what you are carrying in plain language.
SAY
Get words you can actually use to begin the conversation.
CONNECT
Choose a human or resource when you are ready.
LISTEN
Give leadership aggregate signals without an individual behavioral profile.
One system, described from both ends.
These two descriptions have to fit together exactly. If the person's account of HABLA and the organization's account of HABLA can both be true at once, the product is honest; if they cannot, one of them is a sales document. Each has its own page, at the same depth.
If you are the one using it
Words, resources, and a decision that stays yours
No account and no app to install. Statements to choose from rather than a text box. Language you could actually use, the points of help your organization has listed, and crisis resources that cannot be removed. Reaching out is a separate, deliberate step — and skipping it is a complete way to use HABLA.
If you are the one accountable for it
Which topics keep reaching the surface, and what moved
HABLA reports reportable topic activity, compared against an equivalent earlier period, with two independent floors underneath every value and the limits of each figure printed beside it. It connects a signal to the organization’s own decision record — among its fields, a question, a decision and an owner — without creating a case file about anyone.
The boundary between the two cards is not a policy that sits between them. It is the absence of a key: anonymous activity and voluntary contact identity are separate systems, and there is nothing to join them on.
What is deliberately absent
Each of these would be straightforward to build and would make a demo more impressive. Every one of them is refused, and the refusals are the reason the rest can be trusted.
What leadership never receives
- User profiles
- Individual risk scores
- Anonymous narrative files
- Session history
- Raw anonymous exports
- A “high-risk employee/student” list
- Per-person engagement dashboards
What HABLA deliberately does not build
The absent things are absent by architecture. What remains is an aggregate signal.
-
What remains, and what leadership actually needs: which topics keep surfacing.
-
Never built. There is no account for one to hang from.
-
Never computed. HABLA makes no clinical or predictive judgement about a person.
-
Never kept. Nothing identifies a return visit as the same person.
-
The shapes inside this boundary are drawn as the objects that would have been built. Each interior is blank because the object was never made, and one side of the boundary is missing because it encloses an absence rather than a reserve.
Three domains. No key between them.
Anonymous activity, voluntary contact identity, and what a customer configured are three separate systems. Configuration is read by both of the others; nothing is read across between them, because no identifier exists that would make such a read possible. This is architecture rather than policy, which is what makes it hold when someone senior asks for an exception.
How the separation works, domain by domain · How HABLA counts, and what it refuses to infer
The question a walkthrough answers is whether the boundary holds.
Bring the hardest version of it — the request your organization would eventually make. The useful part of the conversation is where the answer is no.