anchoring-effect
La primera información recibida influye en juicios posteriores. Use cuando diseñe pricing, comparaciones, o cualquier contexto donde el orden de información importa.
La primera información recibida influye en juicios posteriores. Use cuando diseñe pricing, comparaciones, o cualquier contexto donde el orden de información importa.
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.
La experiencia previa influye en cómo percibimos elementos. Use cuando diseñe para audiencias específicas, aproveche convenciones, o considere conocimiento previo del usuario.
A behavioral model defining the opposing forces in switching decisions—Push, Pull, Anxiety, Habit. Change happens only when (Push + Pull) > (Anxiety + Habit). Core to Jobs-to-be-Done theory.
Use when designing retention mechanisms, habit loops, or auditing why users drop off despite engaging with core features, to structure gamification beyond superficial badges
El 80% de resultados viene del 20% de causas. Use cuando priorice features, diseñe interfaces, o decida dónde invertir esfuerzo de diseño.
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
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.
MUST use before building features, creating components, adding functionality, or designing new behavior. Use when user says 'build', 'create', 'add feature', 'implement', 'design', or describes something new to build. Explores requirements through questions before writing code.
Emerging technologies (prompt engineering, AI agents, red teaming) and leadership roles (product manager, engineering manager, DevRel).
Define what to build at what fidelity to learn what you need without over-investing. Use before starting any prototype.
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.
Use when hiring for early-stage high-growth companies, when filtering out comfort-seekers, or when building teams tackling unsolved technical challenges
Systematic white glove sales methodology for FirstMile pipeline stages 02-07, focusing on volume commitment negotiation, implementation oversight, and revenue realization. Use when advancing deals through discovery, rate creation, proposal, implementation, or addressing volume ramp issues, implementation handoffs, or customer onboarding challenges.