Next up in the series on the root causes of product failure – products that fail because you have ignored the user’s level of experience. The first time someone uses your product, they don’t know anything about it. Did you design your interfaces for new users? After they’ve used it for a while, they get pretty good at using it. How much do you think they like being forced to take baby steps through a guided wizard now?
Tag Archives: Agile
Posted in Interaction design, Interface Design, Ishikawa Diagram, Kano Analysis, Prioritization, Product Management, Requirements, Requirements Models, ROI, Software development, UX
Tagged Agile, elastic users, expert users, learning curves, novice users, personas, prodmgmt, user personas
67 Comments
Why Do Products Fail? – Incomplete Solutions
This article continues the series exploring the root causes of product failure. Even when you target the right users, and identify which of their problems are important to solve, you may still fail to solve the problems sufficiently.
Specializing Generalist
The ideal agile team is made up of specializing generalists – but what does that really mean? The goal isn’t to prevent functional silos of expertise, it is to allow people to cover for each other.
Read the rest of the article …
Posted in Agile, People management, Process Improvement, Software development
Tagged Agile, specializing generalist, team
41 Comments
Good Stuff on Agile and UXD
Best practices for user experience design and agile. I don’t have the brainpower at the moment, or the experience and eloquence in general, to say it better than these guys. So this week, I’m phoning it in, and deferring to these folks to say it far better than I can.
Read the rest of the article …
Cadence Versus Risk
I’ve been thinking about the software development process. Big, upfront, design and requirements. User research and analysis. Market insights, gained on exploration or over time. Release cadence – how quickly you get, and incorporate, feedback from your customers about your product. How quickly you react to your competitors’ reactions to your actions.
Read the rest of the article …
Satisficing Sprints
Satisficing probably makes more sense than perfecting your product.
Can? Open.
Worms? Everywhere.
Are we really saying “don’t make it perfect?” Yup.
Market Driven Competitive Advantage
Your strategy should be driven by the needs of the market. Becoming market-driven is critical to intentional product success. But it is not enough to understand your market. You have to sustain your understanding, and take advantage of it, competitively.
Posted in Agile, Product Management, Requirements gathering, ROI, Software development
Tagged Agile, agile product management, enthiosys, market driven, ROI, tuned in
15 Comments
Good Enough For Now
Adam Bullied wrote a really good article about not losing motivation in the face of challenges. His closing quote spun us off on a philosophical tangent about being “good enough.”
Successful Products: Lucky or Intentional?
Is your product successful because you were lucky, or because you were methodical and intentional?
Do you want to build a plan where you are dependent on good fortune, or do you want to make your own “luck?” Both approaches work, but only one makes sense as an intention. Slide 3 of your presentation to a venture capitalist should not say “And then we get lucky!”
Latest Articles
Comments on all Articles
