Resources for defining product features

Last time I posted resources for exploring users. Here's a couple more to help define your product features:

Value Proposition

The value proposition can build upon other early activities in a design process, and help map out key characteristics of your product. It's useful with a persona or empathy map to highlight the opportunities and pains your product could solve. Here's the template:

️ Prioritisation Matrix

Along the way, and from the value proposition canvas, we may have started generating lots of product ideas and features to solve the problems your users are having.

Eventually though, we can only solve problems that are feasible and worthwhile as we have limited time and resources. A prioritization matrix helps here to identify the most important problems whilst satisfying user needs. Map your ideas out on here, and focus on those with most impact:

@Graeme These seem slightly useful for me, but user story mapping is far more important. Perhaps these might supplement for some perspective regarding benefits and value vs effort, but probably only after user story mapping. I'm trying to determine what my initial focus for the prototype MVP should be.

@doug that definitely makes sense for your diabetes project! For mine on imposter syndrome, it wasn't as useful as imposter syndrome is in the mind. I might come back round to doing one as my prototype takes shape.

There isn't really an order to this, and we can come back around and make use of different design techniques as we get feedback from prototypes.

@Graeme I found this article on Try Design Thinking + Scrum quite helpful for integrating design with the development lifecycle. It highlights the importance of combining design thinking (empathize, define, ideate, prototype, test) phases with iterative agile Scrum sprint builds (backlog, plan, review, retrospective). It also mentions user story mapping as a useful technique for establishing a feature backlog.