In a modern lean product development, mission product teams are becoming increasingly the standard. But how to define a mission for a team? This is a very easy approach to draft quickly a team mission statement.
How does a Mission Statement help a team?
- Provides a sense of purpose and direction
- Helps to create the identity of the team
- Becomes a template for making critical decisions
- Gives a starting point for defining goals, structure, strategy
Mission Statement → “Why do we exist as a team?”
- Time horizon of 1 to 3 years or more
- Why + Who + What
- Short, clear and concrete statement
- Team members create the statement together and shared regularly
Last year I had the pleasure of meeting Bruce McCarthy
in London, co-author of Roadmapping
, founder of Product Culture
, public speaker and recognised expert in the product management community.
By having few conversations with him and looking at my professional experience of last years, I realised how crucial is building the right product culture that actually help solving customers problems, which ultimately leads to company success.
Bruce mentions that product culture is not necessarily a process itself and it's not related to product management functions only. It is actually a mindset about why companies build solutions and do business. It's about few operating principles that focus on continuously developing and delivering products that solve customers problems, leaning on modern agile methodologies:
1. Customer-driven mission
2. Outcome over output or process
3. Leadership over management
4. Team over function
5. Technology is a core asset
It's super interesting how those principles converge into a systemic view of product development and are naturally the mantra of successful companies everywhere.
There are plenty of psychology studies and case studies that demonstrate that the old models of command & control management are completely dis-functional in a volatile and fast evolving digital market. In this context embracing uncertainty becomes a basic requirement and building the right product development process increases the confidence to do the right things. Bruce and his co-authors provide a framework to create roadmaps that focus on business outcomes rather than project deliverables. In this sense nobody defines exactly final deliverables (not at high level and not at the beginning at least), it's rather about defining the expected achievement as drivers. This requires of course a cross-functional mindset and a systemic leadership approach instead of a top-down management decision making. This means the teams must be enabled to reach the expected achievements and driven by a hands-off senior roles, which become accountable for the outcome.
I think this is one of the most common challenges in fast growing startups and this is the field on which I will concentrate myself in the next few months.
Stay tuned and reach me for comments!
By having few conversations with him and looking at my professional experience of last years, I realised how crucial is building the right product culture that actually help solving customers problems, which ultimately leads to company success.
Bruce mentions that product culture is not necessarily a process itself and it's not related to product management functions only. It is actually a mindset about why companies build solutions and do business. It's about few operating principles that focus on continuously developing and delivering products that solve customers problems, leaning on modern agile methodologies:
1. Customer-driven mission
2. Outcome over output or process
3. Leadership over management
4. Team over function
5. Technology is a core asset
It's super interesting how those principles converge into a systemic view of product development and are naturally the mantra of successful companies everywhere.
There are plenty of psychology studies and case studies that demonstrate that the old models of command & control management are completely dis-functional in a volatile and fast evolving digital market. In this context embracing uncertainty becomes a basic requirement and building the right product development process increases the confidence to do the right things. Bruce and his co-authors provide a framework to create roadmaps that focus on business outcomes rather than project deliverables. In this sense nobody defines exactly final deliverables (not at high level and not at the beginning at least), it's rather about defining the expected achievement as drivers. This requires of course a cross-functional mindset and a systemic leadership approach instead of a top-down management decision making. This means the teams must be enabled to reach the expected achievements and driven by a hands-off senior roles, which become accountable for the outcome.
I think this is one of the most common challenges in fast growing startups and this is the field on which I will concentrate myself in the next few months.
Stay tuned and reach me for comments!