I’m encouraged by the number of people talking about how they are taking on more responsibility to lead design. Emma’s blog post was great about her decision to take on a new role, and Ale’s call out to bring together more people in lead design roles has had a great response.
More and more I feel like I’m stepping outside recognised design communities to have conversations about design.
I think that this is important. For me, the practice of design is secondary to being able to translate design into something more impactful.
Seniority in design is about personal responsibility.
A disclaimer to start with. While everyone can take personal responsibility, not everyone has the same circumstances, privilege or types of choices to make when doing so.
But, whatever your situation, everyone can can take personal responsibility for their work as a designer.
“Complexity in the work. Simplicity in how we approach the work.”
Following on from my previous blog post, I’m a big advocate of designing simple models, or frameworks (including working from first principles).
When we’re working to solve problems, it’s the simplicity and clarity of frameworks that can help us to work with subject matters that are inherently complex.
In a design process there are two immediate things that matter – the horizon (immediate goal), and the next steps (immediate steps towards that goal).
As you become a more senior designer with responsibility for other designers, one of the challenges you will face is your personal closeness to ‘hands on’ design work.
As well as how close you are to the work, you will have to think about the proximity you have to those doing the hands on work when that isn’t you.
Why prototyping doesn’t mean that you have to write code or build software…
What it means to move to a design mindset…
Ambiguity is a key part of design. It points us to the uncomfortable gap between 'what is' and 'what could be' which is where I believe design adds most value.
Sharing prompts and questions I use when working with product teams.
There’s a lot of design education out there. I get asked sometimes what people should ‘study’?
All design is strategic unless you just see it as implementation.
There’s a question of why designers make so many maps. We love maps. But there can be confusion or misunderstandings about why we’re making them or how they can be useful to service teams.
Thoughts about bias in design.
I’ve worked for a number of years as a consultant, and have worked with many other consultants.
The consultants fallacy is to leave people thinking they need to work harder, or invest more time and money in order to understand your ideas and methods. That they’re doing something wrong when they don’t comprehend how brilliant you are or can’t immediately adapt to your methods, processes, or ways of working.
What we can learn from the military about “mapping backwards” and how this applies to service design
Why artefacts are most useful when they become the design, rather than a plan for doing the design or building a product.
A good rule of thumb.
Don’t accept the low expectations of your teams, clients, or the sector you work in.
Everyone has the opportunity to challenge what’s happening around them. This is whether you have permission to do so, or not.
Challenge people to do more with less.
How we quickly adapt to unfamiliar service models…
Why the quality of your conversations is as important as your process.