stakeholder-alignment

Stakeholder Alignment

Scope

Covers

• Getting to shared understanding on goal, decision, and success criteria
• Mapping stakeholders (deciders/influencers/blockers) and tailoring messaging to what they care about
• Turning “opinions” into decision principles + evaluation criteria
• Running a no-surprises pre-brief loop to surface objections early
• Facilitating an alignment/decision meeting and locking follow-through with clear comms

When to use

• “Help me get exec buy-in for this roadmap change.”
• “We keep leaving meetings ‘aligned’ and then un-aligning—fix the process.”
• “Map stakeholders and create a plan to align them on a proposal.”
• “I need cross-functional alignment (Eng/Design/Sales/Legal) before we commit.”
• “Draft an alignment pre-read + meeting plan + follow-up comms.”

When NOT to use

• You don’t yet have a clear problem to solve (use problem definition first).
• You mainly need a decision framework/roles for a complex choice (use running-decision-processes; this skill assumes you can name the decision and stakeholders).
• You only need a polished deck or talk track (use giving-presentations; this skill focuses on alignment mechanics and artifacts, not slide design).
• The work is ongoing cross-functional coordination, not a discrete alignment push (use cross-functional-collaboration).
• You need to influence or manage your relationship with your manager specifically (use managing-up).
• The request is interpersonal/HR/legal or requires specialist counsel.

Inputs

Minimum required

• Alignment goal: inform / align / decide (and by when)
• The proposal (or decision) in one sentence + why now
• Stakeholder list (or org context to infer it)
• Constraints/non-negotiables (timeline, budget, policy, compliance, customer commitments)
• Current state: what’s already been discussed, and where alignment breaks down

Missing-info strategy

• Ask 3–5 questions from references/INTAKE.md at a time.
• If key info is unavailable, proceed with explicit assumptions and label unknowns.