A data-driven approach grounds a discussion or decision in relevant evidence rather than assumptions alone. For an engineering manager, it can turn a disagreement about priorities, performance, or resources into a conversation about what is happening, what matters, and what to do next. Evidence helps people assess a situation objectively; listening to their perspectives remains essential. section 3.1.3 section 2.5.5
A practical way to use the approach is to:
- Name the decision and its trade-offs. When balancing delivery speed and quality, consider engineering goals, business needs, technical debt, and team well-being rather than optimizing for speed alone. section 2.5.6
- Gather evidence suited to the question. Team measures might include delivery timelines, service-level agreements, project outcomes, technical debt, surveys, and feedback; establish baselines so changes can be evaluated. section 3.2.7
- Invite perspectives and test assumptions. In a conflict, hear people individually before bringing them together for a data-driven discussion. If they remain stuck, a neutral party may help; consensus need not mean complete agreement. section 3.1.3
- Explain the evidence in terms the audience can use. For nontechnical partners, connect a technical problem to reliability, customer effects, service commitments, and short- versus long-term costs. section 9.3.4
- Choose an action, provide support, and check what changes. For a struggling team, make incremental process improvements and use measurements and feedback to assess whether they help. section 4.5.4
Performance discussions need particular care. Use observations, self-assessments, peer feedback, and notes from the relevant period to build a rounded view. Discuss specific behavior and its effects, including strengths as well as gaps; do not assume you know why someone is struggling. Consistent performance standards can help counter bias, while personal circumstances still call for empathy and support. A data-driven review is preparation for a two-way conversation, not a substitute for one. section 4.3.1 section 4.5.1 section 4.2.2 section 4.3.3
Discussing a hiring request
Suppose leadership asks a team to make do with its current staffing. Show the team’s capacity and how its resources are allocated. Then explain the consequences of not hiring—such as project delays or burnout—alongside possible priorities for the existing team. The evidence supports a discussion of risks and choices; it does not guarantee approval for another hire. section 7.1.1
Handling resistance to a change
When a planned change meets pushback, keep communication open, ask clarifying questions, and hold an objective discussion. Early feedback can reshape a phased rollout; a proof of concept or early demo can help test feasibility and build support. What evidence would change the plan, and what support do affected people need? section 13.2.4
