On this page
When I describe my approach as design-led, I don’t mean that I begin by drawing screens.
Visual design is important, but it represents only one part of a much broader discipline.
For me, design-led development begins with understanding the problem and continues through the decisions that shape the product, its architecture, its behaviour and the experience of using it.
It is a way of ensuring that technology serves the intended outcome rather than allowing the available technology to dictate what gets built.
Starting with intention
People generally approach software development because they want something to change.
They may have a new product idea, an operational difficulty, an inefficient process or an existing system that no longer meets their needs.
Often, they also have an idea of the solution.
That is a perfectly reasonable starting point. People understand their own circumstances and frequently have valuable insights into what might help.
My contribution is to explore the intention behind the proposed solution.
What are we actually trying to achieve? Who is affected? What constraints matter? What assumptions are we making? What would success look like?
Discovery is part of the work
These questions are not a delay before the real work starts.
They are part of the real work.
Design makes complexity manageable
A useful system may have to satisfy many different requirements simultaneously.
It might need to be intuitive, secure, accessible, maintainable, performant and capable of evolving as circumstances change.
Those requirements interact.
A decision about how information is organised affects navigation. A decision about user permissions affects both the interface and the application architecture. A decision about where information is processed can have consequences for privacy, performance and operational cost.
Good design is about understanding these relationships and making deliberate choices.
It is not always about finding the most sophisticated solution.
Very often, the better design is the one that removes unnecessary complexity.
The importance of seeing the product as a whole
I tend to approach a problem by considering the complete system.
That doesn’t mean designing every detail in advance. It means understanding how the important parts fit together and where a local decision may have wider consequences.
A user interface, for example, doesn’t exist independently of the data and processes behind it.
Nor does a database exist independently of the people and systems that depend on its information.
Design-led development connects these considerations.
This is one reason I value working across product definition, user experience, systems architecture and implementation. Decisions made in one discipline can be evaluated against the needs of the others.
The objective is coherence.
Designing through working evidence
I also believe strongly in using working implementations to test design decisions.
A diagram can explain an architecture. A wireframe can communicate an interaction. A prototype can reveal assumptions that were difficult to identify in discussion.
Each has its place.
The important thing is to know what is being demonstrated and what remains uncertain.
Know what the evidence demonstrates
A prototype may establish that a particular interaction is useful without establishing that the underlying system is ready for production.
A working technical demonstration may prove feasibility without demonstrating that people want or need the capability.
Design-led development treats these as different forms of evidence.
The design evolves as that evidence improves our understanding.
A practical example
The development of my own website provides a useful example.
One objective was to make a substantial body of professional work accessible to people with different interests and levels of technical knowledge.
That initially appeared to be a navigation and content presentation problem.
But it had wider implications.
How should professional projects relate to research? How should related articles be discovered? How could someone recognise a challenge relevant to their organisation? What should happen when they wanted to discuss it?
Those questions influenced the information architecture, article relationships, visual hierarchy and enquiry experience.
The eventual contextual enquiry system emerged from understanding what someone might want to do after reading an article.
It wasn’t simply a case of adding a contact button. It required designing the connection between the reader’s interest and the next useful action.
The working result can be examined in the accompanying johnstutely.com design and engineering case study.
Design continues during implementation
Design-led development does not mean design is completed before implementation begins.
Some decisions can only be evaluated properly when the system is working.
A component may look appropriate in isolation but prove cumbersome when repeated throughout an application.
An interaction may appear clear during initial design but become confusing in actual use.
Good engineering allows those observations to inform the design without losing sight of the original intention.
This requires judgement. Not every change represents an improvement, and not every attractive idea belongs in the product.
Knowing when to simplify is as important as knowing when to add something.
People and disciplines
I don’t see design-led development as a reason to undervalue specialist expertise.
Quite the opposite.
Different disciplines contribute different perspectives, and those perspectives are essential to understanding a complex problem properly.
What matters is that their contributions remain connected to a shared purpose.
The best outcome is not necessarily the one that satisfies each discipline independently. It is the one that works coherently for the people and circumstances it was created to serve.
The principle I return to
Technologies change. Methods evolve. New tools alter how quickly ideas can be explored and implemented.
The responsibility to understand what should be built remains.
For me, design-led development is the discipline of maintaining that understanding throughout the work.
Begin with the intended outcome. Design the relationships that make it possible. Implement with care. Test against the intention. Change what the evidence tells you needs changing.
That approach has served me throughout my career, and I consider it as relevant now as it has ever been.
Research context
Topic: Design-led development
Explore further
Further reading is listed below.