Results for “stakeholder-communication”

Map every stakeholder before engaging anyone, using an equity-aware process that captures not just obvious sponsors but gatekeepers, impacted communities, and overlooked voices.

Prioritize stakeholders using two complementary grids to set engagement strategy and surface whose voice needs elevating.

Build structured communication templates for malware incidents including stakeholder notifications, executive briefings, technical advisories, and regulatory disclosures with severity-based escalation procedures.

Write stakeholder updates that make progress, risks, asks, and decisions easy to act on.

Plan tailored engagement for a specific stakeholder before critical conversations, milestones, or relationship repairs.

Drafts monthly investor updates, quarterly board decks, and high-signal stakeholder communications that surface wins, misses, risks, and asks clearly.

Guide product managers through strategic roadmap planning by orchestrating prioritization, epic definition, stakeholder alignment, and release sequencing into a structured process.

Implement the NIST Privacy Framework COMMUNICATE function covering CM.AW awareness raising and CM.PO communication policies. Provides transparency mechanisms, stakeholder engagement frameworks, privacy notice templates, and communication workflow guidance.

Build and maintain one coherent company story across all audiences — employees, investors, customers, candidates, and partners. Detects narrative contradictions and ensures the same truth is framed for each audience's needs.

Write a roadmap narrative that connects customer problems, company goals, bets, and sequencing.

Produces a plain-language stakeholder summary from an existing feature specification, for sharing with non-technical stakeholders before implementation kicks off. Use when the user wants to draft a stakeholder summary, executive summary, or business summary of a feature spec or PRD. Does not write the spec itself — use plan-a-feature. Does not sequence the build into phases — use plan-a-phased-build. Does not produce an implementation plan — use plan-implementation.

Build evidence and narratives that connect design decisions to measurable user, product, and business outcomes.

Manages and analyzes incidents, post-incident reviews, and collaboration workflows in Allma via its REST API, covering incident discovery, timeline tracking, stakeholder communication, and retrospective analysis.