Engineering team productivity audit. In 3 months, or the money is on me.
"Our teams haven't delivered the majority of the roadmap for 3 quarters in a row." — every CEO who ends up on this call. I come in, find the leverage, agree the plan, run the tiger team. Sprint completion goes from 50% to 80%. If it doesn't, you don't pay.
Sound familiar?
"I'm not sure what to put in the sprint. We have so many things to do. We are busy like hell."
— Engineering Manager
"Delivery poorly estimates their work. Every task takes twice the time. I can't help it."
— CPO
"Some devs are underperforming. Constant changes, people coming and leaving."
— PM
"I just hear excuses. Product and Tech blaming each other. We are not in kindergarten."
— CEO
Inefficiency patterns I see over and over
- Teams have low trust and deliver half of the planned weekly work.
- Teams aren't working on what matters most — the roadmap. Is there even a product strategy in place?
- Disconnect between product and engineering, visible in the gap between dev tasks and company strategy.
- Low focus: too many things in parallel. No clear WIP limit.
- Developers not cooperating with PMs. Low discovery.
- Too much work bounces back due to quality. Productivity keeps decreasing.
- No clear priority agreement between support / new features / tech debt / bugs.
The maths behind the audit
A 60-person org running at 50% instead of 80% burns roughly 11 million CZK a year. The audit costs a fraction of that. The 3-month engagement pays for itself before month 4.
How it works — 3 months
- Step 1 — 1st month
Seek the most valuable efficiency opportunities.
We embrace the current situation and find the way out. People are tired, busy, or biased — so we skip gut feeling and go on proven hypotheses and data. We agree the top 3 opportunities in writing, expressed in metrics.
- Team efficiency + agility
- Team leadership
- Team spirit
- Engagement to product
- 20-min intro sessions with each team + relationship building over coffees, lunches, socials
- Jira-extracted metrics: roadmap contribution, weekly completion, ad-hoc interruption, epic cycle time, delivery predictability, lead time, delivery quality
- Step 2 — 2nd month
Proposal and evaluation.
Uncover the results, share the proposed battle plan, adjust and commit. I present findings scored on Agility / Predictability / Focus / Quality / People / Leadership. Then a detailed proposal — specific timeline, specific owners.
- Findings + scored rating across 6 areas
- Impact vs. effort matrix of opportunities
- Detailed boost plan with owners and dates
- Team + leadership sign-off
- Initial "playground" fixes to prep the ground for execution
- Step 3 — 3rd month
Adoption. Hard work.
Tiger team formed to execute improvements. No time for excuses. Weekly written updates. Public Miro roadmap. Predictable delivery cadence.
- Tiger team ownership of each opportunity
- Weekly chat/email updates to leadership
- Public Miro roadmap of the initiative
- Team-health board tracked continuously
The guarantee
No outcome, no money. If the KPIs we agree in month 1 aren't hit by month 3, you don't pay the final instalment.
This isn't a marketing line — it's how I priced my first 20 audits, and it's how I still do it. It keeps me honest. If the situation genuinely can't move in 3 months, we find out in month 1 and stop.
Logistics
- Time allocation: 2 days a week for 3 months. At least 1 day on-site.
- Requirements: transparency from top, time allocation for the team, access to Jira and any relevant tooling.
- No extra licenses: I bring my own Jira extractor and Tableau/PowerBI templates.
- Company size: ideal for orgs with 20-200 engineers. Smaller and larger orgs need a modified engagement.
Ready to fix it?
Emailmarian@marian.coachwith the current sprint-completion rate, the number of engineers, and the North Star you're trying to move. I'll come back within 48h with the fit and a scoping call proposal.
From the blog
All posts →
Don't Do DORA Metrics First: Rethinking Team Performance Indicators
What's the purpose of having expensive highly performing teams if they don't work on things that matter the most, having 60% off-roadmap contribution?
· By Marian
Read →

How to Build Trust with Engineering Teams
In engineering management, my vision is to create a productive software delivery environment that developers are proud to work in, with a focus on tangible…
· By Marian
Read →

10 Questions to Find the Right Engineering Management Role
Feeling stuck or burned out? Use these 10 questions to realign your engineering management role and find a path that truly fits your goals and strengths.
· By Marian
Read →