Flash Points: Clarity Beats Consensus

Projects don't fail because people disagree. They fail because no one is sure who gets to decide. In this episode of Project Command: Flash Points, Lieutenant Duke Cuneo breaks down a hard leadership truth: consensus feels collaborative—but clarity drives results. On the fireground, we instinctively understand unity of command. Someone has it. Everyone aligns to it. Input flows. Adjustments are made. But authority is never in question. Yet in project work—especially in fire-EMS operations, staffing models, and policy changes—we often trade command for prolonged consensus. Meetings multiply. Feedback cycles expand. Alignment becomes the goal instead of progress. And slowly, the project drifts. This Flash Point explores: Why discussion without direction creates a vacuum The difference between input and ownership How indecision quietly erodes trust Why clarity is leadership—not authoritarianism Practical behaviors clear leaders demonstrate consistently Consensus can improve decisions. But clarity is what makes them happen. If you're leading a project right now, ask yourself: Have I been clear—or just inclusive? Clarity beats consensus. Every time.