3 constraints before I build anything

Author: Jordan Lord | Published: 2026-04-07 | Generated: 2026-04-29 | Domain: jordanlord.co.uk Tags: ‘#productstrategy’ ‘#constraints’ ‘#softwaredevelopment’ ‘#innovation’ ‘#productdesign’

---

TLDR

Jordan Lord uses three hard filters to decide whether an idea is worth building: it must fit a precise one-page plan, produce reusable core technology separate from the product, and be shaped by a visible defining constraint. Together, these constraints narrow the search space, establish product identity, and prioritize compounding long-term leverage over complex, unfocused projects. If an idea fails any one of them, Lord does not build it.

Key Takeaways

• Write a one-pager first: The document is a non-negotiable north star for planning, communication, and resolving disagreements; if the idea cannot be expressed clearly in one page, it needs more research, prototyping, or simplification.
• Build separable core technology: A product should create reusable IP—a method, library, tool, skill, or language—that survives product pivots and compounds over time.
• Prioritize leverage over product-only work: Lord cites Git, HashiCorp Configuration Language (HCL), and Kubernetes as examples of core technologies that outlast or extend beyond their original product contexts.
• Choose a defining product constraint: A prominent, user-visible constraint gives a product its feel and identity while reducing feature creep and decision overhead, as blocks do for Minecraft and flat-pack assembly does for IKEA.
• Use the constraints as a final gate: Any idea that fails the one-page, separable-tech, or defining-constraint test is rejected.

Images & Media

None present in article.

Referenced Links

• Jordan Lord — Author’s website and blog homepage.
• RSS feed — Site subscription feed.
• Subscribe to the Mailing List — Email subscription page.