How I lead
My role is to make the customer problem, strategic choice, expected outcome, and constraints legible. Strong teams can do remarkable work when that context is real.
Start with the customer problem, the business opportunity, the strategic choice, and the measure of success. A roadmap is useful only after those are clear.
In practice: At Covers, that meant framing mobile as a customer relationship and commercial system, not a list of app features.
Shipping creates an opportunity for impact. It is not the impact itself. Define the expected behavior before launch and report honestly after it.
In practice: At theScore, portfolio reviews connected releases to sessions, time in product, audience growth, and commercial inventory.
Good strategy concentrates attention. The hard part is saying no to plausible work so the team can do the consequential work well.
In practice: At OwnersBox, product choices had to work for customers, portfolio economics, and a startup's finite capacity at the same time.
Written strategy, clear decisions, executive updates, and direct team context let many people move with more confidence and less coordination cost.
In practice: Across roles, I have built operating frameworks and communicated product direction to teams, executives, and broad company audiences.
Leadership is most useful when the mandate is ambiguous, constraints change, or the organization is under pressure. Clarity matters more than theatre.
In practice: I have worked across startup constraints, scaled live systems, shifting ownership contexts, and multi-team portfolios.
Developing teams
Product managers need more than autonomy. They need context, direct feedback, a clear standard for judgment, and room to build their own point of view.
My approach combines written strategy, regular decision review, outcome reporting, and coaching that changes with the PM’s experience and the stakes of the work.