[Programs](<https://www.thekeating.co/programs/>) / [Product development & quality](<https://www.thekeating.co/programs/product-development/>) / [Use cases](<https://www.thekeating.co/programs/product-development/use-cases/#main>)

[The development engine](<https://www.thekeating.co/programs/product-development/#look-inside>) [Start a review](<https://www.thekeating.co/contact/?source=discovery&landing_path=%2Fprograms%2Fproduct-development%2F&intent=discovery&cta_page=%2Fprograms%2Fproduct-development%2F&cta_placement=navigation&program=product-development>)

# Twelve jobs inside your development engine. Start with one, or build the whole thing.

Each one is designed, built in your accounts, then run by us or handed to your team. They share the same data, so each one you add makes the others work better.

1.  [Briefs **1**](<https://www.thekeating.co/programs/product-development/use-cases/#area-briefs>)
2.  [Specs & samples **4**](<https://www.thekeating.co/programs/product-development/use-cases/#area-samples>)
3.  [Suppliers & changes **3**](<https://www.thekeating.co/programs/product-development/use-cases/#area-suppliers>)
4.  [Release **2**](<https://www.thekeating.co/programs/product-development/use-cases/#area-release>)
5.  [Quality loop **2**](<https://www.thekeating.co/programs/product-development/use-cases/#area-quality>)

01

## Briefs

What to make, from what customers actually said.

-   Customer briefs
    
    ### Turn customer evidence into product briefs worth testing
    
    Briefs written from what customers said, with the sources attached and the open questions still open.
    
    1.  Gather
    2.  Group
    3.  Draft
    4.  Decide
    
    [Turn customer evidence into product briefs worth testing](<https://www.thekeating.co/use-cases/customer-briefs/>)
    

02

## Specs & samples

Accepted samples in fewer rounds, on one revision.

-   Development readiness
    
    ### Keep samples, tests and production readiness moving
    
    One register of every sample, test and quote by revision, so blockers show up with an owner before they move a date.
    
    1.  Define
    2.  Connect
    3.  Surface
    4.  Propagate
    5.  Confirm
    
    [Keep samples, tests and production readiness moving](<https://www.thekeating.co/use-cases/development-readiness/>)
    
-   Fit revisions
    
    ### Turn fit comments into the next revision
    
    Every fit comment checked against tolerance and tied to one revision, with a proposed fix your patternmaker approves.
    
    1.  Collect
    2.  Measure
    3.  Propose
    4.  Approve
    
    [Turn fit comments into the next revision](<https://www.thekeating.co/use-cases/fit-revisions/>)
    
-   Sample policy
    
    ### Decide which styles need a physical sample
    
    A written rule for which styles need a physical sample, with the history behind each call and the cost of getting it wrong.
    
    1.  Classify
    2.  Check history
    3.  Set policy
    4.  Track
    
    [Decide which styles need a physical sample](<https://www.thekeating.co/use-cases/sample-policy/>)
    
-   Block library
    
    ### Reuse approved blocks, materials and past fixes
    
    The next style starts from a block, a material and a fix that already passed.
    
    1.  Collect
    2.  Approve
    3.  Match
    4.  Reuse
    
    [Reuse approved blocks, materials and past fixes](<https://www.thekeating.co/use-cases/block-library/>)
    

03

## Suppliers & changes

Quotes on the approved version, and changes everyone sees.

-   Quote comparison
    
    ### Compare supplier quotes against the approved spec
    
    Every quote checked against the approved revision before anyone reads the price, with the real cost per unit beside it.
    
    1.  Receive
    2.  Check
    3.  Compare
    4.  Decide
    
    [Compare supplier quotes against the approved spec](<https://www.thekeating.co/use-cases/quote-comparison/>)
    
-   Specification change
    
    ### Trace a specification change to everyone it touches
    
    One change to a specification reaches the factory, the mill, costing, the lab, the studio and the catalog, and you see who has acknowledged it.
    
    1.  Spot
    2.  Trace
    3.  Release
    4.  Notify
    5.  Confirm
    
    [Trace a specification change to everyone it touches](<https://www.thekeating.co/use-cases/spec-change-impact/>)
    
-   Material substitution
    
    ### Qualify a substitute when a material runs short
    
    When a material runs short, the substitute is compared on total cost and tested before it ships, with the decision kept against the revision.
    
    1.  Trigger
    2.  Compare
    3.  Test
    4.  Decide
    
    [Qualify a substitute when a material runs short](<https://www.thekeating.co/use-cases/material-substitution/>)
    

04

## Release

Complete, evidenced packages before the factory starts.

-   Production handoff
    
    ### Hand off a complete production package
    
    A complete, versioned package that the factory confirms it has, before the first run starts.
    
    1.  Assemble
    2.  Check
    3.  Close
    4.  Confirm
    
    [Hand off a complete production package](<https://www.thekeating.co/use-cases/production-handoff/>)
    
-   Compliance evidence
    
    ### Keep compliance evidence tied to every product
    
    Every test report and certificate linked to the product and revision it covers, and ready when a broker or retailer asks.
    
    1.  Collect
    2.  Match
    3.  Check
    4.  Decide
    
    [Keep compliance evidence tied to every product](<https://www.thekeating.co/use-cases/compliance-evidence/>)
    

05

## Quality loop

Complaints tied to what shipped, and fixes that stick.

-   Complaint cohorts
    
    ### Tie every complaint to the revision and lot that shipped
    
    Complaints counted against what shipped, by revision and lot, so a problem shows up as a rate with a cause.
    
    1.  Collect
    2.  Classify
    3.  Join
    4.  Count
    5.  Flag
    
    [Tie every complaint to the revision and lot that shipped](<https://www.thekeating.co/use-cases/complaint-cohorts/>)
    
-   Corrective action
    
    ### Turn recurring quality issues into fixes that stick
    
    A recurring problem becomes a case with an owner, a fix and a check on the next lot that it held.
    
    1.  Open
    2.  Investigate
    3.  Fix
    4.  Verify
    
    [Turn recurring quality issues into fixes that stick](<https://www.thekeating.co/use-cases/corrective-action/>)
    

## Not sure which job comes first? A development review finds it.

[Start with a development review](<https://www.thekeating.co/contact/?source=discovery&landing_path=%2Fprograms%2Fproduct-development%2F&intent=discovery&cta_page=%2Fprograms%2Fproduct-development%2F&cta_placement=closing&program=product-development>) [**Talk it through first**15 minutes](<https://cal.com/nkeating/15min>)

We reply within one business day.

---

Source: [https://www.thekeating.co/programs/product-development/use-cases/](<https://www.thekeating.co/programs/product-development/use-cases/>)

[Contact Keating & Co](mailto:nelson@thekeating.co) · [Agent guidance](https://www.thekeating.co/llms.txt)