Handbook
/
Execution & Delivery
Communication That Drives Execution
Good communication accelerates everything. Here's how to communicate for results.
Communication is the operating system of your startup. When it works, teams align, decisions happen, and execution flows. When it doesn’t, misalignment creeps in, work gets duplicated, and things fall through cracks. Great execution requires great communication.
Why Communication Matters
Alignment Requires It
Everyone needs to know:
What we’re trying to achieve
Why it matters
What they should do
How pieces fit together
Without communication, everyone’s working in the dark.
Speed Depends on It
Fast execution requires:
Quick information flow
Fast decisions
Rapid coordination
Communication delays slow everything.
Trust Builds Through It
Teams trust when:
Information is shared
Rationale is explained
People feel informed
Silence breeds suspicion.
Communication Principles
Clarity Over Quantity
Good communication is:
Clear
Concise
Actionable
Not just lots of words.
Context Is Everything
Don’t just tell people what:
Why does this matter?
How does it fit?
What’s the background?
Context enables better work.
Repetition Matters
Key messages need repetition:
People forget
New people join
Context fades
Say it more than feels necessary.
Medium Matters
Match communication to need:
Urgent? → synchronous
Detailed? → written
Sensitive? → face to face
Reference-worthy? → documented
Types of Communication
Top-Down
Leadership to team:
Strategy and priorities
Company updates
Major decisions
Vision and direction
Bottom-Up
Team to leadership:
Progress and blockers
Customer feedback
Ideas and concerns
Ground truth
Communicating Grievances
Disagreement is healthy. Silent resentment is toxic. Knowing how to voice concerns effectively is a critical skill.
Why It Matters
Unvoiced grievances:
Fester and grow
Lead to disengagement
Cause surprise departures
Block honest collaboration
How to Raise Concerns
Be direct, not passive-aggressive:
State the issue clearly
Avoid hints or hoping someone figures it out
“I’m concerned about X” not “Some people think…”
Focus on the problem, not the person:
Describe impact and behavior
Avoid character judgments
“The deadline changed three times” not “You’re unreliable”
Come with context:
Why does this matter?
What’s the impact?
Have you tried anything?
Propose solutions when possible:
“Here’s what might help…”
Even imperfect ideas show investment
Disagree and Commit
After voicing concerns:
Your input was heard
A decision was made
Now execute fully
Disagree loudly before decisions. Commit fully after.
Creating Space for Grievances
For leaders:
Ask explicitly: “What’s not working?”
React well to criticism (or you won’t hear more)
Follow up on raised issues
Distinguish between venting and actionable concerns
The goal isn’t zero grievances. It’s honest communication that surfaces problems early enough to fix them.
Horizontal
Peer to peer:
Coordination
Knowledge sharing
Collaboration
Support
All Directions
Every type matters. Prioritize all.
Written Communication
When to Write
Write for:
Detailed information
Reference material
Async collaboration
Record keeping
Good Writing
Effective written communication:
Gets to the point quickly
Structures for scanning
Uses clear language
States action items clearly
Documentation
Document important things:
Decisions and rationale
Processes
Architecture
Key knowledge
Write once, reference many times.
Async First
Default to async:
Allows thoughtful response
Respects time zones
Creates record
Reduces meetings
Sync when necessary, not default.
Verbal Communication
When to Talk
Talk for:
Complex discussions
Sensitive topics
Rapid back-and-forth
Relationship building
Effective Meetings
When you do meet:
Clear purpose
Right attendees
Follow agenda
End with actions
1:1 Conversations
Regular individual conversations:
Build relationships
Surface issues
Provide support
Give feedback
Team Communication Rhythms
Daily
Quick standups (15 min)
Slack/chat updates
Blocker flags
Weekly
Team meetings (30-60 min)
Status updates
Priority alignment
Monthly/Quarterly
All-hands
Strategy updates
Retrospectives
Planning sessions
As Needed
Project kickoffs
Decision meetings
Incident response
Celebrations
Communicating Decisions
Share the Decision
Be explicit:
“We decided X”
“This is final”
“This is what changes”
Share the Rationale
Explain why:
“We chose this because…”
“We considered X but…”
“The trade-offs were…”
Share the Impact
What happens now:
“This means you should…”
“This affects…”
“Next steps are…”
Communicating Bad News
Early
Share bad news fast:
Don’t wait for certainty
Don’t wait until it’s worse
Give people time to react
Direct
Be clear:
State the news plainly
Don’t bury the lead
Don’t sugarcoat excessively
Complete
Include what matters:
What happened
What it means
What we’re doing
What they should do
Constructive
Focus forward:
What we learned
How we’ll prevent
Path forward
Communicating Change
Explain the Why
Why is this changing?
What problem are we solving?
What opportunity are we pursuing?
What drove this decision?
Acknowledge the Impact
Recognize what changes:
What’s affected
Who’s affected
What’s hard about it
Provide the Path
What happens next:
Timeline
Specifics
Support available
Questions answered
Communication Anti-Patterns
Information Hoarding
Keeping information to yourself.
Problem: Others can’t do their jobs. Trust erodes.
Fix: Default to sharing. Transparent unless sensitive.
Assuming Understanding
“Everyone knows this.”
Problem: They often don’t. Misalignment results.
Fix: Confirm understanding. Repeat key messages.
Too Much Communication
Flooding channels with noise.
Problem: Important things get lost. Overload.
Fix: Curate. Prioritize signal. Right channel for right message.
Too Little Communication
Going silent.
Problem: Vacuum fills with speculation. Trust erodes.
Fix: Regular updates. Even “no news” is news.
Wrong Medium
Using Slack for complex decisions. Email for urgent issues.
Problem: Miscommunication. Slow response.
Fix: Match medium to message type.
Communication Tools
For Real-Time
Slack/Discord
Phone/video
In-person
For Async
Email
Documents
Video recordings
Comments
For Knowledge
Wiki/Notion
Documentation
Runbooks
FAQs
Use Consistently
Pick tools and stick with them:
Everyone knows where to look
Information doesn’t fragment
Habits form
Improving Communication
Audit Current State
Where does information get stuck?
What’s communicated poorly?
Where is there confusion?
Address Gaps
Add missing communication
Fix broken channels
Train on tools
Get Feedback
Ask team how communication is working
Survey periodically
Watch for symptoms
Iterate
Communication needs evolve:
As team grows
As work changes
As tools improve
Key Takeaways
Communication is the operating system of execution—when it breaks, everything suffers
Clarity over quantity: concise, actionable, contextualized
Repetition matters: say important things more than feels necessary
Match medium to message: async for detailed, sync for complex, written for reference
Document decisions with rationale: what, why, and what now
Share bad news early, direct, and complete—then focus forward
Avoid anti-patterns: information hoarding, assuming understanding, wrong medium
Default to transparent: share unless there’s a good reason not to
Communication needs evolve as you grow: audit, improve, iterate
Right channel, right message, right time—consistency enables clarity
AIMake has access to all of this
Our AI has access to the entire Startup Handbook. Ask it anything about building your startup.
Get started
Previous
Building and Maintaining Momentum
Next
Decision-Making for Startups