FRAMEWORK ≠ OUTCOME: HOW TO CHOOSE A DESIGNER
Design frameworks are ubiquitous. Great outcomes are not. So what really determines the value of a designer’s process?
THE ILLUSION OF PROCESS
Everyone has a process. Five steps. Seven stages. A mix of research, ideation, design, feedback, and delivery. Some are codified, others even trademarked. The sequences and names may change but the structure does not.
This isn’t a dismissal of process. A structured approach has utility. No matter how individual, refined, or publicly lauded a process is though it cannot guarantee an outcome. And it certainly cannot guarantee success.
THE MYTH OF ASSURANCE
Design frameworks are often presented as consequential. Follow the steps, trust the method, and the result will follow. The promise of the automatic answer is rarely fulfilled.
Consider two political leaders, each presented with the same policy review. The same data. The same constraints. The same process of inquiry. One may double down, the other may withdraw completely. The outcome is not in the process. It is in the hands of the decision-maker.
Design is no different.
Even with identical briefs, the end result will diverge. Not because the framework was faulty but because the values, judgement, and interpretive lens of the designer were different. They can vary greatly, and they matter.
THE APPEAL OF STRUCTURE
Frameworks often appeal to clients because they suggest rigour. They give order to a process that is viewed as inherently risky or frivolous. They are loved by designers as they feel it brings a level of respect to their profession they yearn for. Both instinctively know though that process is insurance for the bargain each make in undergoing a 'creative' process.
HOW SHOULD A CLIENT CHOOSE?
So, if frameworks are standardised, and past work is context-specific, how can a client make an informed choice?
Style offers surface cues. Personality profiling may offer indicators. Neither though can reveal how a designer will resolve real-world ambiguity. The differentiator is not ideals. It is not even aesthetic compatibility. It is judgement.
Clients need to understand how a designer thinks, not just what they’ve made.
DECISION-MAKING AS THE DIFFERENTIATOR
What distinguishes one designer from another is not their process, but how they interpret a problem. How they structure choices. How they reconcile constraints.
What value system do they bring to bear on the problems that must be solved? What lens shapes their view of the world?
FINAL REFLECTION
Rather than ask clients to trust a framework, give them something to judge. Share the routes you rejected in favour of those you believed held greater potential. Help them see the rationale. Help them recognise the values behind the decision.
Let them ask themselves, “Is that the choice I would have made?” And even if the answer is no, make it clear why your answer was yes.
THE ILLUSION OF PROCESS
Everyone has a process. Five steps. Seven stages. A mix of research, ideation, design, feedback, and delivery. Some are codified, others even trademarked. The sequences and names may change but the structure does not.
This isn’t a dismissal of process. A structured approach has utility. No matter how individual, refined, or publicly lauded a process is though it cannot guarantee an outcome. And it certainly cannot guarantee success.
THE MYTH OF ASSURANCE
Design frameworks are often presented as consequential. Follow the steps, trust the method, and the result will follow. The promise of the automatic answer is rarely fulfilled.
Consider two political leaders, each presented with the same policy review. The same data. The same constraints. The same process of inquiry. One may double down, the other may withdraw completely. The outcome is not in the process. It is in the hands of the decision-maker.
Design is no different.
Even with identical briefs, the end result will diverge. Not because the framework was faulty but because the values, judgement, and interpretive lens of the designer were different. They can vary greatly, and they matter.
THE APPEAL OF STRUCTURE
Frameworks often appeal to clients because they suggest rigour. They give order to a process that is viewed as inherently risky or frivolous. They are loved by designers as they feel it brings a level of respect to their profession they yearn for. Both instinctively know though that process is insurance for the bargain each make in undergoing a 'creative' process.
HOW SHOULD A CLIENT CHOOSE?
So, if frameworks are standardised, and past work is context-specific, how can a client make an informed choice?
Style offers surface cues. Personality profiling may offer indicators. Neither though can reveal how a designer will resolve real-world ambiguity. The differentiator is not ideals. It is not even aesthetic compatibility. It is judgement.
Clients need to understand how a designer thinks, not just what they’ve made.
DECISION-MAKING AS THE DIFFERENTIATOR
What distinguishes one designer from another is not their process, but how they interpret a problem. How they structure choices. How they reconcile constraints.
What value system do they bring to bear on the problems that must be solved? What lens shapes their view of the world?
FINAL REFLECTION
Rather than ask clients to trust a framework, give them something to judge. Share the routes you rejected in favour of those you believed held greater potential. Help them see the rationale. Help them recognise the values behind the decision.
Let them ask themselves, “Is that the choice I would have made?” And even if the answer is no, make it clear why your answer was yes.