How Startup Founders Should Brief a Design Project
For startup founders · Based on Cecilia Kim Design Project Launch Framework
// TL;DR
The Cecilia Kim Design Project Launch Framework helps startup founders brief design work in a way that protects runway. It structures the opening moves — a Design Discovery Call, UI inspiration and mood board alignment, locked visual direction, then a separate UX phase built around a Feature Brain Dump and MVP refinement. Use it whenever you kick off branding, a product, or a landing page, especially a combined engagement. For founders, the biggest wins are MVP discipline (ship three-to-five core screens first), branding-first sequencing that prevents redone work, and early alignment that keeps expensive design cycles short.
How should a founder brief a designer?
Brief with context, not pixels. The Design Discovery Call is where you give your designer everything they need: what your product is at a fundamental level, the problem it solves, who it's for, and what makes it different. Add your feature ideas, any brands or apps you admire, existing assets, and — critically — your timeline, budget, and who signs off on decisions. You don't need a visual direction; a good designer will generate options for you to react to. Insist on a written summary afterward so both sides are aligned before work starts.
Why does branding need to come first?
Branding establishes the foundational visual elements — colors, typography, logo, personality — that get applied to everything else. If you rush your team into designing a landing page or app before the brand is locked, you'll almost certainly pay to redo that work when the brand direction shifts. For a full engagement, the correct sequence is branding → product UI → landing page. Locking branding first means every downstream deliverable is built on final assets with no color or type guessing, which is the cheapest possible way to move fast.
How do you decide what to build first?
Use the Feature Brain Dump and MVP discipline. First, get every feature you want on the table — dream ideas, competitor features, the whole vision. Then narrow ruthlessly to the minimal viable product: only the core features that must exist to launch, typically three to five main screens. This is often a hard conversation, but cutting a feature from the MVP doesn't kill it — it means you're being strategic about what to build first. You ship the core, learn from real users, and refine based on evidence instead of assumptions. For a founder burning runway, this is the difference between one focused launch and months spent half-building everything.
How does early alignment protect runway?
The framework front-loads alignment so you don't discover misalignment after weeks of design. Your designer presents curated visual directions and mood boards, and you react — replacing vague words like "clean" with concrete shared references. You approve a UI direction from three to five mockups before any wireframes exist, and you approve wireframes before visual design is applied. Because the big decisions happen early and cheaply, the later phases produce no major surprises. That predictability is exactly what a capital-constrained startup needs.
One more founder-level lever: know your industry design language. Fintech leans blue and conservative for trust; AI uses soft gradients; crypto uses neon dark mode; wellness uses purple and calm tones. Knowing the conventions lets you and your designer decide intentionally whether to fit in or stand out — a strategic choice, not an accident.
Next step: Before you hire or brief anyone, write down your product's problem, audience, differentiator, must-have features, timeline, budget, and decision-maker. Then decide your sequence — if you need branding, product, and a landing page, commit to branding first. Bring that to your Discovery Call.
// FREQUENTLY ASKED QUESTIONS
How do I know which features belong in my MVP?
Your MVP includes only the features genuinely required for the product to launch and deliver its core value — usually three to five main screens. Start with a full Feature Brain Dump, then ask of each item: can we launch and learn without this? If yes, defer it. Cutting features isn't deleting them; it's sequencing, so you can build on real user feedback rather than assumptions.
Should I lock branding before building my app?
Yes. Branding defines the colors, typography, logo, and personality that every other deliverable applies. Building your app or landing page before branding is finalized means redoing work when the brand direction changes. For combined projects, sequence branding first, then product UI and UX, then the landing page, so downstream design uses final assets with no guessing.
What should I prepare before the Design Discovery Call?
Prepare your product's core definition — the problem, audience, and differentiator — plus a feature wishlist, any apps or brands you admire, existing assets, your timeline and budget, and who approves decisions. You do not need a visual direction. Coming in with clear constraints and a clear decision-maker structure makes the call faster and the resulting written summary more accurate.