Portfolio leadership · 5 min read
How I prioritize a portfolio of four product teams
The mandate, decision frame and people leadership behind mobile strategy, repeat utility and commercial investment at Covers.
Four teams change the question
My current mandate at Covers spans four product teams and three direct Product Manager reports. The portfolio connects mobile, community, handicapping, sports data and core betting experiences. The management question is larger than what any one team should ship next.
I need the work to add up to a customer relationship and a commercial proposition. A useful mobile experience, a better web-to-app journey and a sportsbook integration can each make sense individually. They become a strategy when the sequence explains how one makes the next more valuable.
The Covers mobile case study describes that thesis: a historically web-first product needs an app with a recurring job in the customer's life. My role includes people leadership, portfolio investment priorities and the business cases behind those choices.
Start with the behavior, then compare the investments
I start by asking what repeat behavior the product should earn. For this portfolio, the answer involves live utility, identity, useful picks and a coherent path through the betting journey. It cannot stop at a list of features.
That creates a common language for comparing very different opportunities. A team can explain which behavior its work improves, how that behavior connects to retention or commercial value, and what evidence would justify the investment.
An illustrative planning comparison looks like this. These are examples of the questions to ask, rather than a published roadmap or a claim about specific experiments we ran.
| Investment | Customer job | Evidence to seek | Portfolio question |
|---|---|---|---|
| Live scores and game context | Get a useful answer quickly | Repeat use and successful task completion | Does this create a reason to return? |
| Web-to-app continuity | Continue the task after installing | Activation and preserved journey context | Does acquisition lead to useful app behavior? |
| Identity and preferences | Get information that fits the fan | Retention and relevance of repeat visits | Does personalization improve the next visit? |
| Sportsbook integration | Act without reconstructing the decision | Journey completion and partner conversion | Does the commercial step preserve customer trust? |
The table matters because it prevents unlike opportunities from being compared only by confidence, stakeholder enthusiasm or the number of features involved. It does not produce an automatic answer. It makes the judgment easier to inspect.
Sequence the work that unlocks the next choice
A portfolio has dependencies that a single-team roadmap can miss. A growth journey is less valuable if the first app session does not deliver the promise. Personalization needs useful signals. Monetization depends on an experience the customer trusts enough to use again.
I describe the sequence as four questions:
- What must work reliably before we ask more of the customer?
- Which investment makes another team's work more valuable?
- What can we learn before committing more capacity?
- What would cause us to change the order?
This is where product strategy meets investment responsibility. Choosing one initiative means choosing what will wait. The business case needs to make that consequence visible, along with the customer value, operating cost and uncertainty.
Give PMs a mandate they can own
Direct reports need a clear outcome, decision boundaries and enough context to develop their own point of view. They also need feedback on their judgment, rather than only on the quality of a presentation or the completeness of a roadmap.
My earlier role at theScore included managing five PMs, hiring, performance management, promotions and PM development. That experience reinforced the connection between portfolio leadership and people leadership: a clear strategy gives a PM something meaningful to own, and strong PMs improve the strategy through the decisions they make.
The leadership page describes the operating practices behind this work. The theScore case study shows how the product thesis connected several live experiences into one portfolio.
Keep launches, results and forecasts separate
A launch proves that a team delivered an experience. A measured result describes what happened after customers used it. A forecast describes what the business case expects to happen. Those are three useful pieces of information with different meanings.
A portfolio review should preserve that distinction. It should state the scope of a result, the measure being used, the period covered and the contribution of the team. It should also say what remains uncertain.
The practical standard I use is simple: someone outside the team should be able to understand the choice, the evidence behind it and what would change our mind. Across four teams, that clarity helps turn separate roadmaps into a product direction.