Before a single pixel is pushed or a wireframe drawn, I need to understand the full picture. The kickoff isn't a formality — it's the foundation everything else is built on.
Structured questions that cut through ambiguity fast
Everyone in the room, everyone on the same page
Success defined before design starts — always
Real insights shaping every decision from day one
I've seen what happens when teams skip the kickoff. Six weeks in, everyone has a different version of the project in their head. I've been in those rooms. It's not pretty — and it's completely preventable.
Discovery Intake
Before my first design meeting, I send this intake to every stakeholder. Not to be bureaucratic — but because the answers reveal everything about whether a project is set up to succeed.
Completed before kickoff meeting — takes 10 minutes, saves weeks of confusion
"What are we actually building — and what is it not?"
"Why are we building this right now — and why does it matter?"
"Who is this for — and who are we building it with?"
"How will we know when we've succeeded?"
How I Run It
I've refined this over 13 years. It's not rigid — it adapts to the team, the project, the culture. But the bones stay the same.
I send the discovery intake 48 hours before the kickoff meeting. This forces people to think before they talk. The meeting becomes a conversation, not a brainstorm from scratch. When everyone arrives with answers, we spend time aligning — not explaining.
The meeting has one job: get everyone aligned on the same version of the project. I walk through the What, Why, Who, How — out loud, together. Disagreements surface here, not six weeks later. I capture everything in real time on a shared FigJam board everyone can see.
I push every team to answer the hardest question in the room: what does done actually look like? Not "the design is delivered" — but what changes for the user, the business, the product. We write it down. We agree on it. We refer back to it constantly.
I don't wait until the design phase to talk about users. I bring existing research, analytics, and customer feedback into the kickoff room. If we don't have research, I flag it as a risk. Designing without user insight isn't design — it's guessing.
Within 24 hours, every person in that room gets a written summary of what was decided. Goals, open questions, next steps, owners. This isn't bureaucracy — it's respect for people's time. It also creates accountability. People show up differently when they know there's a record.
Goals & Objectives
What does the company need this project to achieve? Revenue growth, retention, market expansion? I make sure design decisions can always be traced back to a business outcome — not just aesthetic preference.
What does the user need to accomplish — and what's getting in their way? Every project has a user goal at its core. My job is to make sure that goal is never crowded out by internal priorities.
What principles guide this specific project? Speed? Simplicity? Trust? Accessibility? I establish these early so every design decision has a filter to run through — making reviews faster and feedback more focused.
Before design begins, everyone agrees on the metrics that matter.
Surface assumptions, constraints, and dependencies before they become blockers.
No matter the business pressure, user needs stay central to every decision.
One document, one board, one place where the project lives — always current, always shared.
Timeline pressure, unclear ownership, missing research — named now, not discovered at sprint review.
User Insights
I make it my job to be the user's voice in the room. Before any kickoff, I pull together everything we know — and make clear everything we don't.
I audit every piece of user research, support ticket data, NPS feedback, and usability study we have. Even old research reveals patterns. It saves the team from designing solutions to problems users don't actually have.
Who is the primary user — and do all stakeholders agree on who that is? You'd be surprised how often they don't. Getting this aligned in the kickoff prevents entire design directions from being built for the wrong person.
I map the current pain points before proposing any solution. This grounds the team in user reality — not wishful thinking. The best design solutions come from deeply understanding what's broken, not from what looks good.
What don't we know — and how much does it matter? I surface research gaps as risks. Sometimes we proceed with assumptions clearly labeled. Sometimes we pause for a quick research sprint. Either way, the team decides with eyes open.
Numbers tell a story that users can't always articulate. Where are people dropping off? What features get ignored? What paths do power users take? I bring these into the kickoff to ground design decisions in actual behavior.
What job is the user hiring this product to do? Not the feature list — the underlying motivation. When a team agrees on the JTBD, design reviews become sharper, faster, and less about personal taste.
Stakeholder Alignment
Engineers, PMs, executives, designers — each one has a slightly different mental model of what's being built. My job in the kickoff is to collapse those models into one.
I document every stakeholder — their role, their influence, and what they care most about. Not everyone has the same definition of success, and that's fine. What's not fine is not knowing it.
Business wants speed. Engineering wants clean architecture. Users want simplicity. These tensions are real — and they're better surfaced in a kickoff than discovered mid-sprint when everything has to be rebuilt.
How often do we sync? Who's the design decision-maker? What's the escalation path? I set this up in the kickoff so the project runs smoothly — not just the first two weeks, but all the way to launch.
The kickoff summary becomes a living document. I revisit goals and decisions at every major milestone. Alignment isn't a one-time event — it's a practice.
Facilitator · User Advocate · Visual Direction
Requirements · Prioritization · Business Goals
Feasibility · Architecture · Timeline
Strategy · Budget · Executive Alignment
User Insights · Data · Validation
Teams that invest 2 hours in a proper kickoff save 20 hours of rework later. I've seen it over and over. The projects that launch on time, on budget, and actually get used — they all started with everyone in the same room, asking the hard questions.
I'll get back to you within 24 hours.
Thanks for reaching out. I'll be in touch soon.