Coaching, not surveillance · what a manager can and cannot see
No surveillance.
A junior ships a clean PR and the tests pass. You still do not know whether they understood it. This page is the line between a coaching signal and a watchtower, written down.
Configuration and goals. Never scores.
Someone has to set the rep up: which channel it lands in, when it closes, which skills a team is aiming at. Setup is the whole of what an admin gets.
The admin Hub
- Holds
- Slack setup, channel routing, close scheduling, skill goals, workspace billing, who is on the roster, and which skills each engineer is aimed at.
- Never holds
- A score, an accuracy figure, an answer history, or a view of who has been practicing.
The channel everyone reads
- Holds
- The question, and what it was about.
- Never holds
- Scores, accuracy figures, or a count of how many people answered. In a team of six, how many answered is a fact about named people.
Your own numbers
- Holds
- Your answers, your accuracy, your streak. Visible to you, on every plan.
- Never holds
- A manager's view of any of them, on any plan we sell.
The one exception
The whole product holds exactly one team-shaped figure, the Slack leaderboard, and it is yours to control. Only the person who asks for it sees it. It stays hidden until 3 distinct people have answered, the same floor stated in the privacy policy. You appear as an anonymous handle like Player-1234 unless you choose a public name. When a manager sets a skill expectation, that is a goal they wrote, not a window into your work.
Team buys practice depth, not visibility into people: on-demand practice curated for each engineer, every domain open, more channels. No plan we sell shows a manager individual answers. If that ever changes, this page and our privacy policy change first, in writing, before a single customer gets the feature, and we will email every existing customer when they do.
The count
Stated here · enforced in the privacy policyA promise is only worth its smallest number.
- 0HR and compensation integrationsNo connector exists, and none is planned.
- 1Team-shaped figure in the whole productThe Slack leaderboard, hidden until 3 people have answered.
- YouEveryone who can see your scoresYour answers, accuracy and streaks, on every plan.
Four things we will not build.
Every measurement tool has two faces, the way yin carries yang: the same signal that coaches can be turned to rank, the same leaderboard that celebrates can be turned to shame. We do not pretend the dark face away. We design for the light one and refuse to build the dark one.
- 01
Celebrate practice, never punish gaps
The surfaces we build make showing up feel good: streaks, daily reps, the scoreboard of a live game among the people playing it. What we will not build is the inverse: automated messages naming whoever scored worst, shame columns, worst-of-the-week posts. A gap is a training target, not a verdict.
- 02
No HR or compensation exports
Atomic Reps does not connect to Workday, Lattice, BambooHR, Greenhouse, compensation tools, or performance-management systems. Practice signal stays inside Atomic Reps. There is no export designed to feed a review cycle, and we will not build one.
- 03
No automated peer-shaming surfaces
We will not ship a message that says someone scored worst this week. We will not name individuals as outliers in any rollup. A live game scoreboard stays in the room where the game was played; it never becomes a standing record posted to the channel.
- 04
Tool, not enforcement
Atomic Reps declares its intent and designs for the good case: coaching input, onboarding diagnosis, a team deciding what to train next. We refuse to build the punitive surfaces above, and past that line we trust the people on the other end. A tool cannot legislate how it is held, but it can refuse to be shaped like a weapon.
And if we are acquired or wind down? Who runs this, the notice period, and your export window are already written down on the continuity page.
The loop belongs to the people inside it.
A rep that is wrong for your systems is a bug in the question, not a gap in you.
Senior engineers can challenge a question that feels wrong for the way their team builds, and a childish or surface-level rep is something we want reported. The point is a tighter loop and a more useful signal for the team, never a test that seniors have to pass.
Written down, then enforced.
The position
Honour is one of the values the product was built on. This page is that value turned into a product boundary.
The enforcement
Security and the privacy policy carry the mechanisms and the floors these commitments rest on.
We sell this product. Read the commitments above as a position we can be held to, not as a neutral report.
AtomicReps30″Coaching, not surveillance
We celebrate the reps, never the ranking.