A product program goes sideways when the first meeting celebrates the idea and leaves the hard facts for later. A product design kickoff checklist keeps that meeting honest by naming who must be present, which goals and constraints are real. It also records which research already exists and which decisions still need an owner before anyone opens a sketch file.
This guide is for founders, brand leads, and agency partners starting a physical product. It is only the opening packet, not the full development path that follows. The product development process covers the stages that follow. Use the checklist below to decide whether concept work is allowed to start.
What a Product Design Kickoff Checklist Covers
A product design kickoff checklist is a short list of facts, owners, and open questions that a team confirms before design work begins. It is a working document, not a ceremony. If a line is blank, that line becomes the work of the meeting.
Physical products need a different list than a software sprint or a digital interface project. A screen can still change after launch. A molded housing, a sewn soft good, or a powered device cannot change as easily. The kickoff has to surface cost, volume, materials, safety, and the path to making the product before form exploration starts.
The Baldrige Excellence Framework from NIST treats leadership, strategy, customers, and operations as one performance system. A product kickoff is the small version of that idea. The team names what good means, who decides, and which evidence later reviews will accept.
Generic project agendas stop at goals, roles, and a timeline. That is useful, and it is not enough here. A physical program also needs the user, the use setting, the target cost, the first production volume, and the constraints that would kill a concept. Leave those out and the first concepts will answer the wrong question.
Treat the checklist as a gate, not a formality. Concept sketches may start when every required line is either filled or assigned to a named person with a date. A vague promise to circle back later is not a filled line.
Who Should Be in the Room
The room should be small enough to decide and complete enough to catch a bad assumption. Four roles matter more than the raw headcount.
The decision owner can accept a tradeoff in the meeting. That is usually a founder, a brand director, or the agency lead who owns the client relationship. If this person cannot attend, move the meeting to a day they can. A proxy who must "check with someone" turns every choice into a second meeting.
The product owner knows the user and the business result. They can say who the product is for, what job it replaces, and which claim the brand is willing to make in public. They also know which public claims are off limits.
A making lead should be present even if outside partners will build the product later. This person flags materials, assembly, and cost problems while they are still words. Product design work at Jackson Hedden starts with manufacturability, cost control, and market fit in the same conversation, because those three fight each other if they are planned in sequence.
Invite one person who will live with the result in the field: a buyer, a clinician, a retail partner, or a service lead. They will name constraints the core team treats as details. Keep silent observers out of the room. People who cannot speak in the meeting will not defend the record later.
Write the roster on the checklist before the invite goes out:
Decision owner, with authority to accept scope and cost tradeoffs.
Product or brand owner, with the user and the claim.
Making lead, internal or partner, for materials, assembly, and cost.
One downstream voice from sales, service, retail, or clinical use.
Note taker who is not also facilitating.
If a required person is missing, record the name and the date they will review the notes. Do not pretend a partial roster means the kickoff is complete.
Goals, Requirements, and Constraints to Lock
Goals, requirements, and constraints are three different lists. Teams blend them and then argue about taste. Separate them on the checklist so a disagreement has a place to land.
Goals say why this product exists.
A goal is a business or user outcome. Not a feature. "Win a design award" is not a goal. "A patient can use it at home without a training visit" is a goal. Write one primary goal and no more than two secondary goals. Extra goals become unofficial requirements and blow the first cost target.
State the goal in the user's setting. A product used in a wet kitchen, a clinic, a job site, or a carry-on bag fails for different reasons. If the team cannot name the setting, the goal is still a slogan.
Requirements say what must be true.
Requirements are testable. "Comfortable" is not a requirement. "A gloved hand can open the latch in one motion" can be tested on a model. Pull requirements from the user job, from safety or retail rules the brand already knows, and from promises already made to customers or investors.
Keep the first list short. Ten clear requirements beat forty soft ones. Mark each as must or should. A must that fails stops the concept. A should can move if cost or timing demands it, and the decision owner has to say so out loud.
Constraints say what the team cannot change.
Constraints are the walls. Typical ones for a physical product are target unit cost, first-run volume, and launch window. Also list forbidden materials, brand assets that must carry over, and channels that set pack size or weight. A constraint without a number is a wish. "Affordable" is not a cost. "Under a set retail price, at a named first volume" is a constraint.
Ask which constraint is allowed to bend if two of them conflict. Teams that will not answer that question in the kickoff will answer it after tooling money is spent. Put the answer in the notes.
The table below is the readiness check. Fill it in the meeting. A row marked Missing blocks concept work until an owner and a date are attached.
Kickoff input: Primary user and use setting.; Ready: Named person and place.; Partial: Audience only.; Missing: No user named.; What a gap blocks: Concept direction and test plan.
Kickoff input: Primary goal.; Ready: One outcome in plain words.; Partial: Several competing goals.; Missing: Slogan only.; What a gap blocks: Scope and success test.
Kickoff input: Must requirements.; Ready: Short testable list.; Partial: Mixed with wishes.; Missing: None written.; What a gap blocks: What the model must prove.
Kickoff input: Target cost and first volume.; Ready: Both numbers agreed.; Partial: One of the two.; Missing: Neither.; What a gap blocks: Material and process choices.
Kickoff input: Known constraints.; Ready: Listed with owners.; Partial: Named but unmeasured.; Missing: Not discussed.; What a gap blocks: Whether a concept is even allowed.
Kickoff input: Existing research.; Ready: Sources attached.; Partial: Anecdotes only.; Missing: None.; What a gap blocks: Whether new research is the next step.
Do not average the rows into a score. One Missing row on cost or on the user is enough to hold concept work. Partial is acceptable only when a named person will close it before the next working session.
Research Inputs to Bring, Not Invent
Kickoff is the wrong time to discover that nobody has talked to a user. It is the right time to lay existing evidence on the table and admit what is missing. Bring inputs. Do not invent them in the room to keep the meeting moving.
Useful inputs are specific. A competitor teardown, a return log, five interview notes, a retail planogram, a failed prototype, or a materials limit from a current supplier all count. A mood board with no source does not. If the only input is the founder's memory, write that down. Memory is a source, and it is a weak one.
Sort what you have into three piles before the meeting, then confirm the sort live:
Evidence the team will treat as fact, with a source named on the page.
Signals the team believes but has not checked. Name a test that would confirm or kill each one.
Questions nobody can answer yet. Assign each one to a person and a date.
That order matters. Facts set the requirements. Signals become the first prototype questions. Open questions become the research plan, not a hidden part of the concept phase. Prototyping is where a team makes a model to test a question. It is a poor place to discover that the question was never agreed.
Also bring the assets the product must live with. Logos, color limits, pack formats, instructions the brand already uses, and parts shared with a current product all constrain form. An agency partner should bring the campaign promise too. If the ad claim and the product reality do not match, the kickoff is the cheapest moment to say so.
When research is thin, the next step is research, not concepts. Say that in the notes. A short interview round or a look at returns will cost less than a month of forms that solve a guessed problem.
Decisions, Deliverables, and the Next Step
A kickoff fails when everyone leaves inspired and nobody leaves with a page. End the meeting with decisions, a packet, and one next block of work.
Decisions to record before anyone stands up.
Each decision needs an owner and a status: decided, deferred, or rejected. Deferred items need a date. Rejected items need a reason, or they return in the next review as if they were new.
Who the product is for, and who it is not for.
The single primary goal.
The must requirements, separated from the should list.
Target cost, first volume, and which constraint bends first.
Which research is accepted as fact.
What the next two weeks will produce, and what they will not.
If the decision owner will not close an item, mark it deferred. Do not let the group "generally agree." General agreement dissolves by the next morning.
Deliverables that leave with the team.
The packet can be short. Six pages of clear notes beat a slide deck nobody opens. Store it where the whole working team can find it, and date it.
Roster and decision rights.
Goal, must requirements, and constraints, including the numbers.
Research log with facts, signals, and open questions.
Decision log with owner and status.
Risks that could stop the program, each with a next check.
The single next step, with a date and what done means.
Risks at this stage are usually knowledge gaps, not production drama. Unknown user tolerance, an unproven material, a channel the brand has not sold in, or a cost target no similar product has hit are all kickoff risks. Later gates, including a first-article review, depend on this list being honest.
The next step is one block of work.
Pick one next block. Common honest choices are a research sprint, a requirements workshop, or a narrow form study. Do not start all three. The product development timeline is where a team plans the path from concept to shelf. The kickoff only chooses the first block and the date it will be reviewed.
Money and making capacity belong in that choice. A product development budget sets what the program can spend. The kickoff does not build the budget. It does record whether a budget exists, who owns it, and whether the first block fits inside it. If there is no budget owner, concept work is theater.
Run the meeting in this order so the packet fills itself:
Confirm the roster and who can decide.
Read the goal out loud and cut it to one sentence.
Walk requirements, then constraints, and mark conflicts.
Review research piles and retire anything that is only a hunch.
Log decisions, deferred items, and rejected ideas.
Name the next block, the owner, the date, and what done means.
Close by reading the Missing rows from the table. If any remain without an owner, the kickoff is not finished. Schedule the follow-up before people leave. A team that starts concepts on a partial packet will redo the work when the missing fact arrives.
Use the checklist as general guidance for a first working session. Brands and agencies that need a product to be buildable, not just presentable, still need a clear user, a clear constraint set, and a next step the team can finish. The work archive shows programs that reached a real product. When the product is ready to be made in volume, the manufacturing conversation covers suppliers, cost, and production support. That conversation belongs after the kickoff, not instead of it.
Frequently Asked Questions
What should a product design kickoff checklist include?
Include the decision roster, one primary goal, testable must requirements, numbered constraints, the research you already trust, open questions with owners, and a single next block of work. Add a decision log before the meeting ends. Leave out concept sketches until the missing rows have owners.
Who should attend a physical product design kickoff?
Bring the person who can accept a tradeoff and the person who owns the user and the claim. Also bring someone who understands materials and making, plus one downstream voice from retail, service, or clinical use. Skip observers. If the decision owner cannot attend, move the meeting.
How long should a product design kickoff meeting be?
Plan on one working session long enough to walk the checklist, often about 60 to 90 minutes when the packet was shared ahead of time. A first meeting with no pre-read will run long or finish with blank rows. Either outcome means you need a second session, not a rushed concept start.
How do you prepare for a product design kickoff?
Send the roster, the draft goal, and any research three days ahead. Ask each attendee to mark what they believe is fact and what is still a guess. Collect cost, volume, and channel limits from the decision owner before the meeting so the room is not inventing numbers live.
What is the difference between a kickoff and a design brief?
The kickoff is the meeting and the decision record. The brief is one document that may come out of it, or may already exist and serve as an input. This checklist does not teach brief writing. It checks whether the facts a brief would contain are actually known.
What should happen the day after kickoff?
The note taker sends the packet the same day. Owners of deferred items start those tasks. Everyone else does not open new concept directions. The next review looks only at the agreed block of work and the Missing rows that were supposed to close.
