---
title: "Just wrapped a Q4 review call with a client team (Financial Services, 35 developers)."
date: "2025-12-03"
language: en
text: full
source: "LinkedIn"
format: "Post"
credit: "By Damir Majer"
contributors:
  - name: "Damir Majer"
    role: author
original: https://www.linkedin.com/feed/update/urn:li:share:7401891929342324736
canonical: https://damirmajer.com/notebook/2025-12-03-just-wrapped-a-q4-review-call-with-a-client-team-financial-s/
---

# Just wrapped a Q4 review call with a client team (Financial Services, 35 developers).

LinkedIn · Post · By Damir Majer · 3 December 2025

The metric that stood out: 73% reduction in production incidents.

12-15 incidents/month → 2-4 incidents/month

Not from hiring more people.\
Not from working longer hours.

From systematic code quality improvement over 18 months.

Here's what changed:

Before (18 months ago):\
→ Manual testing only (no TDD, no automation)\
→ Code reviews = rubber stamping (5 min, no real feedback)\
→ Deployments = Friday evening panic (fix Saturday)\
→ Team Lead: "We dread every release"

After (today):\
→ TDD introduced systematically (80% test coverage)\
→ Code Review discipline (every PR reviewed, 30 min average)\
→ Refactoring budget (10% sprint capacity for quality)\
→ Team Lead: "Deployments are boring now. That's good."

The numbers:\
→ Investment: 18-month systematic transformation program\
→ Savings: Firefighting time + churn prevention\
→ ROI: 335% over 18 months

The human impact:\
→ Developers: "I sleep better at night"\
→ Customers: +40% satisfaction score\
→ Management: Predictable delivery (no more surprises)

"Deployments are boring" = mission accomplished.

What metric would prove success for your team?

#EngineeringExcellence #CaseStudy #ContinuousImprovement

## Sources

- [View the original on LinkedIn](https://www.linkedin.com/feed/update/urn:li:share:7401891929342324736)
