Simplicity In Design

Simplicity In Design

Sometimes it is painfully obvious that too many people have worked on a product, everyone needs to have their say. It feels cluttered, wordy and over-complete. That’s the case because it is just too easy to add. We see something new that might work too, and we’re adding it. What is much harder however, it is to remove. Because you don’t want to leave anything out, make it feel incomplete; everything seems important. And this is especially troublesome if you’re working in a team. You don’t want to upset people by removing any of their ideas. So, people keep adding and adding and now you have a junk drawer of ideas. We all have one of those drawers at home, filled with stuff we might need, someday. So, it is no surprise that we’re creating the opposite of what we’re really trying to achieve. All you are doing is making noise and now it’s getting really hard to make out what it was all about in the first place. Your team is happy, but you just lost your audience.


Sometimes we just need to open our junk drawer and ask ourselves, is this for my audience or is this for me?


You need to have someone like Mary Kondo on the team, to help you simplify. Simplicity does not mean to take away or make it shorter; it is not the same as minimalism; simplicity is not found in the amount of the content – Simplicity is more in relation to time. The time it takes for your audience to understand what you’re trying to say and having an understanding of what you want them to do. For example, an abbreviation actually adds more complexity because it might take the audience a while to decipher. Shorter? Yes. Simple? Perhaps – if the abbreviation is used a lot and has been made very clear to the reader. In that case it will bring more simplicity because we understand the abbreviation and now we can focus on other things. Yes, in a way, simplicity is very complex. Another example about simplicity: ‘’Everything should be made as simple as possible, but not simpler.’’, a quote by Albert Einstein. Because if we take away too much, it is no longer understandable and so it will take your audience longer to understand where you are going. It is up to us to discover that perfect line in between.

Let’s talk about your presentations - your slide decks. Those ideas you came up with that once worked really well for that one presentation. I know you love those ideas, but do they still work? I’m sure you’ve kept those slides in your deck, but it has run its course. In my work I help speakers with their stories and visuals, and a big portion of what I do is discovering the non-essential so it can be removed. When you are the expert and you are trying to present to an audience, you need to know that there is a distance between you: a knowledge-gap. You need to figure out how big of a distance this gap is so you can work your way back and actually build a story that resonates with your audience. I’ve seen so many decks that contained people’s entire junk drawer, and they start calling it ‘their master deck’. But it’s mostly your archive combined with even more current slides. What this creates is a presentation that is all about you. Sometimes we just need to open our junk drawer and ask ourselves, is this slide for my audience, or is this slide for me? And if Mary Kondo was helping you with your presentation: Does this slide spark joy to my audience?

Regards,

‘Simplicity In Design’ (S.I.D.)

I totally agree Sid once to lose the simplicity you lose the audience!

You are nailing it. In development its crucial to figure out the essence of what we are trying to build and who we are building the software for. Only if you have this complete picture, you can create an abstract low fidelity design (wireframes, sitemaps and architecture (domain model). "Agility" means that you choose the most important feature that will need to be built "Given that this is the bigger picture as we understand it now". Its our job as developers to try and understand the business and its customers. We then base our entire decision making on that knowledge. With scrum iterations we reflect on our assumptions about business and our technical choices made. Ruud Keizer and Israel Roldan Leon I'm pretty sure that you have an opinion on this :)

What a great piece, Sid, thank you. I love the idea of the junk drawer. I also hadn’t considered the team aspect and how that contributes. It might be well-meaning, a version of "It's dangerous to go alone! Take this" The flip side is that junk drawer is packed.

Sid van Wijk as the co creator of nearly all my presentations you know how much I value clarity of design and it’s best friend - simplicity. For those that don’t know, when Sid and I are working in a story I write it out. Sometimes word for word, sometimes point by point. Then I leave it. If my story can’t excite Sid in the design then I’ve not been clear enough to empower him to keep it clean and simple in the visualisation. It’s epic teamwork that keeps us both fully productive and engaged

To view or add a comment, sign in

More articles by Sid van Wijk

Others also viewed

Explore content categories