Browse by category—each method summarizes the idea, when it applies, and links to skills your team can run end to end. Add what you use in Hamster when you are ready.
Agile is an iterative approach to building products where teams deliver small, functional increments in short cycles called sprints, typically one to four weeks long. Instead of planning everything upfront, teams gather feedback after each increment and adjust their priorities, designs, and direction accordingly. The goal is to reduce risk and waste by learning continuously, responding to change rather than following a rigid plan.
Pricing an AI product requires working backward from unit economics — specifically the cost of each inference call or token generation — then designing tiers that align customer value with your variable costs. The best AI product pricing models combine a predictable base (seat or subscription) with a usage-based component that scales revenue as customers consume more AI capacity. This protects gross margins while letting customers start small and grow.
The Ansoff Matrix is a 2x2 strategic planning framework created by H. Igor Ansoff that maps growth strategies along two dimensions: products (existing vs. new) and markets (existing vs. new). It produces four quadrants — market penetration, market development, product development, and diversification — each representing increasing levels of risk. Teams use it to systematically evaluate and prioritize growth opportunities before committing resources.
The double diamond is a design process model created by the British Design Council in 2005. It visualizes the design process as two connected diamonds representing four phases: Discover, Define, Develop, and Deliver. Each diamond pairs divergent thinking (exploring broadly) with convergent thinking (narrowing focus), guiding teams from problem exploration through to tested solutions. The first diamond ensures you solve the right problem; the second ensures you build the right solution.
The four fits framework is a growth model created by Brian Balfour that aligns four interconnected dimensions: Market-Product Fit, Product-Channel Fit, Channel-Business Model Fit, and Business Model-Market Fit. Rather than treating product-market fit in isolation, it maps all four fits as an ecosystem where each fit constrains and enables the others, creating a foundation for sustainable, scalable growth to $100M+ revenue.
The GIST Planning Framework is a product planning method created by Itamar Gilad that organizes work into four layers: Goals (measurable outcomes), Ideas (hypothetical solutions), Step-projects (small validation experiments), and Tasks (daily work items). A product manager uses GIST to replace speculative roadmaps with evidence-driven planning, testing ideas cheaply before committing full resources.
A product roadmap is a strategic plan that communicates a product's direction over time. The GO Product Roadmap, created by Roman Pichler, is a goal-oriented variant that organizes roadmaps around desired outcomes (like user acquisition or retention) rather than feature lists. Each goal is paired with specific features, metrics, and a timeframe, keeping teams focused on value creation instead of output debates.
The HEART Framework is a UX measurement methodology developed at Google by Kerry Rodden. It organizes user experience metrics into five categories—Happiness, Engagement, Adoption, Retention, and Task Success. A product manager uses a Goals-Signals-Metrics process within each category to translate broad product objectives into quantifiable, actionable metrics that drive data-informed decisions across the product lifecycle.
Impact Mapping is a collaborative strategic planning technique created by Gojko Adzic that helps a product manager visualize connections between business goals and deliverables. It uses a four-level mind map—Goal, Actors, Impacts, and Deliverables—to ensure every feature or initiative traces back to measurable business value. Teams use it to prioritize work, reduce waste, and align stakeholders around outcomes rather than outputs.
Jobs-to-be-Done (JTBD) is a framework that reframes product decisions around the underlying task a customer is trying to accomplish, not the product itself. A product manager uses JTBD to uncover the functional job, map each step of that job, write measurable desired outcome statements, and identify where current solutions fall short. This reveals precisely where new features or products will create the most value.
Kanban is a visual workflow management method where work items move across a board through columns representing stages like 'to do,' 'in progress,' and 'done.' Teams pull new work only when capacity opens up, governed by work-in-progress (WIP) limits. This pull-based system surfaces bottlenecks, reduces multitasking, and promotes continuous delivery without requiring fixed-length iterations or sprints.
The lean startup is a product development methodology created by Eric Ries that replaces long planning cycles with rapid experimentation. Teams build a minimum viable product, measure how real customers respond, and learn whether to pivot or persevere. The core loop, Build-Measure-Learn, compresses the feedback cycle from months to days, reducing waste by validating assumptions before committing resources to full-scale development.
The MoSCoW method is a prioritization technique that categorizes requirements into four groups: Must-have (critical for launch), Should-have (important but not vital), Could-have (desirable if resources allow), and Won't-have (explicitly deferred). Teams use it to define MVP scope, align stakeholders on priorities, and build focused product roadmaps. It was originally developed by Dai Clegg within the DSDM framework.
The North Star Framework is a product management model where teams align around a single North Star Metric (NSM) that captures the core value customers receive from a product. A product manager identifies this metric, maps the input metrics that influence it, and uses both to guide prioritization, roadmap decisions, and cross-functional alignment. Developed by Sean Ellis, the framework prevents teams from optimizing vanity metrics and instead focuses effort on sustainable, value-driven growth.
The North Star Metric is a single, company-wide metric that captures the core value customers receive from a product. A product manager uses it to align cross-functional teams, prioritize the product roadmap, and connect daily work to sustainable business growth. It is supported by input metrics that teams directly influence, creating focus and accountability across the organization.
The Now Next Later framework is a product roadmap format that organizes work into three priority horizons instead of fixed dates. "Now" holds committed, high-certainty work. "Next" contains validated problems awaiting capacity. "Later" captures strategic ideas still being explored. Created by Janna Bastow in 2012, it replaces timeline-based roadmaps with a sequence-driven approach that communicates intent without false precision.
An OKR (Objective and Key Result) is a goal-setting framework where teams define a qualitative, inspirational Objective — what they want to achieve — paired with 2–5 quantitative Key Results that measure whether they got there. Popularized by Andy Grove at Intel and later adopted by Google, OKRs are typically set quarterly, shared transparently, and scored on a 0.0–1.0 scale to drive focus, alignment, and ambitious outcomes.
The Opportunity Solution Tree (OST) is a visual framework created by Teresa Torres that helps a product manager map the path from a desired business outcome down through customer opportunities, potential solutions, and validating experiments. It ensures product teams stay outcome-focused, explore multiple solutions before committing, and use evidence from continuous discovery to make better decisions about what to build next.
Outcome-Driven Roadmapping (ODR) is a product planning approach where teams organize their roadmap around measurable business outcomes rather than feature deliverables. A product manager defines the target result first, such as reducing churn by 15% or increasing activation by 20%, then identifies which initiatives might move that metric. Work is prioritized by expected impact on outcomes, and progress is tracked by whether the metric moved, not just whether the feature shipped.
The RICE framework scores initiatives by Reach (users affected), Impact (how much it moves a metric), Confidence (certainty of estimates), and Effort (work required). Score = (Reach × Impact × Confidence) ÷ Effort. Higher scores mean higher leverage on the roadmap.
Scrum is an agile framework that organizes product development into fixed-length iterations called sprints, typically lasting one to four weeks. Cross-functional teams work through defined roles (Product Owner, Scrum Master, Developers), ceremonies (sprint planning, daily stand-ups, sprint reviews, retrospectives), and artifacts (product backlog, sprint backlog, increment) to deliver working software incrementally while continuously inspecting and adapting their process.
Shape Up is a product development methodology created by Basecamp where teams commit to fixed time windows (typically six weeks) and deliberately vary scope to fit. A product manager shapes the problem and solution at the right level of abstraction, bets on which projects deserve cycles, then gives a small team full autonomy to build and ship. Cool-down periods between cycles prevent burnout and create space for fixes, exploration, and preparation.
User story mapping is a visual planning technique created by Jeff Patton that arranges user stories in a two-dimensional grid. The horizontal axis shows user activities in chronological order across the journey, forming a narrative backbone. The vertical axis organizes stories by priority beneath each activity. This layout lets teams see the whole product experience at once, identify gaps, and slice coherent releases that deliver end-to-end value rather than disconnected features.
The technician manager entrepreneur framework, introduced by Michael E. Gerber in The E-Myth Revisited, identifies three personalities inside every business owner: the Technician who does the work, the Manager who creates order and systems, and the Entrepreneur who drives vision and growth. Sustainable businesses require all three in deliberate balance, not dominated by the Technician's impulse to just keep doing the craft.
V2MOM is a strategic planning framework created by Marc Benioff at Salesforce. It stands for Vision, Values, Methods, Obstacles, and Measures. Teams write a one-page document answering five questions: Where are we going? What matters most? How will we get there? What stands in the way? How will we know we succeeded? V2MOMs cascade from the CEO down to every individual, creating full organizational alignment.
The waterfall methodology is a linear, sequential project management approach where work flows through distinct phases — requirements, design, implementation, testing, deployment, and maintenance — each completing fully before the next begins. Originally described by Winston Royce in 1970, waterfall works best for projects with stable, well-understood requirements where predictability and thorough documentation are priorities over iterative flexibility.
Working Backwards is a product development framework pioneered at Amazon where a product manager begins by writing a mock press release describing the finished product from the customer's perspective. The team then works backwards from that ideal experience to define requirements, surface risks, and build only what's needed. It replaces speculative roadmaps with a forcing function for customer-centric clarity before any code is written.
The Product Team Competencies Framework, created by Neal Cabage, organizes core product manager skills along two axes: strategic versus tactical and internal versus external. By plotting competencies on this 2D grid, teams can objectively assess individual strengths, identify collective gaps, calibrate role expectations from associate to senior PM, and build targeted development plans that connect daily work to career growth.
The Spotify Model is an organizational framework that structures engineering teams into small, autonomous squads, each owning a piece of the product. Squads are grouped into tribes for coordination. Chapters connect people who share the same discipline across squads, while guilds create voluntary communities of interest across the entire company. The model prioritizes team autonomy and loose coupling over standardized processes, aiming to preserve startup speed as an organization scales.
Claude's Constitution is Anthropic's alignment document defining how Claude should reason, behave, and make decisions. Rather than enforcing rigid rules, it cultivates contextual judgment grounded in core values like honesty, helpfulness, and harm avoidance. For SEO practitioners, understanding this constitution unlocks more reliable AI outputs, because prompts that align with Claude's values consistently produce higher-quality, more trustworthy content and analysis.
Constitutional AI is an alignment method developed by Anthropic that trains Claude to be helpful, harmless, and honest by following a predefined constitution of ethical principles. Instead of relying on extensive human labeling, the model critiques and revises its own outputs, then undergoes reinforcement learning from AI feedback (RLAIF). This scalable approach enables Claude to self-correct harmful responses while maintaining helpfulness.
A design sprint is a five-day process developed by Jake Knapp at Google Ventures for answering critical business questions through rapid prototyping and user testing. Teams map a problem on Monday, sketch competing solutions on Tuesday, decide on a direction Wednesday, build a realistic prototype Thursday, and test it with five target users on Friday. The goal is to compress months of assumption-laden work into a single week of focused learning.
The gstack framework is an open-source, MIT-licensed skill pack that structures AI-assisted coding workflows into 23 specialist skills and 8 power tools. Created by Garry Tan, it introduces multi-agent perspectives, including CEO, engineer, and QA roles, so developers can move from high-level decisions to implementation with consistent quality. Teams access skills through slash commands inside Claude Code or compatible agents.
The taste skill frontend framework is an open-source collection of portable SKILL.md instruction files that teach AI coding agents to produce higher-quality frontend UI. Instead of generating generic, cookie-cutter interfaces, agents following these skill files apply deliberate rules for typography, spacing, layout density, motion, and design-system consistency. It works with tools like Cursor, Claude Code, Codex, and Gemini CLI.
The 7 P's Marketing Mix is an extended marketing framework created by Booms and Bitner that adds People, Process, and Physical Evidence to the original 4 P's (Product, Price, Place, Promotion). It works as a structured market analysis tool by ensuring teams evaluate every dimension of their offering—from service delivery to tangible proof points—so marketing strategies align with customer expectations across the entire journey.
AI SEO is the practice of optimizing content so it appears in AI-generated answers from platforms like ChatGPT, Google AI Overviews, and Perplexity. It combines Answer Engine Optimization (AEO), Generative Engine Optimization (GEO), and LLM Optimization (LLMO) to structure content, build topical authority, implement schema markup, and earn citations from large language models — ensuring your brand is visible wherever AI synthesizes information for users.
The copywriting framework is a conversion-focused methodology built on four pillars: clarity over cleverness, specificity over vagueness, benefits over features, and customer language over jargon. It provides page-specific guidance and CTA formulas for homepages, landing pages, pricing pages, and feature pages — ensuring every word earns its place by moving readers toward action.
The Ecosystem Journey Framework is a structured system for organizing every customer journey an organization touches into a managed hierarchy of four levels (L0 through L3). It moves teams beyond static journey maps toward dynamic journey management, connecting touchpoints across departments so organizations can spot patterns, prioritize improvements, and align around shared customer outcomes.
The McKinsey Consumer Decision Journey (CDJ) is a framework that replaces the traditional marketing funnel with a circular customer journey model. It maps four phases — initial consideration, active evaluation, moment of purchase, and post-purchase experience — reflecting how modern consumers loop through research, peer recommendations, and brand interactions before buying and potentially becoming loyal advocates who skip evaluation entirely.
The Planned Journey Framework is a customer journey mapping approach developed by SKIM Group for high-involvement, infrequent purchases like cars, financial products, and electronics. It divides the decision process into three stages: latent (pre-need), evaluation (active research), and buying (final selection). By connecting insights across these stages, teams identify where brand consideration shifts and where to optimize touchpoints for maximum impact.
The RACE Framework is a digital marketing planning model created by Dr. Dave Chaffey that organizes the customer journey into four stages: Reach (building awareness), Act (encouraging interaction), Convert (driving sales or leads), and Engage (fostering loyalty). Each stage defines specific objectives, KPIs, channels, and tactics, giving teams a structured roadmap to optimize marketing performance across the entire funnel.
The Six Forces Model is a strategic framework that adds complementary products as a sixth force to Michael Porter's original Five Forces. It gives teams a more complete picture of industry competitiveness by accounting for how products and services outside your direct market, such as software ecosystems or accessory markets, shape profitability, buyer behavior, and strategic positioning. It is especially relevant in technology-driven and platform-based industries.
The 4Ls sprint retrospective is an agile reflection technique where teams categorize feedback into four areas: Liked (what went well), Learned (new insights), Lacked (what was missing), and Longed For (desired improvements). Teams brainstorm individually, share and cluster responses on a board, discuss themes, and commit to specific action items for the next sprint. It was created by Mary Gorman and Ellen Gottesdiener to make retrospectives more structured and actionable.
The five-step sprint retrospective framework is a structured approach for agile teams to reflect on completed iterations and plan improvements. Created by Esther Derby and Diana Larsen, it consists of five sequential phases: setting the stage, gathering data, generating insights, deciding what to do, and closing the retrospective. Each phase builds on the previous one to transform raw observations into concrete action items that drive continuous improvement.
Start stop continue is a structured feedback and retrospective framework that organizes insights into three categories: things to start doing (new beneficial actions), things to stop doing (ineffective practices to eliminate), and things to continue doing (effective behaviors to maintain). Teams collect input from all participants, discuss and prioritize items in each category, then convert them into concrete action items for the next cycle.