Skip to main content

Your submission was sent successfully! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates from Canonical and upcoming events where you can meet our team.Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

An error occurred while submitting your form. Please try again or file a bug report. Close

  1. Blog
  2. Article

Canonical
on 30 July 2010

Design by enthusiasm


As many of you are most probably aware I work for Canonical and some of my blog posts from here are syndicated to design.canonical.com. I was asked a rather interesting question on that blog and partly due to the impatience of the asker decided to respond by way of a post. My other motivation for responding in this way because I didn’t want an interesting question to be lost in the comments.

The question: “I wonder if the ‘open for all’ in FOSS makes the design part suffer from ‘design by comitee’? What are your thoughts on this?” – Tor Løvskogen Bollingmo

It can be hard to avoid any design anywhere being subject to influence by committee. It is very hard to avoid being influenced by people who are louder, stronger, more powerful, more persuasive and to avoid giving discussions too much weight. Get too many stakeholders involved and things can quickly get messy. This is the very reason I am an advocate of user-centred design. Good data is the ultimate opinion neutraliser.

In open-source, it seems to me, we suffer from a proliferation of design by enthusiasm. A passing comment turns into a mock-up, which turns into some code and before you know it – KAPPOW! – ladies and gentlemen, we have a feature!

We definitely don’t want to curb our enthusiasm, but I do think we need to learn to direct it.

Ideas are cheap. Let’s learn to be discerning. Let’s get enthusiastic about building great things for a set of target users to fulfil a particular need.

Related posts


Erin Conley
10 July 2025

In pursuit of quality: UX for documentation authors

Documentation Article

Canonical’s Platform Engineering team has been hard at work crafting documentation in Rockcraft and Charmcraft around native support for web app frameworks like Flask and Django. It’s all part of Canonical’s aim to write high quality documentation and continuously improve it over time through design and development processes. One way we i ...


Lyubomir Popov
23 June 2025

Improving our web page creation workflow: how structured content is slashing design and development time

Ubuntu Article

Co-authored with Julie Muzina A year ago, during our Madrid Engineering Sprint, we challenged ourselves to dramatically reduce, or even eliminate, the need for constant design involvement in the day-to-day creation of web pages. Our strategy for achieving this is based on a smarter, more structured approach to content. The challenge: brid ...


Leia Ruffini
14 April 2025

How we ran an effective sprint to refresh our design website, Part 1

Design Article

Part 1 of how we ran a design sprint to refresh our website. Sharing what worked, what didn’t, and lessons from designing for open source in mind. ...