01Why does "process design" decide quality?
Most rework is born not of a lack of ability but of the absence of process. "Just make it, and check when it's done" — this ad-hoc way concentrates checking at the end, and when a problem is found there, all prior phases must be redone.
The idea that prevents this is lifecycle design. Distribute checks (gates) through the middle of the process, and at each phase judge "may we proceed to the next?" Catch a problem near the phase where it arose. The earlier you catch it, the smaller the rework (this increase is quantified in section 05).
Process design is not something to think out from scratch for each case. Hold one standard lifecycle, and adjust it to the scale and medium of the case. The 10 phases this volume shows are the template for that standard.
02The whole course of a received case — 10 phases
Break the whole course of contract production into 10 phases. For each, make explicit the main work and the main owner.
| # | Phase | Main work / check |
|---|---|---|
| 1 | Receiving the request | Confirm SoW, responsibility boundary, confidentiality; first judgment of advertising applicability (Vol. 1) |
| 2 | Concept confirmation | Fix the intended appeal and the primary sources to reference (package insert, approved scope) |
| 3 | Regulatory map | Lay out the applicable norms in four layers (Vol. 3) |
| 4 | Production | Actual production while referencing the regulatory map |
| 5 | AI check | First-pass screening of violation candidates (Vols. 5 & 6) |
| 6 | QC | Quality check of consistency, typos, citations, visual elements (Vol. 7) |
| 7 | QA | Assurance of regulatory compliance, the deliver/return decision (Vol. 8) |
| 8 | Delivery | Signed delivery, attaching the grounds of judgment (Vol. 10) |
| 9 | Audit response | Presenting records to client review and regulatory queries |
| 10 | Record-keeping | Storing the decision process and version control (Vol. 10) |
This phase list can be merged or omitted according to scale. Adjustments like merging 5 and 6 for a small case are free. But the four — "applicability judgment (1)," "fixing primary sources (2)," "regulatory map (3)," and "QA (7)" — are not omitted for any case. This is the minimum line of process design.
03Where to place the quality gates
Placing a gate between all 10 phases is excessive. From rework cost and detection effect, concentrate resources on four main gates.
- Gate A (after phase 2): Are the concept and primary sources fixed? Entering production while this is vague yields the most expensive rework
- Gate B (after phase 3): Is the regulatory map exhaustive? An omission of an applicable norm is hard to catch downstream
- Gate C (after phase 6 = QC): Does the produced material meet the standard for quality (consistency, citation, visuals)?
- Gate D (after phase 7 = QA): Is regulatory compliance assured, and may it be delivered? The last line of defense
Gates A and B are upstream gates, C and D downstream gates. What is most slighted in vendor quality management is the upstream gates — pressured to start making things fast, the confirmation of concept and regulatory map gets skipped. But rework cost is maximized when an upstream gate is skipped (section 05).
04Make the gate's pass criteria explicit
A gate must not be passed on "it seems fine somehow." Define for each gate explicit pass criteria (a checklist).
"It's roughly done and seems fine, so on to the next."
The pass criteria are not put into words. The judgment depends on the person's feel, varying by person and by day. Later you cannot explain "why it was passed."
"Gate B pass criteria: (1) the applicable medium's norms are listed in four layers; (2) each efficacy/effect statement is tied to the corresponding line of the package insert; (3) points to confirm are listed and assigned to owners — confirm all three are met."
The conditions of passage are itemized, and whoever judges reaches the same conclusion. The judgment is also recorded.
The principle of building pass criteria is one: build "points that could be flagged later" into the gate criteria in advance. Turn points flagged in the past by internal review or the client into criteria, and the same omission never happens again (this idea is explored in the check regime of Vol. 4).
05The earlier the gate, the cheaper — the escalation of rework cost
Why are upstream gates important? Because rework cost grows exponentially the further downstream the process.
| Phase where the problem is found | Range of rework | Relative cost |
|---|---|---|
| Concept confirmation (2) | Only the direction is corrected | Small |
| During production (4) | Remake of the relevant part | Medium |
| QA (7) | Major revision of the material, re-QC | Large |
| After delivery / audit (9) | Recall, revision, trust damage | Maximum (includes irreversible) |
06Make responsibility allocation explicit — separate the maker and the checker
Another pillar of process design is responsibility allocation. Assign to each phase a "main owner (who makes / drives)" and a "checker (who judges the gate)", and separate the two.
- Separation of making and checking: The person who produced something does not double as the QC/QA of their own work. One's own oversight is hard to see oneself (the same principle as the Material Review series)
- Explicit checker per gate: For each main gate, decide in writing who bears responsibility for the pass judgment. Eliminate "somehow everyone looked at it"
- A designated escalation target: Decide in advance to whom the checker raises a judgment when in doubt
Making responsibility allocation explicit supports not only quality but the response when trouble arises. If "at which phase, who, checked what" is recorded, even when a problem occurs you can identify the phase of cause and move to improving the process rather than a person-dependent hunt for the culprit (the specifics of records are in Vol. 10).
07A self-check for lifecycle design — three questions
When designing the process of a new case, three questions to check.
- "Are the four mandatory phases (applicability, primary sources, regulatory map, QA) built into the process?" — If any is missing, do not omit it on grounds of scale. Hold the minimum line
- "Does each main gate have explicit pass criteria?" — If not, turn "points that could be flagged later" into criteria. Do not pass on feel
- "Is a main owner and a checker assigned separately to each phase?" — If they are combined, separate making and checking
Start production only after a process design to which you can say "yes" on all three. The time spent on design returns many times over in downstream rework saved.
08Summary — "design" the process per case
The points of this volume. (1) Quality is secured not by adding at the end but by gates distributed through the process. (2) A received case breaks into 10 phases, and at least 4 (applicability, primary sources, regulatory map, QA) are not omitted. (3) Make pass criteria explicit at the four main gates, and allocate investment with weight upstream. (4) Assign a main owner and a checker separately to each phase.
"Rather than spend time on design, I want to start making things fast" — on the floor of contract work, this temptation is always there. But a case that runs off without designing the process will surely stall somewhere downstream and be remade all the way back upstream. The first time spent on design is not a cost but the greatest time-saving investment.
Hold one standard lifecycle and adjust it per case. Place pass criteria at each gate, and separate the one who makes from the one who checks. These are not "carefulness" but the engineering of fast and reliable production. From individual-dependent quality to quality anyone can reproduce — that skeleton is the process design of this volume.
Vol. 3 (in preparation) takes up the core of phase 3 — the regulatory map. It organizes the PMD Act, advertising standards, the MSA guideline, and JPMA into four layers and makes concrete the procedure for mechanically mapping received materials. From the next volume, we fill in the content of the process designed here.