Private-by-Default: How to Use Wearable Data Without Betraying Your Team

There is a version of physiology-first sales performance that I refuse to build, and it is the version enterprises ask for most often: give managers a dashboard of their team's sleep and recovery data.

The request is usually well-intentioned. A leader sees a rep struggling, wants an early signal, and reasons that recovery data would help them intervene sooner. What actually happens is that the data becomes a performance artifact. Once a number can affect your standing, you manage the number. People learn to game recovery scores the way they learned to game activity metrics, and the signal you wanted disappears within a quarter.

So the boundary is architectural, not cultural. Physiology data stays with the participant. It is not exported, not aggregated to a named individual, and not available to anyone in the reporting line. In our pilots, the vendor contract says so, the data map says so, and the council reviews the boundary annually.

What managers see instead is behavior: next-step rate, mutual action plan adoption, call-review quality, forecast accuracy. These are the things a manager can legitimately coach. Nobody needs to know your heart rate variability to observe that your last four discovery calls ended without a date attached.

There is a second reason for the boundary beyond ethics. Individual physiology data is noisy and easy to misread. Trend matters; single days rarely do. Handing a manager a number they are not trained to interpret produces confident, wrong conversations.

Use your own data as trend, not verdict. Look at it weekly rather than daily. If a score would change what you do today, act on it; if it would only change how you feel about yourself today, close the app.

Opting out of physiology tracking entirely has to preserve employment, standing, and territory. If it does not, you do not have a program. You have a condition of work.