Your analysis framework determines how Pilea categorizes incoming feedback into backlog item types. Choosing the right one means your backlog reflects the kind of work your team actually tracks - whether that's bugs and features, jobs to be done, or UX Quality.
‼️ Important: The analysis framework is set per workspace and cannot be changed after setup. If you want to use a different framework, create a new workspace.
What is an analysis framework?
When feedback arrives in Pilea - from Intercom, HubSpot, a survey, a file etc, the AI reads it and creates a backlog item. The framework you choose determines what type that backlog item gets assigned.
For example, if a user says "the login flow is confusing," Pilea might classify that as a Bug (Backlog management), a Functional job (Jobs to be done), or an Efficiency issue (UX Quality) - depending on your framework.
The three frameworks
Backlog management
Best for: Teams that plan work as features, improvements, bugs, and technical debt.
Backlog items are categorized as:
Feature - Something new to build
Improvement - An enhancement to something that already exists
Bug - Something that's broken or not working as intended
Technical debt - Underlying code or architecture that needs addressing
This is the most common choice for product teams. If you're unsure which framework to choose, start here.
Jobs to be done
Best for: Teams that want to understand the underlying goal behind each piece of feedback, not just the surface request.
Backlog items are categorized as:
Functional job - A practical task the user is trying to complete
Emotional job - How the user wants to feel while using the product
Social job - How the user wants to be perceived by others
This framework is common in UX research and discovery-heavy teams. It shifts focus from "what did they ask for" to "why did they ask for it."
UX Quality
Best for: Teams focused on improving the quality of the interaction - not just adding features, but making the existing product work better.
Backlog items are categorized as:
Learnability - How easy it is to understand the product for the first time
Efficiency - How fast experienced users can accomplish tasks
Errors - How often users make mistakes and how recoverable those mistakes are
Satisfaction - How pleasant the experience feels overall
Accessibility - How well the product works for users with different abilities
This framework maps to usability heuristics and is a strong choice for design-led teams or products where user experience is a primary differentiator.
Which framework should you choose?
If your team... | Choose... |
Plans work as bugs, features, and improvements | Backlog management |
Wants to understand user intent behind requests | Jobs to be done |
Is focused on improving interaction quality | UX Quality |
Is unsure | Backlog management |
How your framework is set
Your first workspace is automatically set to the Backlog management framework. There's no framework selection step during onboarding - you can start organizing feedback right away.
If you'd prefer a different framework, create a new workspace after onboarding and choose your preferred framework during that workspace's setup.
Want to use a different framework?
The framework is locked to the workspace it was created with. If you want to try a different framework, create a new workspace by clicking your workspace name in the top-left sidebar and selecting Add workspace, then choose the framework you want during that workspace's setup.