This content originally appeared on DEV Community and was authored by Gásten Sauzande
If you’ve ever looked at your Zenhub board at the end of a sprint and thought:
“Why does it look like the team barely did anything?”
You’re not alone.
And in most cases, it’s not that the team is slacking — it’s that invisible work is stealing the spotlight.
What Is Invisible Work?
Invisible work is any effort that doesn’t make it onto your board but still eats up time and energy:
- Quick Slack requests that turn into an hour-long rabbit hole.
- Bug fixes that never got logged as issues.
- Helping another team debug their blocker.
- Ad-hoc meetings, support calls, or “just five minutes” tasks.
None of this is bad — in fact, it’s often critical.
But when it’s not tracked, your velocity, burndown charts, and estimates look completely off.
Why It’s a Big Deal
Invisible work hurts your team in two major ways:
- False estimates – Next sprint looks like you’re underperforming because you didn’t account for these extra tasks.
- Morale drops – The team feels like they’re doing tons of work, but the board (and leadership) says otherwise.
That gap creates tension and makes it harder to plan realistically.
How to Make Invisible Work Visible in Zenhub
Here are three ways I’ve tackled this problem after 100+ sprints:
✅ Create an “Unplanned Work” pipeline
Whenever something comes in mid-sprint, log it here. At the retro, you can quantify how much unplanned work hits each sprint.
✅ Add a quick “Support & Interruptions” issue
For teams constantly pulled into Slack or meetings, create a recurring issue each sprint. Add estimates for the expected time sink.
✅ Retro tracking
Use your retro to ask: “What did we do this sprint that isn’t on the board?” Then log those tasks before you close.
A Better Way Forward
The truth is: invisible work will always exist.
But when you acknowledge it, track it, and bake it into planning, your team suddenly looks a lot more like reality.
Instead of being “slow,” you’re simply being honest about where time goes.
💡 To help with this, I put together a free Scrum Master Checklist you can use to track sprint planning, daily standups, and retros — so invisible work stops flying under the radar.
👉 Download the Free Checklist here
What’s the most common invisible work you see in your team? Drop it in the comments — I’d love to compare notes.
This content originally appeared on DEV Community and was authored by Gásten Sauzande
Gásten Sauzande | Sciencx (2025-09-23T19:34:18+00:00) The Invisible Work Problem: Why Your Team Looks Slow (But Isn’t). Retrieved from https://www.scien.cx/2025/09/23/the-invisible-work-problem-why-your-team-looks-slow-but-isnt/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.