The Toolkit
Frameworks You Can Use
I build systems for everything. After years of working with founders at the zero-to-one stage, I kept rebuilding the same frameworks from scratch for every engagement. So I turned them into tools. These are the ones I actually use. Not theoretical models built to look credible. Working documents stress-tested across real products, real teams, and real deadlines. Take them. Use them. Break them and rebuild them for your own context. That's the whole point.
→ Tool 1: The Soul File [ File Link Soon ]
What it is A single document that captures the core identity of a product or company. Not a brand book. Not a style guide. The essential truth distilled into voice, values, personality, and positioning. One living document that every team member can reference before making any decision that touches the outside world.
Why it matters Most brand problems aren't design problems. They're alignment problems. The founder thinks the brand sounds one way. The marketer writes it another way. The designer interprets it a third way. The Soul File eliminates that gap. One source of truth for who you are, how you sound, and what you'd never say.
When to use it Before you design anything. Before you write copy. Before you brief anyone external. If your team can't articulate who your product is in one conversation without contradicting each other, you need this before you need a designer.
What's inside
Brand essence in one sentence
Voice attributes with examples of what each sounds like in practice
Personality spectrum: where you sit between formal/casual, playful/serious, technical/accessible
Language principles: words you use, words you never use, how you handle jargon
Positioning statement: what you do, for whom, why it matters, and what makes you different
Anti-examples: brands you respect but deliberately don't sound like, and why
→ Tool 2: The First Five Minutes Map [ File Link Soon ]
What it is A step-by-step mapping of what a new user experiences in their first five minutes with your product. Every screen, every decision point, every moment of clarity or confusion. Annotated with what the user is likely thinking, feeling, and deciding at each step.
Why it matters The first five minutes determine whether someone becomes a user or a bounce statistic. Most teams know their onboarding needs work but can't pinpoint exactly where the problem is. This map makes the invisible visible. You can't fix what you haven't documented.
When to use it When activation is low and you don't know why. When you're about to redesign onboarding. When a new team member needs to understand the current experience before proposing changes. When you suspect the problem is in the flow but everyone's arguing about individual screens.
What's inside
Screen-by-screen flow documentation
User mental state at each step: what they know, what they're expecting, what they're uncertain about
Decision points: where users have to choose something and what information they have to make that choice
Friction markers: where users hesitate, where they drop off, where they need help
The "first win" identifier: what's the earliest moment a user experiences value?
Time stamps: how long each step takes and where the experience feels slow
→ Tool 3: Landing Page Scorecard [ File Link Soon ]
What it is A structured evaluation framework for scoring any landing page across five dimensions in under ten minutes. Each dimension gets a rating and a specific, actionable recommendation.
Why it matters Most landing page feedback is vague. "It doesn't feel right." "Can we make it more engaging?" "I think we need more social proof." This scorecard turns subjective impressions into specific, measurable evaluations. You stop debating feelings and start fixing problems.
When to use it Before a launch. After a launch that underperformed. During any conversation about why visitors aren't converting. When you need to give a founder or marketing team clear, prioritized feedback without spending a week on an audit.
What's inside
Dimension 1: Headline clarity. Does the headline communicate what you do and for whom in under five seconds? Score 1-5 with specific criteria for each level.
Dimension 2: Value proposition strength. Is the benefit specific, believable, and differentiated? Or generic and interchangeable with any competitor?
Dimension 3: CTA effectiveness. Is there one clear action? Is the copy compelling? Is the button visible without scrolling?
Dimension 4: Social proof quality. Are the testimonials specific and credible? Do the logos mean something to the target audience? Is the proof relevant to the claim?
Dimension 5: Visual hierarchy. Does the page guide the eye in the right order? Is there clear information architecture? Does the design support or compete with the message?
Overall score with priority recommendation: the single most impactful thing to fix first
→ Tool 4: Conversion Friction Identifier [ File Link Soon ]
What it is A structured worksheet for identifying exactly where and why users drop off in any core product flow. Combines quantitative data with qualitative observation to produce specific intervention recommendations.
Why it matters Most teams have analytics. Few teams turn analytics into design actions. The gap between "we know where users drop off" and "we know why and what to do about it" is where most conversion opportunities die. This framework closes that gap.
When to use it When you have analytics showing drop-off but haven't translated that data into specific design changes. When conversion is acceptable but you know there's meaningful upside on the table. When you need to prioritize which friction points to fix first.
What's inside
Flow mapping template: document every step in the flow with the percentage of users who complete each step
Drop-off analysis for each step: what the user sees, what you're asking them to do, what might be causing hesitation
Friction classification: is it a clarity problem (they don't understand), a trust problem (they don't believe), a motivation problem (they don't care enough), or a mechanics problem (it's too hard)?
Intervention recommendations: three specific changes to test for each friction point, ranked by expected impact and implementation effort
Priority matrix: which fixes to ship first based on drop-off volume and fix complexity
→ Tool 5: Design System Starter Kit [ File Link Soon ]
What it is A minimal, opinionated framework for starting a design system that will actually get adopted. Not a comprehensive component library. The foundation layer that makes everything else consistent without requiring months of upfront investment.
Why it matters Most design systems fail because teams try to build everything at once. They spend months creating a comprehensive library, launch it, and watch adoption stall because the system was built in isolation from the team's actual workflow. This starter kit focuses on the 20% that delivers 80% of the consistency.
When to use it When your product has outgrown ad-hoc styling but isn't ready for a full system. When inconsistency is creeping in and you need quick wins. When you've tried to build a design system before and it became shelfware.
What's inside
Design tokens: color, typography, spacing, elevation, and border radius defined as a single source of truth
Core components: the ten components that appear on more than 50% of your screens, documented with clear usage guidelines
Naming conventions: how to name tokens, components, and variants so the system stays organized as it grows
Adoption playbook: how to introduce the system to a team without mandating it, including pairing sessions and migration strategy
Health metrics: how to measure whether the system is working (adoption rate, consistency score, time-to-build)
→ Tool 6: AI Feature Personality Framework [ File Link Soon ]
What it is A structured approach to defining how an AI-powered feature should behave inside your product. Not prompt engineering. A product design framework for deciding the personality, boundaries, tone, and behavior of any AI interaction.
Why it matters Most AI features feel the same. Generic, overly helpful, slightly robotic. That's because teams focus on making the AI capable without deciding how it should feel. The interface personality of an AI feature is a brand decision, not a technical decision. And it's one of the most underinvested areas in AI product design right now.
When to use it When building any AI-powered feature and the default behavior feels generic. When your AI doesn't match the rest of your product's personality. When you want your AI interaction to feel like a product experience, not a chatbot.
What's inside
Personality definition: is the AI a tool, an assistant, a collaborator, or something else? Each comes with different expectations.
Tone spectrum: where the AI sits between formal/casual, confident/hedging, concise/explanatory
Boundary map: what the AI should never say, topics it should redirect, how it handles questions outside its scope
Error and uncertainty behavior: what happens when the AI doesn't know? Does it say so? Does it suggest alternatives? Does it ask clarifying questions?
Brand alignment check: a comparison between your product's voice (from the Soul File) and your AI's current voice, with specific adjustments
→ Tool 7: Stakeholder Alignment Canvas [ File Link Soon ]
What it is A one-page framework for getting founders, product, engineering, and design aligned before any major initiative starts. Fills the gap between "we've decided to build this" and "everyone agrees on what this actually means."
Why it matters Most projects don't fail because of bad design or bad engineering. They fail because different people were building toward different definitions of success. The alignment canvas forces those differences to the surface before work starts, when they're cheap to resolve, not after three weeks of building, when they're expensive and demoralizing.
When to use it At the kickoff of any project that involves more than one team or takes more than two weeks. When a project has stalled because people are pulling in different directions. When requirements keep shifting mid-build.
What's inside
The problem we're solving: one sentence, agreed upon by everyone in the room
Who we're solving it for: specific user segment, not "everyone"
What success looks like: measurable outcome, not "improve the experience"
What we're not doing: explicit scope boundaries that prevent creep
Key decisions to make before design starts: the questions that will derail the project if left unanswered
Dependencies and risks: what could block this and what's the backup plan
→ Tool 8: Product Messaging Hierarchy [ File Link Soon ]
What it is A layered messaging framework that defines what your product says at every level of detail. From the five-second headline to the two-minute explanation to the full product narrative. Each layer builds on the one above.
Why it matters Most products have messaging that works at one level but breaks at another. The homepage headline is clear but the feature descriptions are confusing. Or the detailed explanation is strong but the elevator pitch is weak. This framework ensures consistency from the broadest to the most specific level of communication.
When to use it When you're launching or repositioning. When different team members describe the product differently. When your landing page, pitch deck, and product copy feel disconnected.
What's inside
Level 1: The five-second version. One sentence. What you do and for whom. No jargon. A stranger should understand this.
Level 2: The thirty-second version. Three sentences. What you do, why it matters, and what makes you different.
Level 3: The two-minute version. Full value proposition. Key benefits with specific proof points. Who it's for and who it's not for.
Level 4: Feature-level messaging. Each major feature described in terms of user benefit, not technical capability.
Level 5: Objection handling. The three biggest reasons someone wouldn't buy, and the specific response to each.
Consistency test: read all five levels back-to-back. Do they tell the same story at different resolutions?
