EM Tech #17: From Field Experience to Feature Design

Hey EM Tech Family! 👋

It's been a minute (okay, more like over six months) since my last newsletter, and I've missed our conversations about the intersection of technology and emergency management. You might be wondering where I've been, and that's working and embracing the chaos of my little kids.

The Career Plot Twist

Remember when I used to write about emergency management technology from the field? Well, if you've been following me lately, I've switched seats – from being a user of emergency management software to actually building it. For the past 12+ months, I've been heads-down working on something that keeps my mind preoccupied (in a good way): creating a communication product that aims to transform and simplify how we communicate throughout incidents, critical events, and pre-planned events.

The Complexity Challenge

Here's what I never fully appreciated from the user side: consolidating legacy systems into a single, powerful platform isn't just a technical challenge – it's a philosophical one. Eventually the products we use become feature powerhouses, packed with capabilities that customers have relied on for years. But here's the catch: some advanced features, while powerful, can make the products increasingly complex to use. The challenge is to maintain simplicity but forming a consolidation of workflows that continue to get the job done. And when it comes to communicating during stressful times we must make it as simple as possible.

Think about it: when was the last time you used every feature in your incident management system or mass notification system? When stress levels are high and seconds count, do you really need seventeen different ways to configure a notification template?

The Art of Feature Curation

One of the most challenging aspects of this journey I've taken during my career pivot has been deciding what stays and what goes. We're asking tough questions:

• Which features are actually used regularly?
• Which features are loved versus merely tolerated?
• Can we combine similar features into something more intuitive?
• How do we maintain power while reducing complexity?

It's like being a chef trying to simplify a complex recipe without losing the flavor. Some ingredients might seem essential because they've always been there, but are they really making the dish better?

From EM to PM: A Journey of Discovery

Transitioning from emergency manager to product manager has been like learning to speak a new language while teaching others your native tongue. Working on technology that my former colleagues and peers use to save lives is both humbling and exhilarating.

But here's what keeps my mind preoccupied: how do we guide users through this transition? How do we convince someone who's mastered a complex workflow that a simpler one might be better? It's not just about building new technology – it's about changing mindsets.

Breaking Free from "The Way It's Always Been Done"

The hardest part? Stepping away from established patterns. When you've been doing something one way for years, change can feel like loss. I get it – I was on the user side not long ago. But sometimes we need to ask: are we doing it this way because it's the best way, or because it's the familiar way?

Some of you "power users" can perform incredible feats with the systems you use today. You learned every shortcut, every hidden feature, every workaround. Asking you to change is asking you to temporarily become beginners again. That's a tough sell.

The Light at the End of the Tunnel

But here's what excites me: when we get this right, we're not just building another emergency management tool. We're creating something that combines the power of current solutions with the simplicity and intuition that modern technology can offer. Imagine having all the capabilities you need, but accessed through an interface so natural it feels like an extension of your thinking.

What's Coming

Get ready for a fresh perspective on EM Tech. Future newsletters will dive deep into:

• The psychology of feature design in critical systems
• Real examples of how to simplify complex workflows
• How field experience shapes product development
• The future of emergency management communications
• User stories and how they're shaping our direction

Let's Talk

This is where you come in. I want to hear your thoughts:

• What features in your current systems do you love? Which ones drive you crazy?
• How do you balance power and simplicity in your operations?
• What would make your emergency management technology more intuitive?
• What challenges are you facing with your current emergency management technology?

Your experiences and insights aren't just valuable – they're essential to getting this right. Drop a comment below or connect with me directly. Let's make these newsletters a two-way street, where your voice helps drive the conversation about the future of emergency management technology.

Stay safe and stay connected,

James

P.S. Next week, I'll share some surprising discoveries about feature usage patterns that challenged everything we thought we knew about emergency management software. Trust me, you won't want to miss it!