Naming a categoryinto existence.

When I joined, CalmWave had a product with no category. They were solving alarm fatigue in ICUs — a decades-old clinical problem — but what they'd actually built was significantly bigger: a platform that made systemic operational fragmentation visible and actionable across clinical, IT, and administrative teams.

The messaging didn't know this yet. The product was positioned as alarm-reduction software. Nurse wellness was mentioned vaguely. Customer discovery ran forty-five minutes of "what do you actually do?" Pipeline was zero.

The surface problem was positioning. The real problem was deeper.

Design contradicted narrative. Product prioritization was reactive. Writing anything — a pitch deck, a sales one-pager, a product brief — required weeks of internal negotiation, because there was no shared strategic foundation to reason from.

I designed the narrative architecture for a new category — Operations Health for healthcare — the connective layer that makes systemic operational fragmentation visible and actionable across hospital systems. The layer underneath clinical decision support, IT infrastructure, and staffing.

The hardest brand problem is creating the category before anyone knows it exists. That requires seeing what the product actually is before the company can articulate it, building the narrative logic that makes the category inevitable, and then executing across every surface — identity, product, sales, culture — until the story holds.

This is the work I find most interesting: the transition moment, when a company has outgrown its original narrative but hasn't yet earned the bigger one it's reaching for.