03 / 04Manufacturo2023Product Designer5 months

The compliance system that closed million-dollar aerospace contracts.

Dealbreaker to differentiator. Nonconformance tracking became the feature that let Manufacturo close aerospace and defense contracts — moving from a gap customers cited as a dealbreaker to a feature mentioned positively in competitive evaluations.

Manufacturo's nonconformance list, with a defect record opened from within a work order
Fig. 01 · Nonconformance tracking inside the manufacturing workflow
The problem

Without AS9100-compliant nonconformance tracking, you can't sell to aerospace.

Compliance gap

The existing system couldn't generate the documentation AS9100 auditors require. AS9100 is the quality-management standard that governs aerospace manufacturing.

Workflow gap

There was no structured way to move a defect from discovery through disposition to resolution with multiple stakeholders involved.

Visibility gap

Without trend analysis, quality teams couldn't identify recurring defects. They were reacting to the same problems on repeat.

Manufacturo was positioned to compete for this market. The platform was capable, but every serious prospect in aerospace and defense hit the same wall: no compliant nonconformance tracking meant no deal. Millions of dollars in contracts were blocked by one missing feature.

What they had vs. what aerospace requires
Existing system

A lightweight nonconformance tracker designed for high volumes of identical units, with simple defect routing: pass or fail.

What AS9100 requires

A complete chain of accountability: document the defect, create a disposition to fix it, evaluate the plan, stamp approval, execute the fix, verify the work, and track for trends. Multiple steps, multiple stakeholders, a full audit trail.

Designing the solution

The gap was blocking sales.

Speed versus documentation depth. The quality engineer needs to move fast under pressure. The compliance officer needs a complete record that may not be needed for months. These are in direct conflict. I solved it by designing documentation to happen as a byproduct of the workflow itself: the quality engineer does their job, and the audit trail builds itself.

Changing the mental model
Old mental model

Part broken? Tag it, set it aside, move on.

New mental model

A full chain of accountability, from discovery through resolution.

Decisions
  1. Decision 01

    Get the full scope agreed before the first wireframe.

    Early conversations made it clear that documentation alone wouldn't satisfy AS9100 auditors, and workflow alone wouldn't close deals. I built the case that three components had to ship together:

    • Workflow integration — technicians can automatically pause work when a defect is found.
    • Defect logging — a wizard captures the critical information and groups similar defects, so trends can be analyzed later.
    • Defect resolution — solving a defect is called dispositioning, and its discrete steps (planning, approval, execution, verification) need a clean, managed workflow.

    Solving two of the three wasn't a partial win. It was a failed product. I got leadership aligned on the full scope before a single wireframe existed.

    The three pieces: flagging a defect from within a work order, the issue-creation wizard, and the issue-resolution workflow with disposition type, risk assessment and approvals
    Fig. 02 · Flag a defect from within the work · the issue wizard · the resolution workflow
  2. Decision 02

    Design the data model for the questions that come later.

    The schema optimized for fast defect entry is not the schema that supports trend analysis six months later. Most teams discover this after the fact, when they try to add corrective-action reporting on top of mounds of data. I designed the data model to support all three layers from day one, even though trend analysis wasn't on the immediate roadmap. When corrective action was green-lit, it shipped in weeks instead of months, because the architecture was already there.

  3. Decision 03

    Reject the linear approval chain.

    Under production pressure, people don't work in order. A linear chain gets routed around, and an audit trail full of workarounds is worse than no audit trail. The data model allowed parallel disposition tracks, so multiple defects from the same inspection could each progress independently. Production kept moving, and the audit trail stayed clean.

  4. Decision 04

    Surface schedule risk to the planners.

    Defects affect the manufacturing schedule. Automatically pausing the work order helps the technician on the floor, but the risk to the schedule has to reach the production planners. I added visual cues so potential changes to timing surface where they're managed, and resolved issues are tracked through final assembly.

Outcomes

Results.

40 → 10Minutes to document

A roughly 40-minute effort became a roughly 10-minute guided wizard.

2Major customers unblocked

The release unlocked sales to two customers previously blocked by missing compliance support — the best quarter in company history.

ZeroExtra work for the audit trail

Audit-ready reports generated automatically from normal workflow records.

  • The system worked under pressure

    Quality engineers stopped routing around the system because it was faster to use it than to work outside it.

  • The audit trail built itself

    When auditors asked for Q2 nonconformance documentation, the answer was a report, not a two-day email dig.

  • Dealbreaker to differentiator

    Nonconformance tracking moved from a gap customers cited as a dealbreaker to a feature mentioned positively in competitive evaluations.

  • Major sales closed after release

    Two key sales that would not have been possible without nonconformance reporting.