The skills and practices for effective, professional interaction with clients.
Communication is the connective tissue of client relationships. It's not just what you say, but how, when, and where you say it. Effective communication builds trust, prevents problems, and creates the conditions for successful collaboration. Poor communication causes more project failures than poor design.
Communication Fundamentals
Clarity
Say what you mean:
- Simple, direct language
- One idea per sentence
- Avoid jargon unless client shares it
- Confirm understanding
Timeliness
Respond promptly:
- Same-day response to emails (acknowledgment if not full answer)
- Proactive updates before asked
- Meeting follow-ups within 24 hours
- Don't let clients wonder
Professionalism
Maintain standards:
- Proper grammar and spelling
- Appropriate tone
- Reliable follow-through
- Respectful always
Transparency
Share appropriately:
- Be honest about progress
- Surface problems early
- Explain your thinking
- Acknowledge uncertainty
Communication Channels
Best for:
- Formal communication
- Documentation
- Detailed information
- Asynchronous updates
Practices:
- Clear subject lines
- One topic per email
- Action items highlighted
- Appropriate length (not novels)
Meetings
Best for:
- Complex discussions
- Presentations
- Relationship building
- Real-time problem solving
Practices:
- Clear agenda in advance
- Start and end on time
- Document decisions
- Follow up in writing
Chat (Slack, Teams)
Best for:
- Quick questions
- Informal updates
- Rapid coordination
- Team communication
Practices:
- Don't expect instant response
- Move complex discussions to email/call
- Keep it professional
- Summarize decisions elsewhere
Phone/Video Calls
Best for:
- Nuanced conversations
- Relationship building
- Urgent issues
- Tone-sensitive topics
Practices:
- Schedule when possible
- Be present and focused
- Follow up with written summary
- Use video when relationship matters
Project Management Tools
Best for:
- Task tracking
- Status visibility
- File sharing
- Comment threads
Practices:
- Keep updated
- Use consistently
- Don't duplicate across systems
- Train clients on usage
Meeting Management
Before the Meeting
Prepare:
- Clear agenda circulated in advance
- Materials ready (presentation, files)
- Technical setup tested
- Goals defined (what should we accomplish?)
Invite appropriately:
- Only necessary participants
- Decision-makers if decisions needed
- Clear start/end time
During the Meeting
Facilitate effectively:
- Start on time (acknowledge those present, don't wait forever for latecomers)
- State purpose and agenda
- Manage time and tangents
- Ensure all voices heard
- Capture decisions and action items
Participation:
- Listen actively
- Take notes
- Ask clarifying questions
- Stay focused
After the Meeting
Follow up promptly:
- Summary of discussion
- Decisions made
- Action items with owners and deadlines
- Next meeting if needed
Send within 24 hours while memory is fresh.
Written Communication
Email Best Practices
Subject lines:
- Specific and descriptive
- Include project name
- Indicate action needed (e.g., "For Review:", "Decision Needed:")
Structure:
- Lead with the key point or ask
- Support with necessary detail
- End with clear next step
- Use formatting (bullets, bold) for scannability
Tone:
- Warm but professional
- Match client's style (adapt to their formality level)
- Positive where genuine
- Direct without being brusque
Templates
Create templates for common communications:
- Project kickoff
- Status updates
- Deliverable presentations
- Feedback requests
- Invoice reminders
- Thank you / wrap-up
Templates save time and ensure consistency.
Documentation Discipline
Put important things in writing:
- Decisions made
- Scope changes
- Approvals given
- Feedback received
- Agreed timelines
Verbal agreements are risky. Document what matters.
Difficult Conversations
When to Have Them
Don't avoid necessary conversations:
- Scope creep happening
- Timeline at risk
- Budget concerns
- Quality issues
- Relationship strain
Address early. Problems grow when ignored.
How to Approach
Prepare:
- Know what you need to say
- Anticipate their perspective
- Have solutions, not just problems
- Choose appropriate setting
Open carefully:
- Acknowledge the relationship
- State the issue clearly
- Focus on situation, not blame
Listen:
- Let them respond fully
- Seek to understand
- Acknowledge their view
Resolve:
- Propose solutions
- Find common ground
- Agree on next steps
- Document the outcome
Specific Difficult Situations
Delivering bad news:
- Be direct, don't bury the lead
- Explain what happened
- Take responsibility if appropriate
- Present the path forward
Saying no:
- Acknowledge the request
- Explain why no (briefly)
- Offer alternatives if possible
- Be firm but kind
Addressing client behavior:
- Focus on impact, not intent
- Use "I" statements
- Be specific about what needs to change
- Maintain respect
Ending a relationship:
- Be professional and brief
- Complete obligations
- Don't burn bridges
- Move on without drama
Setting Expectations
At Project Start
Be explicit about:
- How you'll communicate (channels, frequency)
- Response time expectations
- Meeting cadence
- What you need from them (timely feedback, decisions)
- What they can expect from you
Throughout the Project
Reinforce:
- Remind of upcoming deadlines
- Note when waiting on client input
- Flag timeline risks early
- Update if anything changes
Managing Client Expectations
Under-promise, over-deliver: Build in buffer so you can exceed expectations.
Be realistic: Don't agree to impossible timelines or scope.
Educate: Help clients understand how design work unfolds.
Redirect: When expectations are misaligned, address early.
Communication Tone
Finding the Right Register
Match communication style to:
- Client's culture (formal vs. casual)
- Project stakes (casual for small, formal for enterprise)
- Relationship stage (more formal early, relaxed over time)
- Topic seriousness (formal for problems, warm for wins)
Being Human
Professional doesn't mean robotic:
- Show personality appropriately
- Acknowledge personal milestones (births, holidays)
- Celebrate project wins
- Be a real person
Maintaining Boundaries
Professional also means boundaried:
- Work hours for non-urgent matters
- Personal life stays personal
- Relationships are professional first
- Respect their boundaries too
Listening
Active Listening
During conversations:
- Focus fully on speaker
- Don't plan your response while they talk
- Ask clarifying questions
- Summarize to confirm understanding
Reading Between Lines
What clients don't say:
- Hesitation may mean concerns
- Over-enthusiasm may mean unrealistic expectations
- Topic avoidance may signal problems
- Tone shifts may indicate issues
Gathering Input
Creating space for clients to share:
- Ask open-ended questions
- Allow silence for thinking
- Follow up on interesting threads
- Make it safe to raise concerns
Remote Communication
Virtual Meeting Best Practices
- Camera on when possible
- Professional background
- Good audio quality
- Minimize distractions
- Engage visibly (nod, react)
Asynchronous Considerations
Different time zones and schedules:
- Don't expect immediate response
- Be clear about urgency
- Batch communications
- Respect their working hours
Building Rapport Remotely
Harder without in-person:
- Extra warmth in communication
- Video calls for relationship building
- Ask about them, not just project
- Find connection points
Communication Rhythm
Proactive Communication
Don't wait to be asked:
- Regular status updates
- Early warning on issues
- Check-ins between milestones
- Celebrate progress
Reactive Communication
When responding:
- Acknowledge quickly
- Full response in reasonable time
- Don't leave people hanging
- Follow up if you need more time
Communication Frequency
Balance visibility with overload:
- Major milestones need communication
- Problems need prompt communication
- Small progress doesn't need constant updates
- Match to project pace and client preference