How to Provide Effective Project Feedback
Your feedback is essential to creating a successful project. This guide explains how to provide clear, actionable feedback that helps our team deliver exactly what you need.
When to Provide Feedback
Key feedback opportunities include:
- Design Review - When mockups or wireframes are presented
- Development Review - When staging site is ready for review
- Testing Phase - When testing functionality before launch
- Post-Launch - Any issues or improvements after going live
How to Give Clear Feedback
Be Specific
Instead of: "I don't like the header"
Try: "The header text should be larger and use our brand blue (#2563eb) instead of black"
Provide Context
Explain why you want a change:
- "Our customers are mostly mobile users, so buttons need to be larger"
- "This section should emphasize our 24/7 support as it's our key differentiator"
Use Screenshots
Annotate screenshots to show exactly what you mean. Tools like Snagit, Lightshot, or even your phone's screenshot editor work well.
Prioritize
Mark feedback as:
- Must Have - Critical changes required before launch
- Should Have - Important but not blocking
- Nice to Have - Future improvements if time/budget allows
Submitting Feedback
- Log into your Client Area
- Navigate to your project or open a support ticket
- Provide feedback in writing (creates a record)
- Attach screenshots or documents as needed
Review Cycles
Most projects include a set number of revision rounds. To make the most of these:
- Consolidate all feedback before submitting
- Get input from all stakeholders at once
- Avoid piecemeal changes that require multiple rounds
Questions?
If you're unsure how to provide feedback or need clarification, reach out to your project manager.
