Prototyping, modelling, testing

Imagine you want to bake a new type of cookie. You wouldn't bake 100 dozen cookies right away, would you? You'd probably try baking just one or two first to see if the recipe works, if it tastes good, and if it bakes properly. That's the idea behind prototyping, modelling, and testing in design!

• Modelling (say: MOD-uh-ling): This is like making a small, simpler version of your idea to understand it better. Think of it like drawing a map before you go on a trip, or building a small LEGO model of a house you want to build. It helps you see the big picture and how things fit together.

• Prototyping (say: PRO-toh-tipe-ing): This is like making that first test cookie. It's a rough, early version of your product that you can actually touch and try out. It might not look perfect, but it helps you check if the main parts of your idea work. For example, if you're designing a new phone, a prototype might just be a block of wood with buttons drawn on it, to see how it feels in your hand.

• Testing (say: TEST-ing): This is when you try out your model or prototype to see if it does what it's supposed to do. Does your test cookie taste good? Does your phone prototype feel comfortable? You try to break it, stretch it, or use it in different ways to find out what works and what doesn't. It's like playing a video game to find all the bugs before it's released.

Let's think about a company designing a brand new smartphone. They don't just draw it on paper and then start building millions of them. That would be super risky!

1. Modelling: First, they might create a CAD model (Computer-Aided Design model). This is like a super detailed 3D drawing on a computer. They can spin it around, look at it from all angles, and even see how the internal parts might fit together, all without building anything physical. They might also make a simple foam model (a physical model made from foam) to get a quick feel for the size and shape in someone's hand.

2. Prototyping: Next, they'd create several prototypes. The first might be a "looks-like" prototype – a non-working phone that just looks like the real thing, to see if people like the design and feel. Then, they might make a "works-like" prototype – a clunky, ugly version that has all the internal electronics working, but doesn't look finished. This helps them test the software and hardware separately.

3. Testing: Finally, they'd put these prototypes through rigorous testing. They'd drop them, soak them in water, press the buttons thousands of times, and have real people use them for weeks. They'd gather feedback like, "The camera button is too hard to reach," or "The battery dies too quickly." All this feedback helps them improve the design before the final product is made.

Here's the typical journey a design takes through modelling, prototyping, and testing:

1. Idea Generation: Designers come up with many ideas for a product.
2. Initial Modelling: They create simple sketches or basic 3D computer models to visualize the ideas.
3. Refined Modelling: More detailed models are made to explore specific features and how parts connect.
4. Early Prototyping (Rough): A quick, cheap prototype is built to test the core function or shape.
5. Testing Early Prototypes: Users or engineers try out the rough prototype and give feedback.
6. Iterative Design (Repeat!): Based on feedback, the design is changed and improved.
7. Advanced Prototyping (Closer to Final): More refined prototypes are built, looking and working more like the final product.
8. Extensive Testing: These advanced prototypes undergo lots of tests, including safety and durability checks.
9. Final Adjustments: Any last-minute changes are made based on the extensive testing results.
10. Production: Only after all these steps is the product ready to be manufactured for everyone.

Just like there are different types of cookies (chocolate chip, oatmeal, sugar!), there are different types of models and prototypes, each with its own job.

• Physical Models: These are tangible (you can touch them!) versions of your design. Think of a clay model of a car or a cardboard model of a building. They help you understand size, shape, and how it feels.
  • Scale Models: These are smaller (or sometimes larger) versions of the real thing, like a toy car that's a perfect miniature of a real car. They help you visualize big objects in a smaller space.
  • Mock-ups: These models often look like the final product but might not actually work. They're great for showing how something will look or feel.
• Graphical Models: These are drawings, diagrams, or computer-generated images. They are digital and don't take up physical space.
  • CAD Models (Computer-Aided Design): Super detailed 3D drawings on a computer that allow designers to see every angle and even simulate how parts move.
  • Flow Charts: Diagrams that show the steps in a process, like how an app guides you from one screen to another.
• Mathematical Models: These use numbers and equations to predict how something will behave. For example, engineers might use a mathematical model to predict how much weight a bridge can hold before it breaks.

Each type helps designers answer different questions about their product before it's actually built, saving time and money.

Even experienced designers can make mistakes! Here are some common ones and how to be smarter than them:

1. Skipping Testing: Some designers get excited and jump straight to making the final product without enough testing.
   • ❌ Wrong Way: "My idea is so good, I don't need to test it!" (Like baking 100 cookies without tasting the first one).
   • ✅ Right Way: Test early, test often! Even a quick, rough test can reveal big problems before they become expensive ones.
2. Testing Too Late: Waiting until the prototype is almost perfect before getting feedback.
   • ❌ Wrong Way: Spending months perfecting a prototype, then realizing users hate it.
   • ✅ Right Way: Get feedback from others (even friends or family) on your models and early prototypes. It's easier and cheaper to change a drawing than a finished product.
3. Not Learning from Mistakes: Testing reveals problems, but if you don't use that information to improve, the testing was useless.
   • ❌ Wrong Way: "Oh, the button broke during testing, but it's probably fine for most people." (Ignoring the problem).
   • ✅ Right Way: See problems as opportunities! Every broken part or negative comment is a chance to make your design even better. Iterate (make changes and try again) based on what you learn.
4. Only Testing One Thing at a Time: Focusing on just one part of the product and ignoring how it works with other parts.
   • ❌ Wrong Way: Testing if the phone screen works perfectly, but not checking if the battery lasts when the screen is on.
   • ✅ Right Way: Think about the whole system. How do all the pieces work together? Test different parts together to see if they cause new problems.