Skill Development Progress

For two decades, I’ve seen engineering teams operate under relentless pressure – to ship features, fix bugs, and meet deadlines. But often lost in this whirlwind is a deliberate focus on how those features are built – on the growth of the engineers building them. We meticulously track velocity, bug counts, and deployment frequency. But what about skill development progress? It's surprisingly difficult to measure, yet arguably more crucial for long-term team health and innovation.

Consider this: a recent report by Gartner indicates that 70% of organizations lack the necessary skills to fully execute their digital strategies. This isn't just about filling positions; it’s about proactively cultivating the talent you already have.

This isn’t about turning engineers into coding robots. It’s about recognizing that a static skillset quickly becomes a liability in our rapidly evolving industry. And it's about building a system that doesn't just track output, but actively fosters and measures growth.

The Problem with Traditional Metrics

Many traditional engineering metrics inadvertently discourage learning. Velocity, while useful, can incentivize engineers to stick with what they know to maintain speed. Bug counts, while important, don’t tell you why the bugs happened – were they due to a lack of experience with a new technology, a misunderstanding of a core concept, or simply carelessness?

I remember one team I led where we were fiercely focused on adhering to a specific methodology. It quickly became less about delivering value and more about hitting all the prescribed ceremony checkpoints. Engineers were more concerned with filling out the right Jira tickets than truly understanding the problem they were solving. This wasn’t about the methodology itself, but a cautionary tale about prioritizing process over progress – a trap any team can fall into when rigidly applying any framework without critical reflection. Jørgensen and Sjøberg’s work highlights the danger of simply repeating processes without reflecting on what’s learned, or not learned, from experience.

We risk creating teams of highly proficient implementers but lacking the adaptability and critical thinking skills to tackle truly novel challenges.

Shifting Focus: Defining & Measuring Meaningful Growth

So, how do we move beyond simply tracking output and start measuring skill development progress? It starts with defining what that means. Here’s a framework I’ve found useful, categorized into three key areas:

1. Technical Proficiency: This is the most obvious, but often the least nuanced. Don't just measure "lines of code" or "features completed." Consider:

• Technology Adoption: Are engineers actively learning and applying new technologies relevant to the team’s goals? Track participation in training courses, contributions to internal tech talks, or the number of "first-time" implementations of a new tool or library.
• Code Review Contributions: Look beyond simply receiving code reviews. Are engineers proactively giving thoughtful and constructive feedback? This demonstrates a deeper understanding of code quality and design principles.
• Complexity Handled: Are engineers consistently tackling increasingly complex tasks? Track the types of bugs they resolve or the scope of features they build.

2. Problem-Solving & Design Skills: This is where true growth happens. Look for evidence of:

• Root Cause Analysis: When bugs occur, are engineers simply fixing the symptom, or are they digging deeper to understand the underlying cause? Encourage thorough post-mortems and documentation.
• System Thinking: Can engineers see how their work impacts the larger system? Are they considering potential side effects and dependencies?
• Design Participation: Are engineers actively involved in the design process, offering valuable insights and challenging assumptions?

3. Collaboration & Communication: Engineering is rarely a solo activity. Assess:

• Knowledge Sharing: Are engineers actively sharing their knowledge with others through documentation, mentoring, or internal presentations?
• Constructive Feedback: Are they able to give and receive constructive feedback gracefully?
• Cross-Functional Collaboration: Can they effectively communicate technical concepts to non-technical stakeholders?

Actionable Steps for Implementation

Measuring skill development isn’t about adding more burdensome tasks. It's about integrating it into existing processes:

• Regular 1:1s: Focus on growth conversations, not just task updates. Ask engineers about what they’re learning, what challenges they’re facing, and what support they need. Specifically, try asking questions like: “What’s one thing you learned this week?” or “What skill are you hoping to improve in the next month?”
• Performance Reviews: Move beyond simply evaluating past performance. Set clear growth goals for the future and track progress against them.
• Dedicated Learning Time: Encourage and provide dedicated time for engineers to explore new technologies, read articles, or attend training courses. Recognizing that time is a constraint, consider allocating a percentage of each sprint (e.g., 10-20%) for dedicated learning activities.
• Internal Tech Talks & Workshops: Create a culture of knowledge sharing within the team.
• "Learning Pairs": Have engineers pair program on tasks where one is learning a new skill from the other.

The Future of Tech Education & Continuous Learning

Drew Procaccino et al.'s work on early prediction of software development success highlights the importance of foundational skills and proactive identification of potential roadblocks. The increasing demand for specialized technical skills necessitates a focus on continuous learning for all engineers.

While standardization might address skill gaps, we must be careful not to stifle creativity and innovation. The most valuable engineers aren’t just proficient in specific technologies; they’re adaptable, resourceful, and lifelong learners.

Investing in skill development isn’t just good for your engineers; it’s essential for the long-term health and success of your team and organization. It’s time to prioritize measuring growth alongside output.

To get started, identify one skill each team member wants to develop in the next quarter and create a plan to support their growth. Start small, be consistent, and watch your team thrive.