Project Breakdown

Intermediate

Structure an internal app or customer product before research and workflow planning.

What you’ll learn

Understand how Project Breakdown differs by journey
Review and confirm each planning section
Use the completed breakdown as input for research

Overview

Project Breakdown turns the project idea into structured planning context. It is the first major step after project creation and prepares the project for research, workflow alignment, features, architecture, and handoff.

The breakdown adapts to the journey you chose during project creation.

Internal App Breakdown

Internal apps use six sections that focus on operational clarity:

Capability Goal - What the internal app needs to help the team accomplish.
Users & Roles - Who uses the app and what each role needs to do.
Core Tasks & Operating Flow - The main work the app supports.
Core Modules / Screens - The key areas the app needs.
Data, Systems & Controls - The data, source systems, rules, access, and reporting needs.
Success Outcome & Planning Gaps - What success looks like and what still needs a decision.

Use this path for approval workflows, dashboards, admin consoles, internal portals, operations tools, and automation support.

Customer App Breakdown

Customer apps use five sections that focus on product-market clarity:

Purpose - Why the product exists.
Problem - The problem it solves.
Target Users - The customers or users it serves.
Core Features - The first important capabilities.
Goals - The outcome the product should reach.

Use this path for products that customers, partners, consumers, or developers outside your organization will use.

Review Each Section

Open Project Breakdown from the project sidebar or next action card. Review the suggested content for each section and edit anything that does not match the real goal.

Keep each answer practical. For internal apps, name the roles, tasks, systems, rules, and outcomes. For customer apps, clarify the customer, problem, value, and first-version scope.

Complete The Breakdown

Confirm each section once the content is accurate enough to guide the next step. Empty or vague sections make later research and workflow planning less useful.

Tip: You do not need perfect wording. Focus on decisions that will affect the workflow, feature scope, and technical direction.

Next Steps

After Project Breakdown, internal apps continue to Internal Research. Customer apps continue to Market Research.