The last brand touchpoint nobody designs

When the brand color is already a safety color

Black+Decker's identity runs on orange. Under ANSI Z535, the standard governing safety labeling on US consumer products, orange is the assigned color for WARNING — one step below the red reserved for DANGER, one above the yellow used for CAUTION.

That's not a stylistic tension, it's a functional one. Use brand orange decoratively across a manual and every genuine warning has to compete with page furniture that looks exactly like it. Avoid orange entirely and the document stops looking like the brand at all. The system has to draw a line: where orange signals hazard, where it signals brand, and how a reader can tell in a quarter of a second.

The audience compounds it. Black+Decker sells to homeowners, not trade technicians — someone assembling in a garage with whatever tools are on the shelf, not a trained tech with a torque wrench and a service background. Every assumption a professional manual is allowed to make, a consumer manual has to earn.

Six documents, one system

Each piece has a different reader, a different press, and a different way of failing. The trim sizes aren't arbitrary — they're what the piece has to be to work where it gets used.

• Illustrated Parts Breakdown

  11 × 8.5 in · LandscapeBallooned exploded view with a fixed parts table — item number, part number, description, quantity. Landscape because exploded views are wide.

• Assembly Instructions

  8.5 × 11 in · Saddle-stitchedPictorial-first, minimal text. Hardware shown at actual size so a bolt can be laid on the page to identify it.

• Quick Start Card

  5.5 × 8.5 in · 12pt C1SWordless. Every instruction carried by image alone — the hardest constraint in the set, and the fastest test of whether the sequence works.

• Product Spec Sheet

  8.5 × 11 in · Two-sidedDimensioned orthographic views, specifications table, and a photoreal render sharing one page — the only piece where both belong.

• Safety & Compliance Insert

  5.5 × 8.5 in · FoldedANSI Z535 signal words and panels, ISO 7010 symbols, multi-language layout. Where brand orange yields entirely to the standard.

• Documentation Design System

  11 × 8.5 in · Plus templatesGrid, line weights, callout conventions, icon set, the orange rule, type scale — and the working Word and InDesign templates behind them.

One CAD source, every deliverable

The pipeline matters more than any single page. Illustrations are generated from the CAD assembly rather than traced from renders, so part hierarchy, names, and quantities carry through into the parts table instead of being retyped — and when the model changes, the figures follow.

The assembly comes in as STEP with its tree intact, then gets restructured: engineering organizes parts by how the product was designed, and documentation needs them ordered by how it gets built. Different trees, and the second one belongs to the reader. Sequencing happens before any art is drawn — steps ordered and failure points flagged as a written outline with thumbnails, while changes are still cheap. Mirrored parts, similar-looking hardware, and orientation-dependent pieces are where consumer assembly actually goes wrong.

Only then does line art get made, and it gets made to the constraint. In-box literature prints one or two colors on lightweight uncoated stock, often web press. That rules out gradients, fine screens, and reversed type below 8pt, and it sets a floor on line weight. Photoreal renders are reserved for the spec sheet, which is printed properly.

Compliance as the default output

The orange rule is the clearest example of what a documentation system is for. Brand orange is permitted in headers, step numbers, and structural furniture. It is prohibited anywhere inside a safety panel, where ANSI Z535's signal-word colors govern absolutely. One rule, written down once, and the conflict never has to be argued again.

Every PDF in the set is delivered tagged, with defined reading order, alt text on all figures, and color pairings verified against contrast requirements rather than assumed to pass. Accessible documentation usually gets retrofitted after layout, which is when it's most expensive and least effective. Building it into the templates means compliance is what the template produces by default rather than a remediation pass.

That's the same instinct behind the Tensar render library and every asset system I build: solve it once, structure it so it's reusable, and hand it over in a state where the routine case never comes back to the designer.

A system, not a set of files

The deliverable that matters isn't any single document. It's the templates and standards that produce all six consistently, and would produce the seventh without me. Grid, type scale, line weights, callout conventions, the orange rule, and accessibility settings live in the template rather than in the head of whoever laid out the last one.

Which is the argument for treating in-box literature as a brand surface in the first place. It's the cheapest document in the product and the only one every customer is guaranteed to read.