I just stepped in a puddle of something lukewarm while wearing my favorite wool socks, and frankly, it is the most honest thing that has happened to me all week. It is a sharp, immediate betrayal. One moment you are walking with purpose, and the next, your entire sensory world is centered on a damp, squelching heel. It reminds me of the exact moment a CIO realizes they’ve miscalculated their licensing requirements for a hybrid workforce. It’s that same sudden, cold realization that the ground you thought was solid is actually a mess of leaking pipes and poorly sealed joints.
‘They want the soda, but they don’t want the ceiling to stay up. People are 109 percent ridiculous.’
“
That’s where we are with the modern workplace. We want the flexibility of the ‘work from anywhere’ dream, but we are trying to build it on the licensing architecture of a 1999 call center. We are obsessed with optimization. We optimize our calendars, our Slack notifications, and our ergonomic chairs. Yet, when it comes down to the fundamental way we authorize a human being to actually do their job, we revert to a binary choice that feels like a corporate personality test: User or Device? It sounds like a technical question. It isn’t. It’s a confession of how much you actually trust the people on your payroll.
The Tax on Mobility (Sarah’s Story)
Imagine Sarah. Sarah is a high-performer. She has a desktop at the office for when she needs to focus, a laptop for when she’s ‘collaborating’ in a coffee shop, and a smartphone that she uses to check emails while waiting for her kid’s 49-minute soccer practice to end. In the eyes of a Device-based licensing model, Sarah is three people. She is a collection of hardware. To license her correctly under a device model, you have to pay for each of those entry points. It’s a tax on her mobility. It’s a financial penalty for her being exactly the kind of agile employee the HR brochure promised she could be.
Licenses Required for Sarah
License Required for Sarah
Then you have Mark’s team. They are the 29-person skeletal crew that keeps the servers humming. They don’t have assigned desks. They have a bank of 9 terminals in a darkened room that smells faintly of ozone and regret. They rotate. They hot-desk. They are the only people for whom a Device CAL makes any logical sense, because the hardware is the constant and the humans are the variables. But even then, the system feels rigged. The moment Mark tries to check a log from his tablet at home because a server is screaming at 2:39 AM, the model breaks. The bureaucracy demands a box, and Mark is refusing to stay inside it.
The Cost of Friction
I’ve seen this play out in 59 different boardrooms. The CFO looks at the spreadsheet and sees that Device CALs are cheaper on paper if you just count the workstations. But they aren’t counting the friction. They aren’t counting the 19 minutes Sarah spends every morning trying to figure out why her remote session won’t authenticate because she’s on her ‘unauthorized’ personal tablet. We are saving pennies on the license and losing dollars on the soul. It’s a classic Winter F.T. observation: ‘You saved forty-nine dollars on the bracket, but now the whole balcony is sagging. Hope you didn’t want to stand out there.’
Friction Metrics: A Quick Look
When you look at RDS CAL, you are forced to confront the reality of your floor plan. Not the physical floor plan with the stained carpets and the flickering lights, but the digital floor plan. If you choose the User CAL, you are acknowledging that the human is the center of the work. You are saying that Sarah is Sarah, whether she is at her desk or on a train. You are licensing her talent, her access, and her right to contribute. It is an expansive view. It is, dare I say, a leap of faith in the humanity of the enterprise.
The Ghost in the Machine
The User (Passport)
Assets to be empowered.
The Device (Leash)
Variables to be managed.
But many companies are terrified of that leap. They would rather manage the 1099 machines they can see and touch than the 619 humans they cannot fully control. There is a safety in the Device CAL. A device doesn’t quit to go work for a competitor. A device doesn’t need a mental health day. A device stays where you put it. Or at least, that’s the lie we tell ourselves. In reality, devices are transient, they break, they are replaced, and they are increasingly blurred with personal property. The ‘device’ is a ghost.
[The machine is a tether; the user is a pulse.]
(Metaphorical Transition)
I once asked Winter F.T. why he became an inspector. He told me it was because he hated secrets. He hated the way a builder would slap a coat of paint over a dry-rotted beam and call it ‘renovated.’ Licensing is the dry-rotted beam of the digital transformation. We talk about ‘cloud-first’ and ‘mobile-first,’ but our back-end authorizations are still rooted in a 1989 mentality of ‘who is sitting in this chair right now?’ It’s a contradiction we refuse to solve because solving it requires us to admit that the old ways of measuring productivity-eyes on screens, butts in seats-are dead.
Optimization vs. Humanity
We optimize the bandwidth. We optimize the CPU cycles. We optimize the cooling in the data center to within 0.9 degrees of efficiency. But we don’t optimize for the way a human brain actually moves through a workday. A brain doesn’t work in 8-hour blocks on a single machine. It works in bursts. It works in 9-minute increments between meetings. It works while walking the dog. By forcing a User vs. Device choice, the software vendors are making us choose which type of inefficiency we are most willing to tolerate. Are we willing to overpay for the human, or are we willing to throttle the human to save money on the machine?
I’m sitting here now, my left foot bare and cold on the hardwood, the wet sock a lonely ball on the floor. It’s a small misery, but it’s distracting. That’s what bad licensing is. It’s a small, persistent misery that sits under the surface of every workflow. It’s the pop-up window that says ‘License Not Found.’ It’s the IT ticket that stays open for 9 days because the procurement department is arguing over whether a contractor counts as a user or a temporary device access point.
The Building Code Parallel
Winter F.T. would walk into your server room, look at your licensing agreement, and probably find 19 code violations in the first 9 minutes. Not because you’re a criminal, but because the code wasn’t written for the way you’re living. The building code for a 1929 tenement shouldn’t apply to a 2029 smart-loft, yet we are trying to run modern, distributed, high-availability remote desktop services using logic that assumes the internet is a novelty.
The Value Illusion
There is a specific kind of arrogance in thinking we can categorize human behavior into 29-page EULAs. We think if we define the ‘User’ clearly enough, we can ignore the ‘Human.’ But humans are messy. They forget passwords. They lose phones. They work from the beach when they said they were at the dentist. A Device CAL is a leash; a User CAL is a passport. And in a world where the best talent can work for anyone, anywhere, you probably want to be the company that hands out passports.
I once recommended a 99-device license for a creative agency… The resulting audit was like stepping into a cold puddle in the dark. It cost them $9799 in true-up fees and cost me a lot of sleep.
“
We focus on the cost of the license because it’s a hard number we can put in a pivot table. We don’t focus on the cost of the ‘No.’ The cost of telling an employee ‘No, you can’t access that from there.’ The cost of a developer who spends 19% of their week fighting with the VPN because their home desktop isn’t a ‘registered device.’ We are optimizing for the audit, not for the output. It’s a structural failure. It’s a notched-out load-bearing beam.
STRUCTURAL MORALE DANGER
85% CRITICAL
The point where license mismatch collapses morale.
Winter F.T. once told me that the most dangerous buildings aren’t the ones falling down; they’re the ones that look perfectly fine but are one vibration away from a collapse. That’s your IT infrastructure if your licensing doesn’t match your culture. If you have a culture of freedom but a licensing model of incarceration, you are building on a fault line. You are one ‘unauthorized device’ away from a devastating compliance fine.
[The audit is the earthquake; the license is the foundation.]
The Choice: Asset vs. Agent
Are your people assets to be managed, or are they agents of growth?
Device CAL: Manage Assets
User CAL: Empower Agents
If we continue to optimize for the machine, we shouldn’t be surprised when our people start acting like them-rigid, prone to crashing, and requiring constant rebooting. The choice between User and Device isn’t just a line item. It’s a declaration of values.