I’m seeing more companies than ever commit to the product model, and the shift is unmistakable. Boards are leaning in, CEOs are being pushed, and the subtext is clear: valuation. That pressure can be a powerful accelerant, but it also introduces a very real dynamic—when pilot teams become the vehicle for transformation, the politics around them can either unlock momentum or quietly poison the well.
In my experience, the politics of pilot teams surface fast: who gets on the team, which domain gets picked, how success is framed, and whether the rest of the organization views the pilots as an elitist “special ops” unit or a path for everyone to follow. If I don’t address these dynamics head-on, I watch pilot teams deliver isolated wins that never translate into a durable product operating model.
Here’s how I approach it. I start by being explicit about purpose: pilot teams exist to de-risk the transformation by proving that empowered product teams, operating on clear outcomes, can deliver business impact in weeks—not quarters. I select problems that are meaningful enough to matter (activation, retention, expansion, cost-to-serve) and bounded enough to win. I staff a cross-functional triad—product manager, product designer, and a senior engineering lead—augmented with forward deployed engineers so the team can learn with customers in real contexts and rapidly ship. The language is deliberate: these are product teams, not projects, and discovery is not optional.
To neutralize the politics, I make the rules visible and fair. Team selection is transparent, criteria-based, and time-boxed. Success measures are defined up front and mapped to valuation drivers—retention, net revenue retention, conversion, and CAC payback—so the board and CEO see line of sight from product outcomes to enterprise value. I secure executive air cover for autonomy and decision rights, and I hold the same governance bar every two weeks: discovery evidence, shipped increments, customer signals, and outcome movement.
Execution-wise, I emphasize product discovery as the engine of speed and learning. The team commits to a tight loop: frame the problem, explore multiple solutions, test with real users, instrument everything, and ship small but frequent increments. We visualize the bets, we narrate the learnings, and we make trade-offs explicit. This cadence builds credibility quickly and reduces the urge to micromanage—because the evidence is always on the table.
The most consequential decision comes after the first 6–12 weeks: what do we scale? I codify the ways of working that made the pilot succeed—team topology, discovery practices, decision rights, metrics, and tooling—and then distribute them through enablement, not edict. I avoid the trap of permanent “hero teams.” Instead, we use the pilots to seed a repeatable product operating model that any team can adopt.
When I present progress, I speak in outcomes and learning, not activity. I show how the pilot teams shortened time-to-insight, increased the pace of value delivery, and built the muscles we’ll rely on at scale. I’m candid about what didn’t work and why; that honesty reduces organizational resistance and builds trust with leadership.
If you’re standing up pilot teams now, start by aligning the board and CEO on the outcomes that matter, pick one or two high-impact domains, staff a truly cross-functional team without hoarding all-star talent, and time-box the effort to about 90 days. Publish a one-page charter, instrument the metrics, and pre-commit to decisions based on thresholds: scale, iterate, or stop. Do this well, and the politics fade into the background while the product model—and your product management leadership—speaks for itself.
Inspired by this post on SVPG.
Leave a Reply