The intuition that a wireless device spends its battery talking is almost always wrong. A field device — a tracker, a sensor, a meter — transmits for seconds and sleeps for hours or days, so the current it draws while doing nothing dominates the total. A few microamps of avoidable sleep current, drawn continuously, outweighs the entire energy of a year's transmissions. That is why the datasheet's active-mode figure barely matters and its omissions — real quiescent current, brown-out behaviour, how cleanly a peripheral actually powers down — matter enormously.
So the design starts as an energy budget, not a feature list. Every event — a wake, a sensor read, a location fix, a transmission, a return to sleep — is accounted in microamp-hours, and the sum against the battery capacity is what sets the achievable reporting rate and life. Location is usually the surprise: a satellite fix can cost more energy than a day of everything else, which turns when and whether to acquire one into a battery decision rather than a feature toggle. And every wake carries a fixed overhead, so waking twice as often can cost far more than twice the energy.
The battery itself is not a constant, which is where lab results and field results diverge. Capacity falls in the cold and sags under pulse load, so a cell that comfortably lasts on the bench can fail in winter if the current pulses were not modelled. And because a three-year life cannot be tested in three years, it has to be proven by measuring the energy of each event, combining it with the duty cycle and a temperature-aware battery model, and projecting — a projection that is only as honest as the measured sleep current behind it.