You have probably tracked your hours at some point, whether it was a time sheet, a billing log or a mental tally of how long you sat at your desk. That number told you almost nothing about whether the work mattered. A growing body of research and a handful of very public company decisions suggest the rest of the working world is finally catching up to that fact.
The shift is simple to state and harder to execute: measure what was produced, not how long someone was logged in producing it. If you are still running your team, your business or your own workday on hours, you are optimizing for the wrong number.
Why the Hours Number Was Always Misleading
Hours worked assumes that time and output move together, and for most knowledge work, they simply don’t. Workers spend only about 25% of their time on the skilled, creative work they were actually hired to do, while another 60% disappears into what Asana’s Anatomy of Work Index calls “work about work”: status updates, tool-switching and hunting for information. Hours logged has no way to tell the two apart.
The gap between busy and productive shows up clearly in focus-time data too. Knowledge workers rack up 5.5 hours of daily screen time but produce only 2 hours and 48 minutes of genuinely productive output, and 40% never get a single uninterrupted 30-minute block in an entire workday. Hours logged captures none of that distinction. A person can be online for nine hours and produce two hours of real value, or the reverse.
The Companies Already Making the Switch
This isn’t a hypothetical shift. GitLab, one of the largest fully remote companies in the world, built its entire culture around this principle, stating plainly in its public handbook that it measures impact rather than activity, evaluating people on what they deliver instead of when or how long they were working.
The change is showing up outside tech too. WPP, one of the largest advertising holding companies in the world, made the case publicly that its future depends on tying fees to actual business results instead of hours billed and headcount deployed, a structural bet that outcome-based work is where client expectations are heading. When a decades-old, hours-billed industry starts unwinding its own business model, that’s a signal worth paying attention to.
What This Is Actually Solving
The deeper problem outcome-based work addresses is disengagement, not just inefficiency. Only 31% of workers in the U.S. and Canada are engaged at work, the highest regional figure in the world, which means most of the workforce is coasting through hours that look productive on paper and are not. Globally, Gallup estimates low engagement costs the world economy roughly $10 trillion a year in lost output.
Hours-based tracking quietly rewards presence over performance, which is exactly the behavior that produces disengagement in the first place. When the only thing being measured is whether you showed up, showing up becomes the entire job. Shift the measurement to outcomes, and the incentive structure changes with it.
Why This Isn’t Just a Remote-Work Story
It would be easy to file this under remote work policy and move on, but the shift applies just as much if you sit in an office every day. The problem was never where the work happened, it was what got counted as work in the first place. An open floor plan full of visibly busy people tells you nothing about whether that busyness produces anything.
Freelancers and solopreneurs have quietly been living this reality for years, often without naming it. Nobody pays you for the hours you spent staring at a blank page; they pay for the piece you deliver. That mindset, uncomfortable as it can be, forces a clarity that salaried hour-tracking rarely does: You learn quickly which of your hours actually matter and which ones are just motion.
The AI layer makes this even more urgent to fix. As more repetitive tasks become automated, the hours a person spends at a desk will keep shrinking while their potential output holds steady or grows. An hours-based system has no way to account for that shift; it just keeps measuring the wrong thing more precisely.
How to Start Measuring Outcomes Instead of Hours
Start by defining what “done” actually looks like for each major responsibility on your plate, not how long it should take. A clear outcome, a client proposal sent, a feature shipped, a campaign launched, gives you something concrete to track. A time estimate does not.
Set a small number of outcome metrics per role rather than dozens of activity metrics. Two or three clear deliverables you can check against reality each week will tell you more than a spreadsheet full of hours logged ever could, and it removes the temptation to reward whoever looks busiest.
Protect blocks of uninterrupted time the way you would protect a client meeting. Deep work researchers consistently find that recovering from a single interruption takes close to 25 minutes, so the real cost of a fragmented calendar isn’t the interruption itself; it’s everything that gets derailed around it.
When You Manage a Team, Not Just Yourself
Communicate the shift explicitly rather than letting it happen by accident. People who have spent years being evaluated on visible activity, being online, responding fast, attending every meeting, will not automatically trust that outcomes are what’s actually being rewarded unless you say so directly and follow through with how you run performance conversations.
Build in regular, lightweight check-ins on outcomes rather than a single annual review. Continuous, outcome-focused conversations catch problems while they’re still fixable, and they give people real-time feedback on what’s actually working instead of a verdict handed down months later.
Resist the urge to replace hour-tracking with a different kind of surveillance, like monitoring keystrokes or idle time. That just swaps one flawed proxy for a worse one. The entire point of outcome-based work is trusting people to manage their own time in exchange for being genuinely accountable for what they deliver.
Featured image from MDV Edwards/Shutterstock
