What do you do if you wake up to A LOT of comments in your doc?
Martin Mariฤรกk
2 replies
Imagine you wake up to A LOT of comments in your Figma / Notion / Google Doc file. Some are meaningful. Others not so much. Few comments even contradict each other. ๐คฏ
Imagine pushing back to 10+ of those comments.
Thatโs 10+ conversation threads opened.
Which is a great strategy...
...to waste time. ๐
Instead, I use this system:
1. Identify the low-effort & meaningful.
2. These are your no-brainers: Act and resolve.
3. Summarise the rest, and write a brief message:
3.1. Push back by explaining your opinions and insights.
3.3. List open questions, and topics for discussion.
3.4. Propose what might be the next steps.
3.5. Offer to schedule a call.
I like how it immediately adds value:
โ
Design improvements are a top priority.
๐ This shows you are committed to the project.
โ
The message is easy to respond for busy clients.
๐ This shows you are easy to work with.
What works for you?
Replies
Christopher Anderson@christopher_andersona
Oof, that sounds overwhelming! When dealing with a flood of conflicting comments, I like your strategy of identifying the meaningful ones to act on right away. For the rest, summarizing key points, pushing back with your own insights, and offering a discussion or call to align is smart. Shows you're on top of things but also collaborative. Personally, I also find it helpful to tag people on specific open questions to get clearer feedback. And if it's a real mess, sometimes hopping on a quick call to talk it through in real-time can cut through the noise faster than endless back-and-forth comments. ๐๐ฌ But your approach sounds like a solid way to efficiently handle the comment deluge! ๐ช
Share
Oof, been there! ๐
What works for me is to quickly skim through all the comments first thing in the morning and resolve any quick, easy ones right away. Then I'll summarize the key themes/questions that are emerging and write up a thoughtful response to address those, pushing back where needed and suggesting next steps. If it's still a mess after that, I'll propose hopping on a call to hash it out. The key is being responsive and adding value, while also being judicious with your time. Hope that helps! Let me know if you have any other tricks that work well.