By creating templates, your team will save time when creating new features, products, components, objectives, releases, companies, portal cards, insight notes, or any element that you can add a description to while ensuring that the most valuable information is included.
In this article
How to create a new template
You can create templates for features, products, components, objectives, releases, companies, portal cards, insight notes, or any element that you can add a description in.
You can easily create a new template in just a few clicks.
- Open a new description and click on the Template icon or where it says choose from template in the text editor.
- When the template modal opens click CREATE NEW and create your new template.
- Once the template is ready, click Create.
Selecting, editing, or deleting a template
Note
If you have already entered content into your description and you select a template, then the template will be appended to the existing content.
If you have already created a template simply open a new feature, products, components, objectives, releases, companies, portal cards, insight notes, or any element that you can add a description to and click on the Template icon. A new modal will open where you can select, edit or delete an existing template by hovering over it.
Template examples
Note Templates
Request Details*
What is the customer requesting? Please provide details on the request so we can better understand why this is important to them.
Your Answer:
Use Case*
How will they use this feature? In what business scenarios will they do this?
Your Answer:
Pain Points*
Without this feature what issues is the customer currently facing? Be detailed and explain why this causes pain for the customer.
Your Answer:
Benefits*
Justify this request. Why/How does this improve the user’s experience? Back up this request with real benefits that the feature will deliver.
Your Answer:
Use Case
What does the user need this for?
Problem:
what is the user trying to solve?
Can you provide an example:
How do you do this now:
Delta-Next template for discovery interviews
🔗 Links
(e.g. a recording)
🏢 Customer context(who’s the customer, their role, how they currently use the functionality in question, or what kinds of problems they need to solve etc.)
✅ We were right about(which assumptions or hypotheses were confirmed? what parts of our solution worked well?)
❌ We were wrong about(which assumptions or hypotheses were disproved? what parts of our solution didn’t work?)
🤔 We didn’t know about(things to consider that we haven’t previously)
🔍 We want to learn more about(what do we need to discover further?)
✨ New ideas(any ideas for our solutions based on the interview)
📜 Raw notesFeature Templates
💡 Problem
📖 User Story
🎨 Design
🙈 Analytics
🛑 Out of scope
- Abc
- ABC
⛓ Dependencies
🉑 Acceptance Criteria
- Given
- When
- Then
🎯 Measuring Success
- ABC
- ABC
🛳 Release Strategy
What is this?
Provide a short description about the "feature" - help us understand the customer need to the business problem it would solve
Add text here
Hypothesis
State your hypothesis
Add text here
Success metrics
How will we know if the need/problem has been solved?
Add text here
Open questions or limitations
What open questions do you still have, if any?
Add text here
Timebox
How much time would you be willing to invest to solve this need/problem? (state in weeks)
Solution Brief
[Link] to a long-form detailed brief, including:
- Goals
- Problem
- User Story
- Acceptance Criteria
- Design (notes for delivery and requirements)
- Metrics to track
- Analytics requirements
- Roll-out strategy
- GTM
- Follow-up brief
- Notes
🙋♀️ User Story
As a user, I want to...
📝 Design
Link:
ABC:
🙋♂️ Acceptance criteria
- Expected behavior
- Current behavior that remains unchanged
Objectives Templates
Link to Product Brief (optional)
🤔 Problem- What's the problem?
- What are the company-level goals this will help fulfill?
- Who is it for?
- What metrics will we move?
- What are some example solutions?
file_download Download our notes and features templates
Comments
Article is closed for comments.