Palash Sarkar has received every kind of client feedback imaginable — from precise, actionable notes to vague reactions like "it just doesn't feel right yet." Handling both well without spiraling into endless unfocused revision rounds is a specific skill, not a matter of just doing whatever's asked.
Ask "Why" Before Making the Change
When feedback arrives as a requested change — "make the logo bigger" — Palash Sarkar asks what problem that change is meant to solve before implementing it literally. Often the underlying concern (the logo doesn't feel prominent enough) has a better solution than the one initially proposed, and understanding the real goal prevents revision rounds that treat symptoms instead of causes.
Structured Revision Rounds, Not Open-Ended Ones
Every project scopes a defined number of revision rounds upfront, each with a clear purpose — round one addresses structural feedback, round two addresses visual refinement, and so on. Open-ended "keep sending changes" arrangements are where projects lose momentum and scope creeps without anyone deciding it should.
Distinguishing Preference From Problem
Not all feedback points to an actual problem — sometimes it reflects personal taste that doesn't align with the strategic direction already agreed on. Palash Sarkar pushes back respectfully when feedback conflicts with agreed strategy, backing that pushback with the reasoning established earlier in the project, rather than simply implementing every note without discussion.
Key Takeaways
Effective feedback handling isn't about implementing every note exactly as written — it's understanding the real concern behind a note, structuring revision rounds with purpose, and defending strategic decisions when a note conflicts with them. Palash Sarkar's revision process is built to make every round count.
Book a free consultation with Palash Sarkar at palashsarkar.com/book-a-call — he works with startups, agencies, and global brands from Dhaka, Bangladesh.