Home | Twitter
You are a product designer, developer, writer, information architect, etc. and somebody asks you
Is [enter your expertise here] important?, you will answer
Sure, because it makes [xyz] better..
But how important are you for the success of a product? Or maybe asked better: When are you important to a product?
The following pyramid depicts the hierarchy of a product's needs (borrowed from Maslow). Which aspects are totally necessary, which are useful and which just icing on the digital cake?
(Price, availability, accessability, language, ...)
Is it available in their country? Can they afford it? Can they physically use it? Is it in a language they understand?
(Useful features, stability, ...)
Does your product solve a problem for people? Does your product work well (enough)?
(Structure, flow, performance, ...)
Is your product well structured and thought through? Is it responsive? Are things where people expect them to be? (Often called UX design)
(Color, brand, typography, common icons redesigned ...)
Does your product (visually) stand out? Can people recognise it from screenshots? (Often called UI design)
(Motion & sound design, witty copy, ...)
Is your product delightful to use?
Let me know what you think about this: @st_phan on Twitter or send me a mail to hello ät stephanbogner dot de – Cheers!