I run digital product for Medicare Part D at Humana, leading the team behind the tools and experiences roughly 10 million members touch every year. I didn't start out in product, though. I got here by way of engineering, internal consulting, and a few years buried in spreadsheets doing finance work, and that mix still shapes how I think. I write about all of it every week in PM Pulse, a newsletter for people who'd rather borrow a good framework than reinvent one.
What actually gets me up in the morning is making healthcare make sense to the people stuck dealing with it. Most of my work lives inside Medicare Part D and pharmacy benefits (prior authorization, provider portals, self-service tools), and the people on the other end are often older, on a fixed income, and the least equipped to fight back if the system lets them down. I think a lot about the gap between "technically compliant" and "something a member can actually use without calling in scared."
I'm just as into the craft side of product: taste, specifically. Not frameworks, but the judgment call you make before the data exists to back you up. Anyone can ship a prototype in a day now. Knowing what's actually worth building is the part that still takes years to earn.
Strategy that stays on a slide is just decoration. My job is to make it ship.
Most companies already own everything they need. What they're missing is the discipline to point it at something. Assets are what you have; activities are what you do with them, and that gap is where the value actually lives.
Every product decision is really a decision about somebody's time. I try to ask "what clock is this person racing against" instead of "what does this feature do." It's usually the more honest question.
Ideas don't move because you convinced a room. They move because you found the three or four right people at each level and worked through them. That's the whole game with organizational change.
GE's Corporate Audit Staff dropped me into a new business every four months with no ramp time. There's no faster way to learn than that: take the feedback without getting precious about it, start executing before you feel ready, and fix it in the next rep. Outcomes are what get graded, not how good the plan sounded on day one. Tenacity is just what gets you from a rough first attempt to a decent third one.
I started at GE Healthcare in the Edison Engineering Development Program, basically an accelerated bootcamp for new engineers, with four rotations across CT and MRI development. This is where I actually learned what human-centered design means, how to run a project end to end, and how to think in systems instead of isolated tasks.
From there I joined GE's Corporate Audit Staff, an internal consulting program selective enough that roughly 40% of GE's C-suite came up through it. I rotated every four months into a different GE business (Healthcare, Oil & Gas, Power, Digital), which is a fast way to learn you don't need to be the smartest person in the room to add value. That led to a Supply Chain Strategy role at GE Power, where I ran P&L work and picked up the finance and stakeholder-management instincts I still lean on today.
Eventually I wanted to combine the engineering and strategy sides of my background, so I made the jump into product management, first at CVS Health, working on pharmacy benefits and virtual care strategy, while finishing my MBA at Kellogg on the side. I've been at Humana since 2021, and today I'm Director of Digital Product & Contact Center Experience for Medicare Part D. I also sit on the board of Tuk Took Bites, a small food startup, because apparently I can't resist a good product problem even outside of healthcare.
- Writing PM Pulse, a weekly newsletter. Every week I take a framework (JTBD, S-curves, whatever fits) and point it at something actually happening in healthcare or product, instead of teaching the framework in the abstract.
- Sitting on the board of Tuk Took Bites, a food startup, where I use the role to keep stretching into product marketing and branding, the scrappy way: pick something I don't know yet, use AI to get up to speed fast, and see what breaks. I'd rather be bad at something new for a month than comfortable at something old for a year.
- Building my own AI workflow. I use Claude less like a one-off assistant and more like a research partner that remembers context: a running frameworks library, a prompt library, a pipeline that gets a little better every week instead of starting from scratch.
- Practicing taste on purpose, a standing weekly habit of writing down an opinion on a product before I check what anyone else thinks of it. Small thing, but it's the only way I've found to actually build judgment instead of just collecting opinions.
Open-source Claude Skills and working documents, free to install and use.