Everyone knows the Pareto Principle. 80% of outcomes come from 20% of effort. It is one of those ideas that sounds smart in a meeting and gets printed on motivational posters. I nodded along to it for years, especially in the early days.
Then I applied it to myself. I took my actual calendar, my actual deliverables, my actual week, and sorted every activity by one question: did this move anything forward?
The answer breaks something in you. Because it is not 80/20. The real ratio, when you are honest, is closer to 95/5. Maybe 3-4h out of a 50h week produce something that matters. The rest is noise you mistake for work. And the worst part: you perform that noise with REAL PRIDE. I know I do.
In summary:
• The Pareto Principle is generous: the real ratio is uglier
• We do not have a productivity problem, we have a relevance problem: most of what we do does not need to exist at all
• Status work is the biggest lie in management: reports nobody reads, trackers nobody checks, syncs nobody needs. They exist because they feel like work
• AI makes the invisible visible: feed your weekly output to AI tools and watch them replicate it in minutes. That work is mechanical. It always was
• The 5% that matters is the work we avoid: judgment calls, confrontation, saying no, sitting with ambiguity. THE HARD STUFF. The stuff with no template
💀 What 95% Looks Like When You Write It Down
Bad week. 10h days, zero to show for it. So I open a spreadsheet and list every single thing I do. Every meeting, every meaningful Slack thread, every non-robotic email, every document I spend some decent time on it. One column added: “What happened because of this?”
The stakeholder report I spend 2h on? 3 out of 14 recipients open it (best case). None reply. I have been writing it for monre than 8 months.
The dependency tracker? 26 items, updated manually every Wednesday. I ask 4 of the 6 leads whether they use it. 2 say “sometimes” - and i gues it was simply to show some empathy case the dont. 2 do not know where to find it.
The risk register? I review 6 months of meeting notes. Not once has a stakeholder referenced it in a decision. It exists because I created it, and I maintain it because it exists.
4 recurring meetings. I replay each one. In how many does something happen that a Slack message could not have handled? Maybe 1 out of 4. i ve also learned im too fast scheduling recurring calls.
That is what 95% looks like and it is not laziness, quite the opposite, its hard work pointed at nothing. Artifacts nobody consumes, maintained by someone who is too busy producing them to notice.
🤖 The AI Mirror
After the spreadsheet exercise, I do something that makes it worse. Or better. Depends on the day.
I take everything I produce that week outside of meetings: the status updates, the risk summaries, the stakeholder emails, the slide reformats, the dependency maps. I feed all of it to a few AI tools. Mainly Claude. I give the raw inputs: Jira data, GitHub logs, Slack threads, meeting notes, and ask them to produce the same outputs.
They do it in minutes. Not perfectly. Maybe 70-80% of the quality. But here is the thing: when the original output has zero impact, the difference between 100% quality and 70% quality is the difference between zero and zero, which a huge time save.
The gap between what I produce and what AI produces is mostly formatting preferences and tone. Not judgment, insight, or the kind of expertise you build over a decade. Just how I like my bullet points and which shade of red I use for “at risk.”
That is a bad evening. I sit with it for a while, angry at myself. I have spent years polishing work that does not matter. I have gotten good at something nobody needs. The AI does not take my job but it shows me QUICKLY that a big piece of my job is empty.
🔧 Kill the Ritual, Keep the Information
So do I just stop reporting? No. The information matters. The ritual of me manually compiling it every Wednesday does not.
I took the 3 artifacts eating most of my time: the stakeholder report, the dependency tracker, and the risk register. Instead of killing them, I killed the manual process behind them.
Here is the setup: One GitHub repo. A scheduled agent that runs every night at 2 AM. It pulls from Jira, GitHub PRs, CI pipeline logs, TestRail, the team calendar, and whatever else your team uses as source of truth. By the time you open your laptop at 9, the board is updated. No human touched it.
The trick is not tracking everything. It is tracking at the right altitude. Nobody needs to know that ticket PROJ-4821 moved from “in review” to “merged.” What they need to know is: are we on track for the Q2 release? Is test coverage trending up or down? Are blockers accumulating faster than we resolve them?
So you design the board in layers:
Top layer: the executive view. 3-4 things a VP cares about. Each workstream gets a health signal: on track, at risk, blocked. One line per initiative, color-coded. Version releases and their target dates. Product updates shipped this week versus planned. This replaces the stakeholder report. If someone wants to go deeper, they click through. Most will not, and that is the point.
Middle layer: the program view. Milestone progress, cross-team dependencies, upcoming deadlines. Jira epics roll up here, not individual tickets. TestRail test suite pass rates aggregate by feature area, not by individual test case. Team availability pulled from the calendar, because a key engineer on holiday the week before a release is a risk nobody tracks until it is too late. The agent flags trends: test pass rate dropped 12% this week, 3 epics have no activity in 10 days, 2 dependencies have no owner, your lead backend dev is out next week and owns 4 open blockers.
Bottom layer: the raw data. The ticket-level detail, the individual PR status, the specific test failures. It exists for the people who need it. Engineers debugging a pipeline, QA leads investigating a regression. Nobody else has to see it.
What the agent does every night:
1. Pulls from Jira and rolls tickets up to epic and initiative level. Calculates velocity trends, flags epics that are falling behind based on burn rate, not just due dates.
2. Reads GitHub for deployment health. Not individual PRs but aggregate: how many deployments this week, failure rate, rollback frequency. The shape of the trend matters more than any single data point.
3. Hits the TestRail API for test coverage and pass rates by feature area. A test suite going from 94% to 87% pass rate over 2 weeks tells you more than any manual risk register ever will.
4. Checks the team calendar for upcoming absences and cross-references them against open blockers and ownership. A vacation is not a risk. A vacation by the only person who can approve a deployment the week before launch is.
→ Generates a daily digest that lives at the top layer. What changed at the initiative level, what is at risk, what needs a decision. Push it to Slack or email, wherever your stakeholders already look. I do Slack.
The whole thing took me a weekend to set up. I stopped sending the stakeholder report and shared the link to the board instead. The dependency tracker? Same data, zero manual updates. The risk register? A filtered view on the same board, alive instead of a static document buried in a Confluence folder.
Something like 7h/week returned to me and it was not by working harder or waking up earlier, but by building a system once that replaced the ritual forever. And the board is better than my reports: more current, more accurate, more accessible. I had been the bottleneck all along.
The 95% does not disappear. It gets absorbed by infrastructure. The question is whether you are the infrastructure or you build the infrastructure. So I’m gonna continue building..
🧠 The 5% That Keeps Everything Alive
So what is the 5%? What actually moves things forward in a week like that?
One conversation. A project is 3 weeks from deadline and 8 weeks from done. Everyone knows it byt nobody is saying it. I sit down with the sponsor, walk through the math, and propose a reduced scope that ships on time. Redraw the flow. That conversation takes 45 minutes. It saves the quarter. It saves relationships that were starting to crack under the pressure of a deadline nobody believed in. WE got marketing material to promo the work.
One “no.” A VP wants to add a workstream to an already overloaded program. I have the data ready (thanks Claude). I push back. The VP pushes harder. I hold. The workstream gets deferred. so existing commitments stay on track. That takes maybe 2h of prep and a 30-minute meeting. ugly conversation but the team does not have to absorb another commitment they cannot deliver.
One observation. I notice 2 team leads have stopped talking to each other. no camera on calls, Tickets bounce back and forth with passive-aggressive comments. Nobody asks me to fix it or names this big elepahnt in the room. I pull them virtually aside separately, then together. some days of awkward conversations. One of them tells me it started over a code review comment a while ago.
That is the 5%. Judgment. Confrontation. The willingness to say the thing nobody wants to hear. Sitting with ambiguity long enough to see what others miss.
And here is the uncomfortable part: there is no way to schedule it. No template. No weekly cadence. The 5% shows up disguised as interruptions, tensions, silences in meetings where someone should be speaking but is not. It requires you to be present. Actually present. Not drafting a status report in another tab while someone is telling you, between the lines, that they are about to quit.
So how do we make the 5% more of our week? We do not add it. We subtract everything else. Block 2h every morning with nothing in it. No agenda. No deliverable. Just space to think, notice, and act on the things that only a human who gives a damn can act on. The first week feels unproductive. The second week you start catching things you have been missing for months.
The 95% does not just waste my time. It blinds me. It fills every gap where the 5% could live.
🎯 Final Thought
Here is what makes this personal, not professional.
When I look at that spreadsheet, I do not just see a time management problem. I see an identity problem. The reports, the trackers, the syncs: those are my proof of work. My evidence that I am earning my salary. My answer to the question every project/program/ops manager dreads: “What do you actually do?” Without them, I do not know how to answer that question. And that terrifies me more than any reorg or layoff ever has.
I think this is true for a lot of us in operations, project management, program management. We build rituals of reporting and tracking and aligning, and over time the rituals become the job. The actual job, the judgment and the conflict and the hard calls, gets pushed to the margins. We are too busy maintaining the machinery of looking busy to do the work that matters. We are not overworked. We are over-ritualized. And the rituals are not for the organization. They are for us.
So try this. Take your last week, list everything you did, add one column: “What happened because of this?” Not “this keeps stakeholders informed” honest. Actually honest. Did someone make a decision based on it? Did something change? Did anything move?
If the answer is mostly silence, you have a choice. Keep performing the 95% because it is comfortable, it fills the calendar, and it answers the question “What do you do?” Or strip it away and spend that time on the 5% that your organization actually needs from you: the hard calls, the uncomfortable conversations, the thinking that has no template.
The 95% is safe. It has checklists, recurring calendar events, and the warm glow of productivity theater. The 5% is scary, ambiguous, and it requires you to be right or to be wrong and own it. Choose the scary one. Your organization does not need another status report. It needs someone willing to say what nobody else will.