Product
Product
Slicing
Slicing
Embedded Files
Why start here?
Why start here?
It makes sense to start with Product Slicing when you are having challenges with narrowing down what features to focus on. Slicing helps with decision-making for both discovery and delivery work.
Product Slicing helps improve alignment of development efforts to strategic outcomes, makes design and delivery tradeoffs easier, and increases the likelihood of creating better customer experiences.
How it works
How it works
Narrowing a Slice by market segment
Focusing a Slice by Role or Situation
Using lightweight personas to make tradeoffs
Evaluating a Persona Journey for end-to-end success
Using a Story Map to collaboratively create a Slice
Sizing a Slice to a reference class and release costs
Mapping impacts to the Stakeholders Landscape
Identifying good product metrics for a Slice
Who gets involved
Who gets involved
The core group should be the people in roles responsible for making design tradeoffs and delivery execution. This is usually at least the:
product manager
designer
technical roles
testing
(Slicing should be collaborative, so really, the more the merrier.)
Other people in roles typically impacted by launching or releasing a product slice should also be considered, such as:
dev-ops
sales training
services / implementation
support readiness
product marketing
If some ancillary stakeholders can’t participate directly, we can accommodate them through readouts and other feedback mechanisms as needed.
Slicing worksheets
Slicing worksheets
The worksheets and canvases below are used during our structured learning.
Everything is licensed Creative Commons, so feel free to try them out!
If you have questions about using any of the tools, please reach out!
Google Sites
Report abuse