%% Last Updated: - [[2021-02-17]] - [[2020-09-05]] %% ## What It Is: Shaping work involves taking something from a raw idea and turning it into an actionable project that is ready to be pitched. ^301e3e ## Who shapes? In general, a small group of managers or senior staff shape work for the rest of the team. The Shaper is ideally a generalist, skilled in both design work and implementation/technical work. If this is not possible, there can be more than one Shaper. ## When does shaping occur? The shaping team works in parallel with the development team in a staggered manner, working on the next cycle's bets while the team is building this cycle's bets. ## What are the steps involved in shaping work? ### 1. Set boundaries - Determine the [[Root problem]] and come up with a tentative solution that is narrowed down depending on the **appetite**: - Small batch - one designer and one or two programmers for 1-2 weeks. - Big batch - same size team, but for 6 weeks. > An appetite is completely different from an estimate. Estimates start with a design and end with a number. Appetites start with a number and end with a design. We use the appetite as a creative constraint on the design process. ### 2. Create a prototype / [[Proof Of Concept]] Come up with a rudimentary design of the desired end result, including implementation. [[Prototyping techniques]] ### 3. Reduce scope, address risks and rabbit holes Identify potential risks and rabbit holes and think through how they can be avoided. - Questions to ask ourselves: - Does this require new technical work we’ve never done before? - Are we making assumptions about how the parts fit together? - Are we assuming a design solution exists that we couldn’t come up with ourselves? - Is there a hard decision we should settle in advance so it doesn’t trip up the team? - Approach a technical expert.