Do, Try, Consider — How we give product feedback at Asana

The Framework

Do

“Do” is used for mandatory feedback. It overrules the team, and so we use it very rarely — just for times when a decision is hard to reverse and has a big impact on quality or system complexity. Most projects never get any “do” feedback, and the rest mainly get 1 or 2.

How to respond to “Do” feedback

Teams try to find a solution and implement it by the next milestone. Then they’ll loop back with stakeholders to let them know it’s done.

Try

“Try” is used to request a specific exploratory next step like drawing some options or looking into the code to cost something. After doing the exploration, the team is empowered to decide whether to change course or not.

How to respond to “Try” feedback

Teams share the explorations back to stakeholders and with let them know if they are going to use one of the new explorations or stick with the original plan:

Consider

“Consider” is used to share ideas or alternate ways of thinking about a problem. After thinking through the point briefly and responding, the team is empowered to take the feedback or not.

How to respond to “Consider” feedback

Teams think about the feedback and respond either in the moment, or in a written follow-up.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Jackie Bavaro

Jackie Bavaro

Author of Cracking the PM Career & Cracking the PM Interview, https://amzn.to/3If6X9U. Previously @ Asana, Google & Microsoft.