Still more Getting Real
Continued from More notes on Getting Real.
Human Solutions
Build software for general concepts and encourage people to create their own solutions
Don't force conventions on people. Instead make your software general so everyone can find their own solution. Give people just enough to solve their own problems their own way. And then get out of the way.
From "Human Solutions"
Don't track feature requests
There was no need for a list or lots of analysis because it was all happening in real time. You can't forget what's important when you are reminded of it every day.
And one more thing: Just because x number of people request something, doesn't mean you have to include it. Sometimes it's better to just say no and maintain your vision for the product.
From "Forget Feature Requests"
Ask People What they Don't Want
And don't give it to them!
From "Hold the Mayo"
Get something real up and running quickly
Once you're there, you'll be rewarded with a significantly more accurate perspective on how to proceed. Stories, wireframes, even html mockups, are just approximations. Running software is real.
With real, running software everyone gets closer to true understanding and agreement. You avoid heated arguments over sketches and paragraphs that wind up turning out not to matter anyway. You realize that parts you thought were trivial are actually quite crucial.
Real things lead to real reactions. And that's how you get to the truth.
From "Race to Running Software"
Work in Iterations
Allow your users to tell you what to do while there's still time to do it.
Get your story straight. Make sure the pieces work. Then launch and revise. No one is as smart as all of us.
—Seth Godin, author/entrepreneur
From "Rinse and Repeat"
Comments
Post new comment