From an open brief to a fixed form
The client had a direction, not a definition. This is the account of how the problem was named — and why the answer looks the way it does.
Stakeholder input, traced
A brief with no fixed edges
Three rounds of stakeholder review surfaced competing priorities: brand visibility, operational simplicity, and cost ceiling. Each shaped a decision.
The initial brief named a feeling, not a function. Before any design could begin, the actual problem had to be isolated from the surrounding noise.
The constraint that looked like a limitation — a fixed print budget — became the structural reason the final system is modular. The restriction did the design work.
Decisions made visible
Each iteration was documented against the stakeholder note that prompted it. Version three exists because a department head flagged a legibility issue in week two.
The colour reduction in the final system was not an aesthetic preference — it was the direct response to a production cost cap confirmed in meeting four.
The form followed the process
The delivered system is modular, print-ready, and extensible. Every visual decision in it traces back to a named constraint or a documented stakeholder exchange.