Perspective shaped by two decades building product organizations, platform strategies, and operating models across retail, telecom, media, and SaaS. The problems are always part organizational, part technical. The advantage belongs to whoever figures that out fastest.
These are the patterns behind the work.
From Darrin Johnson
Three executives, three priorities, no shared roadmap. Decisions get made in hallways and reversed in meetings. The product team is stuck waiting for alignment that never comes.
The role exists on paper but there's no operating model, no stakeholder alignment, and no shared definition of what product management means at your organization. The function needs to be built, not just filled.
Teams building shadow tools. Duplicate assets piling up because search doesn't work. The platform was fine three years ago but the organization has outgrown it and nobody owns the problem.
Cross-team dependencies nobody mapped. A planning process that takes days when it should take hours. Eight teams operating independently with no portfolio-level view of what's actually being built.
Every engagement starts with listening. These aren't frameworks I import. They're patterns I've seen work across very different organizations.
Took a platform product from first release to $7M annual revenue in 18 months. Created a reseller channel that opened a down-market segment and drove half of total sales.
Identified through structured user research that a consumer smart home product had a far larger market as a property management platform. Pivoted positioning, expanded the user base tenfold, and built $1.8M in recurring revenue.
Redesigned content operations across 150+ local TV stations, eliminating 42% of duplicate assets and cutting time-to-publish by 10%. A meaningful competitive edge in a business where being first in search drives revenue.
Consolidated eight independently operating product teams into a shared planning increment process, reducing multi-day planning cycles to a single half-day session and surfacing cross-team dependencies for the first time.
I take on a small number of engagements where the problems are real and the organization is ready to do the work.
Start a conversation →