The executive case
You cannot fix what you only learn about after someone speaks up.
Most of what an organization learns about its people arrives through channels that require someone to already be willing to speak: the form, the call, the counselor, HR, the EAP. HABLA™ is built for what happens before that — and it turns what surfaces into something a leadership team can put on an agenda.
The question this page answers
Did the thing we changed do anything?
Your decisions and actions are recorded against the periods either side of them. HABLA will not claim your action caused the change — but it shows you what moved, and when, and what you did.
What you hear, what you do not, and what changes.
The middle row is the one worth arguing about. It is not a claim about the people an organization serves — it is a property of the channels above it, and you can check it against your own.
| The state | What a leadership team can see |
|---|---|
| Before HABLA | What you already hear: the people who submit the form, make the call, visit the counselor, contact HR, or use the EAP. That is a real signal, and it is the one your organization is already acting on. |
| Still without HABLA | What you do not hear: the moment before that, when someone knows something is wrong but may not know what to say, who to approach, or what will happen if they speak. Each of those channels is only reached by someone already willing to use it, so what the rest are carrying does not arrive through them. |
| With HABLA | The same weeks, this year and last. Which topics moved, when access happened, and the decisions you recorded either side of a change — every figure under a floor of ten activity events. |
Five questions the first report answers
Not a count. A count is not an insight — forty-two taps on one topic tells you nothing you can act on. These are the questions the reports are built backwards from, and every one of them is a question about the organization rather than about a person.
How often it arrives is a question about your plan rather than about this page.Aggregate monthly reporting is on the list of what every plan includes, at every tier, and the periods themselves are fixed and non-overlapping. What every plan includes.
- Is this getting better or worse?
- The same weeks, this year and last, side by side. A count on its own means very little. The same count against last November — when you changed the pay cycle — is a conversation you can have with your board.
- When does this actually reach people?
- Access timing across the period: hour of day, day of week — all twenty-four hours and all seven days, the quiet ones carrying a zero rather than being left out. It arrives whole or not at all. The reporting floor is applied to each hour of each day before the month is added up, so a quiet hour arrives as a zero and the hour breakdown is published — and that zero means no activity in that hour reached the reporting floor, which is not the same as nothing having happened. What can hold the profile back is the population floor: where a wider profile published beside a narrower one would let a unit too small to report on its own be worked out by subtraction, the wider one is withheld for that period. When it does arrive and something consistently reaches people on Sunday evenings while your support line opens Monday at nine, that is a staffing decision you can make on Monday.
- Where is it surfacing?
- By site and by audience pack — which reflects the placement experience someone used, not where anyone was — wherever the population is large enough to report without narrowing toward individuals. Where it is not, the activity rolls up rather than disappearing — and where publishing the wider figure beside a narrower one would let that smaller unit be worked out by subtraction, the wider figure is held back for the period as well.
- What is going well?
- Appreciation topics sit alongside concern topics, so that a system which can only receive complaints does not teach everyone in the organization that it is a complaints system. What is going well is reported in the same shape, and under the same floors, as what is not. It is not a morale score, it does not rank your sites against each other, and it is never netted off against a concern — a period with more of one does not make less of the other.
- Did the thing we changed do anything?
- Your decisions and actions are recorded against the periods either side of them. HABLA will not claim your action caused the change — but it shows you what moved, and when, and what you did.
Measures chosen to survive being gamed
Every number an organization is judged against eventually gets managed toward. These were picked on the assumption that yours will be too.
Movement
Which topics rose and fell against the comparison period. The largest topic is usually last period’s largest topic; movement is where a decision lives.
Time to first action
Days from the close of a reporting period to a logged decision. It measures the organization — which is the only part you can actually change.
Actions closed
Decisions you recorded that reached an outcome — completed, or deliberately not pursued. Not “issues resolved”: HABLA cannot see a resolution, only what you recorded.
And four we will not report, whatever you offer for them
- Engagement rate — it would reward distress
- Unique users — HABLA cannot count people, and says so
- A wellbeing index — a composite score about human beings
- Anything attributed to a named person, team lead, or manager
The restraint is why the signal is worth having.
A system people believe is watching them produces careful answers, and careful answers are worthless to you. HABLA is built so that it cannot identify the person behind a topic — and that architectural fact is what makes the pattern you receive an honest one.
This is also the part that survives a change of leadership. Restraint written into three separate data domains with no key between them does not depend on the next executive team agreeing with this one.
That restraint is one argument written in four places, and each of them can be checked on its own before you buy anything: the architecture that keeps the data domains separate, the counting rules that suppress a value below the floor, the pricethat does not move with how much difficulty you find, and the contractthat fixes four answers whatever is offered for them.
Bring one question you cannot currently answer.
A walkthrough is most useful when it starts from something specific your organization has been unable to see. We will tell you plainly whether HABLA would show it.