-
Notifications
You must be signed in to change notification settings - Fork 0
/
Shape-Up-Who-does-the-Shaping.html
1 lines (1 loc) · 9.83 KB
/
Shape-Up-Who-does-the-Shaping.html
1
<!DOCTYPE html> <html lang="pl"> <head> <meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1" /> <title>Shape Up, Who does the Shaping? · Rafal Makara</title> <meta property="og:title" content=" Shape Up, Who does the Shaping? "> <meta property="twitter:title" content=" Shape Up, Who does the Shaping? "> <meta property="og:description" content=" Shape Up is a product development methodology popularized thanks to Ryan Singer, a Head of Product Strategy at Basecamp. I cover the topics not entirely covered in the book to make your implementation of Shape Up much easier. "> <meta name="twitter:card" content="summary" /> <meta name="twitter:site" content="@rafalmakara" /> <meta property="og:image" content="https://rmakara.github.io/assets/20220328_header.jpg" /> <meta name="twitter:image" content="https://rmakara.github.io/assets/20220328_header.jpg" /> <meta name="description" content=" It is one of the articles in the Shape Up series. For Table of Contents go to: Shape Up, IntroductionWho does the Shaping?The most common question for the ..."> <link rel="icon" href="https://rmakara.github.io//assets/favicon.ico"> <link rel="apple-touch-icon" href="https://rmakara.github.io//assets/apple-touch-icon.png"> <link rel="stylesheet" href="https://rmakara.github.io//assets/core.css"> <link rel="canonical" href="https://rmakara.github.io//Shape-Up-Who-does-the-Shaping"> <link rel="alternate" type="application/atom+xml" title="Rafal Makara" href="https://rmakara.github.io/feed.xml" /> </head> <body> <aside class="logo"> <a href="https://rmakara.github.io//"> <img src="https://avatars0.githubusercontent.com/u/1880231?v=4" class="logo-avatar"> </a> <span class="logo-prompt code">Back to Home</span> </aside> <aside> <p class="goodbye"> This blog is no longer maintained <br/><br/> Subscribe to new articles at <a href="https://www.sorryengineering.com/">https://www.sorryengineering.com/</a> </p> </aside> <p class="menu"> <br /><br /> <a href="/">EN Articles</a> | <a href="/pl">PL Articles</a> <br /> <a href="/about">About me</a> | <a href="/help">How can I help?</a> | <a href="https://www.linkedin.com/in/rafalmakara/">My LinkedIn Profile</a> </p> <div id="content"> <article> <div class="divider"></div> <div class="center"> <a class="prev" href="/Shape-Up-Shaping-vs-Building">Previous article - Shape Up, Shaping vs Building</a> </div> <div class="divider"></div> <h1 class="title">Shape Up, Who does the Shaping?</h1> <div class="center"> <time class="code">2022-04-18</time> </div> <div class="divider"></div> <blockquote> <p>It is one of the articles in the Shape Up series. For Table of Contents go to: <a href="https://rmakara.github.io/Shape-Up-Introduction">Shape Up, Introduction</a></p> </blockquote> <h2 id="who-does-the-shaping">Who does the Shaping?</h2> <p>The most common question for the Shaping phase is who does the Shaping. Basecamp answers this question in <a href="https://basecamp.com/shapeup/1.1-chapter-02#who-shapes">Who Shapes</a> chapter of the book.</p> <p>The conclusion that we may see is to involve someone aware of the design, business, and technicals. It usually leads to building a team who can collaborate to create the following pitches. There should also be someone empowered to set the concrete level of investment (Appetite).</p> <p>From my perspective, the composition of the Shapers may differ. Here’s how.</p> <h3 id="board--founder--leader-does-the-shaping">Board / Founder / Leader does the Shaping</h3> <p>In early-stage companies, usually, there is a Product Leader / Chief Product Officer who will be strongly involved in the Shaping process. In many organizations, this person will be the only one to have the authority to make the calls on the following features to implement.</p> <p>The good thing about that is that it lowers the need to involve the whole team in the discovery process and doesn’t create the need to educate everyone with the domain knowledge. Ouch, stop! Writers of the most modern books would blame me for that, but yes… I think this approach is ok in many cases.</p> <p>However, there are two main drawbacks of going this way.</p> <p>The first one is that once the organization gets bigger, the CPO becomes a bottleneck for everyone else.</p> <p>The second one is that it produces a team of people focused on just the delivery. To read more on this topic, go to <a href="https://www.svpg.com/missionaries-vs-mercenaries/">Missionaries vs Mercaneries by Marty Cagan</a>.</p> <h3 id="product-trio-does-the-shaping">Product Trio does the Shaping</h3> <p>Once your company evolves, you may take another approach, which doesn’t narrow the Shaping process to just a single person. There is an idea of the Product Trio in <a href="https://www.producttalk.org/2021/05/continuous-discovery-habits/">Continuous Discovery Habits book by Teresa Torres</a>. It is similar to <a href="https://www.agilealliance.org/glossary/three-amigos/">Three Amigos</a> popularized in Scrum. Both views are about bringing different perspectives together and letting them collaborate.</p> <p><a href="https://www.producttalk.org/2021/05/product-trio/">Product Trio</a> is made of a Product Manager, Engineer and Designer. These people might be a “Head/Chief Level”, but do not have to. This is very effective composition for shaping the future of the product.</p> <p>The critical aspect you need to take care of in this approach is encouraging these people to collaborate. It is NOT about permitting them to Shaping in separation from each other.</p> <h3 id="everyone-does-the-shaping">Everyone does the Shaping</h3> <p>The third approach is to let everyone write Shapes/Pitches. This step raises involvement on all levels within the organization. It may surprise you with many valuable ideas that you will get from people.</p> <p>To make them successful, it is mandatory providing everyone with a Product Vision and Strategy. Without sharing the strategic context with them, the likelyhood of shaping something irrelevant to your strategic goals is relatively high. People will get demotivated and stop participating in discovery activities if you reject many of their ideas during the Betting Table while choosing your own ones.</p> <p>Once you share the context and strategy with them, you need to ensure they have the time for it. Most likely, Builders will not have the time to write the Pitches during the Building Phase. Of course, they may try to do that during the Cooldown phases.</p> <p>Also, many people will have great ideas, but they’ll not be willing to write that down just because they might not be the best writers. In such a case, you can share a simple Google Form with everyone asking them to describe their idea in 2 sentences and recommend the Appetite. Then you may review the survey, get in touch with them and help write the final Shape/Pitch.</p> <h3 id="mix-all-above">Mix all above</h3> <p>Once you know three different approaches, you may mix them together.</p> <p>Allowing everyone at the company to work on the Shapes while you’re still letting CPO or Product Trio do it is a good move. It enables leaders to execute the strategy, and also it gives all employees the possibility to participate in the future of the product.</p> <p>Then you can bet on the Pitches from these various sources.</p> <p>Just think about how to make this mixture work.</p> <h2 id="ask-for-feedback-on-the-pitch-early">Ask for feedback on the Pitch, early</h2> <p>There is a single risk worth mentioning for the Shaping.</p> <p>Many people tend to keep their hard work hidden as long as something becomes “demoable”.</p> <p>During the Shaping process, it is worth publishing drafts and sharing the Pitches in the early stages (before the Betting) so that other people can provide some feedback.</p> <p>Even if just one person is working on a Shapes, opening them for feedback from everyone leads to positive results.</p> <h2 id="who-does-the-building">Who does the Building?</h2> <p>Obviously, the ones who can code and design — however, at least one more person must be involved.</p> <h3 id="include-the-owner-of-the-pitch-into-building">Include the owner of the Pitch into Building</h3> <p>Builders will need direct and constant access to the person who prepared the Pitch or any other person who understands the <em>why?</em> behind the Pitch.</p> <p>Soon, we will focus more on the project roles and responsibilities.</p> <p>For now, keep in mind that Shape Up is not meant to be a waterfall process. People who wrote the Pitch need to be involved during the Building phase to support Builders with knowledge and feedback.</p> <p>The following article will discuss <a href="https://rmakara.github.io/Shape-Up-Are-Shapes-The-Problems-To-Solve">how concrete the Pitches should be</a>.</p> </article> <div class="divider"></div> <div class="page-navigation code"> <a class="home" href="https://rmakara.github.io//" title="Back to Home">Back to Home</a> <br/><br/> <a class="next" href="/Shape-Up-Are-Pitches-The-Problems-To-Solve">Next article: Shape Up, Are Pitches the problems to solve?</a> </div> </div> <br/> <aside> <p class="goodbye"> This blog is no longer maintained <br/><br/> Subscribe to new articles at <a href="https://www.sorryengineering.com/">https://www.sorryengineering.com/</a> </p> </aside> <div class="footer"> <span class="block">© 2023 Rafal Makara</span> <span class="block"><small></> Powered by <a href="https://jekyllrb.com/">Jekyll</a> and <a href="https://github.com/heiswayi/the-plain">The Plain theme</a>.</small></span> </div> </body> <script> (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) })(window,document,'script','//www.google-analytics.com/analytics.js','ga'); ga('create', 'UA-92815270-1', 'auto'); ga('send', 'pageview'); </script> </html>