Commonly Used Methodologies by product managers

The Six-Directional Modeling Method is a structured approach for analyzing and designing complex systems by examining six dimensions (e.g., function, data, process, people, time, and constraints). It enables teams to identify blind spots early, align goals, and develop actionable plans through multi-perspective integration, particularly suited for cross-functional collaboration to mitigate risks from single-dimensional decisions.

The Two-Pizza Rule is a team size management method that advocates keeping teams small enough to be fed by two pizzas (typically 6-8 people), to maintain communication efficiency, decision speed, and team cohesion. This approach emphasizes the advantages of small teams in agile development, innovation projects, and rapid iteration, by limiting size to avoid bureaucracy and communication overhead.

Learning by Doing is a methodology that emphasizes acquiring knowledge and skills through practice, experience, and reflection. It posits that genuine learning occurs during the process of action, not merely through theoretical instruction. This approach is particularly suitable for scenarios requiring the transformation of abstract concepts into concrete capabilities, such as skill training, product development, and team collaboration.

North Star Metric is a product growth and strategy management method that identifies and focuses on a single core metric to drive team decisions around creating user value. It helps organizations maintain alignment in complex environments, avoid scattered efforts, and ensure all actions contribute to long-term sustainable growth.

Usability Testing is a research method that evaluates the ease of use and effectiveness of a product by observing real users interact with it, aiming to identify design flaws and optimize user experience.

User Interviews are a qualitative research method that systematically collects user needs, behavioral motivations, and experience feedback through one-on-one or small group conversations. They help teams deeply understand users' genuine thoughts, providing direct evidence for product decisions and avoiding design biases based on assumptions.

API-First Design is a software development methodology that prioritizes designing and defining API interfaces before building applications. By treating APIs as the core product, it fosters team collaboration, enhances development efficiency, and ensures system consistency and scalability. It is suitable for scenarios requiring rapid iteration, parallel development across multiple teams, or building microservices architectures.

A/B Testing is an empirical method that randomly assigns users to different versions (e.g., Version A and Version B) to compare their performance, enabling data-driven decision-making. It is widely used in product optimization, marketing strategies, and user experience improvements, helping teams reduce subjective speculation and validate hypotheses with quantifiable evidence.

The Hook Model is a product framework for designing habit-forming mechanisms, consisting of four cyclical stages: Trigger, Action, Reward, and Investment. It helps products build sustained user engagement by creating behavioral loops, particularly effective for digital products requiring frequent interaction, such as social media, games, and utility apps, enabling teams to systematically design user behavior paths to improve retention and activity.

Event Modeling is a structured approach for designing and building complex software systems by identifying and documenting key events and their relationships within a business domain. It helps teams understand business processes, define system boundaries, and guide technical implementation, emphasizing a business-centric, event-driven perspective to describe system behavior. It is suitable for distributed systems, microservice architectures, or domain-driven design projects requiring clear alignment between business logic and data flow.

Event Storming is a collaborative modeling method that visualizes domain events in business processes to help teams quickly understand complex systems, identify key issues, and design solutions. It emphasizes cross-functional participation, using tools like sticky notes on large walls to build event flows, fostering communication and consensus.

Deductive Reasoning is a method of deriving specific conclusions from general rules, useful for validation, standard setting, and repeatable decision processes.

Inductive Reasoning is a method of deriving general patterns from specific observations, especially useful for exploration, pattern discovery, and hypothesis formation before validation.

Card Sorting is a user research method where participants group and label content cards, helping teams design clearer information architecture and navigation.