Minimum Lovable Product (MLP)
In an era where AI lowers the cost of building software, viability is obsolete. The differentiator is joy and emotional connection. Prioritize "Wow" over "Aha"—brand is product interaction.
marginal-user-framework
Use when facing conversion plateaus, expanding to new markets, or when aggregate data fails to reveal growth bottlenecks, to identify high-leverage improvements by focusing on worst-case users
long-horizon-holdout
Use when running experiments on platforms where user value compounds over time, when growth teams claim credit for revenue that would have happened anyway, or when short-term wins don't translate to long-term value
Hierarchy of Marketplaces
A roadmap for marketplace domination. Level 1: Focus on a "thimble" to maximize Happy GMV. Level 2: Tip the market via growth loops. Level 3: Dominate to capture economic rents. Not all GMV is equal.
Hierarchy of Engagement
A three-level framework to gauge growth quality. Level 1: Core Action completion. Level 2: Retention via accruing benefits and mounting loss. Level 3: Self-perpetuating loops. Don't optimize for MAU—optimize for engaged users.
gamification-triad
Use when designing retention mechanisms, habit loops, or auditing why users drop off despite engaging with core features, to structure gamification beyond superficial badges
Culture-as-Product Operating System
Treat company culture as a product you build for employees. Iterate on it using feedback loops (NPS), identify bugs, and evolve it—don't try to preserve a static version.
PR/FAQ Product Validation
Write a future-dated Press Release and FAQ before any coding begins to ensure the product solves a real customer problem. Work backwards from the customer, not forward from capabilities. Amazon's foundational process.
Product Strategy Stack
A hierarchical framework forcing alignment from top down—Mission, Company Strategy, Product Strategy, Roadmap, Goals. Strategy precedes goals; goals measure progress against a strategy.
seasonal-planning
Use in rapidly evolving industries like AI where 6-month plans become obsolete, when needing to balance direction with agility, or when traditional annual roadmaps fail
Single Consciousness Roadmap
A planning framework where the entire company operates off a single, rolling two-year roadmap with synchronized releases. Use when shipping frequently but customers aren't noticing, or when engineering and marketing are out of sync.
strategic-narrative
Use when traditional problem/solution pitches fail to differentiate, when teams are misaligned around messaging, or when entering Series B/scaling phases where founder-led sales no longer scale
Agent Mindset Termination Protocol
When firing someone, separate the business decision from humane implementation. Act as their talent agent—actively use your network to help them find their next role.
Diagnose with Data, Treat with Design
Use data to establish business observability (diagnosing problems) but use creative design thinking to solve them (treatment). Resolves the conflict between data-driven and intuition-driven product development.
lazy-vain-selfish-users
Use when designing onboarding flows, writing marketing copy, or creating the first-mile product experience to capture attention from indifferent users
Selective Micromanagement Matrix
Leadership is a dynamic range. When confidence in team direction is low, temporary tactical micromanagement is the correct move—not autonomy. Teach the framework, then pull back.
Single-Threaded Leadership Model
An organizational model where a single leader is fully accountable for a specific goal and controls all cross-functional resources needed, minimizing external dependencies. Amazon's alternative to matrixed organizations.
Three Levels of Product Work
Understand that product work happens at three levels (Impact, Execution, Optics) and conflicts arise when people argue from different levels. Use to diagnose team misalignment.
Waterline Model
Diagnose team problems by checking structural issues (goals/roles) at the surface before diving deep into personality conflicts. 80% of team problems are structural, not personal.
Willow Tree Leadership Style
A metaphor for managing change—remain rooted in core purpose while being extremely flexible in tactics, absorbing storms of change without breaking. Use during pivots, restructures, or industry upheavals.
bar-test-positioning
Use after drafting positioning statements, before writing website copy, or when marketing language sounds corporate rather than human
Causal Interview Protocol
A JTBD interviewing technique to reconstruct the customer's timeline and uncover causal mechanisms behind a purchase. Resembles criminal investigation—penetrate surface-level answers to find the struggling moment.
shackleton-hiring
Use when hiring for early-stage high-growth companies, when filtering out comfort-seekers, or when building teams tackling unsolved technical challenges
Left-Hand Column Detox
A technique to translate harsh internal thoughts into constructive external dialogue. Say the thing you think you cannot say—but detoxify it first. Use when sensing tension or unspoken issues in meetings.
In-The-Details Review Loop
A leadership cadence where the CEO/Leader reviews actual work (designs, prototypes, copy) weekly rather than just metrics or status slides. Use when feeling product quality is slipping or team is moving too slowly.
House Operational Architecture
A three-part structural framework for building a scalable company—Foundation (Founding Documents), Posts & Beams (Supporting Structures), and Mechanicals (Operating Cadence). Use when moving from PMF to scaling the org.
chatter-driven-development
Use when designing futuristic agentic workflows, when wanting AI to proactively act on team communications, or when eliminating the bottleneck of formal specifications
curiosity-loops
Use when facing a significant decision (career pivot, product direction, technical choice) and feeling stuck or indecisive, when seeking contextual advice rather than generic recommendations
organizational-kayfabe
Use when navigating large organizations where official strategy seems doomed but leadership isn't ready to hear it, when dealing with status updates that feel disconnected from reality, or when feeling burned out by organizational politics
LNO Time Management Framework
Categorize tasks into Leverage (10x), Neutral (1x), and Overhead (<1x) to escape the trap of treating all tasks as equally important. Apply perfectionism only to L tasks.
nlx-design-stack
Use when designing AI agents or chatbots, when raw model outputs feel like a black box, or when building natural language interfaces that need structure and trust
historian-decision-model
Use when joining a new company, taking over legacy products, or proposing strategies that were previously attempted to avoid repeating past mistakes
Energy Audit and Zone of Genius
Review your calendar, color-code activities by energy impact (Green/Red), and systematically delegate draining tasks to maximize time in your Zone of Genius.
Dimensionality of Self-Management
View yourself as an entity with infinite dimensions rather than a single good/bad identity. Strengths and weaknesses are often the same trait in different contexts. Use during performance reviews or when receiving tough feedback.
three-layer-agent-stack
Use when building AI-powered products or agents, when raw model intelligence isn't enough to solve user problems, or when designing the architecture for agentic workflows
4P Opportunity Framework
Evaluate opportunities by assessing Potential BEFORE Probability, then check Passion and Prowess. Prevents risk aversion from killing high-upside ideas.
unstuck-scaling
Use when AI agents frequently hit dead ends, when reliability is the main constraint on scaling utility, or when general model improvements don't solve specific blockers
taste-driven-core
Use for core product areas defining long-term brand value, when A/B tests are fragmenting product vision, or when short-term optimization threatens architectural integrity
founder-prenup
Use before starting a company with co-founders, when bringing on a new co-founder, or annually as a relationship health check to prevent the 65% of startup failures caused by co-founder conflict
gardening-mindset
Use when dealing with ecosystems, network effects, or high-uncertainty environments where the right answer cannot be known in advance, when rigid planning consumes more value than it creates
Corporate Innovation C-Corp Model
To replicate startup speed in large companies, launch new products as separate legal entities (C-Corps) with distinct brands, reporting directly to the CEO, bypassing standard chains of command.
pre-mortem-kill-criteria
Use before launching products or signing contracts, when needing to combat sunk cost fallacy, or when standard pre-mortems fail to change behavior
Pre-Mortem Framework
Instead of waiting for a post-mortem after failure, imagine the project has already failed spectacularly and work backward to uncover hidden risks. Use before kicking off any major initiative, product launch, or high-stakes project.
playing-to-win
Use when defining long-term product strategy, when needing to pivot from horizontal to vertical focus, or when teams struggle with prioritization due to serving too many use cases
Opportunity Cost Minimization
Stop optimizing for positive ROI and start focusing on minimizing opportunity cost—choosing the BEST possible use of time, not just a good one. Use during quarterly planning and roadmap prioritization.
Frontier of Understanding (NCTs)
Before setting outcome goals, identify your understanding level. If you don't know the levers, set a learning goal, not a revenue goal. Don't commit to outcomes you can't control.
inner-scorecard
Use when deciding between a high-status opportunity and a riskier path that feels more aligned, when feeling trapped despite external success, or when auditing if your decisions serve your values or others' expectations
J-Curve Career Framework
High-growth careers are J-Curves, not stairs—you jump off a cliff (take risk), struggle for 6-9 months (bottom of J), then shoot up exponentially. Use when deciding between safe promotion vs stretch role.
ai-teammate-model
Use when designing AI agent products, defining roadmaps for agentic workflows, or evaluating how to evolve AI from passive tool to proactive partner in software development
Personal Operating Manual
A document created by a leader that articulates their values, quirks, and expectations to accelerate mutual understanding with their team. Use when onboarding new team members or taking over a new team.
Page 1313 of 1594 · 79686 results
