"User Feedback" Asana Template

"User Feedback" Asana Issue Template

Use our "User Feedback" Asana issue template to help your teams build better, faster.

Magical.pm

Finding the Right Template For Your Team

Selecting the right Asana issue template is important in building your product and project management workflow. Some teams prefer simple, sparse issues that get to the point, while others prefer complex, documentation-rich issues. Each team is different, and your template should evolve as your team's needs change. With that in mind, we've assembled a library of Asana issue templates to help your team find what works. Our "User Feedback" template, which you can find below, is a great starting point.

What Does "Right" Look Like?

The right Asana issue template will match your team's stage, maturity, and purpose. Early in the product development process, your team is likely small and working on proof of concepts, where flexibility and quick pivots are key to success. Your team will likely want the lightest-weight issue template possible at this stage, enabling quick iteration without the burden of unnecessary documentation. Your issue template will evolve with your team, and as your team grows, so will your processes. Even with team growth, it's important to document as little as possible to maintain agility. The phrase "as little as possible" is intentionally chosen. If you under-document, you will lack a history of your team's work, the decisions you made, and their "why." You don't want to over-document, either. A good barometer for this is to ask yourself, "Is someone going to read what I'm writing?" If the answer is "yes," you're probably on the right track. If the answer is "no" or "not really," you're probably over-documenting. Striking the right balance is key to maintaining your velocity, and selecting the right Asana issue template can help you stay on the right track.

1

Stage-Appropriate

Ensure your template strikes the right balance between over- and under-documenting.

2

Flexible

Maintain flexibility as your team grows by optimizing for the least documentation possible.

Template

Our "User Feedback" Template

You can copy and paste this Asana issue template into Asana to create your own, or use Magical.pm to generate it with AI.

User Feedback Task

[Provide a concise summary of the user feedback received, including the source (e.g., surveys, support tickets, reviews) and key themes identified.]

Issues Identified

[List the most common concerns or pain points raised by users, along with any patterns or recurring issues.]

Action Plan

[Describe the proposed next steps to address the feedback, including potential fixes, improvements, or further investigation needed.]

To-Do:

• [Identify and outline the first actionable task based on user feedback.]
• [Specify the second actionable task required for implementation or further research.]
• [...continue listing all relevant tasks...]

Acceptance Criteria:

• [Clearly define the first success condition or expected outcome after implementing feedback-driven changes.]
• [Specify the second success condition or expected outcome.]
• [...continue listing all acceptance criteria...]

Good PMs use templates. Great PMs use templates in Magical.pm.Generate "User Feedback" issues with Magical.pm, the AI product management co-pilot.

Example

"User Feedback" Template Example

Here's an example of our Asana issue template in action.

User Feedback Task

Recent feedback from Hitchhiker’s Guide to the Galaxy App users (via surveys & support tickets) highlights navigation confusion, slow response times, and missing intergalactic travel recommendations.

Issues Identified

• "Don’t Panic" button is hard to find on mobile.
• Route planner struggles with multi-planet itineraries, often failing for Magrathea.
• Sluggish performance when retrieving restaurant recommendations (e.g., Milliways).
• Lack of offline mode—users stranded in dead zones complain about inaccessibility.

Action Plan

• Redesign "Don’t Panic" button for better visibility on all screen sizes.
• Fix route planner bugs & improve planetary travel logic.
• Optimize API calls for faster restaurant lookups.
• Develop an offline mode with cached travel guides & emergency tips.

To-Do:

• Update UI to highlight "Don’t Panic" button on mobile.
• Debug & optimize multi-planet route calculations.
• Improve restaurant recommendation response times via caching.
• Implement offline support for critical guide content.
• Conduct user testing on changes before release.

Acceptance Criteria:

• "Don’t Panic" button is easily accessible on all devices.
• Route planner correctly handles Magrathea & other complex destinations.
• Restaurant lookup times are ≤ 2 seconds.
• Users can access key travel info offline in dead zones.

Generating Asana Issues with Magical.pm

While you can use this template manually in Asana, it's also compatible with Magical.pm, our AI issue generator. Using Magical.pm, you can instantly turn natural language like "unsink the Titanic" (feeling brave?) into perfectly formatted Asana issues. Magical.pm works hand-in-hand with Asana. When you generate a issue with Magical.pm, it is formatted in markdown, meaning it will perfectly copy into Asana, retaining everything from code blocks to headings. Internally, we copy issues from Magical.pm to Asana daily, making our workflows significantly faster. This workflow strikes a healthy balance: everything we love about human-generated requirements – the details and context – without the cognitive load and time overhead of perfect formatting, grammar, and writing.

Magical.pm

Use Magical.pm to Generate Perfect Asana Issues Every Time

Generate Asana Issues with Magical.pm