On this page
Questions you could ask me
In the early 2000s, I worked as a consultant for the UK’s Department of Trade and Industry on a web project associated with its Foresight work looking towards 2020.
The initiative involved sixteen departmental teams contributing their views, priorities and concerns about the future.
My responsibility was to develop a public-facing website through which that information could be presented.
On paper, that may sound like a straightforward web-development assignment.
In practice, one of the greatest challenges was bringing together the perspectives of sixteen groups without producing a design that felt like sixteen separate websites.
Many stakeholders, one experience
Every organisation has its own priorities.
When multiple teams contribute to a shared initiative, those priorities can overlap, diverge or compete.
A website has to accommodate legitimate differences without making the experience unnecessarily complicated for the people who use it.
That was the central design challenge.
The Foresight work concerned forward planning and public information. The material needed to be accessible, comprehensible and organised in a way that made sense beyond the internal departmental structure.
The design therefore had to do more than represent the views of the people commissioning it.
It had to serve the people reading it.
A change in responsibility
I initially became involved alongside a London agency.
During the project, the DTI ended its arrangement with that agency, and my responsibilities expanded to include the visual design as well as the technical development.
That meant taking responsibility for the way the website looked, how people navigated and understood it, and how the underlying implementation supported those decisions.
It was a combination of disciplines I have frequently worked across: user experience, visual design and systems engineering.
I was not simply implementing somebody else’s finished design.
I was helping shape the solution.
Working directly with government stakeholders
I worked closely with senior civil servants at the DTI, attending meetings at its St James offices approximately every two weeks.
Those meetings were an important part of the process.
Requirements needed to be understood, alternatives discussed and decisions translated into something that could actually be built.
With sixteen departmental teams contributing to the programme, there was considerable scope for competing preferences to become competing design instructions.
I was conscious of the familiar danger of designing by committee.
The challenge wasn’t to ignore stakeholders. Their knowledge and requirements mattered.
It was to understand what they were trying to achieve and find a coherent way of representing those needs within a single design.
That requires listening carefully, asking questions and being prepared to explain why some approaches work better than others.
Design and engineering belong together
One advantage of being involved in both the interface and its technical implementation was that I could consider the implications together.
A proposed layout or interaction wasn’t an isolated visual decision. It had consequences for how information would be structured, maintained and presented.
Equally, the engineering shouldn’t dictate an unnecessarily difficult experience for users.
Both sides needed to inform one another.
I’ve always found that this reduces the distance between a requirement, the proposed solution and the work necessary to deliver it.
It doesn’t eliminate compromise.
It makes those compromises more informed.
Delivering the work
Despite the complexity of the project and the change in responsibilities, I delivered the work on time and within budget.
For a government contract, that mattered.
There were agreed objectives, constraints and expectations. A successful design that couldn’t be delivered within those boundaries would not have been a successful project.
The experience reinforced the importance of maintaining clear priorities while accommodating legitimate stakeholder requirements.
It also reinforced the value of taking responsibility for the complete solution, rather than treating design, implementation and delivery as unrelated activities.
What stayed with me
The technology used for a government website in the early 2000s is not the most interesting part of the story today.
The enduring problem is how to turn multiple perspectives into a coherent service.
That challenge exists in government, business systems, enterprise software and almost any project involving several stakeholders.
People need to be heard. Their requirements need to be understood.
But the resulting system still needs a clear purpose.
Good design isn’t the absence of competing opinions. It’s the ability to work through them without losing sight of the people the system is intended to serve.
That is a lesson I’ve carried into many projects since.
Project context
Topic: Professional projects
Explore further
Further reading is listed below.