Feature Mapping

Purpose

Feature Mapping takes a feature or epic and decomposes it into a structured map of user steps and acceptance rules. It helps teams see the full scope of a feature, identify thin slices for incremental delivery, and ensure nothing is missed.

At a glance

How to run

1. Name the feature (2 min) — Write the feature title on a card at the top.
2. List actor steps (15 min) — Walk through the user's journey step by step. Write each step on a card in a horizontal sequence.
3. Add acceptance rules (20 min) — Below each step, add the business rules and acceptance criteria that apply. Use green cards for rules and red cards for questions.
4. Identify slices (15 min) — Draw horizontal lines across the map to define thin vertical slices. Each slice should be independently releasable.
5. Prioritize slices (5 min) — Number the slices in delivery order. The first slice is the MVP.
6. Capture stories (3 min) — Each slice becomes one or more user stories in the backlog.

Materials needed

• Feature or epic description
• Coloured cards or sticky notes (steps, rules, questions)
• Large whiteboard or Miro
• Story-template cards

Pitfalls & common mistakes

• Mapping the system, not the user — Focus on what the user does, not what the backend does.
• No slicing — Without slicing, the map is a nice picture but does not help with incremental delivery.
• Missing edge cases — Add a pass for error scenarios and alternative paths.
• Doing it alone — Feature mapping needs diverse perspectives: product, dev, design, test.

Inclusion & accessibility

• Provide the feature description in advance.
• Use both colour and shape for card types.
• Walk through the map aloud so remote participants can follow.

Variations

• User Story Mapping — Jeff Patton's broader format mapping the entire user journey.
• Impact Mapping — Start from goals and actors before mapping features.
• Domain Event Discovery — Focus on domain events rather than user steps.

When NOT to use this

• For very small features that are already clear and can be one story.
• If the team does not yet understand the user — do user research first.

Source & further reading

• Sherif, K. (2018). "Feature Mapping — a lightweight requirements technique." johnfergusonsmart.com
• Patton, J. (2014). *User Story Mapping*. O'Reilly.