UI Design is not restricted to static display only. Motions helps designers improve user experience. The article “Motion in UX Design” explains why:
- It drives user’s attention and hints at what will happen if a user completes a click/gesture.
- It helps you orient users within the interface and provides guided focus between views.
- It provides a visual feedback.
Check out the very good examples as well!
Many startups fail, and now there is a study showing why they fail. Interestingly, I see two reasons on top:
- Business model not viable
- Money issues
The money issues are of diverse nature, though money seems to play a major role when startups fail. It is more of a concern, though, that the business model is a major reason for failure, because that could have been anticipated beforehand in most cases.
Read the full analysis here.
Last week, I linked a very good post about how to say NO to a feature request. But then, when should you say YES to a feature request? There are a couple of questions to answer:
- Does it fit your vision?
- Will it still matter in 5 years?
- Will everyone benefit from it?
- Will it improve, complement or innovate on the existing workflow?
- Does it grow the business?
- Will it generate new meaningful engagement?
- If it succeeds, can we support & afford it?
- Can we design it so that reward is greater than effort?
- Can we do it well?
- Can we scope it well?
I especially like to way to look on long-term cost.
Obviously, it is not feasible to develop every single feature request people have. There are various reasons to say NO most of the time, and this article give good advice on how to argue with requesters. I highly recommend it.
Designing complex products requires more thought than designing simple products, obviously. Here are some insights on what to focus on. The list is certainly open for additions, but it focuses on some important points. It is definitely worth a read.
Donny Reynolds points out that apps on mobile phones have two major drawback: discoverability and delivery. Both aspects are possible setbacks to individual apps’ success and to the platform’s success as a whole.
The proposed solution is to provide streamed apps on demand.
But wait – isn’t that websites?
There has been a discussion about whether to hire product managers that have product management experience or to hire product managers that explicitly do not have this experience. This article highlights the arguments in favour of PM experience:
Good (great) product managers bring a critical mix of technical talent, business insight and market/customer/user insight
Even startups have product experience, even if there is no dedicated PM role
Subject matter experts have no PM skills
Product management is harder than you might think
“A weekend at the dude ranch doesn’t make you a cowboy.”
Yerrie Kim speaks about how to act as a product manager in the early stage of product development and how to act in the growth stage of product development. She highlights the dimensions Technology, Customers and Team.
There is pretty much insight in the speech, but the difficult thing would be to realise when to move on from early phase to growth phase. This is not a sudden change but rather an evolution.
Ken Norton is well-known in the product management scene, and this slide deck summarizes nearly everything there is to know about software product management. A must-read for every new product manager and also for most PM veterans.
Leading Cross-functional Teams
I recently wrote about product managers for enterprise product. Now it’s time to write about product managers IN an enterprise.
Things are pretty different in large enterprises compared to fast and small start-ups. You need to be patient, accept a much higher grade of complexity, and do some other things, as explained in the article Product Management Career Resilience.