Jellyfish CTO: Feelings aren't facts and why DORA doesn't cut it

In this week's installment of the Level Up podcast, Kenneth Rose, the co-founder and CTO of OpsLevel, sat down with engineering leader Eli Daniel from Jellyfish. The heart of their discussion beat around a central theme that resonates deeply with us: the transformative power of metrics in engineering leadership.

From the Ground Up: Eli’s Path

Eli Daniel didn’t just appear at the pinnacle of engineering leadership; he climbed every rung of the ladder. With a rich history from CTO at Wevo Conversion to leading Bridge's engineering efforts, Eli brings to the table a seasoned perspective on navigating the shift from hands-on coding to leadership. It’s a journey many of us are on or will embark upon, marked by the shift from making to mentoring.

Metrics: More Than Numbers

Eli's philosophy cuts through the common misconception that metrics are merely a collection of numbers. He posits metrics as the compass that guides decision-making and leadership. Shifting away from reliance on gut feeling or experience alone, he champions a data-driven strategy. This perspective unlocks a clearer understanding of how teams operate, the direction projects are heading, and where the opportunities for growth lie.

The Role of Productivity Metrics

Here’s where it gets practical. Eli zeroes in on productivity metrics as the north star for engineering teams. These metrics—cycle times, throughput, issue resolution rates—serve as quantifiable insights that spell out how effectively a team is operating. They’re not just numbers; they’re narratives about our teams' day-to-day struggles and victories.

Thoughtful Implementation: A Balancing Act

Eli warns against the siren song of being overly metrics-driven, where numbers trump human factors, potentially skewing incentives and dampening morale. Instead, he envisions metrics as part of a balanced leadership toolkit. It’s about leveraging data to inform and guide, not dictate.

Building a Metrics-Informed Culture

The conversation also navigated the delicate terrain of culture. Introducing metrics isn’t just about the numbers—it’s about the message you’re sending to your team. Eli underlines the importance of clear, open communication regarding the role and intent behind metrics. This transparency metamorphoses metrics from an oversight tool into a shared instrument for team empowerment and development.

What Lies Ahead for Engineering Metrics

Peering into the horizon, Eli’s optimism about the future of engineering metrics shines through. He anticipates a refined approach where metrics evolve in tandem with team dynamics and technology advancements, becoming even more aligned with overarching organizational goals.

Conclusive Insights

Drawing from Eli Daniel’s discourse, it’s evident that judiciously curated and applied metrics can be game changers in the realm of engineering leadership. They foster an environment where data paves the way for insightful leadership, nurturing teams that are not just productive, but are also aligned and motivated.

For those at the helm of engineering teams, or those aspiring to lead, this conversation is a treasury of insights on leveraging metrics to sculpt a high-performance culture.

Embarking on this metrics-informed journey promises not just enhanced productivity and clarity, but a transformation in the very fabric of engineering leadership. Let’s navigate this together, shall we?

‍

‍

Jellyfish is a platform that helps engineering leaders translate and maximize the business impact of their teams. Visit the Jellyfish website to learn more.