Course contentsShow
← Software Engineering
Lesson 1814 of 1,93352. Technical LeadershipFree lesson

Using Data and Evidence

Learn how to gather and present objective data, prototypes, and analysis to inform group decision-making.

Using Data and Evidence

What You'll Learn

You'll learn how to gather and present objective data, prototypes, and analysis to make technical discussions more productive and decisions more defensible.

Why Data Beats Opinion

In technical discussions, opinions can deadlock teams. "I think approach A is faster" versus "I think approach B scales better" creates friction. Data transforms these debates into collaborative problem-solving. When you present benchmarks, prototypes, or metrics, you shift the conversation from "who's right" to "what does the evidence suggest?"

Think of data as a shared flashlight in a dark room—everyone can see the same thing and discuss what they observe together.

Types of Evidence for Technical Decisions

Quantitative Data: Performance benchmarks, load test results, memory profiling, latency measurements, error rates from logs, or cost projections.

Prototypes and Spikes: Small, time-boxed implementations that answer specific questions ("Can this library handle our scale?" or "How difficult is this migration?").

Qualitative Evidence: User research findings, incident post-mortems, developer experience surveys, or dependency analysis showing coupling.

External Research: Industry case studies, academic papers, competitor analysis, or open-source project experiences.

Presenting Evidence Effectively

Don't just dump data—tell its story. Start with the question you're answering ("Will switching databases improve our query performance?"), show your methodology ("I benchmarked 1000 requests against both systems"), present findings clearly ("Database B was 3x faster for reads but 20% slower for writes"), and connect to the decision ("Given our read-heavy workload, B appears better").

Be honest about limitations: sample size, test environment differences, or assumptions you made. This builds trust and helps others evaluate the evidence critically.

Making Evidence Actionable

The best evidence points toward a decision. "We should choose option X because the data shows Y, which addresses our constraint Z." Not "here's data, you figure it out."

Key Takeaway: Objective data, prototypes, and documented analysis transform subjective technical debates into evidence-based decision-making, building consensus and trust across your team.