Unmeasured: Part 5 – Rethinking productivity for a human future
We questioned the obsession with “more” in Part 0, we exposed the wrong metrics in Part 1, we showed how running the business is easier to measure than changing it in Part 2, we dissected fake agility in Part 3 and finally we revealed the emotional wreckage of productivity theater in Part 4.
Now it’s time to ask: Is the system really broken or was it just built this way?
To me, it works as designed, still, let’s go fix it.
Productivity isn’t the enemy. Our definition is.
The problem isn’t that we want to be productive. The problem is what we’ve come to mean by productive. Faster. Louder. Busier. Visible. Measurable. Exhausted.
We’ve collapsed “productive” into “busy”, and then we wonder why teams move fast but go nowhere. Real productivity (the kind that actually changes things, builds value, and sustains people) is slower. It doesn’t neatly fit into sprint cycles, it doesn’t show up well in dashboards and it can’t b automated or templated. And that’s exactly why it matters.
Beyond output: measuring value and health
If we want a future worth building, we have to move beyond measuring units of work produced. We have to measure what actually creates progress:
- Outcomes, not just deliverables
- Learning velocity, not just story points
- Sustainability of pace, not just effort levels
- Creative breakthroughs, not just task lists
- Psychological safety, not just attendance
You can automate output. You can’t automate meaning.
Rethinking systems, not just speed
The future of productivity isn’t about speeding up tired systems with better tools. It’s about redesigning the systems themselves. Systems that:
- Leave space for deep work, real rest, and human rhythms
- Reward challenging the status quo, not just clearing the backlog
- Trust teams to make decisions, instead of drowning them in status meetings
- Make recovery, creativity, and long-term thinking visible parts of performance
in short: Systems that see people as humans—not resources to be optimized. We don’t need faster teams. We need smarter environments.
So while we are at it: We should drop “HR” as in human resources. This technical framing on people is dehumanizing.
What real metrics could look like
Imagine this:
- Instead of asking, How many tasks were completed this week? You ask, What friction did we remove?
- Instead of tracking sprint velocity like a blood sport, you ask, What did we learn that will make the next sprint smarter?
- Instead of bragging about being heads-down all quarter, you celebrate, What breakthroughs did space and rest create?
Numbers still matter—but they need to tell the right stories. Stories of impact, not just activity.
Copilot, AI, and the future of human work
AI is already taking over the visible, repeatable tasks:
- Summarizing meetings
- Drafting reports
- Automating workflows
That’s not the threat. That’s the opportunity.
Because the parts of work that remain human, the ambiguous, the relational, the creative, the emotional, those are the parts we’ve historically undervalued and undermeasured. The future belongs to teams that stop fighting to outpace the machines and start doubling down on what machines can’t replicate: Judgment. Creativity. Empathy. Adaptability. Vision.
AI can draft a plan. Only humans can know whether it’s the right plan.
Closing: Beyond Unmeasured
We don’t need another round of optimization. We need a new philosophy of work. One that starts with a different set of assumptions:
- People are not productivity machines
- Value is not the same as volume
- Rest is not a reward; it’s a requirement
- Thinking time is not wasted time
- Trust is not optional—it’s operational
This isn’t about working less, it’s about working right.
It’s about asking not just, How much did we do? but, Was it the right work? Did it matter? Did we leave space for better ideas, better systems, and better lives?
Better work begins with better systems. And better systems start when we finally measure the things that truly matter.
More parts of this series
Published on:
Learn moreRelated posts
You are holding GitHub Copilot Wrong!
Most developers think that one can’t really use GitHub Copilot wrong. There is a chat interface that lets you also choose a model, so th...
You are holding GitHub Copilot Wrong!
Part 0 showed why constant prompting, re-prompting, and steering GitHub Copilot feels fragile. Not because Copilot is unreliable, but because ...
Building a Multi-Hierarchy Ticket Classification System (Because Keywords Aren't Enough)
Look, I love a good keyword-based system as much as the next developer. They’re fast, predictable, and when your user says “VPN,&r...
Secretless cross-tenant dataverse access
Client secrets are like hiding your house key under the mat; easy to grab and impossible to audit. Certificates are just slightly better, beca...
How Azure CLI handles your tokens and what you might be ignoring
Running az login feels like magic. A browser pops up, you pick an account, and from then on, everything just works. No more passwords, no more...
How Dev Proxy teaches you to make your apps more resilient
I added Microsoft Dev Proxy to my Mermaid → Dataverse converter, because I wanted to test how it handled rate limits and API errors. What I go...
Building Azure functions that never store secrets — ever
What if your function could hit Microsoft Graph with no client secrets, no certs, and no Key Vault entries? That is exactly what a Managed id...
Introducing Mermaid to Dataverse Converter
Why diagrams matter (and why they usually fail us) Entity-Relationship Diagrams (ERDs) are the universal shorthand for talking about data mode...
It’s OK to be seen trying
It’s OK to be seen trying Somewhere along the way, we started believing that you’re only allowed to speak after you’ve figured everything out....
Stuck in pilot - Part 1: no foundations, no future
“We just need to test the AI. We’ll figure out the data later.” That sentence has quietly killed more AI pilots than any model failure ever ...