In September 2026, Indonesia's Ministry of Industry launched its Design Canvas & Design Maker programme under the theme “Read the Market, Design the Product” for small and medium-sized fashion and craft businesses. Participants are encouraged to understand consumers, their needs and market opportunities before moving from concepts into prototypes and product refinement.
The message is simple, but it addresses a common problem in creative work.
Teams begin designing too quickly.
The moodboard opens. References accumulate. Colours are selected. Forms begin to take shape.
Yet a more important question remains unresolved:
What problem are we actually trying to solve?
A Moodboard Is Not the Starting Point for Every Product
Moodboards have a legitimate role. They can align a team around atmosphere, visual language, materials, tone and references.
But a moodboard cannot tell you whether a customer needs an additional pocket in a garment, whether packaging is difficult to open, whether a product fits the space in which it will be used or whether a dashboard contains the information required for an everyday decision.
That is the difference between designing the appearance of a product and designing the product itself.
Indonesia's Ministry of Industry makes a similar distinction in its 2026 Design Canvas programme. Participants first explore business potential, consumer needs and preferences, and market opportunities. Design Maker then moves concepts into prototyping and refinement while considering design, function and the potential for higher-value products.
This does not mean creativity must wait for a spreadsheet full of research.
It means creativity should understand the question it is attempting to answer.
User Needs Are Not the Same as Following Trends
Being market-oriented can easily be misunderstood as following whatever is currently popular.
Trend awareness is only one input.
In fashion, customers may want a certain visual style, but purchasing decisions can also depend on comfort, care requirements, sizing, garment length, climate and where the item will actually be worn.
In F&B, premium-looking packaging can still fail if it leaks, stacks poorly or does not protect the product.
A digital dashboard may look contemporary while remaining ineffective if users need several unnecessary steps to reach the action they perform every day.
Indonesia's 2026 Creative Business Incubator programme also emphasised understanding customer needs, customer problems and value propositions in developing fashion and craft businesses.
Reading the market therefore means asking more than:
“What do people currently like?”
It also means:
“What are customers trying to do, and what makes that difficult?”
Find the Problem Before Locking the Solution
The same principle appears in one of the most widely recognised design frameworks, the Design Council's Double Diamond.
It begins with Discover—understanding the challenge and user needs—followed by Define, before moving into Develop and Deliver. The process does not begin by selecting a finished solution. It first expands understanding of the problem and then narrows that understanding into a clearer challenge.
For digital systems, ISO 9241-210 similarly places human-centred activities throughout the lifecycle of interactive-system development, with attention to users and the context in which systems are used. Its scope is interactive systems rather than every category of physical product, but the principle reinforces the value of understanding use before finalising a solution.
For businesses, this early stage can feel slow because it does not immediately produce something that looks finished.
Yet it is precisely when change is still inexpensive.
Changing an assumption before production is usually very different from changing tooling, packaging, inventory or an entire interface after launch.
Constraints Are Not the Enemy of Creativity
Designers are not designing only for users.
Products must survive the real world.
There is a selling price.
Material cost.
Minimum order quantity.
Production equipment.
Regulation.
Distribution.
Packaging dimensions.
Warehouse capacity.
Technical limitations.
Development time.
A solution that customers like but that cannot be manufactured or supported with viable economics is not yet successful product design.
That is why constraints should enter the process relatively early.
A chair may need to fit a specific environment. A garment needs a realistic size range. Packaging must survive distribution. A digital feature must be supported by backend systems and operational processes.
Constraints do not necessarily reduce creativity.
They often create a better brief.
A Prototype Is a Question, Not a Miniature Final Product
Another common mistake is treating the prototype as a presentation.
Its primary role is to help the team learn.
A prototype can reveal whether a handle is comfortable, whether a garment moves properly, whether a label can be understood, whether packaging opens easily or whether someone can navigate an application without being instructed.
The Design Council places development, testing and refinement before the final solution is selected and prepared for delivery.
The more polished a prototype becomes too early, the easier it is for a team to become emotionally reluctant to change it.
The best prototype is not always the most beautiful one.
It is the prototype that resolves the most important uncertainty before the next major investment is made.
From Problem to Form
As a simple working framework, GATICORP views early product development through the sequence:
Context → User → Problem → Constraint → Value → Form
Context: under what conditions will the product be used?
User: who will actually use it?
Problem: what friction or need should it address?
Constraint: what business, production, technology and regulatory limits exist?
Value: why is the solution useful or worth choosing?
Form: what shape, interface, material and expression should it take?
This is not a universal design methodology, and the steps do not always need to be linear.
It simply reinforces one principle: form arrives after enough of the surrounding problem has been understood.
Colour, typography, material, shape and detail do not become less important.
They become better informed.
Good design is not anti-aesthetic.
It allows aesthetics to strengthen a product that already has a reason to exist.
Before asking “What should this product look like?”, businesses should first be able to answer a more fundamental question:
“Who is it for, and why do they need it?”
Sources & Editorial Notes
- Indonesia Ministry of Industry/BPIFK — “Kemenperin Strengthens Fashion and Craft SMEs through Market-Based Design Innovation,” 2 October 2026. Used as current context for Design Canvas & Design Maker 2026, its consumer-oriented and co-creation approach, consumer-needs discovery and the movement from concepts into prototyping.
- Indonesia Ministry of Industry — Creative Business Incubator 2026, August 2026. Used for context on customer needs, consumer problems and the Value Proposition Canvas in fashion and craft business development.
- Design Council — The Double Diamond. Used as a reference for the Discover, Define, Develop and Deliver process. The Double Diamond is a widely used design framework, but this article does not claim that every project must follow it linearly.
- ISO 9241-210:2019 — Human-centred design for interactive systems. The 2019 edition remained current following review and confirmation in 2025. Used as a reference for human-centred design of interactive systems. Its scope primarily covers interactive systems and is not generalised here as a design standard for all physical products.
- Examples involving fashion, packaging, F&B and digital interfaces are editorial illustrations rather than findings measured against particular companies or products.
- The Context → User → Problem → Constraint → Value → Form sequence is a GATICORP editorial framework, not an official framework issued by the Ministry of Industry, Design Council or ISO.
- The article does not argue that aesthetic exploration or moodboards are unimportant. Its argument is that visual decisions are stronger when built on sufficient understanding of context, users, problems and constraints.
Published: October 8, 2026
