Career·
Share
Lead a Cross-Functional Project
Successfully lead a project across teams without formal authority.
Project duration (weeks to months)
8 steps
Overview
A playbook for leading projects that span multiple teams and functions. Covers alignment, communication, decision-making, and delivery when you don't have formal authority over everyone involved. Essential for ICs taking on leadership opportunities.
Prerequisites
- Project scope defined
- Stakeholder support
- Cross-functional team identified
- Time to dedicate to coordination
Steps
1
Understand the Landscape
2-4 hoursMap stakeholders, dependencies, and potential challenges.
Prompts to use:
Deliverables:
- •Stakeholder map
- •Team dependencies
- •Potential blockers identified
- •Key relationships to build
Tips:
- •Identify who has decision-making authority
- •Understand each team's priorities and constraints
- •Note potential conflicts early
- •Find allies who can help you navigate
2
Build Initial Alignment
1-2 weeksAlign all parties on goals, scope, and approach.
Prompts to use:
Deliverables:
- •Shared project goals
- •Scope agreement
- •RACI or role clarity
- •Success criteria aligned
Tips:
- •Meet with each stakeholder 1:1 first
- •Find shared interests and common ground
- •Be explicit about roles and responsibilities
- •Document agreements in writing
3
Establish Communication Cadence
2-3 hoursSet up regular communication rhythms across teams.
Prompts to use:
Deliverables:
- •Meeting cadence defined
- •Communication channels established
- •Status update format
- •Escalation path
Tips:
- •Weekly syncs for active projects
- •Use async updates where possible
- •Create a shared Slack channel or doc
- •Define how to escalate blockers
4
Lead Without Authority
OngoingInfluence and motivate without formal power.
Deliverables:
- •Trust built with team members
- •Blockers removed
- •Conflicts navigated
- •Momentum maintained
Tips:
- •Lead with "we" not "I"
- •Make others' jobs easier
- •Give credit generously
- •Remove blockers rather than assigning blame
- •Use influence, not authority
5
Navigate Conflicts & Trade-offs
As neededResolve disagreements and make trade-offs across teams.
Prompts to use:
Deliverables:
- •Conflicts surfaced early
- •Trade-offs made explicit
- •Decisions documented
- •Alignment restored
Tips:
- •Surface conflicts early, don't avoid them
- •Focus on shared goals when resolving disputes
- •Escalate when needed - it's not failure
- •Document decisions so they stick
6
Drive Execution
OngoingKeep the project moving and hold teams accountable.
Deliverables:
- •Milestones tracked
- •Blockers resolved
- •Dependencies managed
- •Progress visible
Tips:
- •Track progress visibly (shared doc, dashboard)
- •Follow up on commitments
- •Address slips early, not at deadline
- •Celebrate milestones to maintain momentum
7
Communicate Progress
WeeklyKeep stakeholders informed with clear, regular updates.
Prompts to use:
Deliverables:
- •Weekly status updates
- •Stakeholder briefings
- •Risk communications
- •Success stories shared
Tips:
- •Proactive communication builds trust
- •Share risks early with mitigation plans
- •Tailor updates to audience
- •Highlight team wins, not just your own
8
Close & Reflect
2-4 hoursWrap up the project and capture learnings.
Prompts to use:
Deliverables:
- •Project retrospective
- •Learnings documented
- •Thank yous sent
- •Relationships strengthened
Tips:
- •Do a retrospective with the full team
- •Thank everyone publicly
- •Document what worked and what didn't
- •Use learnings for next cross-functional project