Results for “stake”

Map stakeholders on a power/interest grid and generate a tailored communication plan for each group.

Provides strategic leadership frameworks for vision, fundraising, board management, culture, and stakeholder alignment.

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

Create clear roadmap communication artifacts for internal and external stakeholders, including presentations, release notes, changelogs, and feature announcements.

Applies the ArchiMate enterprise architecture framework to structure analysis, break down complex problems, and align stakeholders with a common vocabulary.

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

Turns product ideas into structured specs for AI tools or stakeholder review, with quick feature specs and full project scopes.

Draft an Amazon-style press release to define customer value and align stakeholders before building a product or feature.

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.

A stakeholder asks to make search faster.

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

Create a six-frame storyboard that shows a user's journey from problem to solution, using a classic narrative arc to build empathy and align stakeholders.

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

Build an Opportunity Solution Tree from outcomes to opportunities, solutions, and tests. Use when a stakeholder request needs problem framing before you decide what to build.

Evaluate codebase against enterprise ICP for production readiness, compliance, and multi-stakeholder journey coverage

Turn research into a decision-ready brief tailored to a specific stakeholder and decision.

Answer any data question, scaling effort from a one-number lookup to a full stakeholder-ready analysis with a recommendation.

Guides the periodic DPIA review lifecycle including trigger identification for regulatory changes, new data categories, technology changes, and breach incidents. Covers version control, stakeholder sign-off procedures, and DPIA register management per Art. 35(11). Keywords: DPIA review, PIA update, review cadence, version control, Art. 35(11), periodic review, trigger events, stakeholder sign-off.

Runs focused experiments to validate feasibility of an idea, saving artifacts to .planning/spikes/ and supporting both idea and frontier modes.

Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.

Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.

Brainstorm an inspiring, achievable, and emotional product vision that motivates teams and aligns stakeholders.

Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.

Applies the Federal Enterprise Architecture Framework to design scalable, maintainable, and interoperable enterprise systems and solutions.

Create a practical onboarding plan for a new team member with outcomes, first-week structure, stakeholder introductions, learning path, and manager check-ins.

Choose a prioritization framework based on product stage, team context, and stakeholder needs.

Produce a decision-ready legal briefing — daily digest, topic research, or incident write-up — scoped to what a non-lawyer stakeholder needs to decide or act on.

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

Guide teams through MITRE's Problem Framing Canvas to clarify problem statements before jumping to solutions.

Creates a structured design brief covering project overview, problem statement, target audience, goals, scope, context, deliverables, and timeline.