From products to needs: how an organization changes — episode materials (Series #Management)
Sunday’s Code of Leadership episode (S2E31, #89) was about a large fintech company that tried organizing work around customer needs. Imagine someone saves up a down payment for a car and gets approved for a loan. Then the insurance turns out to be too expensive and the purchase falls through. The insurer had its reasons for setting that price. Who owns the whole purchase?
Here’s what I covered:
🔸 Where product team autonomy ends Verticals let business units develop their products with less dependence on a shared queue. But when buying a car, at each step it matters which car the customer has picked, how much they’ve saved and what loan they expect. Teams have to agree on who passes that context along and who decides what to do if one step stalls.
🔸 Why segments matter One person needs a car now. Another can wait and save for a bigger down payment. The need is the same, but the right loan amount and monthly payment can differ.
🔸 How to work out the economics of several products Using an illustrative example with a deposit, investments and life insurance, I show how to calculate weighted LTV: each product’s contribution to the customer relationship depends on how likely they are to take it up.
🔸 Where the tesseract came from On the slides I rotate a projection of a four-dimensional cube, a tesseract: needs, segments, product platforms and technical platforms. From what I saw, some cases needed more coordination after the redesign. I’d pick one customer journey and look at which decisions teams now make differently.
Episode materials: — Episode page with timestamps and slides — Video: YouTube, VK Video — Audio: Podster, Apple Podcasts — Written notes
Who makes the call where you work when one team has good reason to say no, and the customer can’t move forward without them?
#CodeOfLeadership #Management #Leadership #OrgDesign #Product