The Platform Constituent Stack
by Brandon Chu • VP of Product (at time of recording) at Shopify
Former investment banker and Kraft Foods employee who pivoted to tech by founding a startup (Tunezy). After an acquisition, he worked at FreshBooks before joining Shopify, where he spent 7+ years scaling from PM to VP, eventually leading Product Acceleration.
🎙️ Episode Context
Brandon Chu, VP of Product at Shopify, discusses the unique product culture at Shopify, emphasizing their 'digital by default' approach and the importance of 'founder skills' for PMs. He explores the nuances of Platform Product Management, specifically the need to stack-rank constituents. The conversation also covers his philosophy on decision-making velocity, the career-accelerating power of writing, and how Shopify uses 'Bursts' to maintain connection in a remote-first world.
Problem It Solves
Resolves strategic deadlocks when a feature benefits one group (e.g., developers) but hurts another (e.g., end-user privacy).
Framework Overview
A prioritization model specifically for platform PMs to resolve conflicts between multiple stakeholders (Merchants, Developers, Buyers) by establishing a clear hierarchy of needs.
🔺 Priority Pyramid
When to Use
When designing APIs, data-sharing policies, or ecosystem rules where stakeholders have zero-sum interests.
Common Mistakes
Trying to please everyone equally, leading to a diluted platform value proposition; failing to protect the primary constituent.
Real World Example
Shopify prioritizes Merchants (Entrepreneurs) first. If an app developer wants data that helps them but spams the merchant's customer, Shopify blocks it. Contrast with Amazon, which stacks the Consumer first, often at the expense of the Seller.
You have to understand those principles and the stack rank of the constituents there to be able to make good policy and design choices.
— Brandon Chu