Knowing the real needs of users and developing features aligned with those needs are key factors in building successful products. In Lean Inception, teams align on features — what the user wants to do. The next step is moving from features to user stories, using techniques like the Product Backlog Building (PBB) Canvas to break down each feature into actionable, user-centered stories that guide delivery.
This article will help you:
-
Understand what a feature is in Lean Inception
-
Define a user story, based on the PBB Canvas
-
See how to write and validate good user stories
-
Explore five real examples — including one with a technical enabler
What Is a Feature in Lean Inception?
A feature is something the user wants to do. Plain and simple.
Think of it as a user action or goal — expressed in everyday, user-friendly language. No tech jargon, no internal system talk. Just what the user wants.
In Lean Inception, I describe a feature as an interaction between the user and the product. For example: print an invoice, check my account balance, or invite a friend via social media.
We define features during the Lean Inception workshop — but only after we’ve nailed the product vision, understood the personas, and mapped their journeys. That way, every feature has meaning. It’s not just a random idea; it solves a real user need, supports a business goal, or improves a step in the journey.
Write features clearly and simply. Everyone on the team — from business folks to developers — should understand them. That shared clarity helps with alignment and prioritization. Once you’ve listed the features, the team will review them from technical, business, and UX perspectives. Then, you’ll decide the MVP and what comes next.
In short: a feature is a piece of your product’s value, rooted in real user needs and shaped through collaboration.
Now, how do you write a good feature?
Let’s look at a simple example:
✅ Good Feature
Log in to access your account
This describes what the user wants to do — in plain language.
🚫 Bad Feature
Authentication module with token refresh
This one dives into implementation details. It’s technical and doesn’t speak from the user’s point of view.
Feature Writing Tips
-
Start with a verb
-
Focus on what the user does
-
Skip the tech talk — no internal system details
-
Keep it short and collaborative
What Is a User Story?
A user story is a short, clear description of functionality — told from the user’s point of view.
In How to Define, Prioritize and Refine User Stories using the Product Backlog Building Canvas (which I co-wrote with Fábio Aguiar), we lean on this simple idea, originally popularized by Mike Cohn: user stories help the team understand what the user wants, why they want it, and who it matters to.
It’s a lightweight, powerful way to describe functionality — and a great bridge between Lean Inception features and your product backlog.
The 3 Ws of a User Story
A good user story answers three questions:
-
Who wants it? (the user or persona)
-
What do they want? (the action)
-
Why do they want it? (the benefit or reason)
User Story Standard Format
The classic format works because it’s clear and repeatable:
As a [persona], I want to [action], so that [benefit].
Example:
As a user, I want to log in with my credentials, so that I can access my account.
INVEST and 3Cs for Good User Stories
Here are a few models we like to use in practice:
INVEST (from Mike Cohn & William Wake)
-
Independent – Can be built and delivered on its own
-
Negotiable – Leaves room for conversation and refinement
-
Valuable – Delivers something meaningful to the user
-
Estimable – The team can roughly estimate the effort
-
Small – Sized right for planning and delivery
-
Testable – Has clear criteria for success
The 3 Cs (from Ron Jeffries)
-
Card – The story itself
-
Conversation – Dialogue to clarify and refine
-
Confirmation – Acceptance criteria to validate
From Features to User Stories: 5 Real Feature Examples
Let’s take a look at how Lean Inception features turn into user stories. You’ll see how each story focuses on the user’s experience — not the system’s behavior.
Sample Feature: Log in to access your account
User Stories:
-
As a user, I want to log in with a username and password, so that I can securely access my account.
-
As a user, I want to recover my password if I forget it, so that I can regain access without needing support.
-
As a user, I want to complete a CAPTCHA, so that I can prove I’m not a bot.
-
As a user, I want to be required to set a strong password, so that my account remains secure.
Sample Feature: Schedule an appointment with a service provider
User Stories:
-
As a customer, I want to see available time slots, so that I can choose a convenient appointment time.
-
As a customer, I want to select a date and time, so that I can book an appointment that fits my schedule.
-
As a customer, I want to receive a confirmation after booking, so that I know my appointment is confirmed.
-
As a customer, I want to reschedule or cancel my appointment, so that I can adjust it if my plans change.
Sample Feature: Receive notifications about important updates
User Stories:
-
As a user, I want to receive a notification when my appointment is confirmed, so that I stay informed.
-
As a user, I want to get reminders before upcoming events, so that I don’t forget them.
-
As a user, I want to choose how I receive notifications (email, SMS, app), so that it matches my preferences.
-
As a user, I want to disable notifications I don’t need, so that I avoid information overload.
Sample Feature: Search for soccer matches without using geolocation
User Stories:
-
As a non-registered soccer player, I want to search for matches near a manually entered address, so that I can find games close to where I am.
-
As a registered soccer player, I want to search for matches near my workplace, so that I can find games after work.
-
As a registered soccer player, I want to search for matches near my residence, so that I can find nearby games on weekends.
Sample Feature: Add a profile picture
User Stories:
-
As a user, I want to upload a photo to my profile, so that others can recognize me.
-
As a user, I want to see my uploaded profile picture, so that I know it was saved successfully.
-
As a user, I want to change or remove my profile picture, so that I can keep my profile up to date.
- Research image storage solutions (e.g., AWS S3, Firebase) to enable secure photo upload functionality (Technical Enabler) ⚠️
⚠️ Note: This is not a user story — it’s a technical investigation (a spike) that supports delivery of real stories.
From Features to Stories: Turning Insight into Action
Lean Inception helps you discover the right features — grounded in real user needs. Then, tools like the PBB Canvas guide you in breaking those features down into clear, actionable user stories.
To build the right product:
-
Start with a feature that reflects a real user goal
-
Break it down into user stories using the As a / I want to / So that format
-
Add clarity with acceptance criteria, UI sketches, and ongoing team conversation
-
Identify enablers (like spikes) that support delivery — but don’t mix them up with user stories
It’s all about moving from alignment to action — together with your team.
