March 5, 2026

Disruption Happens Part 1: The Silence After the Scale

Disruption Happens. How Will You Respond?

For the last five years, my professional life was defined by scale.

At HP, I led technical program management for consumer services. I drove the development process for massive ecosystems—subscription services and apps generating billions in revenue. I wasn’t writing the code, but I was architecting the machine that built it.

Then came the San Diego site shutdown. Suddenly, the calendar was empty.

The "In-Between" Season

Like anyone else, I looked for the next thing. But the market was fractured. Many opportunities required relocation or felt like a step backward, focusing on maintaining the past rather than building the future.

It is a disorienting season for a leader who is used to having a roadmap. But I realized that if I believe there is a larger plan for my life, then waiting must serve a purpose.

So, I made a commitment. I would not just wait for the next job. I would steward the time. I treated my unemployment as an R&D phase to answer one question: "Who am I becoming while I wait?"

The Humility (and Magic) of Starting Over

I turned my attention to AI: The new baseline for every competitive roadmap.

Honestly? It was about 75% magic and 25% frustration.

The Magic: It wasn't just about writing code; it was about the team it replaced.

The Engineer: Tools like Cursor made writing syntax feel effortless, handling the boilerplate so I could focus on logic.
The Designer: I used AI to bridge my gap in UI/UX, turning my rough ideas into polished MUI components and responsive designs.
The Strategist: I used LLMs as a sounding board to stress-test product features and refine workflows. Suddenly, I wasn't just a solopreneur; I was a fully staffed product pod.

The Frustration: AI is like an eager junior engineer. It wants to please you, so it guesses. It throws new patterns at the wall. It fixes bugs by introducing hacks.

My challenge wasn't personal discipline; it was imposing discipline on the AI.

I realized my deep experience at HP wasn't obsolete; it was essential. Because I understood the patterns of scalable software, I could guide the AI effectively.

To build something robust, I had to be the Senior Architect. I had to force the AI to follow strict patterns and stop guessing. I provided the governance; the AI provided the syntax.

The ROI of the Wait

Looking back, I realize something startling: I have learned more about technology and value creation in the last 9 months than I did in the previous 5 years.

I’ve gone from "managing the process" to successfully shipping products.

Disruption is an invitation. If I had jumped immediately into another Director role, I would have missed this transformation. Because I was forced to wait, I became something new: A Builder.

Why I'm Writing This

I’m sharing this series because I know I’m not the only one navigating this shift. I didn't waste the quiet. I used it to build a new capability, and a new way to help companies navigate this shift.

An Invitation:

For the Individual: If you are in the "waiting room" right now, I’d love to hear your story. Connect with me here on LinkedIn and send me a DM—let’s swap notes on navigating the in-between.
For the Company: If you are sitting on a library of static content and wondering how to turn it into a dynamic AI product, I am dedicating time this month to IP Strategy Calls. Let’s look at your data and map out a transformation plan. Book your IP Strategy Call.