How Product Design Leads Kick Off New Initiatives
For in-house product design leads · Based on Cecilia Kim Design Project Launch Framework
// TL;DR
The Cecilia Kim Design Project Launch Framework gives in-house product design leads a repeatable kickoff process for new initiatives. It separates the UI and UX lenses, mandates locking visual direction before wireframing, and structures stakeholder alignment through curated inspiration reviews and mood boards. Use it at the start of any new product, feature, or landing page initiative, before design work begins. For design leads, it standardizes how the team runs discovery, gathers inspiration, aligns cross-functional stakeholders, refines to an MVP, and maps flows — reducing rework, avoiding surprise redesigns, and keeping multi-approver sign-off from stalling delivery.
How do you standardize design kickoff across a team?
Adopt the framework's phase separation as your team's default. Every new initiative opens with a Design Discovery exercise that captures the fundamental problem, audience, differentiator, feature ideas, constraints, and — crucially for an org — the decision-maker structure: is one person approving, or a team? Documenting this up front tells you how to run alignment later. Follow discovery with a written summary so product, engineering, and design share one source of truth before any pixels move. Standardizing this opening means every designer on your team starts the same way, and reviews become predictable.
Why lock UI direction before UX in a product org?
Because doing both at once creates confusion and expensive surprises. The framework insists you gather UI inspiration through a Screenshot Frenzy using the UI lens — colors, gradients, shadows, spacing, typography hierarchy — organize it into distinct vibes, build mood boards for emotion, and lock a visual direction from three to five mockup explorations before touching structure. Then you switch entirely into the UX lens for the Feature Brain Dump, MVP refinement, screen flow mapping, and low-fidelity wireframes. When the visual language is already approved, applying it to wireframes produces no major surprises — only minor tweaks like adjusting a color on a dense data screen.
How do you align multiple stakeholders without stalling?
Use curated presentations, never raw dumps. Organize inspiration in a labeled Figma deck — one section per direction — and walk stakeholders through your reasoning in a structured review. This gives them a framework for decisions and ownership over the outcome, replacing subjective debate over words like "modern" with concrete shared references. When you have a multi-approver structure, run these reviews as decision meetings with the whole sign-off group present, so you get consolidated direction instead of conflicting feedback trickling in later. Handle wireframe and visual-design feedback in structured rounds for the same reason — consolidated input, fewer cycles.
How do you enforce MVP discipline internally?
Run the Feature Brain Dump to let stakeholders express the full vision without judgment — this earns buy-in — then refine to the MVP of three-to-five core screens. Frame cuts as sequencing, not cancellation: ship the core, learn from real users, refine from evidence. Internally, this protects engineering capacity and keeps roadmaps honest. Pair it with intentional convention use — know your category's industry design language so the team makes deliberate choices about following or breaking norms rather than reinventing patterns users already understand and adding friction.
Finally, map the screen flow before wireframing every initiative. A simple boxes-and-arrows diagram surfaces missing and unnecessary steps while they're cheap to fix, long before engineering estimates depend on them.
Next step: Codify this into a team playbook — a discovery template, a shared Figma inspiration structure, a mood board process, and a rule that UI direction is locked before wireframing. Add a standard MVP refinement checklist and a structured-review cadence for your next initiative.
// FREQUENTLY ASKED QUESTIONS
How does this framework handle multi-approver sign-off?
Capture the decision-maker structure during discovery so you know whether one person or a team approves. When multiple approvers exist, run your curated direction reviews as decision meetings with the full sign-off group present, so you receive consolidated direction rather than conflicting feedback arriving piecemeal later. Handling visual and wireframe feedback in structured rounds keeps multi-stakeholder input organized and prevents endless cycles.
Can I use the Screenshot Frenzy for internal design systems work?
Yes. The Screenshot Frenzy applies whenever you need to establish or refresh a visual direction. Use Mobin, Dribbble, and Behance filtered to your industry, apply only the UI lens, and organize saves into distinct vibes. Reference full brand and design systems on Figma Community to see how elements work together. Keep it strictly separate from any UX or component-logic exploration.
How do I stop wireframe feedback from dragging on internally?
Share wireframes in structured rounds rather than accepting continuous ad-hoc changes, and define what counts as a revision versus a new feature request. Map the screen flow first so structural gaps are caught before wireframing. Refining to an MVP up front also limits the surface area under review, so stakeholders give consolidated, focused feedback instead of drip-feeding small changes.