We amend the solution, cut things out of it, or specify details at certain tricky spots to prevent the team from getting stuck or wasting time.Ĥ/ (PM) Write the pitch. Once we think we have a solution, we take a hard look at it to find holes or unanswered questions that could trip up the team. The output of this step is an idea that solves the problem within the appetite but without all the fine details worked out.ģ/ (Designer + PM + Tech lead) Address risks and rabbit holes. We do this at a higher level of abstraction than wireframes in order to move fast and explore a wide enough range of possibilities. Then comes the creative work of sketching a solution. This gives us the basic boundaries to shape into.Ģ/ (Designer + PM + Tech lead) Rough out the elements of the solution. First we figure out how much time the raw idea is worth and how to define the problem. The conversation about building a feature always starts with a “raw idea”, like “customers are asking for group notifications.” Before we all go down the rabbit hole discussing ways we can solve it, we should first set some broad terms on the discussion to make it productive.ġ/ (PM) Set boundaries.
0 kommentar(er)
