Optimizing a 70-Engineer Team: Challenges

I still remember the moment we made the bold decision: shift our team of 70 engineers to a four-day work week. On paper, it was idyllic—a promise of efficiency and improved work-life balance. But in practice, it was a cocktail of opportunities and surprises (not always pleasant). Running a €100M company with such a lean engineering team is like precision juggling. We had to rethink our workflows, standardize our tech stack, and adopt the Scrum framework to orchestrate it all. And let's not even get started on the unexpected challenges that pop up when you shake up the status quo like that. But don't worry, it can work—if you know how to anticipate the pitfalls. Here, I share our roadmap, successes, and the pitfalls to avoid so that your team stays agile and high-performing.

Engineering Workforce Composition: The 10% Rule

At our company, the engineering team makes up only 10% of our total workforce, yet it drives our core innovations. Yes, just 70 engineers in total. This might seem limiting, but it's this very ratio that pushes us to be hyper-efficient and maximize each team member's impact.

First, we've learned to balance skill sets and roles for maximum impact. Instead of over-specializing, we focus on versatile profiles capable of moving between projects. However, this comes with trade-offs: deep specialization can be lost, but the agility and speed of execution are undeniable gains.

As we scaled our team to 70 engineers, we realized that adding personnel isn't linear in terms of productivity. Today's 70 engineers are organized to maximize collaboration and reduce bottlenecks.

Efficiency and Productivity Strategies: What's Worked

To ensure our team performs at its best, I've implemented productivity tools that have truly proven their worth. I orchestrate our workflows for seamless collaboration and avoid the traps of over-meeting that kill action.

• Utilizing Jira for real-time task tracking.
• Integrating real-time data to inform decision-making.
• Adopting internal tools for time savings.

The balance between autonomy and accountability is crucial. We trust our engineers to lead their projects, but we also set clear, measurable goals. This prevents drift while fostering creativity.

Four-Day Work Week: Structure and Impact

Designing a four-day work schedule without losing momentum is a challenge we've successfully tackled. The impact on morale is huge, but adjustments are necessary.

We've opted for a model where three days off allow for better recharging. However, this requires careful task distribution. For instance, heavy tasks are grouped to optimize workdays.

The four-day work week isn't just about cutting work time, it's about reinventing our productive approach.

Be cautious of pitfalls: the temptation to overload workdays can be strong, but that defeats the purpose.

Challenges of Introducing New Methodologies

Adopting new methodologies like Scrum isn't without challenges. Resistance to change is common. I navigate these team dynamics carefully, ensuring each member understands the how and why.

Leadership's role is crucial: without visible and constant support, the transformation can fail. That's why I always test iteratively before full-scale rollout.

Common mistakes include rushing too fast and inadequate communication. Yet, success relies on clear and ongoing communication.

Database and Technology Standardization: A Game Changer

Standardizing our tech stack has been a radical change for our efficiency. By limiting tech sprawl, we've cut costs and increased consistency.

This process isn't without risks, notably vendor lock-in. To avoid this, we've carefully chosen flexible and interoperable tools. Consistency shouldn't kill innovation.

Ultimately, standardization isn't about stifling creativity, but channeling it effectively and sustainably.

Transitioning to a four-day work week and standardizing our tech stack were real game changers, but let's be honest, they came with their own sets of challenges. First, we had to stay agile and focused to navigate these adjustments. Then, we saw morale and productivity shoot up, which directly reflects the impact of these changes. Look, with 70 engineers, we managed a 10% efficiency boost by implementing these strategies. But remember, there are hurdles to introducing new methodologies.

Looking forward, I believe these practices could redefine how engineering teams operate. There's a real opportunity here, but we can't overlook the necessary trade-offs.

So, think about your own team's structure and methodologies. What small changes could drive big improvements in efficiency? Check out the full video "€100M company. 70 engineers." for deeper insights: YouTube.