Your Week Was Full. What Did It Change?
Your calendar had no gaps this week. You made every standup, cleared your review queue, kept your Slack replies fast, and you even finished a refactor you decided to take on. By any visible measure, you worked hard.
But, was your week productive? Name one thing that is different because of your week. A user who you were able to ship a feature request for. A teammate who got unblocked. A decision that got settled.
What outcomes did you drive and how do you measure the value you provided? A busy week and a productive week are measured in different units, and every incentive around you points at the first one.
Visible Activity Is the Easiest Thing to Reward
Software output is hard to measure. Nobody can watch you think through a design, so organizations fall back on what they can see: messages answered, meetings attended, tickets touched. Cal Newport calls this pseudo-productivity, where visible activity stands in as a rough proxy for useful effort.
The response to that incentive is widespread. In a Visier survey of 1,000 U.S. workers, 83% admitted to at least one form of performative work in the past year, and 43% said it eats more than ten hours a week. The reasons people gave were understandable ones: they wanted to look valuable, and they wanted to be seen working.
So the pull toward looking busy is rational. It just optimizes for the wrong audience.
How to Differentiate Productive from Busy
Productive work produces a change someone else can point to. In software, that change takes one of three forms:
- It ships. A user can do something today they couldn't do yesterday.
- It unblocks. A teammate who was stuck is now moving.
- It settles. An open decision is now closed, and work can proceed on top of it.
Notice that most of these do not require writing code. Atlassian's developer experience research found engineers spend about 16% of their time coding. The other 84% is where this question matters most, because that's where activity and impact drift apart quietly.
This is also why the test cuts in both directions. Refining a story before grooming looks like process overhead, but it settles a decision the team would otherwise make badly three weeks later. Sitting in a design review can be the most productive hour of your week or the emptiest one, depending on whether you changed the outcome.
|
|
Where can AI save you time?
My friends at Big Creek Growth put together a quick survey to spot the repetitive work you can hand off to automation.
|
|
Three Ways to Fill a Week Without Changing Anything
These patterns look productive from the outside. Each one fails the same test.
1. Answering everything instantly
A fast reply feels like engagement, and it's the most visible signal you can send. But responsiveness produces availability, not output. Every instant reply also costs you a re-entry into whatever you were doing, and that context switching quietly drains your day.
Ask what your last ten fast replies actually settled. For many of them, an answer two hours later would have changed nothing except your focus.
2. Sitting in meetings where your presence changes nothing
Attending is visible. Contributing is not the same thing.
A meeting counts toward your week only if you made a decision, gave input that shaped one, or left with work you couldn't have gotten async. If you could have read the notes afterward with no loss, the hour produced attendance and nothing else.
3. Building things nobody asked for
This one is sneaky because it involves real engineering. Refactoring a module on a path no one touches. Writing a script for friction you never measured. It feels like initiative, and there's always a plausible story for why it helps.
But internal tools and unrequested polish carry ongoing cost, and work that no user, teammate, or decision was waiting on is work the week didn't need.
AI Gave the Hours Back. Watch Where They Go.
Atlassian's 2025 report surfaced a strange pair of numbers: 68% of developers say AI saves them ten or more hours a week, while 50% say they lose ten or more hours a week to organizational friction. The time AI frees up is being reabsorbed, and the patterns above are exactly the kind of activity that absorbs it.
Saved time is raw material. It becomes productivity only when you point it at something. If AI hands you back Thursday afternoon and Thursday afternoon fills itself, you've automated the wrong half of your job.
The point of the Friday question is not to purge every low-value hour. Some busy work comes with the job, and some slack in a week is healthy.
The point is to be able to answer it. Ask it every Friday for a month and something shifts: you start noticing on Tuesday which work will be productive and which won't.