Framework
Design Systems Thinking
Stop designing individual screens. Start designing systems of experiences. Every interface element is a pattern with explicit rules and constraints — not a one-off creative decision. This shift from instance-level to system-level abstraction is what enables consistent product experiences at scale and makes AI generation enterprise-appropriate.
How it works
- 1Christopher Alexander's pattern language applied to digital: every interface has recurring patterns (buttons, navs, cards, modals, prompts) that should have explicit rules rather than being reinvented each time.
- 2A design system is a 'well-organized bucket of Lego bricks' — but the real power is in the rules that govern how the bricks connect, not just the bricks themselves.
- 3System-level thinking collapses the designer–developer–QA handoff: when every element is a pattern with encoded rules, the same source of truth serves every role.
- 4The shift enables AI generation: a screen is too ambiguous for an AI to generate reliably; a pattern with constraints is specific enough to produce an enterprise-appropriate output.
- 5Knapsack's thesis: the companies winning in the next decade are the ones who get their design system right now — because the design system becomes the substrate for every AI-generated experience.
Hear it on the podcast
Stop Designing Screens, Start Designing PatternsListen to the episodeMore from this episode
Prototype and PruneAI is a proxy for skill, not taste. Generate multiple enterprise-appropriate prototypes using real design system context, then let a human with taste prune down to the right one. Coined by Jules at Meta, reinforced by Scott Belsky. The bottleneck moves from production to curation — and curation is the irreducible human job.The Intelligent Product EngineA three-part architecture that makes AI generation predictable and enterprise-appropriate: context archetypes (different rule sets for different modes), real-time artifact monitoring (Figma and git sync to structured artifacts for humans and AI), and a rules engine (WCAG, brand governance, legal gates, release criteria). Each part is necessary; together they turn generative AI from a prototype toy into a production tool.
Get the next framework first
One email a week with the frameworks, tools, and founder stories from the podcast. Free.
More frameworks for Building the Product
Sprint ZeroBefore writing code, conduct a discovery phase that audits pirate metrics, forces explicit assumption validation, and produces a 1–1.5 month validated roadmap. Sprint Zero converts founder conviction into actionable direction. Almost every founder arrives with a three-month roadmap and no data to support it. Sprint Zero surfaces what is real and what is assumption — and the roadmap that comes out is one the team can build against with confidence.Requirements-First DevelopmentThe CTO's core job is not writing code — it's translating business objectives into technical requirements, then ensuring the code solves the right problem. Start there. Generating code before generating requirements produces something technically functional that solves the wrong problem. The 70% wall is the symptom; deferred requirements are the cause. Requirements elicitation — guided prompting to extract what you actually need — is what separates MVPs from prototypes.The 70/30 Software StackSeventy percent of every new software application is commodity: authentication, user management, CRUD operations, data pipelines, notifications. It was never innovative. Every dev shop had internal boilerplates for it. The competitive advantage in software has always come from the 30% that's unique. In 2026, this matters more: any decent CRM can be built in a day. Automate the 70%; focus all human effort and genuine IP development on the 30%.Engine + NLP + AutomationModern product development converges three capabilities: an existing engine (platform, open-source framework, or no-code tool), natural language AI (NLP you can prompt rather than program), and trigger-based automation (API integration that has existed for 15 years and is now commercializing at scale). Build around the right engine and connect components rather than coding from scratch. In 2025, building from zero is immature.The Flow-First Product PrincipleDesign your product around protecting momentum, not just delivering features. The most valuable intervention in a creative work session isn't the best feature — it's the one that keeps someone from abandoning their project entirely. On Demand Human is built on this principle: 15 minutes of expert help at the right moment is worth more than any feature upgrade, because it preserves the flow state that makes all other work possible.The Virtuous Expertise LadderIn peer expertise marketplaces, today's beginner becomes tomorrow's best helper. The person who just solved a problem is more empathetic, more contextually accurate, and more effective at explaining the fix than a senior expert who solved it years ago. This creates a self-sustaining supply side: as a community matures, freshly-graduated members flow back into the marketplace as helpers. Design for this natural progression — it's both your supply mechanism and your community glue.