The Platform Team Everyone Owns
LedgerPay runs three value streams-consumer payments, merchant tools, and risk-each with its own product owner. A shared platform team of nine engineers owns identity, ledger, and notification services. The platform team has no product owner; requests arrive through a dependency board and are prioritized by the most senior person in the room. Platform lead time is six weeks, and 40% of capacity is consumed by unplanned requests. The risk stream's regulatory release is blocked by an identity change that consumer requested for a growth experiment. Quarterly funding gives each stream a fixed budget, but platform costs are allocated at year-end. Executives want one consolidated roadmap and fewer committees. Each stream PO says they are accountable for outcomes but cannot control platform capacity.
1. What ownership and operating model would you recommend for the shared platform team?
Read the worked answer
Treat the platform as a product with an accountable owner, not as a shared service prioritized by seniority. Recommend a platform product owner or manager with authority over the platform backlog, a published service catalog, and explicit capacity allocation to the three value streams. The platform owner should understand internal customer needs, define platform outcomes such as lead time and reliability, and say no to low-value requests. Create a lightweight intake with a visible queue, acceptance criteria, and service-level targets; the dependency board can remain for coordination but not for prioritization. Fund the platform as a persistent team rather than a year-end cost allocation, and make its capacity visible in quarterly planning. Give the risk stream a reserved capacity or a fast lane for regulatory obligations. The stream POs remain accountable for their outcomes but must plan against agreed platform roadmaps and SLAs. This resolves the mismatch: accountability for outcomes without control over a critical dependency is not real accountability.
2. How should the organization resolve the immediate conflict between the risk stream's regulatory release and the consumer growth experiment?
Read the worked answer
Decide on evidence and regulatory exposure, not on who is most senior. Quantify the risk release cost of delay: regulatory penalty, audit finding, or release window, plus the downstream impact on merchant and consumer commitments. Quantify the consumer experiment: expected lift, confidence, and reversibility. If the risk release has a hard external date and the experiment is reversible, reserve platform capacity for the identity change, defer or descope the experiment, and publish the trade-off. If the experiment is time-critical, offer a smaller identity change that satisfies both, but only if the platform team confirms it does not add risk. Escalate to the portfolio owner with three options and a recommendation, including the cost of each delay. Record the decision and reset expectations with the consumer stream. The anti-pattern is letting the most senior person choose in the room without a cost-of-delay comparison.
3. What governance and metrics should replace annual project funding for these value streams?
Read the worked answer
Move from annual project funding to quarterly capacity funding for persistent value streams, with the platform funded as a product team. At portfolio level, agree outcome-based roadmaps and a single ranked list of cross-stream dependencies; do not consolidate every team into one roadmap. Use a quarterly planning cadence with a capacity reservation for regulatory and platform work, plus a small buffer for unplanned demand. Metrics: platform lead time, percentage of unplanned work, dependency age, flow efficiency, forecast confidence, and outcome measures per stream. Use showback or chargeback so platform cost is visible and streams see the cost of their requests. Governance should focus on investment boundaries, risk, and outcomes, not on approving individual features. Publish a decision log and a dependency health dashboard. Reassess funding quarterly based on evidence; if a stream consistently consumes platform capacity without a return, rebalance. This gives executives the consolidation they want without destroying stream accountability.