Member-only story
Three principles to better present your UI designs

Having a good idea is one thing. But being able to present it is a whole other ball game. While there are about 6M different search results on Google dealing with how to present an idea, there is very little guidance on how to present interface designs.
Why?
Well, (apart from the fact that it is very niche) it is also because they are kinda hard to present. They blend subjective and objective opinions, and sometimes it's hard to balance the two. Telling an emotional story with people cheering in the background isn't going to sell anyone on your registration flow. Just like how just showing a static button design doesn't really inspire anyone either.
A lot of presenting interface design also has to do with trust. The more your stakeholders trust you, the quicker and easier your presentations will be going forward.
There are many different ways to make your stakeholders trust you, and you will find many different approaches. But today, we will be looking at the principles and approaches I use. It's nothing fancy or profound, but hopefully, it will help you.
In this article, we will cover:
- Principle one: Objective, not subjective
- Principle two: Don't tell your stakeholders a story; take them on the journey with you
- Principle three: Bit by bit
- The three principles in action
- Closing thoughts

Principle one: Objective, not subjective
Imagine you go to a gallery and on the wall is a giant abstract painting. People are nodding and praising it — but how do you know it's any good? How do you know that the artist is a master and not a five-year-old?
This is what it is like for a lot of non-creatives. You want to trust the people around you, but you can't actually judge anything for yourself. You may be able to say if you do or don't like something, but you don't know why. When stakeholders feel like this, they give feedback like: "I just don't like it,"…