Share the Numbers With the Whole Team or Keep Them Owner-Only: Decision Tree

Why this matters

Owners split hard on this one. Some post every number on a break-room screen; others keep the whole picture locked in their own head and hand out only vague reassurance. Both extremes cause real damage: total secrecy breeds distrust and lets a slipping crew coast on a false sense of security, and total transparency without framing can leak sensitive figures, spark comparison and resentment between techs, or hand a departing employee a map of exactly where the business is weak. The right answer is not "share everything" or "share nothing," it is a metric-by-metric call. This tree walks it.

Start here: separate the metric from the moment

Before deciding who sees a number, split the question in two: is this metric fine to share with the team in general, and is right now the right moment to share it. A metric can be a good long-term share and a bad one to reveal in the middle of a tense week. Work through the metric question first.

Step 1: Would sharing this number change behavior for the better

The best reason to share a metric with the crew is that seeing it makes people work smarter, not just work harder or feel judged. Ask what a technician would actually do differently if they saw it.

• If seeing the number gives someone a way to improve their own work (their own callback rate, their own on-time percentage, their own completion count), sharing it, at least with that individual, usually helps. People respond to seeing their own performance far better than they respond to being told about it secondhand.
• If the number is something nobody on the crew can influence (overall company profitability, an owner's personal financial exposure, executive compensation), sharing it does not change anyone's Monday morning behavior. It either creates anxiety with no lever to pull, or invites a debate the team has no standing to resolve. Keep this tier owner-level, or share only a summary framed as "the business is healthy" rather than the raw figure.

Step 2: Check whether the number identifies or ranks individual people

This is the fork that causes the most damage when handled carelessly.

If a shared metric is aggregate (team-wide close rate, shop-wide on-time percentage, overall completion count), post it. Nobody is exposed, and the whole crew can rally around a shared number the same way a team rallies around a shared scoreboard.

If a shared metric names or ranks individuals (a leaderboard of who closed the most jobs, whose callback rate is worst), stop and think harder before posting it publicly. Individual performance data motivates some people and humiliates others, and a public ranking often rewards the wrong behavior: a tech who rushes to look good on the board over one who does the job right. The safer default is to share individual numbers privately, one-on-one, where they function as coaching, not comparison. If you do want a public leaderboard, use it only for a metric where fast-and-visible genuinely correlates with good work, and watch closely for gaming once it goes up. See related: A Metric Is Easy to Game and Someone Is Gaming It.

Step 3: Check whether the number is sensitive competitively or personally

Some figures carry risk beyond "did it change behavior."

• Pricing structure, margin, and vendor cost details are the kind of information that walks out the door with an employee who leaves for a competitor or starts a side business. Keep true margin and cost figures owner-level; share simplified versions (a target percentage, not the underlying cost breakdown) if the team needs a number to aim for.
• Anything tied to a specific customer's private details (what a particular account pays, a customer's payment history) should never be broadcast regardless of how it affects morale. This is a confidentiality issue, not a motivation issue.
• A number reflecting badly on a named person's mistake (a specific botched job, a specific customer complaint tied to one name) belongs in a private conversation with that person, not a team-wide share, even if the underlying trend is worth discussing in aggregate.

Step 4: If you are still unsure, default to the framed summary

When a metric fails none of the above tests cleanly but still feels borderline, the safe middle path is not silence, it is translation. Share the conclusion the number supports without handing over the raw figure: "We're behind where we want to be on getting invoices out fast, let's tighten that up this month" carries the message without exposing exact days-to-invoice or dollar amounts. This gives the team direction without opening a debate about a number they cannot fully interpret anyway.

The recap

Ask first whether sharing the number gives someone a lever to pull. Check whether it identifies or ranks an individual, and if so, favor private over public. Screen out anything competitively or personally sensitive and keep that owner-level. When genuinely unsure, share the framed conclusion, not the raw number. The team does not need to see everything you see to trust that you are steering well; they need to see the numbers that help them do their own job better.

References

• U.S. Small Business Administration (SBA), small business management and team communication practices
• Trade-standard practice for field-service performance transparency
• See related: A Metric Is Easy to Game and Someone Is Gaming It; The Review Meeting That Turns Numbers Into Decisions