Chapter 4 — Try and the Failures That Teach

Try is a small salamander-tween (chunky-cartoon soft-skin NOT slimy) with chunky-cartoon iteration-numbered prototypes (v1, v2, v3) lined up on her workbench.

She is small, warm-amber-with-cream-spots, deeply patient-about-iteration, fond-of-saying-”first try fails, second try tells, third try shapes the design.” Her signature feature is the row of iteration-numbered prototypes — each labeled with what went wrong + what to change for the next. Try treats prototypes as DATA, not as products.

This is load-bearing. Try embodies the prototyping + iteration primitive — the heart of design-process pedagogy. AND Try carries the LOAD-BEARING gate that frames first-failure as expected, not as personal-failing. Most novice makers see prototype-1 failure as evidence “I can’t do this.” Try corrects: first prototypes are SUPPOSED to fail in informative ways. The failure tells you what to change for prototype-2. Prototype-2 fails differently, telling you what to change for prototype-3. By prototype-3, the design starts to shape. Try’s whole work is normalizing the iteration-as-design-process AND removing perfectionism-shame from the first-failure.

Try is clear and gentle: “First try fails, second try tells, third try shapes the design. Iteration is the design, not the failure. When your prototype-1 doesn’t work, that’s not ‘I failed.’ That’s ‘the project is doing what it should — telling me what to change.’”

Try teaches the prototyping scaffolds:

• Prototypes are DATA. (Not products. Their job is to teach you what works + what doesn’t. The next prototype incorporates the lessons.)
• Iterate quickly + cheaply. (Don’t make the first prototype with expensive materials. Cardboard + tape. Foam + glue. Sketches. Cheap prototypes fail informatively + are easy to discard.)
• Iteration numbering. (Label v1, v2, v3. Each gets its own notes. Visible iteration = visible learning.)
• Failure-mode documentation. (What broke? When? Under what stress? Write it down. The failure-mode is the design-input for the next version.)
• Anti-perfectionism gate. (LOAD-BEARING: prototype failure is NOT personal failing. The design process EXPECTS first prototypes to fail. If prototype-1 worked perfectly, you probably weren’t aiming high enough.)
• Convergence timing. (Not every project converges quickly. Some take 5 prototypes. Some take 20. Knowing when to keep iterating vs when to ship is craft.)
• Cross-app design language with FlightForge “I missed; I missed; I hit”: Try’s iteration framing parallels FlightForge’s engineering-failure-as-data pattern. Same principle, different domain.

Try grew up in the spring-pool village (MakerForge framing). Her family had been moisture-experimenters for the village — the salamanders whose skin needed careful moisture-balance, learning over generations that each individual tested a thousand microenvironments before finding the right one. They learned that “experimentation IS the way; first-try-fails is how you find the second-try-tells.” Try had carried the lesson forward.

She walked to MakerForge at twelve. Spool (mentor) had asked: “What is prototyping?” Try: “First try fails, second try tells, third try shapes the design. Iteration is the design, not the failure. Prototypes are DATA. Failure-modes are design-inputs.” Spool: “You are appointed.”

In her workshop, Try shows the row of prototypes. “V1 of plant-waterer: water flowed too fast; plant flooded. Lesson: needs flow-restrictor.” She points to v2. “V1’s lesson incorporated. V2 had restrictor + … water flowed too slowly; plant dried. Lesson: restrictor too tight.” V3. “Restrictor adjusted. V3 worked for 3 days, then clogged with mineral residue. Lesson: needs cleanable design.” V4. “Cleanable design. Working well in 1-week test. 4 prototypes; design now shaped.” She says: “I am Try. The primitive I teach is prototyping + iteration. The move is first try fails; second try tells; third try shapes. The failures aren’t failures — they’re data.”

She is gentle: “Don’t be discouraged by your first prototype not working. That’s not ‘you failed.’ That’s ‘the design is doing its job — telling you what to change.’ Maker-craft is iteration. Iteration is built from intelligent failures. Make peace with the failure pile.”

“Iteration is the design. Failure is the feedback. Wear the iteration-pile with pride.”

Voice register

Salamander-tween (chunky-cartoon soft-skin, NOT slimy). Patient-about-iteration, fond of prototype-row demonstration. NEVER frames failure as personal-failing; ALWAYS centers “iteration is the design; failure is feedback” LOAD-BEARING reframe.

Sample lines:

• “First try fails, second try tells, third try shapes the design.”
• “Iteration is the design, not the failure.”
• “Prototypes are data.”

Arc

• Kit 4 — Anchor (LOAD-BEARING anti-perfectionism gate).
• Kits 5-16 — Recurring (every project includes Try’s iteration phase).

Relationships

• Builds on Spec + Mill: Within Spec’s commitments + Mill’s safe builds, Try iterates.
• Cross-app design-language continuity with FlightForge (“I missed, I missed, I hit”): Same anti-failure-shame pattern, different domain.

Cultural-sensitivity gate

LOAD-BEARING failure-as-design-process anchor. Anti-perfectionism explicit. Failure-mode documentation as craft (not as evidence of inadequacy). Off-ramps via “ship when convergence appears” (no infinite iteration required).

Cultural-context note

The “iteration as the design” framing is canonical design-thinking pedagogy (IDEO + Stanford d.school + Tom Wujec’s Marshmallow Challenge). The failure-as-data framing aligns with engineering-design tradition (Henry Petroski’s To Engineer is Human). Salamander-tween chosen for moisture-experimentation biomimicry; rendered chunky-cartoon-soft-skin to defuse “slimy amphibian” coding.