AgileX Solutions, a leading Software as a Service (SaaS) company, is celebrated for its adoption of agile methodologies. However, the company encounters a significant challenge when its non-technical Chief Executive Officer (CEO) mandates the use of quantitative metrics to gauge the engineering team’s performance.
This requirement starkly contrasts with the perspective of the Head of Engineering (HoE), who advocates for a more nuanced, holistic evaluation approach.
The CEO’s insistence on employing analytical tools such as Jellyfish to monitor various metrics—including velocity, burn-down charts, lines of code and commit frequency—sets the stage for a critical exploration of the drawbacks associated with over-reliance on superficial or “vanity” metrics.
This case study delves into the imperative of integrating quantitative data with qualitative insights to foster a balanced assessment framework.
As fellow CTOs and engineering leaders, share your experiences and tips in the comments. Let’s collaborate to create a roadmap for effective leadership in the dynamic environment of a start-up. Your expertise could be the guiding light for many others in similar situations.
Ken K.
My take on this situation (and I’ve definitely been in this position before):
One of the key things to understand is that with this kind of request, the CEO isn’t actually wanting insight into each individual’s or team’s performance to optimize or clean house, rather it’s an indicator that he doesn’t fully trust YOU and how you’re leading, what you’re accomplishing with the department.
Now this isn’t to say you’ve done or are doing anything wrong, either in-fact (what you’re accomplishing) or in trust from the CEO not being strong. But it is pointing out there’s some gap in their ability to trust you’re driving great value from what you’ve got.
Some CEOs need more data and detail than others, and perhaps that is the reason. Often as leaders, even technology ones, we maneuver our teams, deliveries, and departments partially via intuition and finesse, and not precise algorithms or outcomes. Some fantastic CEOs I’ve worked with are good with that, trusting me as the leader to keep them informed about how things are impacting the business.
Other CEOs it’s not that they love data and detail, they’re just subconsciously (or consciously) feeling the need to get involved, control, and take charge. So this speaks to helping build his trust in you, the leader.
Now what I do in these kind of situations is to definitely put in place a series of metrics to regularly talk through with the CEO. I’ll talk about what twist I put on it in a second, but just tracking and putting together metrics actually helps you as well, even if you don’t feel you need them. “If you want to improve a thing, track that thing” “The spotlight of awareness tends to make aligning to goals happen naturally on its own”
Okay, but to metrics. The fundamental twist or distinction I make here is to have the metrics as a whole be about MY OWN success or failure, as a leader, at accomplishing my strategy and targets (which encompasses the teams and individuals). Yes this can feel a bit vulnerable and make you anxious, but IMO it’s the best way forward.
What does this mean?
just my rambling $0.02, but take Responsibility, take Ownership of the ask, the trust building, and opening up to show not just what decisions you’re making, but how and why you make them.
90 Things You Need To Know To Become an Effective CTO
London
2nd Floor, 20 St Thomas St, SE1 9RS
Copyright © 2024 - CTO Academy Ltd
Leave a Reply