You, specifically.
Someone at your company is rolling out HX — or thinking about it — and sent you this link. You have one question: is this bossware? Fair question. Here's the whole answer, with the marketing removed.
Five things, then you can close the tab
- 01Your work sessions in company repos get kept by the company — like the code. That part isn't about you; it's about laptops dying and knowledge walking out the door.
- 02Nobody reads your raw sessions. Not your manager, not an admin. Readable by you, and by a team you explicitly say yes to — that's the whole list.
- 03Everything above you is counted in groups of five or more. If a chart could point at you, it doesn't render.
- 04None of it can touch your performance review, your pay, or your job. That's a signed article, not a settings page.
- 05You can see who accessed data that includes you, whenever you want. The watching goes both ways.
What they see. What they never see.
“They” meaning anyone who isn't you. The left column is the whole list — and the right column is what makes the left column safe.
What the org sees
- Aggregates — team-level patterns, five people minimum
- Trends with context: what's moving, where friction sits
- Sessions you explicitly shared with your named team
- Whether the org answered your raised frictions, and how fast
What it never sees
- Your raw sessions, without your explicit, revocable yes
- Your coach conversations — those answer to you alone
- Any number about you, individually, on any dashboard
- Anything at all from personal projects on personal accounts
And the part most rollouts never say out loud: you are lock number four. Sharing your sessions with your team requires your yes — explicit, scoped to a named roster, revocable, and logged. Three layers of configuration can be perfect and nothing moves without you. Read the whole mechanism on the trust page.
What you actually get
This isn't a tax you pay so leadership gets a dashboard. Most of the value lands on your side of the glass.
A coach with receipts
Something that has actually read your work, reviews it with you, and answers to you alone. Not generic training — your sessions, your patterns, your next step.
The good kind of sharing
“Watch what it does when I ask it this way.” Sessions you choose to share with the people on your code — how craft actually spreads, on your terms.
Listening that answers
Raise a friction and it gets a visible outcome — a fix, a decision, or a reasoned no. The org publishes how long that takes. You can hold them to it.
Four questions that keep everyone honest
A faithful rollout answers all four without flinching — they're straight out of the charter. If any answer wobbles, send whoever's rolling this out to this website.