Who on the Team Should See Which Numbers
Why this matters
Share too little and the crew has no way to know if they are winning, which kills the motivation that comes from seeing your own effort reflected in a real result. Share too much, particularly around pay-sensitive numbers, and you create comparisons, resentment, and conversations you did not intend to start. Most owners default to one extreme without thinking it through: either everything is a locked owner-only secret, or every number is posted on a shared board with no thought given to what it does to the room. Getting this right is a design decision, not an instinct, and it changes depending on what kind of number you are looking at.
Sort every number into one of three tiers before deciding
Instead of deciding visibility number by number in the moment, sort your numbers into a small number of standing tiers, and set the access rule once per tier.
- Whole-team numbers. Reflect collective performance or things everyone can influence together: jobs completed this week, callback rate company-wide, a safety count, a customer satisfaction score. Visible to everyone by default, because everyone had a hand in it and everyone benefits from seeing the trend.
- Individual performance numbers. Reflect one person's own output: their completed jobs, their callback rate, their close rate on estimates they gave. Visible to that person and their direct manager, not broadcast to the whole team by default.
- Owner-level numbers. Reflect the financial health of the business itself: margin, overall profitability, pay rates, cash position. Visible to the owner and whoever directly needs it to do their job (a bookkeeper, a partner), not shared broadly.
Most access mistakes come from treating all numbers as one tier when they are not. A callback rate and a margin percentage are both "numbers," but they belong in different tiers with different rules.
Individual numbers: share with the person, be careful with the room
An individual's own metric is usually good for them to see clearly and often, it is the clearest feedback loop they have on their own work. The complication is whether to show it next to everyone else's.
- Sharing a person's number with them privately, regularly: almost always a good idea. People improve faster when they can see their own trend without having to ask.
- Posting a leaderboard that ranks individuals publicly: works well on some crews and backfires badly on others. It can motivate a team that already trusts each other and turn nakedly competitive for a team that does not. If you try it, watch closely for whether it is producing healthy competition or quiet resentment, and be willing to pull it back.
- Comparing two specific people's numbers to each other in a group setting: avoid this by default. A coaching conversation about one person's number belongs in a private conversation with that person, not a group comparison that puts someone on the spot in front of peers.
Pay-adjacent numbers deserve extra caution
Any number that a crew member could reasonably connect to their own pay, a bonus threshold, a commission calculation, deserves more care than a purely operational metric, because the reaction to it is not just "how did we do," it becomes personal and financial fast.
- Be explicit about what a number does and does not determine before you share it. If a callback rate factors into a bonus and a crew member does not know that, showing them the raw number without the context invites the wrong read.
- Individual pay-adjacent numbers are for that individual and their manager. They are not whole-team numbers even if the underlying activity (like jobs completed) would otherwise be shared broadly.
Whole-team numbers work best framed as "how did we do," not "how do you compare"
When you do share a company-wide number with the crew, frame the conversation around the team's shared result, not an implicit ranking exercise. "Callback rate across the company dropped this quarter, here's what we think is driving it" invites everyone into a shared story. The same number shared without framing invites people to quietly wonder whose fault a bad quarter was, which is a very different, more defensive conversation.
When someone asks for a number you had planned to keep close
A direct question deserves a direct answer about why, not evasion. If a crew member asks to see the company's margin and you are not planning to share it broadly, say so plainly: "that's something I keep at the owner level for now, here's what I can tell you about how the business is doing instead." A clear, honest boundary preserves trust. A vague dodge or a fake number does not, and it tends to get found out eventually.
Revisit the tiers as the team grows
The right answer at three employees is not automatically the right answer at fifteen. A small, close crew can often handle more shared visibility comfortably because the relationships absorb it. A larger team with more distance between the owner and the crew usually needs tighter, more deliberate tiers, because there is less shared context to interpret a number correctly without you in the room to frame it.
References
- General practice on organizational transparency and information-sharing in small businesses
- SBA guidance on team communication and performance management for small employers
- See related: The Review Meeting That Turns Numbers Into Decisions; The Difference Between a Vanity Metric and an Operating Metric