
Sign up to save your podcasts
Or


When a security incident, service outage, or product bug hits your portfolio, you don't get extra hours in the day. You get the same twenty-four hours as everyone else to protect millions in ARR and keep twenty accounts from going red simultaneously.
In this episode, Mark Bernardin walks through the systematic frameworks he's used to manage portfolio crises at companies like Cofense, Deepwatch, and Palo Alto Networks. He explains why the biggest mistake CSMs make during a crisis is treating every account the same - and why that approach fails every single time.
Mark breaks down his crisis triage methodology, showing how to categorize accounts into Critical, Standard, and Stable tiers based on business impact, relationship risk, and strategic value. He shares specific examples from a Saturday morning SOC platform outage at Deepwatch and a critical security vulnerability at Palo Alto Networks, demonstrating how proper triage and communication saved accounts that could have easily churned.
The episode covers crisis communication strategies that maintain trust when everything else is broken. Mark provides the exact template he uses for initial customer acknowledgment within the first hour, and explains how to customize communication for technical stakeholders, executive stakeholders, and operational stakeholders - because they all need different information to do their jobs during a crisis.
Mark also addresses internal coordination, explaining how to prevent your own team from creating additional communication chaos during an emergency. He outlines the four-step coordination protocol: establishing a single source of truth, defining communication ownership, creating internal update cadences, and documenting everything for the post-mortem.
The episode tackles one of the hardest aspects of crisis management: post-crisis relationship recovery. Mark explains why the crisis isn't over when the technical problem is solved - it's over when your customers say it's over. He shares his framework for scheduling post-crisis debriefs with critical accounts, asking for feedback, and acting on what you learn to rebuild confidence in the relationship.
Mark doesn't shy away from the difficult decisions CSMs face during portfolio crises. He discusses how to prioritize resources when you can't give everyone everything they want, how to decline customer requests professionally without making promises you can't keep, and how to make business decisions without apology while still maintaining customer relationships.
This episode is essential listening for any CSM who manages enterprise portfolios, works in high-stakes industries like cybersecurity or financial services, or wants to build crisis management capability before an emergency hits. Mark includes specific guidance for different crisis types - security incidents, service outages, product bugs, M&A announcements, and leadership changes - making this a comprehensive playbook for portfolio crisis management.
The companion download includes crisis triage frameworks, communication templates for initial acknowledgment and stakeholder updates, internal coordination protocols, post-crisis recovery checklists, and a 30-day crisis preparedness plan to help you build response capability before you need it.
By ClearPath CXWhen a security incident, service outage, or product bug hits your portfolio, you don't get extra hours in the day. You get the same twenty-four hours as everyone else to protect millions in ARR and keep twenty accounts from going red simultaneously.
In this episode, Mark Bernardin walks through the systematic frameworks he's used to manage portfolio crises at companies like Cofense, Deepwatch, and Palo Alto Networks. He explains why the biggest mistake CSMs make during a crisis is treating every account the same - and why that approach fails every single time.
Mark breaks down his crisis triage methodology, showing how to categorize accounts into Critical, Standard, and Stable tiers based on business impact, relationship risk, and strategic value. He shares specific examples from a Saturday morning SOC platform outage at Deepwatch and a critical security vulnerability at Palo Alto Networks, demonstrating how proper triage and communication saved accounts that could have easily churned.
The episode covers crisis communication strategies that maintain trust when everything else is broken. Mark provides the exact template he uses for initial customer acknowledgment within the first hour, and explains how to customize communication for technical stakeholders, executive stakeholders, and operational stakeholders - because they all need different information to do their jobs during a crisis.
Mark also addresses internal coordination, explaining how to prevent your own team from creating additional communication chaos during an emergency. He outlines the four-step coordination protocol: establishing a single source of truth, defining communication ownership, creating internal update cadences, and documenting everything for the post-mortem.
The episode tackles one of the hardest aspects of crisis management: post-crisis relationship recovery. Mark explains why the crisis isn't over when the technical problem is solved - it's over when your customers say it's over. He shares his framework for scheduling post-crisis debriefs with critical accounts, asking for feedback, and acting on what you learn to rebuild confidence in the relationship.
Mark doesn't shy away from the difficult decisions CSMs face during portfolio crises. He discusses how to prioritize resources when you can't give everyone everything they want, how to decline customer requests professionally without making promises you can't keep, and how to make business decisions without apology while still maintaining customer relationships.
This episode is essential listening for any CSM who manages enterprise portfolios, works in high-stakes industries like cybersecurity or financial services, or wants to build crisis management capability before an emergency hits. Mark includes specific guidance for different crisis types - security incidents, service outages, product bugs, M&A announcements, and leadership changes - making this a comprehensive playbook for portfolio crisis management.
The companion download includes crisis triage frameworks, communication templates for initial acknowledgment and stakeholder updates, internal coordination protocols, post-crisis recovery checklists, and a 30-day crisis preparedness plan to help you build response capability before you need it.