Palash Sarkar has learned that most project problems that look like design problems are actually communication problems that surfaced too late. Good client communication isn't about being constantly available — it's about being clear and consistent at the moments that actually matter.
Set Expectations Before Work Starts, Not During
Timeline, revision rounds, and what's included in scope get written down and confirmed before a project begins — not clarified reactively when a disagreement comes up mid-project. Palash Sarkar has found that the vast majority of client friction traces back to an expectation that was never explicitly set in the first place.
Written Summaries After Every Call
A verbal agreement on a call is easy to remember differently by both sides a week later. Palash Sarkar follows every client call with a short written summary of decisions made and next steps — a habit that costs a few minutes and prevents entire categories of later confusion.
Deliver Bad News Early, Not Late
If a deadline is at risk or a direction isn't working, Palash Sarkar tells the client as soon as it's clear — not at the deadline itself. Clients consistently respond better to an early heads-up with a plan attached than to a last-minute surprise, even when the underlying problem is the same either way.
Key Takeaways
Client communication that keeps projects on track is mostly about timing: setting expectations before work starts, documenting decisions immediately after they're made, and surfacing problems the moment they appear rather than when they become unavoidable. Palash Sarkar treats this discipline as inseparable from the design work itself.
Book a free consultation with Palash Sarkar at palashsarkar.com/book-a-call — he works with startups, agencies, and global brands from Dhaka, Bangladesh.