{"id":2396,"date":"2017-07-25T14:19:11","date_gmt":"2017-07-25T12:19:11","guid":{"rendered":"https:\/\/blog-alexis.monville.com\/en\/?p=2396"},"modified":"2017-09-04T15:43:04","modified_gmt":"2017-09-04T13:43:04","slug":"team-identity","status":"publish","type":"post","link":"https:\/\/blog-alexis.monville.com\/en\/2017\/07\/25\/team-identity\/","title":{"rendered":"Team Identity"},"content":{"rendered":"<p>The sense of belonging is an important experience to have. Belonging means that we are accepted as part of, as a member of the group, the team, the company.<\/p>\n<p>We want to be part of a team because what defines the team identity is appealing to us. The team is defined by its vision and its working agreements.<\/p>\n<p>When you are building software the open source way, you can identify 3 main categories of team identity:<\/p>\n<ol>\n<li>Upstream project<\/li>\n<li>Downstream product<\/li>\n<li>Jobs to be done<\/li>\n<\/ol>\n<p>1- Upstream project<\/p>\n<p>The team members belong first to the upstream project. They will tend to prioritize what they think is the best for the upstream project. They will be progressively disconnected from the people that are using the technology they build. They could even miss new needs and be surprised that people switch to another technology that is not so different\/better\/other qualifiers&#8230;<\/p>\n<p>2- Downstream product<\/p>\n<p>The team members belong first to the product they build. They will tend to prioritize what they think is the best for the product. They will tend to forget that building the open source way is a great way to understand why people want to use the technology by confronting your point of view and requirements with those of the other members of the community. The extreme is that they will end up being alone, and disrupted by another product.<\/p>\n<p>3- Jobs to be done<\/p>\n<p>The <a href=\"https:\/\/www.christenseninstitute.org\/jobs-to-be-done\/\">Jobs to be done<\/a> theory has been described by Christensen and his colleagues. I wrote an article about one of his book: <a href=\"https:\/\/blog-alexis.monville.com\/en\/blog\/2016\/12\/09\/how-to-measure-our-life\/\">How to measure our life<\/a> and I will probably write another one about <a href=\"https:\/\/www.goodreads.com\/book\/show\/29100334-competing-against-luck\">Competing Against Luck<\/a>.<\/p>\n<p>In short, the Jobs to be done theory explains why people are making choices, hiring or firing a product or service, by focusing on the understanding of the jobs, the problem they are trying to solve.<\/p>\n<p>The teams that identify themselves to the jobs to be done are stronger because they can work on technologies in the open, curate technologies that they need, invest in new technologies that could replace their current core technologies, without losing their identity. They can envision their solution as a sole product, or integrated into other products knowing that the most important thing is the jobs to be done. They can partner with other knowing precisely what they are partnering on without feeling that they could lose\/win something in the partnership. They can focus on their users and solve a specific problem, a specific &#8220;jobs to be done&#8221; without the temptation to expand the scope of what they are doing.<\/p>\n<p>I guess that the jobs to be done should be the first thing you want a team to agree upon.<\/p>\n<p>Thoughts? Please comment, tweet, email&#8230;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p><em>The header picture is from <a href=\"http:\/\/www.laughandpee.com\/\" rel=\"noopener\">Ryan McGuire<\/a>.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The sense of belonging is an important experience to have. Belonging means that we are accepted as part of, as a member of the group, the team, the company. We want to be part of a team because what defines the team identity is appealing to us. The team is defined by its vision and [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2397,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"advanced_seo_description":"","jetpack_seo_html_title":"","jetpack_seo_noindex":false,"jetpack_seo_schema_type":"","_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[1],"tags":[762],"class_list":["post-2396","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-all","tag-team"],"jetpack_shortlink":"https:\/\/wp.me\/paNjQG-CE","jetpack-related-posts":[{"id":2331,"url":"https:\/\/blog-alexis.monville.com\/en\/2016\/08\/05\/contribute-to-the-success-of-openstack\/","url_meta":{"origin":2396,"position":0},"title":"Contribute to the Success of OpenStack","author":"Alexis","date":"August 5, 2016","format":false,"excerpt":"During the OpenStack Summit in Austin, Mark McLoughlin and I delivered a talk titled: \"Contribute to the Success of OpenStack\". Our talk was meant to explain how we were inspired by agile values and principles to improve our internal organization, and how we thought it could impact our ability to\u2026","rel":"","context":"In &quot;General&quot;","block_context":{"text":"General","link":"https:\/\/blog-alexis.monville.com\/en\/category\/all\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2016\/08\/community-1920.jpg?fit=1200%2C800&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2016\/08\/community-1920.jpg?fit=1200%2C800&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2016\/08\/community-1920.jpg?fit=1200%2C800&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2016\/08\/community-1920.jpg?fit=1200%2C800&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2016\/08\/community-1920.jpg?fit=1200%2C800&ssl=1&resize=1050%2C600 3x"},"classes":[]},{"id":2342,"url":"https:\/\/blog-alexis.monville.com\/en\/2016\/10\/12\/how-agile-and-open-source-work-together-in-nearly-perfect-harmony\/","url_meta":{"origin":2396,"position":1},"title":"How Agile and Open Source work together in (nearly) perfect harmony","author":"Alexis","date":"October 12, 2016","format":false,"excerpt":"This article is based on the talk I gave for the Red Hat Agile Day in Raleigh on October 11, 2016. The conversation about agile and Open Source usually starts with an interruption in this form: Agile will not work in an Open Source context because\u2026 That\u2019s usually how a\u2026","rel":"","context":"In &quot;General&quot;","block_context":{"text":"General","link":"https:\/\/blog-alexis.monville.com\/en\/category\/all\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2016\/10\/Jason-Hibbets-Picture.jpg?fit=1200%2C675&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2016\/10\/Jason-Hibbets-Picture.jpg?fit=1200%2C675&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2016\/10\/Jason-Hibbets-Picture.jpg?fit=1200%2C675&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2016\/10\/Jason-Hibbets-Picture.jpg?fit=1200%2C675&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2016\/10\/Jason-Hibbets-Picture.jpg?fit=1200%2C675&ssl=1&resize=1050%2C600 3x"},"classes":[]},{"id":2693,"url":"https:\/\/blog-alexis.monville.com\/en\/2018\/10\/21\/could-your-team-be-managing-itself\/","url_meta":{"origin":2396,"position":2},"title":"Could your team be managing itself?","author":"Alexis","date":"October 21, 2018","format":false,"excerpt":"\"Self-organization\" and \"management\" aren't mutually exclusive. But we'll need to rethink the role of the manager if we're planning to build adaptable teams.","rel":"","context":"In &quot;General&quot;","block_context":{"text":"General","link":"https:\/\/blog-alexis.monville.com\/en\/category\/all\/"},"img":{"alt_text":"group of people sitting indoors","src":"https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2018\/10\/pexels-photo-3184291.jpeg?fit=1200%2C800&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2018\/10\/pexels-photo-3184291.jpeg?fit=1200%2C800&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2018\/10\/pexels-photo-3184291.jpeg?fit=1200%2C800&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2018\/10\/pexels-photo-3184291.jpeg?fit=1200%2C800&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2018\/10\/pexels-photo-3184291.jpeg?fit=1200%2C800&ssl=1&resize=1050%2C600 3x"},"classes":[]},{"id":5393,"url":"https:\/\/blog-alexis.monville.com\/en\/2025\/01\/21\/psychological-safety-the-key-to-collaboration-and-innovation\/","url_meta":{"origin":2396,"position":3},"title":"Psychological Safety: The Key to Collaboration and Innovation","author":"Alexis","date":"January 21, 2025","format":false,"excerpt":"This month, we focus on a cornerstone of high-performing teams and transformative leadership:\u00a0psychological safety. In a world where uncertainty and complexity are the norm, creating environments where individuals feel safe to speak up, take risks, and be themselves is no longer a luxury\u2014it\u2019s a necessity. Psychological safety, as defined by\u00a0Amy\u2026","rel":"","context":"In &quot;General&quot;","block_context":{"text":"General","link":"https:\/\/blog-alexis.monville.com\/en\/category\/all\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2025\/07\/nick-fancher-9Akkxm-Ht4M-unsplash.jpg?fit=640%2C960&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2025\/07\/nick-fancher-9Akkxm-Ht4M-unsplash.jpg?fit=640%2C960&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2025\/07\/nick-fancher-9Akkxm-Ht4M-unsplash.jpg?fit=640%2C960&ssl=1&resize=525%2C300 1.5x"},"classes":[]},{"id":2227,"url":"https:\/\/blog-alexis.monville.com\/en\/2015\/11\/23\/datflock2015-unicorns-distributed-teams-and-bad-agile\/","url_meta":{"origin":2396,"position":4},"title":"DATFlock2015, unicorns, distributed teams and bad agile","author":"Alexis","date":"November 23, 2015","format":false,"excerpt":"I was in Berlin for 2 days to participate to #DATFlock2015 the conference to discuss, learn and share about Distributed Agile Teams. The program was a mix of open space sessions and workshops prepared in advance. OKR, Feedback and Reward Two sessions where particularly useful to me: How to use\u2026","rel":"","context":"In &quot;General&quot;","block_context":{"text":"General","link":"https:\/\/blog-alexis.monville.com\/en\/category\/all\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2015\/11\/2015112015-11-20-15.52.58-scaled.jpg?fit=1200%2C891&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2015\/11\/2015112015-11-20-15.52.58-scaled.jpg?fit=1200%2C891&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2015\/11\/2015112015-11-20-15.52.58-scaled.jpg?fit=1200%2C891&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2015\/11\/2015112015-11-20-15.52.58-scaled.jpg?fit=1200%2C891&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2015\/11\/2015112015-11-20-15.52.58-scaled.jpg?fit=1200%2C891&ssl=1&resize=1050%2C600 3x"},"classes":[]},{"id":2997,"url":"https:\/\/blog-alexis.monville.com\/en\/2019\/09\/30\/adding-another-dimension-to-the-project-management-triangle\/","url_meta":{"origin":2396,"position":5},"title":"Adding another dimension to the project management triangle","author":"Alexis","date":"September 30, 2019","format":false,"excerpt":"The project management triangle is a well-known model showing that the quality of the delivery is constrained by the budget, the deadlines, and the scope. The idea is that it is possible to trade between constraints: ask for an earlier delivery with a smaller scope, for example. And If you\u2026","rel":"","context":"In &quot;General&quot;","block_context":{"text":"General","link":"https:\/\/blog-alexis.monville.com\/en\/category\/all\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2019\/09\/gratisography-paper-eyes.jpg?fit=1200%2C800&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2019\/09\/gratisography-paper-eyes.jpg?fit=1200%2C800&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2019\/09\/gratisography-paper-eyes.jpg?fit=1200%2C800&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2019\/09\/gratisography-paper-eyes.jpg?fit=1200%2C800&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2019\/09\/gratisography-paper-eyes.jpg?fit=1200%2C800&ssl=1&resize=1050%2C600 3x"},"classes":[]}],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/i0.wp.com\/blog-alexis.monville.com\/en\/wp-content\/uploads\/sites\/2\/2017\/07\/425H.jpg?fit=2000%2C1333&ssl=1","_links":{"self":[{"href":"https:\/\/blog-alexis.monville.com\/en\/wp-json\/wp\/v2\/posts\/2396","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog-alexis.monville.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog-alexis.monville.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog-alexis.monville.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog-alexis.monville.com\/en\/wp-json\/wp\/v2\/comments?post=2396"}],"version-history":[{"count":2,"href":"https:\/\/blog-alexis.monville.com\/en\/wp-json\/wp\/v2\/posts\/2396\/revisions"}],"predecessor-version":[{"id":2437,"href":"https:\/\/blog-alexis.monville.com\/en\/wp-json\/wp\/v2\/posts\/2396\/revisions\/2437"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog-alexis.monville.com\/en\/wp-json\/wp\/v2\/media\/2397"}],"wp:attachment":[{"href":"https:\/\/blog-alexis.monville.com\/en\/wp-json\/wp\/v2\/media?parent=2396"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog-alexis.monville.com\/en\/wp-json\/wp\/v2\/categories?post=2396"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog-alexis.monville.com\/en\/wp-json\/wp\/v2\/tags?post=2396"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}