Mistake number nine in the "Early-Stage Mistakes" series: I did not care enough about UI and UX.
We Measured Success in Code
Back when we were building systems and websites, our focus was on speed, accurate calculations, architecture and well-organised data. We considered those the most important measures of a successful system.
How the system looked and how people used it came in a later stage. What mattered to us was that the feature worked correctly, not so much how the user would deal with it.
That was a mistake.
What UI and UX Actually Mean
UI is not just colours and buttons, and UX is not just a nice look.
UI is the interface the user sees. UX is their experience of working with it:
- Can they reach what they need easily?
- Can they finish their work in fewer steps?
- Or do they have to search and think hard just to use the system?
Fast and Accurate, but Exhausting
You can build a system that is very fast and accurate, yet an employee has to open five screens to complete a simple task.
On the other hand, you will find systems whose performance is not the best, yet clients stay with them and prefer them, because they feel comfortable and are easy to use.
The client does not see the architecture or the effort you put into performance. They see the screen in front of them and judge the product by it.
That is when I understood that a product is not sold on its code alone.
What I Learned
- UI and UX are not a finishing touch; we have to think about them from the very first design of the system.
- We have to understand users and their needs, not design the system around how we think as programmers.
- A good look is not the enemy of performance; you can achieve both.
The Bottom Line
Do not build the system with a programmer's mindset alone. Look at it through the eyes of the person who will use it every day.
A successful product is not just one that works well. It is one that people know how to use and feel comfortable using.
Want to Skip These Mistakes?
If you are building a business or a system from scratch and want to avoid these mistakes from day one, talk to us directly.
Message us on WhatsAppLearn more about Alaa Samir, founder of Darory, or send us a message.
The Early-Stage Mistakes Series
- Episode 1: Hiring Before the Work Is Stable: The Most Expensive Mistake of My Early Days
- Episode 2: Polishing One Part While the Whole Project Waits
- Episode 3: "A Technical Fault": The Vague Answer That Almost Cost Us Our Clients
- Episode 4: No Real Rest for the Founder: When Breakdowns Come at the Worst Time
- Episode 5: Taking the Client's Word for It: Why Every Stage Needs a Written Approval
- Episode 6: More Features, Better System? The Mistake of Building Everything the Client Never Needed
- Episode 7: One Post Took Down the Whole Server: Hosting Clients Without an Off-Site Backup
- Episode 9: I Cared About the Code and Forgot the User: Why UI and UX Are Not a Finishing Touch