How to Give Effective Feedback During Development
Your feedback is one of the most important inputs to project success. How you give feedback can directly influence the speed, cost, and quality of what we deliver. This article shares practical guidance for giving feedback that moves the project forward.
The Golden Rules of Good Feedback
- Be specific. "The button is in the wrong place" is helpful. "I don't like it" is not. Tell us exactly what, where, and why.
- Reference the deliverable version. Always clarify which version of the design, prototype, or build you are reviewing — especially if multiple rounds have happened.
- Separate content from design from function. Content ("the text is wrong"), design ("this doesn't match the brand"), and function ("the button doesn't work") are different types of issue and help us triage quickly.
- One voice from the client side. Consolidate feedback from your team before sending. Contradictory or uncoordinated feedback from multiple stakeholders causes confusion and rework.
- Be constructive, not directive. Tell us the problem, not necessarily the solution. "The search results feel slow" is more useful than "rewrite the search algorithm" — we'll find the most effective solution.
How to Submit Feedback
- Log into this portal and navigate to your project
- Open a Support Ticket or respond to the relevant project thread
- Attach screenshots, screen recordings, or annotated images where helpful
- Reference the relevant deliverable (e.g. "Sprint 3 staging site", "Mockup v2 from 10 May")
For design reviews, tools like Loom (free screen recording) are extremely effective — a 2-minute walkthrough is often worth more than a 2-page document.
Review Timescales
We ask that review feedback is provided within the timeframe agreed in your project plan (commonly 2–5 business days per review cycle). Delays in feedback are one of the most common causes of project slippage. If you need more time, let your Project Manager know as early as possible so we can adjust the schedule.
What Happens After Feedback
- Your Project Manager will triage the feedback and categorise items as in-scope fixes or change requests
- In-scope items will be scheduled into the next sprint or revision cycle
- Change requests (outside original scope) will be quoted and require your approval before work begins
- A revised version will be shared for re-review, typically within the timeline stated in your project plan
Approval & Sign-Off
Once a deliverable has been approved (via written confirmation in the portal or by email), it is considered signed off. Subsequent changes to approved items are treated as change requests. This protects both parties and keeps the project on track.