» Organisational changes will reveal weak spots in the current ways of working before you adapt them
» Structure teams differently based on the nature of the work
» There is value in using shared language to describe how teams differ
» Rather than existing in a bubble, each product team should have core members, collaborators and supporters
» How you should divide up teams depends on your product’s overall flow; avoid ambiguous ownership
» Teams should have end-to-end responsibility for a part of the user journey with minimal dependencies
» One approach is to delineate between teams working on a core problem domain, and on those enabling their work
