TL;DR: Want to share Wrike feature suggestions and workspace ideas that spark great discussions? Follow this simple 4-step blueprint to write clear, impactful Product Feedback posts that resonate with fellow Wrikers and make your suggestions easy to discover!
Hello Community! 👋
Got a great idea to make Wrike even better? The Product Feedback forum is the best place to share your ideas, discuss workflow needs, and see what capabilities other teams are looking for.
However, with many ideas being shared across the Community, how do you make sure your feedback post is clear, structured, and easy for everyone to understand?
Here is a 4-step guide to crafting a well-written Product Feedback post that stands out!
1.Search First (Avoid Split Discussions!) 🔍
Before creating a new thread, use the Community Search bar or explore existing product feedback to see if someone has already posted a similar idea.
- Why it matters: If multiple members create separate posts for the exact same request, discussions become fragmented across different threads.
- The Smart Move: If an existing thread already covers your request, hit Upvote, add an 🙂 Agree reaction, and drop a comment with your specific use case. Uniting behind a single thread builds a strong, focused discussion!
2.Focus on the "Why" (The Pain Point) 🎯
When describing your request, don't just state the feature you want, explain the specific problem you are trying to solve.
- Clear Title: Use a descriptive title (e.g., "Option to auto-assign custom fields in Project Blueprints" instead of "Fix Blueprints").
- Describe the Impact: Detail how the current setup creates friction, how much time a change would save, or how it affects your team's day-to-day workflow.
- Why it matters: Other members might use a slightly different process than you, but when they read about your daily challenge they will relate and react with 💡 Insightful or 🙂 Agree!
3.Add Feature Tags for Maximum Discovery 🏷️
Tags are descriptive keywords that connect your post to specific Wrike product features.
- How to use them: When drafting your post, select relevant feature tags like
dashboards, custom-fields, automation, or board-view.
- Why it matters: As covered in our Community Tags Guide, members actively follow and search specific feature tags. Adding them ensures your feedback appears in curated feeds where interested users can easily discover it!
4.Rally Your Peers & Share the Link 📢
Once your post is live, don't just leave it sitting there, share it!
- Share with Colleagues: Send the link to your teammates or fellow Wrike admins and ask them to log into the Wrike Community, share their thoughts, and add their perspective.
- Use Community Threads: Drop your link into community discussions like our Product feedback Wishlist Swap Post to get insights and feedback from other community members!
Ready to Share Your Ideas?
💬 Have you ever created a Product Feedback post in the Community? Drop a link to your post in the comments below, or share your own top tip for writing great feedback! ⬇️
Found this post useful? Tap a reaction below (👍 Like or 💡 Insightful) to show your support and help other members find this guide!
