Three constraints before I build anything

The author, a builder with a decade of experience, introduces three foundational constraints they apply before starting any new project. These constraints emerged from past failures where products became overly complex or lacked a clear identity, and are presented as essential tools for fostering creativity by narrowing the problem space.

• One page or it doesn't get built: This constraint forces clarity and limits complexity. All ideas must be distillable into a single, concise document that serves as the project's 'north star'. This one-pager guides communication, helps resolve conflicts, and ensures the core idea is robust enough to build upon.
• The core tech must be separable from the product: This constraint promotes leverage and originality by demanding a reusable piece of intellectual property that supports the product but isn't the product itself. This 'core tech' (e.g., a library, methodology, or tool) is independent of product pivots, compounding over time, and ensures long-term commitment and alignment with a broader vision.
• One defining constraint must shape the product: This prevents feature creep and imbues the product with a unique identity. This constraint should be obvious to the user, pervading the entire experience (like Minecraft's blocks or IKEA's flat-pack design). It limits scope, simplifies decision-making, and allows a product's design to naturally 'fall out' from this core limitation.

In essence, the author concludes that if an idea fails to meet any of these three critical constraints, it is simply not pursued, ensuring a disciplined and focused approach to product development.