Real-Life Problem Solver - Guided Extension
Estimated time: 4-8 hours (design, adapt, print, and document)
Learning Objectives
- Identify a user problem and evaluate candidate printed solutions
- Adapt an existing model to meet real constraints and safety requirements
- Test, measure, and iterate on a prototype with documented decisions
Materials
- Computer with slicer and access to repositories
- Printer, filament, basic hand tools for post-processing
Step-by-step Tasks
- Interview a potential user (or yourself) and write a 1-paragraph problem statement.
- Search repositories for candidate models; list three options and justify which one you will adapt.
- Adapt the model (scale, add mounts, or modify features) and document the changes in a short changelog.
- Slice, print, and run a supervised test of the prototype; log any failures and corrective actions.
- Produce a final report summarizing performance, measured deviations, and next steps.
Probing Questions
- What assumptions did you make about the user’s context? How could you validate them?
- Which adaptation had the biggest impact on function and why?
Quiz - Your Second Print (10 questions)
- What is a good first question to ask a stakeholder when scoping this project? (short answer)
- Name one safety consideration when adapting a model for daily use. (short answer)
- What is a changelog entry? (one sentence)
- How do you verify a fit for an assembled part? (short answer)
- Why document corrective actions during testing? (one sentence)
- True/False: Once you complete a successful first print, any second project will automatically succeed without iteration. (Answer: False)
- Short answer: Describe one method to gather user feedback on your adapted model before committing to a full production print.
- Practical scenario: Your adapted model prints but feels too fragile in daily use. What are two strategies to improve durability while maintaining the basic form?
- Multiple choice: When you create a changelog, what should you document? (A) Only the successful changes (B) All changes, including failures and iterations (C) Only the slicer settings - Answer: B
- Reflection: Explain how iteration (design -> print -> test -> adapt) leads to better functional outcomes than trying to get the design perfect on the first attempt. Give a specific example from your project.
Extension Problems (10)
- Rework your prototype to improve durability and report trade-offs in weight and print time.
- Create a user test script and run it with two participants; summarize results.
- Convert a critical component to parametric OpenSCAD and publish the variant.
- Add a small assembly guide with tactile cues for non-visual users.
- Compare two filament types for the same part and recommend one with justification.
- Execute a formal design iteration cycle: print, test, measure, analyze, revise; repeat at least 3 times and document improvements.
- Build a comparative analysis: print your part in 2 different materials or with 2 different profiles; measure and compare all key properties.
- Create a complete design dossier: CAD files, iteration history, test results, measurements, lessons learned, and final recommendations.
- Develop a user testing protocol: define success metrics, recruit testers, gather systematic feedback, and iterate based on results.
- Write a design case study: document your entire project journey from initial concept through final manufacture, including all mistakes and successes.