In the humid summer of 1841, a man named Arthur Penhaligon-a junior clerk with the British Admiralty-began a project that would consume the next eight years of his life. He was tasked with reconciling the ledger of “Ship’s Biscuits and Salted Beef” across the entire Atlantic fleet.

Every day, for nearly three thousand days, Arthur arrived at his desk, sharpened his quills, and transferred numbers from stained, salt-crusted logs into a series of magnificent, leather-bound master volumes. His handwriting was a marvel of copperplate precision.

Arthur had spent his entire adult life creating a perfect record of a reality that never existed. He had generated immense activity, but he had achieved zero progress.

The Software Licensing Mirage

This is exactly how we manage Microsoft licensing in the modern enterprise. We have replaced the copperplate quills with Power BI dashboards and the salt-crusted logs with automated discovery tools, but the fundamental delusion remains the same.

The sector has collectively decided that if we are busy-if we are meeting, reviewing, and reporting-then we must be compliant. We mistake the motion of the machine for the movement of the vehicle.

The Hunger as an Emergency

I started a diet today at 4:00 PM. It is now 5:42 PM, and the primary thing I have discovered is that hunger is not an emergency, but it is a very effective filter for bullshit.

When your blood sugar drops, the tolerance for “performative corporate theater” evaporates. I look at the calendar for the average IT department and I see a “Monthly Licensing Steering Committee” meeting. I see a “Quarterly Vendor True-up Preparation” workshop. I see “SAM Tool Optimization” sessions.

Each of these represents hundreds of man-hours. They generate beautiful heat maps and “Compliance Risk Profiles” that glow with a reassuring amber light, suggesting that we are “working on it.”

But if you walk into the server room, or log into the virtual environment, the actual posture hasn’t moved an inch. The licenses haven’t been purchased. The User CALs haven’t been assigned.

The version mismatch between the Windows Server 2022 instance and the legacy 2016 RDS CALs is still there, ticking like a localized time bomb.

As someone who spends a lot of time thinking about the structure of letters-I’m a typeface designer by trade, and my name is Hiroshi V.K.-I see this as a failure of “kerning.”

The Space Between the Letters

In typography, you can have a perfectly designed letter ‘A’ and a perfectly designed letter ‘V’. But if the space between them is wrong, the word is unreadable.

The industry is currently obsessed with the letters-the individual reports, the specific meetings-but it is ignoring the space between them. We have a gap between “Knowing we have a problem” and “Solving the problem.” We fill that gap with meetings, hoping that if we talk about the ‘A’ and the ‘V’ long enough, they will magically move closer together.

They won’t. They only move when you actually change the spacing.

Bypassing the Theater

The core frustration here is that visible effort has become a substitute for actual improvement. In many organizations, it is safer to be “busy failing” than it is to “simply succeed.”

If you spend six months researching the nuances of Microsoft’s licensing terms for Remote Desktop Services, you are seen as a diligent professional. If you simply realize you are short fifty seats and buy them in fifteen minutes, you have bypassed the theater. And the theater hates to be bypassed.

But consider the reality of a production environment. You have users who cannot log in because the RDS grace period has expired. Or you have a looming audit where the delta between your “documented activity” and your “actual keys” is going to cost you six figures in penalties.

In those moments, the leather-bound ledgers of Arthur Penhaligon are worthless. You don’t need a committee. You need the licenses.

This is where the industry’s “Activity-Progress” conflation becomes dangerous. We assume that a complex problem requires a complex, time-consuming solution. Microsoft licensing is certainly complex-the difference between a Per-User CAL and a Per-Device CAL can feel like a theological debate from the Middle Ages-but the solution doesn’t have to be. We have built an entire ecosystem of delay around the act of procurement.

I’m looking at my watch. My diet is currently making the idea of a ham sandwich feel like a religious experience. This heightened state of irritation makes me wonder: Why does the “activity” of getting a quote, getting it approved, and getting it processed take twenty days, while the “progress” of actually licensing the server takes twenty seconds?

It’s because we have been trained to value the struggle. We think that if it was easy, we wouldn’t be doing our jobs. We think that if we don’t have three meetings about the version compatibility of Windows Server 2025, we are being reckless.

But compatibility isn’t an opinion; it’s a technical specification. You either have the right version or you don’t.

The $15,000 Permission Slip

Across the industry, teams are generating motion, process, and paperwork that feels productive. They are “optimizing” their licensing spend by spending more on the optimization process than the licenses themselves would cost.

I’ve seen companies spend $15,000 in internal labor costs to “evaluate” a $2,000 licensing gap. They felt very productive during those meetings. They felt like they were “managing the risk.” In reality, they were just lighting money on fire to stay warm while they waited for a permission slip that they already had the power to sign.

If a server is unlicensed on Monday, and it is still unlicensed on Friday, you have made zero progress, regardless of how many emails you sent about it. True efficiency in this space looks like a reduction in noise. It looks like moving directly from the identification of a need to the fulfillment of that need.

When you cut through the bureaucratic fog, you realize that for things like Microsoft RDS CALs, the complexity is largely an external imposition. You know how many users you have. You know what version of Windows Server you are running.

“I refuse to spend three weeks on a fifteen-minute problem.”

This is why specialized providers are becoming the silent heroes of the IT world. They don’t want to join your committee. They don’t want to see your 50-slide deck on your five-year licensing strategy. They understand that licensing is a utility, not a hobby.

When you need to bridge the gap between “unlicensed” and “compliant,” you need a direct path. Using a resource like the RDS CAL Store is an act of rebellion against the activity trap. It prioritizes the outcome-getting the 2022 or 2025 User CALs into the environment-over the process of talking about getting them.

Beyond the Baseline

We have to stop rewarding the “busy-work” of licensing management. A report that identifies a 20% licensing shortfall is not a success; it is a confession. The success only occurs when that 20% becomes 0%.

In my world of typeface design, there is a concept called “optical correction.” If you place a round letter like ‘O’ exactly on the baseline, it actually looks like it’s floating. You have to slightly overshoot the line to make it look correct to the human eye.

The industry is currently obsessed with the “baseline”-the rules, the audits, the reports. But we are failing the “optical correction”-the actual state of the environment. We are so worried about following the “process” of licensing that we have lost sight of the “result” of being licensed.

My diet will likely fail by 9:00 PM because the “activity” of resisting the fridge is currently outweighing the “progress” of losing weight. I am generating a lot of mental motion, but the scale doesn’t care about my internal monologue. It only cares about what I actually eat.

Similarly, Microsoft doesn’t care about your Licensing Steering Committee. The auditors don’t care about your beautiful Power BI charts. They care about the keys. They care about the entitlement. They care about the “progress” that is represented by a perpetual license, properly versioned and instantly delivered.

We need to stop mistaking the map for the territory.

Arthur Penhaligon’s ledgers were masterpieces of clerical activity, but they didn’t feed a single sailor. Your licensing reports might be masterpieces of corporate diligence, but they don’t authorize a single remote session.