Results for “stakeholder-analysis”

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

Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.

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

Create stakeholder alignment artifacts including responsibility matrices, decision frameworks, and communication plans.

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

Builds a Power × Interest stakeholder map and generates a communication plan per quadrant. Use when managing a complex launch, aligning cross-functional teams, or preparing stakeholder engagement strategy. Triggers on: stakeholder management, stakeholder map, stakeholder alignment, communication plan, power interest grid, cross-functional alignment, executive alignment, managing up.

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.

Analyze user engagement and retention patterns by cohort to identify trends in user behavior, feature adoption, and long-term engagement.

Research companies, industries, or competitor sets using web search and seven analytical lenses to produce structured intelligence for downstream product management tasks.

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.

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

Transforms scattered competitor data into a decision-ready product strategy report with positioning maps, feature matrices, pricing analysis, and opportunity windows.

Analyze political, economic, social, technological, environmental, and legal forces to identify external opportunities and threats for strategic planning.

Evaluate macro-environmental factors across Political, Economic, Social, Technological, Legal, and Environmental dimensions for strategic planning and market entry assessment.

Convert a stakeholder summary markdown file into a single self-contained HTML executive report — bottom line and decision asks up front, supporting detail later — styled with a Test Double-derived palette and self-contained mermaid diagrams. Use when the user wants to turn a stakeholder summary, executive summary, or business summary into an HTML report, generate an HTML version of a summary doc, or produce a shareable HTML file from a summary markdown. Produces an HTML sibling file only; does not publish anything.

Conduct a structured SWOT analysis for a product, identifying strengths, weaknesses, opportunities, and threats with actionable strategic recommendations.

Analyzes competitor products by synthesizing data from pricing pages, app store reviews, job postings, SEO signals, and social media into structured competitive intelligence. Produces feature comparison matrices, SWOT analyses, positioning maps, UX audits, pricing breakdowns, action plans, and presentations.

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.

Decode an incoming message into a structured breakdown that separates the literal ask from the job-to-be-done, before replying to a loaded Slack ping, email, mandate, or escalation.

Performs a gap analysis between two artifacts (a current state and a desired state) and produces a plain-language, stakeholder-readable report indexed by stable gap IDs. Use when the user wants to compare, evaluate, audit, or reconcile one artifact against another. Does not investigate runtime bugs — use investigate. Does not assess module-level architecture — use architectural-analysis. Does not research open-ended options with no second artifact to compare against — use research.

Senior Project Manager for enterprise software, SaaS, and digital transformation projects. Specializes in portfolio management, quantitative risk analysis, resource optimization, stakeholder alignment, and executive reporting. Uses advanced methodologies including EMV analysis, Monte Carlo simulation, WSJF prioritization, and multi-dimensional health scoring. Use when a user needs help with project plans, project status reports, risk assessments, resource allocation, project roadmaps, milestone tracking, team capacity planning, portfolio health reviews, program management, or executive-level project reporting — especially for enterprise-scale initiatives with multiple workstreams, complex dependencies, or multi-million dollar budgets.

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate in a week", "rapid prototype", "test with users", "de-risk before building", "GV sprint", "prototype testing", or "design workshop". Also trigger when a team needs to make a critical product decision quickly, resolve stakeholder disagreements, or test risky ideas before investing in development. Covers mapping, sketching, deciding, prototyping, and testing. For ongoing experimentation, see lean-startup. For customer job analysis, see jobs-to-be-done.