What processes do you have to detect performance problems?

Original prepared answer

Detection of Skill and Behavioral Gaps

One of my core management philosophies is "trust and verify." This principle allows me to provide my managers and engineers with the autonomy they need to apply their creativity and experience while ensuring accountability through structured oversight.

To balance autonomy with performance management, I rely on a combination of high-feedback-loop and short-feedback-loop frameworks.

High Feedback Loop Frameworks

I implement structured processes such as:

• Quarterly Objectives and Key Results (OKRs): I set clear expectations and measuring progress against them.

• Performance Evaluations: Conducted half yearly, these evaluations align with role's expectations and company values.

While effective, these mechanisms often have longer feedback cycles, making it crucial to supplement them with more frequent observation points.

Micro Feedback Loop Frameworks

To track day-to-day progress and identify issues early, I rely on:

• Regular Project Sync-Ups: These meetings help identify blockers, delays, or gaps in technical understanding, allowing me to step in and provide targeted support

• Data-Driven Sprint Planning and Retrospectives: I leverage metrics such as:

• Commit Volume: Low commit volumes may signal skill gaps, engagement issues, or low velocity.

• Missed Story Points or Deadlines: A pattern here may indicate technical gaps or poor estimation.

• Poor Engagement in Team Rituals: Limited participation in discussions or stakeholder engagement may highlight motivation or collaboration concerns.

• Repeatedly Getting Stuck: Consistently needing others to unblock them often points to technical challenges or confidence issues.

These metrics serve as proxies for individual and team performance and often help me differentiate between process inefficiencies and individual skill or behavioral gaps.

Identifying the Root Cause

When I identify a problem, my first step is to determine whether it’s:

• An isolated incident or

• A recurring pattern that’s impacting productivity.

I also assess the scope of the impact:

• Does it affect just the individual's output? or is it slowing down the entire team?

• Is it blocking an external dependency or impacting customer experience?

Example - Systemic Issue Resolution

When I joined Booking, my frameworks revealed that one of our staff engineers was struggling to complete sprint tasks consistently. Upon investigation, I discovered that he had unintentionally become a bus factor for a critical domain area, spending excessive time supporting stakeholders and addressing their queries.

To mitigate this: ✅ We redistributed knowledge across multiple engineers. ✅ Created primary and secondary owners for key domains to share responsibility. ✅ Established clearer stakeholder communication protocols.

As a result, the staff engineer regained focus on his core development tasks, and the issue dissipated over the next few sprints.

This experience taught me that systemic issues like knowledge silos often masquerade as individual performance gaps — addressing them early can prevent broader inefficiencies.

Communicating Negative Feedback

I believe providing constructive feedback is a powerful way to support individual growth, but it requires thoughtfulness, empathy, and clarity.

I make feedback a continuous process and actively use my 1:1s to provide balanced feedback — acknowledging achievements while addressing concerns.

Communicating the Feedback - My Approach

I follow a structured yet empathetic approach:

• Be Clear and Direct: I avoid vague language and instead provide clear, factual observations.

• Set Clear Expectations: I begin by aligning on what’s expected in their role and what success looks like.

• Provide Evidence-Based Observations: Rather than subjective remarks, I present specific instances that illustrate the behavior or performance concerns.

• Explain the Impact: I connect the behavior to its broader impact — whether it’s slowing team progress, creating rework, or affecting stakeholders.

• Collaborate on a Plan for Improvement: My goal is always to be constructive. I offer practical suggestions or a step-by-step improvement plan.

• Provide Support: Often, I actively support the individual by sharing resources, pairing them with a mentor, or dedicating extra coaching time.