VDS

Principles

The design principles that guide VDS.

Introduction

Use this guide to help design and build digital products for Crown Botanic Gardens, Vale. It sets out how we work and provides a reference for our internal teams and to help us guide our external partners - including agencies, freelancers, and third parties. It is based on the UK’s Government Design Principles and has been adapted for Vale’s context.

Crown Botanic Gardens, Vale has developed over more than 250 years from a Royal residence to a world-leading centre for plant science, conservation and horticulture. We continue to grow by adapting to new challenges while staying true to our purpose. Our design choices help people understand who we are and what we value.

This guidance supports collaboration across teams - including horticulture, digital, education, access, and marketing - by focusing on shared audiences and goals.

It also helps Crown Botanic Gardens, Vale work towards its 2030 goal of becoming climate positive, strengthening both physical systems and responsible digital practices.

Start with user needs

In the Crown Botanic Gardens, Vale our design process starts with identifying user needs. If you don’t know what the user needs are, you won’t build the right thing. Do research, analyse data, talk to users. Don’t make assumptions. Have empathy for users and remember that what they ask for isn’t always what they need. At Vale, our users include scientists, educators, families, researchers, conservationists, and plant enthusiasts.

Do less

If we’ve found a way of doing something that works, we should make it reusable and shareable instead of reinventing the wheel every time. This means building platforms and resources that others can build upon, providing data that others can use, and linking to the work of others. We should focus on the irreducible core to help reduce technical debt.

Design with data

In most cases, we can learn from real-world behaviour by looking at how existing services are used. Let data drive decision-making, not hunches or guesswork. Continue collecting data after your service goes live — prototype, test with users, and iterate based on findings. At Vale, relevant data could include visitor behaviour, research insights, plant collections, and environmental metrics. This information should guide design decisions. We use a variety of tools to understand user interactions; Google Analytics 4, Hotjar, VWO and Lyssna.

Do the hard work to make it simple

Making something look simple is easy. Making something simple to use is much harder - especially when the underlying systems are complex - but that’s what we should be doing. Don’t take “It’s always been that way” for an answer. It’s usually more and harder work to make things simple, but it’s the right thing to do. For example, Vale’s expertise spans complex scientific concepts and vast collections. Our job is to make this knowledge accessible without losing accuracy.

Asking the right questions

What are the system constraints and why they exist? Think out of the box to come up with something useful. Collaboration. Divergent thinking.

Iterate. Then iterate again

The best way to build good services is to start small and iterate wildly. Release minimum viable products early, test them with actual users, move from alpha to beta to live adding features, deleting things that don’t work and making refinements based on feedback. Iteration reduces risk. It makes big failures unlikely and turns small failures into lessons. If a prototype isn’t working, don’t be afraid to scrap it and start again.

Vale is for everyone

Accessible design is good design. Everything we build should be as inclusive, legible and readable as possible. If we have to sacrifice elegance - so be it. We’re building for needs, not audiences. We’re designing for visitors of all ages, abilities, and backgrounds. The people who most need our services are often the people who find them hardest to use. Let’s think about those people from the start. We want as many people as possible to use our products. Users should be able to change colours, contrast levels and fonts, zoom in without text spilling off the screen, navigate using a keyboard or speech recognition software, and listen using screen readers. We make text as simple as possible to understand, offering plain English explanations when we use scientific language. The goal of accessible design is to remove barriers and create inclusive product experiences that work for everyone, regardless of ability. We aim for compliance with Web Content Accessibility Guidelines (WCAG) 2.1 AA standard.

Understand context

We’re not designing for a screen, we’re designing for people. We need to think hard about the context in which they’re using our services. Are they walking through the gardens? Are they at home researching? Are they in a classroom? Have they never used a plant identification app before? Context at Vale includes physical spaces (gardens, galleries, labs), digital environments, and the connection between online and offline experiences.

Build digital services, not websites

A service is something that helps people to do something. Our job is to uncover user needs, and build the service that meets those needs. Of course much of that will be pages on the web, but we’re not here to build websites. The digital world has to connect to the real world, so we have to think about all aspects of a service, and make sure they add up to something that meets user needs.

In Vale, digital services must connect to our physical spaces, scientific work, and conservation mission. They must also align with Vale’s institutional mission: to understand and protect plants and fungi, for the wellbeing of people and the future of all life on Earth.

Be consistent, not uniform

We should use the same language and the same design patterns wherever possible. This helps people get familiar with our services, but when this isn’t possible we should make sure our approach is consistent. These are not rigid rules. Every circumstance is different. When we find patterns that work we should share them, and talk about why we use them. But that shouldn’t stop us from improving or changing them in the future when we find better ways of doing things or the needs of users change.

Make things open it makes things better

We should share what we’re doing whenever we can. With colleagues, with users, with the world. Share code, share designs, share ideas, share intentions, share failures. The more eyes there are on a service the better it gets - problems are spotted, better alternatives are pointed out, the bar is raised.

Minimise environmental impact

We need a large amount of energy, water and materials from the real world to build and run digital services. Even a small improvement to a service will help reduce its environmental impact, including climate change, biodiversity loss and pollution. Follow sustainability best practice to reduce the environmental impact of your service across its lifespan. What we do today has a lasting impact on our planet.