When leaders try to manage too many people directly, clarity disappears and momentum suffers. In this episode, I break down the importance of span of control across public safety, healthcare IT, and project teams. Whether you're building a department, spinning up an incident team, or planning a go-live, the rule of 3 to 7 direct reports still holds. Five is the sweet spot—but there are exceptions.

We’ll walk through how ICS uses structure to maintain speed under pressure, how project teams should plan their structure during resource alignment, and why we must review roles and objectives regularly to stay on track. Whether you lead full-time staff or ad hoc teams, this episode is your blueprint for sustainable team design.

People first. Combined process. Progress together.

On this Foundations Friday, How to Speak the Same Risk Language, we break down how project managers and emergency leaders can align around a shared risk language. Whether you're using a THIRA or a risk register, the goal is the same: identify what could go wrong, how bad it might be, and what to do about it. Real teamwork starts when everyone sees risk through the same lens.

Warren Buffett said it best: “Risk comes from not knowing what you're doing.”

On today’s episode, How to Combine Project Risk Tools with Emergency Planning, we’re focusing on how project managers and public safety leaders can speak the same language when it comes to risk. The Federal Emergency Management Agency, or FEMA, created the Threat and Hazard Identification and Risk Assessment—also known as THIRA—to help communities anticipate and plan for the unknown. In the same way, project risk registers help uncover obstacles before they become blockers. Today, we’ll connect the dots between THIRA, stakeholder maps, and integrated risk matrices—so your team can prepare, prioritize, and progress, no matter the scenario.