Blog Post

How to create a team mission

  • By Luca Criscuolo
  • 22 Mar, 2019

Draft an initial mission statement in few steps.

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?

  1. Provides a sense of purpose and direction
  2. Helps to create the identity of the team
  3. Becomes a template for making critical decisions
  4. 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

How to proceed

1. Idea generation

Get in a room with a whiteboard to explore all possible answers to the question “Why do we exist as team?”, “Why are we doing what we do as a team?”

In fact, don’t just ask that question, but keep asking it to drill in on important conversations. Why are we building this software? But really… why? Why now? Why this team? goal is to pinpoint what really matters. A neutral facilitator in the room can help participants stay creative.


2. Crafting the statement

The statement might contain three elements

  1. The Customer (Who do we help?)
  2. The Actions (What we do?)
  3. The Impacts (The change for the better)

A highly structured statement contains all of elements, but you don’t always need a highly structured statement. So use them as a help, not as a must.


Examples of three or two elements:

“We help families in developing areas stay healthy by providing clean water and education.” “Through clean water, we promote security and opportunities into rural economies.”

“To connect the world’s professionals to make them more productive and successful.”

“To be the most customer-centric company, where customers can find and discover anything they might want to buy online, and endeavors to offer its customers the lowest possible prices.”

“To become the number 1 fashion destination for 20-somethings globally.”

“To empower creators to make their best work and get it in front of the audience they deserve.”

“By seamlessly connecting riders to drivers through our apps, we make cities more accessible, opening up more possibilities for riders and more business for drivers.”

“To enrich people’s lives with programmes and services that inform, educate and entertain.”

“To help people worldwide where the need is greatest, delivering emergency medical aid to people affected by conflict, epidemics, disasters or exclusion from health care.”

“To make unique sports cars that represent the finest in Italian design and craftsmanship, both on the track and on the road.”


Remember:

  • You can debate each word over, and over, and over. Don’t let that happen. Committing the group is more important than a perfect sentence.
  • Don’t hurry, let the ideas settle down for a while. Take a first statement draft and re-iterate for one or two times.



A great agile coach of Trivago suggested me the following methodology. I tried it with in one of my last (very challenging) team and it worked out pretty well:

  1. Ask every team member to write one by one on a whiteboard a statement they believe is the right one for the team: We provide <Impact> to <Customer> by <Actions>. Let them write whatever they like, one by one, no comments or feedback. While writing, stealing words from previous sentences is also allowed.
  2. When finished, you have all the statements on the whiteboard and everyone reads them again without giving feedbacks or commenting, only reading.
  3. One by one, everyone underlines in red what they don’t like, and in green what they like in all sentences.
  4. The facilitator writes a common statement by using only the green words, the team discuss the result. Now you have a first draft.
  5. Ask for projects in the next years happening according to that mission statement draft.
  6. Digest the statement for few days, then gather the team again and review the draft.


By Luca Criscuolo March 22, 2019
Look at those two pictures.
By Luca Criscuolo March 22, 2019

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?

  1. Provides a sense of purpose and direction
  2. Helps to create the identity of the team
  3. Becomes a template for making critical decisions
  4. 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
By Luca Criscuolo March 5, 2019
Since few years I make myself busy with the topic "Women in Tech" and "Women in Leadership".

Before the birth of my daughter eight years ago, those topics were part of 10-minutes blog readings that I personally considered empty "feminist fights".

I have two kids a girl and a boy. I slowly realised that, in terms of statistics, my daughter's salary is likely to be 20% less than the one of my son, and she is less likely to cover a leadership role than my son. No matter how hard she will study and work, statics say that she is more likely to lose the competition with her peers men. And, no room for misunderstanding, it's only because she is female.

So I started to look around myself and I quickly noticed that I was surrounded almost by men and, even worse, I met only two women in the executive rounds in the past 10 years. I looked at the physical surroundings: free beer, fußball, table tennis, and plenty of other stuff belonging to us "brothers". Many of my engineering teams were full of "difficult, but super smart" young men, both tech geeks and product rock stars, discussions were often hard, competitive, conflict prone, basically stuff for men. I also noticed that many female colleagues that went into maternity leave, not only disappeared, but were considered like "gone". When they came back they entered a status of "mothers", reducing the working hours and going quickly into secondary roles, even though they were outstanding professionals.

It became clear to me that the tech world around myself was actually build by men around a men culture.

Then I joined Outfittery, a company founded by two great women, where more than 60% of the workforce and half of the management team is female. I worked closely to high profile women, both in the exec team and in my product management team. In this environment I understood the benefits of this equal distribution and I am now dedicated to enable a more balanced working environment.

So what are those benefits, why can I say that gender equality is a good thing?

I have few strongly opinionated people in my team, both male and female. Conflicts are a given in product management and my team is particularly prone to it (and I am proud of it). When I joined Outfittery 30% of my team were women, today the figure is 60%. While we had tough splitting discussions in the early days, today we handle frictions much better and a stronger safety net stands around the team. I personally faced at least two hard escalations during the first year, none during the last 8-10 months. Now, the team certainly matured with time, people come and go. A new equilibrium evolved naturally, but I am convinced that the increased share of women contributed to a more pragmatic and safer dynamic. Even in the management team, I witness how female leaders are more likely to calm brewing escalations (initiated by men or women) with pragmatic actions, which again help the group to streamline a solution.

So assuming that a better balance between genders makes team safer and more solution oriented, how can we foster it?

We have to acknowledge first that male and female have different requirements and it's in the leaders responsibility to build a welcoming environment for both.

  1. Men are prone to fight, women are prone to sociality. When "smart individualists" men dominate conversations eating up the others with their wisdom, the introvert and the more compromise-ready tend to be side-lined and contribute less to the common benefit. In this context, women are often less "loud", so the big-ego guys can quickly marginalise them, especially the younger one. This again restricts the team dynamic and put at risk the emergence of team solutions. Fostering a no-asshole, no rock-stars and big-ego policy will make sure that women gets space and the team benefits from a more balanced and safer dynamic.
  2. Booze is for men, socialising spaces are for everybody. Booze events, table tennis, fuss-ball tournaments are definitely cool things, but I doubt that they are very welcoming for women. I think large shared spaces for informal conversations and even female-only events increase the chances of creating a social and welcoming (and retaining) environment for female talents.
  3. Women have a larger stake with kids, at least at the beginning. Women are naturally more impacted by children, especially during the first year. Women know that part of their energy must be invested into family matters, but they still desire to grow professionally. In order to balance family and job, they are determined to increase efficiency during the office time and work when the kids are finally sleeping. So not enabling them to invest their energy in a flexible way, companies automatically force them to choose (and not balance) between family and professional development. I am a great fan of working flexibility independently from the gender, but I think for women in the family stage it's a hard requirement.
  4. And the most difficult: men have to get their own burden. We men have to understand that our female counterpart needs its own space for growth, challenges and achievements, and it is our own benefit in both family and professional matters. Without our commitment, things will not improve for them and for ourselves. So, yes, we have to take our share of responsibility by modulating our tone, becoming more aware, taking care of whatever we think it's actually "for them" and, as usual, learn from it.

The good news is that I discussed those topics in many events and conversations with tech leaders. I also see an increasing number of young product leaders in the market. So things are improving, but we still have a long way to go in front of us. For myself, I decided to give more and more space to smart women in product management, especially focussing on leadership potentials.

Agree, disagree? Let me know.





By Luca March 4, 2019
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!


Show More
Share by: