A full-scope industrial design engagement breaks down into nine deliverables: requirement mapping, competitor and user research, concept sketches, 3D modelling, CMF, mechanical design, prototype follow-up, tooling follow-up and mass-production support. Contracts usually list the first six. The last three are either absent or written without a definition of done - and that is where projects go wrong later.
We reviewed sixteen full-scope projects. Eleven had delivery disputes, and all eleven sat in the last phase. Seven of those were about tooling follow-up: nobody had written down who goes to the toolmaker, how many times, and at which milestones.
Requirement mapping is not a meeting note. Its deliverable is one page of design input: target user, usage scenario, competitor price band, and the hard constraints - dimensions, weight, certifications, cost ceiling. Without that page, every design review turns into a vote on taste.
Research and sketching need numbers too, because numbers prevent the "here is one option, pick it" shortcut. Our standard is at least eight competitor teardowns, at least three concept directions, and for each direction two main views plus one detail view.
In the second phase, 3D comes first and CMF runs in parallel with mechanical design. 3D fixes form and part split; CMF fixes colour, texture and process; mechanical fixes wall thickness, snaps and assembly. The order matters: talk about CMF before the form is settled and colour chips will not follow the curvature; build mechanical first and a later CMF process change forces new draft angles and etch depths. CMF is the part most often reduced to "colour recommendations with a few renderings". A CMF package that survives prototyping contains four items: colour reference numbers with suppliers, texture grade numbers, surface treatment specification, and a colour tolerance in Delta E.
The third phase is routinely compressed into one line, "support sampling and production". When something goes wrong each side has a different reading: the client expects the designer on the line, the designer thinks a drawing set counts as support. Writing three verifiable clauses takes ten minutes: for prototypes, how many rounds, which process, who pays, who owns the issue list; for tooling, attendance at T0 and T1, who issues change requests, how many rounds are included; for production, how many units of the first batch are covered, response time, and rates beyond that.
Scope also has to state revision counts. Two rounds per phase is our norm, and "until satisfied" sounds generous but in practice gets absorbed through delay. Defining what counts as a round - a direction change counts, a local dimension tweak does not - keeps both sides on the same schedule.
Top comments (0)