Building winning
engineering teams
Skill gets work done. Trust keeps the team intact when the plan breaks, the facts change, or the right decision becomes uncomfortable.
The strongest résumé does not automatically make the strongest teammate.
Simon Sinek popularized a lesson he attributes to Navy SEAL leaders: when they consider who belongs on a high-performing team, they look at both performance and trust. A highly capable person who damages trust can be more dangerous to the team than a solid performer whose conduct is dependable.
This is not an argument against excellence. It is an argument for a fuller definition of it. On an engineering team, performance means more than output. It includes judgment, maintainability, operational care, and the ability to make other people more effective. Trust means that teammates can rely on what you say, raise a concern without retaliation, and expect you to protect the mission rather than your ego.
Skill × trust
Drag the team marker—or click anywhere in the field—to explore how the leadership response changes.
Reading the model: The plot is a leadership lens, not a personality test or validated hiring score. Rate demonstrated behavior in context, revisit it over time, and never use “trust” as a proxy for similarity, comfort, or obedience.
Trust is built in the moments when candor has a cost.
A team does not learn that it is safe to speak from a values slide. It learns from what happens after a junior engineer challenges an estimate, a security reviewer blocks a release, or an operator says the rollback plan is weak. The response becomes precedent.
U.S. Navy leadership material describes psychological safety as a climate with high trust and high accountability: people can surface ideas and risks to the team or mission, while standards remain demanding. That pairing matters. Safety without accountability can become avoidance; accountability without safety can become silence.
Say what the team needs to know while there is still time to act.
-
1
Observe
State the evidence without assigning motives: what changed, failed, drifted, or remains unknown.
-
2
Connect
Explain the consequence for the customer, system, schedule, public, or team.
-
3
Recommend
Offer a next move, name the tradeoff, and identify the decision owner.
-
4
Confirm
Close the loop: who will do what, by when, and what evidence will show it worked?
“Direct” should mean low ambiguity, not low empathy.
Working principle
Ownership turns problems into work.
Jocko Willink and Leif Babin’s framework asks leaders to take responsibility for the conditions they influence: clarity, preparation, communication, coordination, and correction.
Applied well, extreme ownership interrupts blame. The first question after a failure becomes: What could I have made clearer, safer, simpler, or easier to verify? That question produces action. It does not erase individual responsibility, organizational constraints, or facts.
Ownership also needs authority. Asking engineers to “own” outcomes while denying access, time, decision rights, or an escalation path is not empowerment. It is responsibility without control. Leaders own that mismatch too.
Cover and move
Optimize across team boundaries. A local win that transfers risk downstream is not a system win.
Simple, clear, concise
If people cannot repeat the priority and intent, the communication is not finished.
Prioritize and execute
Make the highest-risk constraint visible, resolve it, then reassess the field.
Decentralized command
Share intent and guardrails so the person nearest the evidence can make the next decision.
Plans expire. Principles travel.
Markets shift
Customer needs, budgets, competitors, and timelines move faster than a static roadmap.
Complexity compounds
Dependencies, vendors, data, and automation create failure modes no single person can hold in mind.
Impact spreads
Software decisions shape access, privacy, safety, labor, opportunity, and public confidence.
Evidence changes
The best response is often a disciplined update, not a defense of the original plan.
Loyalty to the team cannot outrank responsibility to the public.
Every engineer eventually encounters pressure where delivery, revenue, reputation, or hierarchy pulls against safety, privacy, truthfulness, accessibility, security, or fairness. The exact stakes vary. The need for professional judgment does not.
The National Society of Professional Engineers places public safety, health, and welfare first. Its code also calls for engineers to work within their competence, communicate objectively, disclose conflicts, and acknowledge errors. Those duties turn trust outward: beyond the manager and the company to the people affected by the system.
-
01
Who carries the risk?
Include people who do not get a seat in the planning meeting. -
02
What evidence are we missing?
Separate an unknown from an assumption presented as fact. -
03
Can someone disagree safely?
Invite the strongest credible objection before commitment. -
04
Who can stop or escalate?
Name the path before urgency makes it politically expensive. -
05
What would ownership require?
Record the decision, monitor consequences, and correct course.
A meeting is only as intelligent as the information it permits into the room.
Psychological safety is not comfort, endless consensus, or freedom from standards. It is the shared belief that raising a question, admitting an error, or challenging a plan will not trigger humiliation or retaliation. That belief determines whether risk becomes visible while the team can still act.
Harvard Business Review has repeatedly connected high-performing teams with psychological safety and practical speaking-up behaviors. Its meeting guidance recommends giving everyone a turn, watching for domination, inviting candid discussion, circulating agendas, and using a round-robin format. These mechanisms matter because permission to speak is weaker when a person must interrupt power to use it.
Time-boxed turns are a useful implementation of that guidance—not a guarantee of a good decision. A timer cannot create trust, and equal airtime does not make every claim equally correct. It can, however, prevent one confident voice from consuming the team’s entire attention budget. Evidence still decides what happens next.
Structure the meeting so silence is a choice—not a consequence of hierarchy.
-
3 minSilent read
Facts, goal, constraints, unknowns.
-
8 minRound robin
Up to 60 seconds per person; passing is allowed.
-
4 minTest the risks
Ask what would make the plan fail.
-
3 minDecide
Owner states choice and tradeoff.
-
2 minClose
Action, evidence, date, escalation path.
Example protocol, not a universal prescription. Adjust the round length to team size and decision risk; do not compel disclosure or manufacture agreement.
A winning team does more than deliver. It remains accountable for what delivery changes.
The team can surface reality quickly, disagree without fracture, decide without hiding tradeoffs, and learn without searching for a scapegoat. Skill makes the response capable. Trust makes it coordinated. Evidence keeps it honest. Ownership makes it actionable. Ethics directs it toward a future worth building.