» Product duos and trios can enhance the team, but are never more important than the team as a whole
» If a team depends on an external decision-maker, could that person join the team to empower them?
» Too often, ‘building’ becomes the default state for a product team, at the expense of other valuable ways of working
» An product team should not be so rigid that it cannot cope with the occasional mandate from above
» Extreme work as a product leader is a systemic issue, not a failing of individuals to set boundaries
» Define performance expectations for your product team clearly using customer value, velocity and quality
» Product managers exist in part to free up the specialists to do their thing
» Being the point of contact with senior executives and stakeholders tends to also make you accountable to them
» Specialists’ expertise is needed to wield a tool effectively, even if it’s easy to use
» Different cultures communicate with varying directness; context heavily influences interpretation and meaning
» Leadership, trust, and decision-making styles differ widely across cultural backgrounds and must be adapted to the team
» Bridging cultural divides requires empathy, flexibility, and awareness of one’s own cultural lens
» A prototype expresses a product concept far better and quicker than a product requirements document (PRD)
» People good at doing a thing themselves are not always good at building a system to do it
» Work is craft: theoretical knowledge and practical experience combined
» Comprehensive introductory training on large language models (LLMs)
» Nonverbal communication can make assistive robots more effective
» Practical suggestions to foster greater alignment between product and go-to-market teams
» The Spotify Model was only ever a snapshot in time at Spotify
» It existed in the context of a company whose leadership valued trust, self-organisation and change
» As Spotify grew, it failed to strike the right balance between autonomy and collaboration
» Alignment to product strategy remains crucial for autonomous teams to deliver valuable work
» Failure to adapt and iterate on team structures and processes will result in your strongest product people leaving
» Accepting that an employee might thrive in another environment is accepting that you (as their manager) could have done a better job
» Rather than focusing on engineering team productivity, examine the causes of their low / negative value work
» When asked for development estimates, ask why they need the information and what they’ll do with the answer
» Different development tasks need varying amounts of user story detail
» Treat your developers with the same thoughtfulness as your users
