Split the Oversized Team
Make a sequence of pod-splitting decisions that preserve outcome ownership and ritual clarity.
The split One 16-person team is too large for fast planning, but a careless split will multiply handoffs. The goal is to reduce coordination load without losing end-to-end ownership. Outcome -> capability -> ritual A useful split starts with a slice of customer value, checks whether the pod can deliver it, then installs the rituals that keep learning visible. Do not split the org chart before you split the work. Choose the boundary Step 1 The team serves both new buyers and sellers. Where do you draw the first pod boundary? Handle scarce skills Step 2 There is one data…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in