Everyone knows they need input from colleagues to take projects from good to great, but not everyone knows how to do it in a manner that feels lightweight or organized. It also doesn't help that collecting feedback often feels like a tangled web of documents, tools, and comments.
And it doesn’t have to be that way!
We’re sharing our best tips for documenting and organizing feedback for projects across all roles, so you don’t have to wrangle scattered comments, replies, and decisions across platforms.
Let's dive in...
Create a clear process for collecting feedback
Set up a schedule to gather input regularly to keep your projects running smoothly.
How often should you collect feedback? It depends on your experience and project scope. Generally, though, reviews should happen at the beginning, middle, and end of a project.
Designate who needs to provide feedback
When too many people are providing feedback, conversations can drag on and nothing moves forward. 😩
Don’t put too many cooks in the kitchen—determine how many colleagues (and which ones) should provide feedback at each project stage.
Add specific details when requesting feedback
The more specific the feedback request, the more valuable the input will be. Every feedback request should include:
🎯 The goal of the project
📝 Necessary background information
❓ Specific questions or issues someone wants input on
Pick one platform to use for feedback
It’s easy for feedback to get lost in the shuffle when switching between tools like Figma and Github. Pick one place to request and share feedback, so team members don’t have to jump from tool to tool.
We know we’re biased, but Threads is our top pick for this very use case. Share links, tag team members, and keep the discussion for each project in one, easy-to-follow thread.
Set response time guidelines
Set response time guidelines upfront, so remote team members across time zones can plan when they’ll provide feedback. We recommend 24-48 hours minimum.
Create a naming system
It’s easy to search and reference feedback if you use a standardized naming system, channel, or title. We recommend using the project name, participants' names, and other qualifiers that will help you stay organized.
Those are likely to be key search terms 🔎 if you look up notes or feedback later!
Make it easy to leave feedback & loop in others
This is where having a tool like Threads, which is both lightweight and async, comes in handy. Ensure your teammates feel empowered to be honest and communicate effectively, allowing everyone to learn quickly and share their context.
Make feedback a part of ongoing growth goals and discussions
Use the input you receive on projects as a guide for ongoing growth and professional development goals. Look for consistent trends or areas of improvement and discuss them with your manager or a trusted teammate to see how you can improve for next time.
With these tips in mind, we hope you'll be able to make collecting feedback a little more manageable.
Interested in trying it out for yourself? Sign up for early access at threads.com.