How Mapon unlocked €217.385 by finding and fixing team issues through feedback
In 3 Months Mapon Unlocked 9,080 Additional Productive Hours
In just 3 months, Mapon unlocked €217,385 in development capacity by catching engineering bottlenecks fully and early. After scaling to six product teams, the fleet management leader needed deeper insights than traditional feedback methods could provide. By implementing Flea's developer experience platform, they achieved the following results:
Productivity Gains
€217.385
9.080
Additional Productive Hours unlocked
Developer Experience
+11,5%
78 → 87
DevEx Score Improvement
Response Rate
90%
Average Survey Response Rate
With a constant 90% survey participation rate, Mapon improved their Developer Experience Score from 78 to 87, placing them well above the industry average of 78.
"Looking at the feedback collection before Flea, I had information from various sources at different times, but I couldn't fully understand what was really important. With Flea, we can now see which problems affected a few people versus systemic issues impacting the entire team."
Egils Lange
Software Development Lead at Mapon
Growing Team Frustrations Within Mapon Required Objective View on Systemic Issues
Mapon provides fleet management and asset tracking solutions across Northern Europe. With headquarters in Riga, Latvia, they operate as part of the Draugiem Group, Latvia's largest IT group.
After noticing growing frustrations within the engineering team, Head of Software Development Egils Lange struggled to get an objective view that would allow him to validate and prioritize systemic issues. With feedback scattered across one-on-ones, team meetings, and watercooler chats, it was impossible to distinguish between individual pain points and broader organizational challenges.
Scattered Feedback Masked Critical Issues
Before implementing Flea, Mapon's engineering leadership faced several challenges in understanding team needs:
A Systematic, Feedback-Based Approach to Developer Experience
After evaluating multiple solutions—including manual feedback collection, custom monitoring tools, and cloud provider productivity reports—Mapon chose Flea for its structured, qualitative-first approach. Unlike traditional engineering metrics, which lack developer sentiment insights, Flea provided a framework to analyze 45 scientifically validated DevEx factors, enabling a holistic view of developer experience.
The solution comprised four key components, each addressing a specific challenge Mapon faced:
2-Hour Setup, 90%+ Response Rate, Closed Feedback Loop
Before Flea, Mapon relied on scattered feedback through various formats like 1:1 meetings, team retros and watercooler chats. The transition to a comprehensive developer experience platform followed a structured approach that ensured quick adoption and immediate value.
Quick Setup & Onboarding
Survey configuration and team onboarding by Flea
2-hour setup time
Feedback Collection via Automated Surveys
Automated quarterly surveys with a two-week response period, three timed reminders and smart nudges ensured high participation and meaningful feedback
90% response rate
Structured Results and seamless Integration
Review of insights with CTO and tech leads
Solution brainstorming using Flea’s recommended actions
Integration into bi-weekly retros and OKR cycles
Structured action tracking through Flea and Slack lists
Closed feedback loop
€217.385 Value Created Through Early Problem Detection
Within three months of implementing Flea, Mapon achieved an 11.5% improvement in their Developer Experience Score (78 → 87). This score, measuring key factors like technical enablement, team dynamics, and career growth, placed them well above the platform average of 78 - indicating exceptional engineering team health. With a 90% participation rate, the improvements reflected true team-wide progress.
Mapon Unlocked 9.080 Additional Productive Hours
By identifying and addressing key bottlenecks early, Mapon achieved measurable improvements in team productivity:
Productivity Increase
+11,5%
77 → 87 DevEx Score Improvement
Additional productive hours
9.080
42 engineers × 1,880 hours × 11,5%
Realized Value
€217.385
Based on €45,000 annual developer cost
Four Major Engineering Challenges Have Been Identified and Resolved with Strong Improvements
Poor Frontend Code Structure & Maintainability
Problem
The frontend codebase suffered from several critical issues, scoring only 33/100 in both reusability and contribution ease. Key challenges included inconsistent design patterns, insufficient architectural documentation, difficulty in testing individual components, and monolithic components that were hard to maintain. Frontend developers particularly struggled with large/bloated components and SCSS module overrides
Action
Initiated discussions with senior frontend developers to formulate clear coding guidelines and refactoring strategy. Planned implementation of consistent design patterns and component library while breaking down monolithic components into smaller, more manageable microservices. Started implementing automated code formatting and strong typing through TypeScript to improve code quality and maintainability.
33→ 53,5
+62%
Result
The score improved from 33/100 to 50/100 (+17 points) for software architecture support, and from 33/100 to 57/100 (+24 points) for code contribution ease. The team successfully began modernizing legacy code through incremental refactoring and improved documentation implementation.
"It turns out that the back-end developers are happy with everything and front-end developers are absolutely not happy with the ecosystem, which allowed us to put this as a priority for this quarter."
- Egils Lange, Software Development Lead
Missing Success Metrics and User Feedback
Problem
Success metrics and KPIs were undefined, with developers having limited access to customer feedback and metrics. Teams struggled to correlate their code changes with user experience impact, and there was poor communication of success metrics across stakeholders. The initial score of 52/100 indicated significant room for improvement, with 33% of developers rating this aspect of their work as poor.
Action
Created a framework for business metric, analytics, and feedback collection & analysis. Implemented regular review processes and established structured user feedback collection. Additionally, they started informing and reminding teams about the need and purpose for collecting success metrics and feedback, with tech leads taking an active mentoring role in this process
52 → 75
+44%
Result
The score improved to 75/100 (+23 points), with 56% of developers now rating it as "Good" compared to the previous assessment. Teams began implementing a data-driven decision-making culture and established clearer success metrics dashboards to be reviewed in team ceremonies
"I think we often implement things that we think the users need, but don't have data to back it up. I can definitely see improvement if we were doing regular checks into how our clients are using our system and if they are using new features we implement."
- Software Engineer at Mapon
Unclear Team Goals
Problem
Developers didn't feel informed about the goals and objectives of their teams. This lack of transparency from product owners to development teams was creating misalignment and affecting developer motivation
Action
Asked product owners to share information more frequently and in a more transparent and detailed manner with developers. They utilized their existing bi-weekly retro meetings to integrate this improved communication process
63 → 89
+41%
Result
The revised communication approach led to significantly improved results in the December survey, with developers reporting better understanding of team goals and increased alignment with product direction
"One of the main problems that developers highlighted was that they didn't feel like they knew enough about the goals and objectives for their teams. It was a pretty straightforward fix and easy win. We just needed better communication."
- Egils Lange, Software Development Lead
Inefficient Refactoring Process
Problem
The existing technical debt process of dedicating every third sprint to improvements proved inefficient. Large technical changes were taking excessive time, with one Excel library migration spanning an entire year despite only requiring four weeks of actual work.
Action
Transformed the approach by rebranding "technical debt" as "technical initiatives" and integrating them into regular sprint planning alongside product goals. Moved away from sporadic technical debt weeks to dedicated, focused resources for larger technical improvements.
73 → 80
+9,5%
Result
Achieved more efficient resource allocation for technical improvements, enabling faster implementation of critical changes. The new process allowed teams to properly scope and dedicate appropriate resources to technical initiatives rather than trying to fit them into spare capacity.
"We migrated one Excel library, for example. In the previous process, it took us one year in those sporadic weeks. And in total, we spent like four weeks on it over one year and so yeah that was quite inefficient."
- Egils Lange, Software Development Lead
Flea Provides Clarity Into What Really Matters to Developers And Data to Convince Upper Management
"Looking back now, I would regret not starting earlier, because Flea is really powerful: it gives me the confidence that I need to know what matters to our developers and it gives me arguments that I need to convince upper management."
"happy developers means productive developers and eliminating unnecessary burdens and toil from the process makes developers happy, makes them productive, generating an overall benefit to the company."
Egils Lange
Software Development Lead at Mapon
The transformation at Mapon revealed four critical success factors:
Clear Signals Drive Confident Decisions
Structured feedback separates true priorities from isolated complaints
Enables confident decision-making based on data rather than assumptions
Provides management buy-in for resource allocation
"Having this data gives me the confidence that I need, it gives me arguments that I need to convince management that we need resources into fixing this because people are highlighting this is a problem."
- Egils Lange, Software Development Lead
Enable Quick Wins Through Data
Address simple but impactful issues early
Use structured insights to validate improvements
Focus resources on validated team needs
"The results themselves weren't overly surprising. It’s more that it helped us by giving a push in the right direction. Like, hey, we have already talked and thought about this thing, but okay, let's put it higher up with the priority list now."
- Egils Lange, Software Development Lead
Surface Hidden Issues
Segmented analysis reveals team-specific challenges
Prevent problems from becoming critical
Enable proactive rather than reactive improvements
"That was really interesting to see what the issues highlighted by different disciplines were. Like, for example, backend developers say, oh, we have a very different view on success metrics and front-end developers say, oh, it's fine, we're happy."
- Egils Lange, Software Development Lead
Drive Continuous Improvement
Integrated with existing processes (retros, 1:1s, OKRs)
Regular feedback cycles maintain momentum
Measurement must be followed by actions
"If you measure and don't do anything it can backfire."
- Egils Lange, Software Development Lead
Join Instaffo and other leading companies in building a more productive, engaged engineering team with Flea.
Because developers know best.
© 2025 Flea Software UG (haftungsbeschränkt)
Made with ❤️ in Berlin