Designing systems — Design, 14–17 years
A product is rarely alone: it sits in a network of parts, people, rules and resources. Systems thinking helps you notice how changing one part can change everything around it.
Idea
A system is a group of connected parts that work together, such as a bike, a school canteen or a bus network. In design, you look not only at the object but also at what enters it, what leaves it and who depends on it. The connections often matter as much as the parts.
Why
Designers use systems thinking because a solution can fix one problem while creating another. A faster delivery service may increase traffic; a cheap package may create more waste. Looking at the whole system helps you find effects that are easy to miss when you focus on one object or one user.
Worked example
A school wants fewer disposable cups. First, map the system: students need drinks, taps provide water, cups are bought and bins receive waste. Next, test a reusable-cup scheme: students borrow a cup, return it, and staff wash it. The design must include deposits, washing time and enough cups, not just the cup itself.
Common trap
A reasonable mistake is to improve the visible part and ignore the surrounding routine. A designer might make a brilliant reusable cup but forget that nobody knows where to return it. This happens because the object is easy to draw and show, while habits, staff time and rules are less visible. A system map makes them visible.
Where it is used
Systems thinking appears in transport, healthcare, websites, energy and public services. When a city redesigns a junction, it considers pedestrians, cyclists, buses, cars, timing and safety together. It is useful whenever several people or parts depend on one another and a local change could have wider consequences.
Keep exploring
Other languages
Loading MyLeoNes™…