By Nick Babich
Key Takeaways
- What a kickoff is: the first working meeting after the contract is signed. It locks how the engagement will run, not what the product should look like.
- How long it should run: 60 to 90 minutes. My default is a timed 75-minute agenda with seven blocks and a named output for each.
- What the client brings: signed scope references, named decision maker, brand and product access, analytics or research you already have, and a list of people who can block the work.
- What must be decided in the room: who decides what, how success will be judged, the first milestone, communication rules, and the first actions with owners and dates.
- What you leave with: a one-page kickoff summary, a decisions log, an actions list, and calendar holds for the first reviews — sent within 48 hours.
- What it is not: a discovery workshop, a brief rewrite, or a vendor pitch. Those belong elsewhere.
A UX design kickoff checklist is the short set of agenda blocks, artifacts and named owners you need for the first meeting after a contract is signed. The meeting aligns the client team and the design team on how the engagement will run: who decides, how success will be judged, what the first milestone is, and what each person owes by when. It is not the place to invent the product strategy or to reopen commercial terms. Teams that work with SaaS product UX studios on our shortlist usually run this call within a week of signature so research and design can start without a second round of “who owns what.”
This guide is for founders, product managers and design leads who have just signed and want the first call to produce decisions, not a recording full of open questions. If you are still comparing UX design studios we evaluate for product engagements, use the checklist below as the agenda you ask each partner to follow once the papers are done. Below: what the kickoff is for, what to bring, a timed 75-minute agenda, a decision-rights map, the artifacts that must leave the room, a worked example, and a short FAQ.
What the Kickoff Is For (and What It Is Not)
The kickoff sits after selection and signature. The UX design contract and SOW already name the scope, fees and high-level deliverables. The kickoff turns that paper into a working agreement the people in the room can follow.
In the room you should:
- Confirm the business goal and how you will know the work succeeded.
- Name the decision maker and the people who advise or can block.
- Walk the first milestone and the dependencies that scare you.
- Agree communication channels, review cadence and response times.
- Capture decisions and first actions with owners and dates.
You should not:
- Re-run vendor selection or compare alternative partners.
- Rewrite the brief from scratch (bring a finished UX design brief or the SOW summary instead).
- Run discovery exercises such as MoSCoW prioritization, journey mapping or problem-statement workshops. Those belong in a discovery workshop when the problem is still open.
- Walk the entire UX design process end to end. Name the next phase and stop.
If the problem, users and release-one scope are still fuzzy, you need discovery, not a longer kickoff. Stretching a kickoff into a workshop produces sticky notes and no decisions.
Client Bring-List: Send These Before the Call
Send materials at least 48 hours ahead so the meeting critiques a plan instead of inventing one. I ask clients for this exact list:
- Named decision maker for scope and priority trade-offs, plus their backup if they miss a review.
- Signed SOW summary (goals, in-scope / out-of-scope, milestone dates, fees) — one page is enough.
- Product and brand access: live product or staging, brand guidelines, design system or UI kit if one exists.
- Evidence you already have: analytics for the flow in question, recent support tickets, sales call notes, past research.
- Technical and compliance constraints: platforms, integrations, security or legal review gates, accessibility bar.
- Stakeholder map draft: who must approve, who advises, who can block (legal, security, brand, a regional lead).
- Tooling preferences: where files live, where feedback is collected, preferred meeting cadence.
- Calendar reality: blackout dates, launch events, and any hard external deadline.
If an item is missing, say so in the invite. A kickoff that discovers on the call that nobody has analytics access or that Legal was never told about the project will burn the first two weeks.
Owners and Decision Rights
Most kickoffs fail on one sentence nobody says out loud: who decides when people disagree. Put this on the screen in the first ten minutes and leave it in the summary.
| Decision type | Decider (one name) | Advisers | Must be informed | Review SLA |
|---|---|---|---|---|
| Scope trade-offs inside the signed SOW | Client product lead | Design lead, eng lead | Sponsor | 2 working days |
| Visual / UI direction inside brand rules | Design lead | Brand, client marketing | Sponsor | 3 working days |
| Research plan and participant criteria | Design / research lead | Client CS or support | Product lead | 2 working days |
| Technical feasibility and sequencing | Eng lead | Design lead | Product lead | 2 working days |
| External blockers (legal, security, brand) | Named blocker owner | Design lead | Product lead | Agreed before kickoff |
Rules that keep the table useful:
- One decider per decision type. A committee is not a decider.
- Every “can block” person gets a dated touchpoint and a response SLA before design starts.
- Advisory input is welcome and not binding. Say that kindly in the room so comments do not become silent change requests.
Timed Agenda: 75 Minutes
This is the agenda I use for a post-signing UX kickoff with five to eight people. Adjust the minutes, not the order. Every block must leave a written output.
| Time | Block | Output it must leave behind |
|---|---|---|
| 0:00-0:05 | Why this, why now | Sponsor states the goal in their own words; urgency classified (real, directional, or internal target) |
| 0:05-0:15 | Success criteria and non-goals | Two or three verifiable criteria with baselines where they exist; at least two explicit non-goals |
| 0:15-0:25 | Roles and decision rights | Filled decision-rights table; blockers with SLAs |
| 0:25-0:40 | First milestone and scary dependencies | Milestone one date, deliverable, and named external dependencies |
| 0:40-0:50 | Working agreements | Channels, review cadence, response times, where files and feedback live |
| 0:50-1:05 | Risks and open questions | Top five risks or questions, each with an owner and a date |
| 1:05-1:15 | Actions and commitment | Action list with owner and deadline; round-the-room confirmation |
Facilitation notes I stick to:
- Send the draft agenda and SOW summary 48 hours ahead with one line: “Read before the call; we will decide, not discover.”
- If a fundamental disagreement about the goal appears, stop the agenda. A kickoff that surfaces “we do not agree” is still a successful kickoff — it just got expensive work cancelled early.
- Park feature debates. Write them on a parking lot and point back to the signed scope.
- Assign a note-taker who captures decisions and actions only, not a transcript.
For a 60-minute version, merge risks into the milestone block and cut working agreements to five minutes (send the channel plan async). For 90 minutes, add ten minutes after success criteria for a short walkthrough of existing research evidence — still no workshop exercises.
Artifacts You Must Leave With
A kickoff that lives only in people’s memories decays in about two weeks. Before the call ends, name who will publish each artifact and by when. My bar:
| Artifact | What “done” looks like | Owner | Deadline |
|---|---|---|---|
| Kickoff one-pager | Goal, success criteria, non-goals, milestone one, roles | Design lead | Same day |
| Decisions log | Each decision, options considered, why it won | Note-taker / PM | Within 24 hours |
| Actions list | Who / what / when for every first action | Note-taker / PM | Within 24 hours |
| Access checklist | Product, analytics, brand, repos, feedback tool — granted or blocked | Client ops + design lead | Within 48 hours |
| Calendar holds | First research readout, first design review, weekly status | Design lead | Within 48 hours |
If two or more of these are missing after 48 hours, the engagement has not actually started. Pause design work until they exist.
Worked Example: Series A SaaS Checkout Redesign
Illustrative numbers for this guide, not a client story. A Series A SaaS company signed a six-week UX engagement to redesign checkout. Eight people join a 75-minute kickoff: head of product (decision maker), head of growth, eng lead, CS lead, design lead, researcher, account lead, note-taker.
What the room decided:
- Success criteria: reduce median time-to-paid from 4.2 days (current analytics baseline) to under 2 days within 30 days of launch; cut checkout support tickets tagged “payment confusion” by half in the same window.
- Non-goals: no pricing-page redesign; no new payment provider in release one.
- Decision rights: product lead decides scope trade-offs; design lead decides UI inside brand; eng lead decides sequencing; Legal reviews claims copy with a 3-day SLA.
- Milestone one (day 10): research readout on five recent lost checkouts and a validated problem statement for the paid path only.
- Actions: CS lead shares last 40 checkout tickets by Friday; eng lead grants staging + analytics access by Wednesday; researcher schedules five customer calls next week; design lead publishes the one-pager today.
Notice what did not happen: no MoSCoW board, no journey map, no wireframes. The kickoff made the engagement runnable. The research and design phases do the product work.
Red Flags in the First Call
- No named decision maker in the invite list. Reschedule until one is confirmed.
- Sponsor sends a delegate who cannot break ties. You will re-litigate every review.
- Scope reopened (“while we are at it…”) without a trade-off against something already signed.
- Blockers discovered live (Legal, security, brand) with no prior touchpoint.
- No baselines for the success metrics people want to claim.
- Action list ends empty. If nobody owes anything by a date, the meeting was a presentation.
After the Kickoff: The First Two Weeks
The kickoff’s real test is week two:
- Ship the first status on schedule even if it is three sentences. Cadence dies if the first update slips.
- Chase silent blockers in week one while chasing is cheap.
- Answer the first “can you also…” with the non-goals list and a single sentence: log it, and the decider can trade it against something in scope.
At the end of milestone one, spend fifteen minutes against the kickoff one-pager: are the success criteria still right, did any risk upgrade, was any decision made outside the log?
FAQ
How is a kickoff different from a discovery workshop?
A kickoff assumes the problem and signed scope are clear enough to start. A discovery workshop is for when the problem, users or release-one scope are still open and need facilitated exercises. Do not stretch a kickoff into a workshop.
Who should attend?
Five to eight people: one client decision maker, one person who talks to users weekly, one technical lead, the design lead, and usually a researcher or facilitator. Add Legal or security only if they can block the work and have not already agreed a review SLA.
What if we only have 45 minutes?
Run success criteria, decision rights, milestone one and actions. Send working agreements and the risk list async the same day. Do not skip decision rights.
When should the kickoff happen?
Within five business days of signature, after access requests are filed and the bring-list is sent. Waiting two weeks usually means the team starts without shared rules and then “kickoffs” mid-project.
Do we need a new brief for the kickoff?
No. Bring the signed SOW summary and the brief you already used. If the brief is missing critical inputs, fix those offline before the call rather than drafting live.
Conclusion
A UX design kickoff checklist is useful only if it produces named owners, timed decisions and artifacts within 48 hours. Use the bring-list, the decision-rights table and the 75-minute agenda above as the working pack. Keep discovery workshops, brief templates and full process maps on their own pages. When the first call ends with a one-pager, a decisions log and a dated action list, research and design can start on Monday without another alignment meeting.
