Sidsaladi9
- 53 skills
- 0 followers
- 6 hours ago last updated
- ▌ Icp · sidsaladi9Defines the Ideal Customer Profile — the firmographic and behavioral traits of accounts that get the most value and convert and retain best, plus qualifying signals, anti-signals, and where to find them. Use when you say "who's our ICP", "who should sales target", "which accounts retain best", "we're closing the wrong customers", or "tighten our targeting" — for B2B accounts, not individual buyer personas.
- ▌ Okrs · sidsaladi9Helps draft and pressure-test OKRs with outcome-based objectives and measurable key results. Use when someone says "draft our OKRs", "set quarterly goals", "are these good key results", "turn this goal into OKRs", "help me write objectives and key results", or "pressure-test our OKRs". Catches the classic failure modes — output KRs, missing baselines, and sandbagged targets.
- ▌ Retro · sidsaladi9Facilitates a structured team retrospective using the well/wrong/confusing framework — gathering observations, tracing them to root causes instead of symptoms, and committing to 2-3 specific improvements with named owners and due dates. Use when you say "let's run a retro," "what went well and what didn't," "sprint retrospective," "post-mortem the launch," or "we keep making the same mistakes."
- ▌ Pricing · sidsaladi9Designs pricing and packaging using value-metric selection, Van Westendorp willingness-to-pay analysis, and good-better-best tiering. Picks the metric you charge on, chooses the model (per-seat, usage, tiered), sets three tiers with anchoring, and stress-tests for money left on the table. Use when you say "how should we price this," "what should our tiers be," "are we underpriced," "per-seat vs usage," or "package our plans."
- ▌ Roadmap · sidsaladi9Use when the user wants to update the roadmap, build a Now/Next/Later view, reprioritize after new information, decide what moves to make room for a new initiative, shift timelines after a dependency slip, or figure out where a new initiative fits. Forces explicit trade-offs and keeps the roadmap anchored to outcomes, not a feature wishlist.
- ▌ Personas · sidsaladi9Create evidence-based user personas — or honest proto-personas when data is thin. Use when someone says "create a persona", "build user personas", "proto-persona for X", "who are our users", or "turn this research into personas". Focuses on goals, jobs-to-be-done, pains, and real behavior, then shows how to use personas to make product decisions.
- ▌ Red Team · sidsaladi9Adversarially attacks a PRD, strategy, or plan to find its holes before reality does — naming load-bearing assumptions, weakest links, and what a skeptical exec or competitor would exploit. Steelmans the plan first, then attacks it hard. Use when you're about to ship a doc to leadership, "this feels too clean," "what am I missing," "poke holes in this," "what would kill this," or prepping for a tough review.
- ▌ Win Loss · sidsaladi9Runs a win/loss analysis across decided deals to find why you actually win and lose, separating stated reasons from real causes. Use when a PM or PMM says "why are we losing deals", "run a win-loss", "analyze these lost deals", "what's killing our close rate", "sales says it's price", or when the same objection keeps surfacing and nobody has checked it against the data.
- ▌ Visualize · sidsaladi9Turns a PM artifact into a clean, self-contained HTML visual you can open and screenshot — a RICE/Kano prioritization matrix, a Now/Next/Later roadmap board, an OKR tree, a metrics scorecard, or a journey-map swimlane. Use when you say "make this visual", "turn this into a board / matrix / chart", "render the roadmap", "show me a scorecard", "visualize this", "I want to screenshot this", or after any skill produces a structured artifact and a picture would land harder than text.
- ▌ Battlecard · sidsaladi9Produces a one-page sales battlecard for a specific competitor — how to position against them, the traps to set, the objections you'll hear, and where to concede. Use when a PM or PMM says "make a battlecard", "how do we sell against X", "sales keeps losing to X", "what do we say when they mention X", or when reps are improvising competitive answers and each one says something different.
- ▌ North Star · sidsaladi9Defines a North Star Metric that captures delivered customer value and decomposes it into 3-4 movable input metrics. Use when you need to "pick a North Star metric," "we're optimizing for revenue and it's hurting us," "build an input metric tree," "what should the team actually move," "align the roadmap to one number," or "our metric is a vanity metric."
- ▌ Pre Mortem · sidsaladi9Runs a Klein pre-mortem on a project — assumes it already failed, brainstorms why, scores each failure mode by likelihood × impact, and attaches a mitigation plus an early-warning signal to the top risks. Use when launching a feature, kicking off a quarter, or before a big bet and you want to ask "imagine this shipped and flopped — what killed it?" or "where is this most likely to go wrong?"
- ▌ Prioritize · sidsaladi9Score and rank features, ideas, or bets and produce a defensible ranked list plus a clear recommendation. Use when the user wants to prioritize these features, decide what to build first, RICE score this backlog, rank these ideas, run a value vs effort 2x2, or pick the right prioritization framework. Picks the framework, defines the scale, scores consistently, and surfaces the close calls.
- ▌ Write Spec · sidsaladi9Turns a vague feature idea or problem statement into a structured, review-ready feature spec or PRD with goals, non-goals, success metrics, and testable acceptance criteria. Use when a PM says "write a PRD", "spec this feature", "turn this idea into a spec", "scope this", "define success metrics", "write acceptance criteria", or needs to break a big ask into a phased spec.
- ▌ House Style · sidsaladi9Capture the company's house style (voice, formatting, terminology, templates, branding) so every other skill generates in your format. Use when the user says "match our format", "use our style", "here's an example doc — write like this", "set up our house style", "make outputs look like ours", or pastes a sample doc / brand guide to learn from.
- ▌ Journey Map · sidsaladi9Build a customer journey map across stages — actions, thoughts, emotions, touchpoints, pain points, and the single biggest opportunity per stage — grounded in evidence with assumptions flagged. Use when someone says "map the customer journey", "build a journey map", "where do users drop off", "what's the experience from awareness to renewal", or "turn this research into a journey".
- ▌ Launch Plan · sidsaladi9Builds a go-to-market launch plan for a feature or product, scaled to a launch tier. Use when someone asks to "plan the launch", build a "go-to-market plan" or "GTM for the new feature", needs a "launch checklist for X", or asks "how should we launch this". Produces audience, messaging, channels, a pre/launch/post timeline with owners, assets, success metrics, and a launch-day runbook.
- ▌ Positioning · sidsaladi9Use when the user wants to position our product, write our value proposition, draft a positioning statement, decide how do we frame this vs competitors, or define messaging pillars. Crafts a positioning statement, value proposition, and proof-backed messaging using April Dunford's method and the value proposition canvas.
- ▌ SQL Queries · sidsaladi9Translates a product question into clean, correct SQL against a described schema and explains it line by line. Covers the core product-analytics patterns — funnels, retention and cohorts, DAU/MAU stickiness, and event counts — plus how to sanity-check the output. Use when you say "write me a query for", "how many users did X then Y", "what's our 7-day retention", "DAU/MAU by week", "build a funnel from signup to activation", or "is this number right?"
- ▌ Growth Loops · sidsaladi9Designs compounding growth loops instead of one-shot funnels, using the Reforge model — classify the loop (viral, content, sales, paid), map inputs → action → output → reinvestment, and locate the compounding step and where it leaks. Use when you say "our funnel is leaking," "growth has plateaued," "how do we make acquisition compound," "what's our viral loop," or "model our content/paid loop."
- ▌ Gtm Strategy · sidsaladi9Chooses the go-to-market motion and channel mix for a product or segment, and checks the unit economics that make it survivable. Use when a PM or founder says "what's our GTM", "should we go sales-led or product-led", "how do we sell this", "which channel", "our CAC doesn't work", or when a launch plan exists but nobody has decided how the product actually reaches buyers at scale.
- ▌ Segmentation · sidsaladi9Segment a market or user base by needs and behavior — not just demographics — then size, score, and pick a beachhead segment with a defensible rationale. Use when someone says "segment this market", "who should we target first", "find our beachhead", "break our users into segments", "which customers do we prioritize", or "TAM/SAM by segment".
- ▌ User Stories · sidsaladi9Breaks an epic, spec, or feature into well-formed user stories with Given/When/Then acceptance criteria, applies INVEST, and splits stories that are too big. Use when a PM says "break this epic into stories", "write user stories", needs "acceptance criteria for X", wants to "split this story", or asks to "turn this PRD into a backlog".
- ▌ Business Case · sidsaladi9Builds an executive business case / ROI model that justifies funding one feature or investment — cost of inaction, options (incl. do-nothing), an expected-value benefit model (reach × adoption × value-per-unit), build+run cost, payback and ROI, sensitivity, and a fund/kill ask. Use when you say "build a business case", "is this worth building", "what's the ROI", "justify this investment", "cost-benefit", "make the case to fund this", or "should we build X or not". Justifies ONE bet against its own cost — it does not rank a backlog (that's prioritize), set a price (that's pricing), or choose direction (that's product-strategy).
- ▌ Market Sizing · sidsaladi9Sizes a market with both top-down and bottom-up methods using the TAM/SAM/SOM framework, states every assumption, reconciles the two estimates, and sanity-checks the result. Use when you need to size an opportunity, fill the market section of a PRD or business case, justify a bet to leadership, or pressure-test a number someone handed you ("how big is this really?", "what's the TAM?", "is this market worth entering?").
- ▌ Meeting Notes · sidsaladi9Turns raw, messy meeting notes or a transcript into a crisp, shareable summary. Use when someone says "summarize these meeting notes", "turn this transcript into action items", "what did we decide", "clean up my notes", or "send a recap". Works for any meeting type — standup, planning, review, 1:1, or stakeholder sync — from pasted notes or a connected transcript tool.
- ▌ Press Release · sidsaladi9Writes the Amazon-style working-backwards press release and FAQ for a product or feature before it's built. Use when a PM says "write the press release", "PR/FAQ", "working backwards doc", "let's write the launch announcement first", "what would we say when this ships", or wants to pressure-test whether an idea is worth building by trying to make it sound compelling to a customer.
- ▌ Release Notes · sidsaladi9Turns a list of shipped changes into audience-tiered release notes — a benefit-led user-facing changelog, a what/why/impact internal log, and a short social announcement cut. Use when you say "write release notes," "draft the changelog," "we just shipped X, announce it," "turn these tickets into release notes," or "summarize this release for customers and the team."
- ▌ Skill Creator · sidsaladi9Create a new skill for this Product Manager OS — in the same format and quality bar as the built-in skills. Use when the user says "make a skill for X", "add a skill", "I keep doing X manually, turn it into a skill", or wants to extend the OS with their own framework or workflow.
- ▌ Tracking Plan · sidsaladi9Designs the event tracking plan for a feature or product area — the event taxonomy, naming convention, properties, and QA checklist that make a metric answerable later. Use when a PM says "what should we instrument", "write a tracking plan", "what events do we need", "we can't answer that from the data", "define the analytics for this feature", or is about to ship something with no way to tell whether it worked.
- ▌ Business Model · sidsaladi9Fills a complete Lean Canvas (or Business Model Canvas) across every block — problem, customer segments, unique value proposition, solution, channels, revenue, cost, key metrics, and unfair advantage — then flags the single riskiest block to validate first. Use when you say "map our business model," "fill a lean canvas," "what's our UVP," "how do we make money," "where's the riskiest assumption," or "pressure-test this idea before we build."
- ▌ Incident Comms · sidsaladi9Drafts the communications a PM owns when something is breaking or just broke — an internal escalation note, customer-facing status updates on the right cadence, a resolution/all-clear, and a short blameless postmortem for leadership. Use when you say "we have an incident", "the launch broke", "draft a customer notice", "status page update", "outage comms", "customers are hitting errors", "we're down", or "write the postmortem". Reactive comms only — not pre-mortem (failure before launch), release-notes (what shipped), or stakeholder-update (routine status).
- ▌ Metrics Review · sidsaladi9Reviews product metrics with trend analysis and turns raw numbers into a scorecard with actions. Use when the user asks to "review our metrics", "run a weekly/monthly/quarterly metrics review", "why did signups drop", "why did this spike", "build a metrics scorecard", or "compare against target". Works with pasted numbers or a CSV; pulls from Amplitude/Mixpanel/GA if connected.
- ▌ Product Vision · sidsaladi9Writes a product vision — the 3-5 year picture of the world your product is trying to create, and what has to become true along the way. Use when a PM or founder says "write the product vision", "what's our vision", "where is this going in three years", "the team can't see the bigger picture", or when every roadmap conversation collapses into next quarter because nothing above it exists.
- ▌ Test Scenarios · sidsaladi9Derives QA test scenarios and acceptance test cases from a spec or user story, covering happy paths, edge cases, error states, data variations, and ML quality-bar/eval cases. Use when you need to "write test cases for this story," "figure out what QA should check," "turn this spec into acceptance criteria," "find the edge cases we're missing," or "design eval cases for this AI feature."
- ▌ Assumption Test · sidsaladi9Surfaces the hidden assumptions an idea depends on, sorts them by risk (likelihood-it's-false × damage-if-false) across desirability, viability, feasibility, and usability, then designs the cheapest test for the riskiest ones. Use when you say "what has to be true for this to work," "what's the riskiest assumption," "should we validate before building," "how do we de-risk this bet," or "this idea feels shaky and I can't say why."
- ▌ Cohort Analysis · sidsaladi9Builds and interprets a cohort retention table — defines the cohort and return event, reads where and when users drop off, compares cohorts over time, and converts the retention curve into a hypothesis and an action. Use when you say "build a cohort table," "why is retention dropping," "are newer signups sticking better," "where do users churn," or "what happened to the March cohort."
- ▌ Market Analysis · sidsaladi9Runs a structured environmental scan using SWOT, PESTEL, Porter's Five Forces, and Ansoff growth options, then synthesizes them into 2-3 strategic implications. Use when you need to assess a market before entering it, pressure-test a strategy, prep a board or planning deck, answer "what are the forces shaping this market" or "where should we grow," or turn scattered market notes into a decision.
- ▌ Spec Vs Shipped · sidsaladi9Audits what actually shipped against what the spec promised, and turns the gap into a decision list. Use when a PM says "did we build what we specced", "what's actually in this release", "the spec says X but the product does Y", "check this against the PRD", "what got dropped", or before writing release notes, a launch announcement, or a retro on a delivery that drifted.
- ▌ Sprint Planning · sidsaladi9Plan a sprint — scope work, estimate realistic capacity, set a goal, and draft a copy-pasteable plan. Use when you say "plan our sprint", "size the backlog", "what fits in this sprint", need a "sprint goal", are deciding "P0 vs stretch", or need to "handle carryover" from last sprint. Works from a pasted backlog or pulls from Linear/Jira if connected.
- ▌ Stakeholder Map · sidsaladi9Maps stakeholders onto an influence/interest grid, captures each one's stance, motivations, and decision power, and derives a per-person engagement plan with a RACI overlay. Use when you say "who do I need to get on board," "map my stakeholders," "build a power/interest grid," "figure out who's blocking this," "who decides vs. who's just informed," or "I keep getting surprised by the same exec."
- ▌ Triage Requests · sidsaladi9Sorts a pile of inbound feature requests from sales, support, and users into themes, quantifies demand behind each, and recommends build / watch / decline with a templated reply for every requester. Use when you say "I have 40 requests to go through," "what are people actually asking for," "triage this feedback dump," "theme these tickets," or "should we build this or say no?"
- ▌ Product Strategy · sidsaladi9Use when a PM or knowledge worker needs to write a product strategy or product vision on a single page. Triggers on "write our product strategy", "product vision", "where to play how to win", "strategy on a page", "what's our strategy", or turning a pile of goals into a coherent, trade-off-driven strategy grounded in Rumelt/Lafley fundamentals.
- ▌ Competitive Brief · sidsaladi9Use when you need a competitive analysis brief or competitor teardown for one or more rivals or a feature area. Triggers include "competitive analysis", "build a battlecard for [competitor]", "how do we compare to X", "where should we differentiate", "competitor teardown", and prepping board or sales materials on the competitive landscape.
- ▌ Feedback Analysis · sidsaladi9Turns a large volume of customer feedback (support tickets, app-store reviews, NPS verbatims, survey free-text) into ranked themes with sentiment, volume, and trend-over-time. Use when you have hundreds or thousands of comments and need to know "what are people complaining about," "what changed since last quarter," or "which theme should we fix first." The quant/at-scale complement to interview-depth synthesis.
- ▌ Value Proposition · sidsaladi9Maps what customers actually want against what your product relieves and creates, using the Value Proposition Canvas, and produces the fit assessment plus the statements that come out of it. Use when a PM says "what's our value prop", "map the value proposition", "why do customers care", "our messaging isn't landing", or when the product does many things and nobody can say which one is the reason people buy.
- ▌ Customer Interview · sidsaladi9Plans and scripts customer discovery interviews using The Mom Test. Use when a user wants to plan a customer interview, write discovery interview questions, build an interview script, generate Mom Test questions, or talk to users about a problem. Produces a non-leading question script grounded in past behavior, plus a note-taking template.
- ▌ Product Brainstorm · sidsaladi9Use when a PM or knowledge worker wants to think out loud with a sharp sparring partner. Triggers on "brainstorm with me", "be my thinking partner", "stress-test this idea", "explore this problem space", "help me think through", or "challenge my assumptions". Diverges to generate breadth, then pressure-tests and helps converge on a next experiment. (For attacking a finished doc before it ships, use `red-team`; for surfacing an idea's riskiest assumption, use `assumption-test`.)
- ▌ Stakeholder Update · sidsaladi9Generate a stakeholder update tailored to audience and cadence. Use when the user wants to "write a stakeholder update", "exec update", "weekly status", "monthly status", "announce the launch", "escalate this blocker", or "make a leadership-friendly version" — and when the same progress needs to be re-cut for execs, engineers, or customers.
- ▌ Experiment Analysis · sidsaladi9Designs and reads A/B tests end to end — a sharp hypothesis, a primary metric plus guardrails, sample size and power, and a frequentist read (significance, confidence interval, practical effect) leading to a clear ship/kill call. Use when you say "design this A/B test," "is this result significant," "how many users do I need," "can we ship this," or "did the experiment win?"
- ▌ Synthesize Research · sidsaladi9Synthesize user research from interviews, surveys, and feedback into structured, evidence-backed insights. Use when you have a pile of notes to make sense of and say things like "synthesize these interviews", "find themes in this feedback", "what are users telling us", "turn this research into insights", or "analyze these support tickets". Extracts themes ranked by frequency and impact, then translates them into roadmap recommendations.
- ▌ Activation Flow Design · sidsaladi9Designs the first-run path that carries a brand-new user from signup to their aha-moment fast — defines the activation event, maps the current first-run, diagnoses the drop-off, and re-sequences the steps with triggers, nudges, and empty states. Use when a PM says "design our onboarding", "improve activation", "get users to the aha moment", "redesign first-run", "new-user flow", "why aren't new users sticking", "activation flow", or "shorten time-to-value". NOT for measuring activation/retention (cohort-analysis, metrics-review), mapping the whole journey (journey-map), or modeling whole-product loops (growth-loops).
- ▌ Opportunity Solution Tree · sidsaladi9Builds a Teresa Torres-style opportunity solution tree that maps customer opportunities to a desired outcome, then to solutions and experiments. Use when the user asks to "build an opportunity solution tree", "map opportunities to our outcome", "OST for X", "structure our discovery", or "what should we focus discovery on". Keeps the team from jumping straight to solutions.