Overview
The Customer Product Journey is for products used by customers, partners, consumers, or developers outside your organization. It is the right path for B2B, B2C, B2B2C, and developer-facing products.
This journey focuses on customer value, market context, product workflow, PRD, features, architecture, and developer handoff.
Create A Customer Project
Open the project wizard and choose Customer apps. Enter the project name and description, then choose the customer context.
Use:
- B2B for business customers.
- B2C for consumers.
- B2B2C for products reaching users through another organization.
- Dev Tool for developer-facing products.
Choose the application types that match the product, such as web, mobile, desktop, API, or other.
Complete Project Breakdown
Project Breakdown structures the product into five sections:
- Purpose.
- Problem.
- Target Users.
- Core Features.
- Goals.
Review the content and make sure it clearly explains who the product is for and what first-version value it should deliver.
Run Market Research
Market Research reviews customer, market, risk, opportunity, competitive, and confidence signals. Use it to sharpen the product direction before workflow planning.
If the report feels too broad, improve the project description or breakdown and run research again.
Align And Map The Workflow
Workflow Alignment captures the product decisions that shape the main customer journey. Answer with clear details about user actions, decisions, constraints, and outcomes.
Application Workflow then turns those answers into a flow map and detailed workflow nodes.
Define Features
Create or generate features from the confirmed workflow. Keep the feature set focused on the first version and remove duplicate or future-scope ideas before handoff.
Use feature details, requirements, acceptance checks, priority, and scope fields to make the build intent clear.
Prepare Architecture
Open Technical Architecture after the feature scope is clear. Review the suggested architecture style, stack choices, and high-level diagram through the lens of the customer type and expected product usage.
Regenerate or adjust recommendations when the product direction changes.
Create PRD And Dev Pack
Generate the PRD when the customer product plan needs a structured requirements document. Review, edit, and export it as needed.
Create the Dev Pack after features, architecture, and any required PRD material are ready.
Next Steps
Create a customer project, complete Project Breakdown, and use the next action card to move through Market Research, workflow, features, architecture, PRD, and Dev Pack.