Releasing version after version before the final version goes live.
Is this a good or bad way to get the 'perfect' end product.
In a debate with Adam Kinder I was looking at the positive side to the rinse and repeat method.
The main points I came up with were as follows:
* By releasing versions it gives the users a feel for the main features that will available on the final product.
* It allows the users to give feedback and have a sense of ownership and feel as if their feedback has had an effect on the final design.
*It allows the designer to get feedback and know what changes NEED to be made rather than what they THINK needs to be changed.
*Gives the designer the opportunity to observe the users actions and patterns in how they will use the product.
*Can help to priorities the jobs in which changes need to be made, and focus the time and effort in the most effective way.
* It prevents the designing team wasting time on areas they think will be effective rather than looking where the users want the changes to be made.
In debate Adam Kinder suggested:
* Early versions can put users of purchasing the final design, because early errors may be vital.
* It depends on the product itself if it is for a bank or a power station operating app, early versions with errors could be lethal.
This is an ongoing debate amongst designers but personally I think early versions are a must.
Google Fight suggests final version is best.. :)
REF: Rinse and Repeat (page 62) from Getting Real by 37 signals.
Rinse and Repeat
Work in iterations
Don’t expect to get it right the first time. Let the app grow and
speak to you. Let it morph and evolve. With web-based software
there’s no need to ship perfection. Design screens, use
them, analyze them, and then start over again.
Instead of banking on getting everything right upfront, the
iterative process lets you continue to make informed decisions
as you go along. Plus, you’ll get an active app up and running
quicker since you’re not striving for perfection right out the gate.
The result is real feedback and real guidance on what requires
your attention.
Iterations lead to liberation
You don’t need to aim for perfection on the first try if you know
it’s just going to be done again later anyway. Knowing that
you’re going to revisit issues is a great motivator to just get ideas
out there to see if they’ll fly.
Is this a good or bad way to get the 'perfect' end product.
In a debate with Adam Kinder I was looking at the positive side to the rinse and repeat method.
The main points I came up with were as follows:
* By releasing versions it gives the users a feel for the main features that will available on the final product.
* It allows the users to give feedback and have a sense of ownership and feel as if their feedback has had an effect on the final design.
*It allows the designer to get feedback and know what changes NEED to be made rather than what they THINK needs to be changed.
*Gives the designer the opportunity to observe the users actions and patterns in how they will use the product.
*Can help to priorities the jobs in which changes need to be made, and focus the time and effort in the most effective way.
* It prevents the designing team wasting time on areas they think will be effective rather than looking where the users want the changes to be made.
In debate Adam Kinder suggested:
* Early versions can put users of purchasing the final design, because early errors may be vital.
* It depends on the product itself if it is for a bank or a power station operating app, early versions with errors could be lethal.
This is an ongoing debate amongst designers but personally I think early versions are a must.
Google Fight suggests final version is best.. :)
REF: Rinse and Repeat (page 62) from Getting Real by 37 signals.
Rinse and Repeat
Work in iterations
Don’t expect to get it right the first time. Let the app grow and
speak to you. Let it morph and evolve. With web-based software
there’s no need to ship perfection. Design screens, use
them, analyze them, and then start over again.
Instead of banking on getting everything right upfront, the
iterative process lets you continue to make informed decisions
as you go along. Plus, you’ll get an active app up and running
quicker since you’re not striving for perfection right out the gate.
The result is real feedback and real guidance on what requires
your attention.
Iterations lead to liberation
You don’t need to aim for perfection on the first try if you know
it’s just going to be done again later anyway. Knowing that
you’re going to revisit issues is a great motivator to just get ideas
out there to see if they’ll fly.
No comments:
Post a Comment