product-skills

Bring engineering, design, research, marketing, and sales onto the same page and keep them there. Covers alignment levels, RACI clarity, and continuous maintenance. Use when teams have different understandings of what's being built, cross-team dependencies are causing problems, or alignment keeps breaking down.

Get buy-in and drive alignment when you have no direct power over the people you need to move. Covers stakeholder framing, pre-wiring decisions, and building credibility over time. Use when pushing for a direction without exec authority, navigating disagreements, or when a proposal keeps getting blocked.

Build a productive relationship with leadership by communicating effectively, managing expectations, and knowing when to push back. Use when navigating executive relationships, seeking alignment on direction, or when leadership requests conflict with team capacity.

Partner with design to create better products, not just prettier ones. Covers when to involve design, how to give useful feedback, and respecting the design process. Use when PM-design handoffs feel clunky, design feedback conversations are unproductive, or design is brought in too late.

Partner with engineering as a collaborator, not a ticket-writer. Covers communication norms, technical empathy, scope negotiation, and building mutual trust. Use when PM-engineering relationships feel transactional, technical decisions are made without product input, or scope conversations become adversarial.

Partner with marketing, sales, and customer success to bring products to market effectively. Covers launch coordination, sales enablement, and feedback loops. Use when launches aren't driving adoption, sales can't articulate the value prop, or customer feedback isn't reaching the product team.

Ship updates people actually want to read. Structures release notes, changelog entries, and product updates with what-changed, why-it-matters, and what-to-do-next. Use when writing changelogs or release announcements.

Write headlines, CTAs, and value props that move people to act. Audits existing copy for weak verbs, vague claims, and missing specificity. Use when writing landing pages, hero sections, email subject lines, or any surface where words need to do real work.

The small words that shape big experiences. Button labels, tooltips, confirmations, placeholders, and the 3-word strings that determine whether a product feels polished or half-finished. Use during any copy audit pass.

Tell the product story in a way that sticks. Structures origin stories, problem narratives, and transformation arcs. Use when building about pages, launch announcements, or pitch decks.

Create structured competitive battlecards for sales, product, and strategy conversations. Covers positioning, objection handling, competitive landmines, and knowing when to walk away. Use when preparing for competitive deals, losing to a specific competitor, or entering a market with established players.

Identify and prioritize feature gaps between your product and competitors. Not just what's missing but which gaps matter, which don't, and which you should intentionally keep. Use when losing deals to missing features, planning roadmap with competitive context, or evaluating build-buy-partner decisions.

Analyze the real cost of switching between products — financial, technical, operational, political, and emotional. Use when trying to win customers from competitors, worried about churn to alternatives, designing migration tools, or setting pricing relative to switching friction.

Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.

Reduce abandonment in every form, signup, and checkout flow. Multi-step logic, field reduction, inline validation, and completion micro-copy. Use when building signup flows, checkout pages, or any multi-field input.

Information architecture that guides visitors from curiosity to commitment. Enforces section order, content hierarchy, and scroll-depth logic. Use when building landing pages, product pages, or any conversion surface.

Present pricing in ways that reduce friction and increase clarity. Handles tier naming, feature comparison, anchor pricing, and plan selection psychology. Use when designing pricing pages, plan selectors, or upgrade prompts.

Build credibility through evidence, not claims. Patterns for social proof, testimonials, logo walls, case studies, and security badges. Use when conversion is low despite good traffic or when the product is new and unknown.

Turn raw customer feedback from multiple sources into clear product insights and priorities. Covers feedback collection, pattern recognition, and separating signal from noise. Use when feedback feels overwhelming, contradictory, or when the team can't agree on what users actually want.

Define user problems with enough clarity and specificity that the team can evaluate solutions against them. Covers problem framing, user evidence, and the gap between stated and real problems. Use when the team can't agree on what problem they're solving, solutions aren't landing, or feature requests are mistaken for problems.

Turn user research into product decisions, not just reports. Covers when to research, what methods to use, and how to act on findings. Use when product direction feels disconnected from users, research exists but isn't informing decisions, or you're building on assumptions.

Communicate product decisions so teams understand not just what was decided but why. Covers framing, transparency about trade-offs, and handling disagreement gracefully. Use when decisions aren't sticking, teams are relitigating past calls, or when stakeholders feel left out.

Use data to inform product decisions without becoming a slave to metrics. Covers when data helps, when it misleads, and how to combine quantitative and qualitative signals. Use when metrics tell confusing stories, when the team over-indexes on data, or when decisions lack any data backing.

Make product decisions with structure and speed, even with imperfect information. Covers decision types, reversibility, and knowing how much analysis is enough. Use when decisions are stalling, when the team is stuck in analysis paralysis, or when decisions keep getting revisited.

Plan and execute product launches that actually drive adoption, not just announcements. Covers launch tiers, cross-functional coordination, rollout strategy, and post-launch monitoring. Use when preparing a feature or product launch, coordinating across teams, or when past launches haven't moved the needle.

Identify, assess, and mitigate product risks before they become fires. Covers risk categorization, mitigation strategies, and communication frameworks. Use when planning complex launches, managing dependencies, or when too many things could go wrong.

Drive predictable delivery without micromanaging the engineering team. Covers sprint planning, blocker removal, scope negotiation, and knowing when to cut vs. push. Use when sprints consistently miss commitments, scope keeps creeping, or delivery feels chaotic.

Turn dead ends into moments that build trust and guide action. Covers zero-data screens, error recovery, loading states, and retention micro-copy. Use when handling empty dashboards, failed searches, or moments where users hit a wall.

When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.

Communicate without annoying. Patterns for in-app alerts, email triggers, push notification copy, and frequency capping. Use when designing notification systems or any touchpoint that competes for attention.

Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.

Organize preferences and controls so people find what they need without getting lost. Information grouping, search, and defaults. Use when building settings pages, preference panels, or admin surfaces.

Everything that needs to be true before real people see this. Pre-launch audit covering copy, meta tags, error states, mobile, performance, analytics, and the things everyone forgets. Use before any launch or public release.

Build sharing into the product without it feeling forced. Viral loops, invite flows, referral incentives, and the moments where asking users to share feels natural. Use when building invite systems or when organic growth needs structure.

Design for the second visit, not just the first. Habit loops, re-engagement triggers, and value reinforcement without dark patterns. Use when retention is low, when building engagement features, or when people stop coming back.

Measure what matters, ignore what doesn't. Defines core metrics by product type, dashboards that surface real signals, and analytics events that tell the full story. Use when setting up analytics, building dashboards, or defining KPIs.

Understand how the business works so product decisions align with commercial reality. Covers revenue models, unit economics, and connecting product decisions to business outcomes. Use when product and business priorities feel disconnected, when you don't understand why leadership says no, or when building features that don't move the business forward.

Design and maintain a metrics framework that tells you whether your product is healthy. Covers metric selection, hierarchy, and the difference between tracking and understanding. Use when metrics feel arbitrary, the team tracks too many things, or nobody agrees on what success looks like.

Focus product work on outcomes rather than output. Covers defining success, connecting features to results, and knowing the difference between shipping and impact. Use when the team ships lots of features but metrics don't move, when success is defined by delivery dates, or when nobody can say what a feature accomplished.

Keep the backlog useful instead of letting it become a graveyard of ideas nobody will build. Covers backlog hygiene, grooming practices, and knowing when to kill items. Use when the backlog has hundreds of stale items, sprint planning takes forever, or the team doesn't trust the backlog.