When is paying for software better than getting it free?
- The tool you need is unique and you have no other options;
or - You're also buying the resources and expertise of the company supplying the software.
A lot of times we get really fancy when we need to do things like "usability testing."
Comments [0]
Examples of this include:
We’re on the verge of the 7th decade since the invention of the computer, and I know it’s heresy for a technologist to point people away from technology. But to solve a problem, you need to know its cause. And if you are honest with yourself about which of your problems can be solved by the latest innovations, then your quality of life will go up.
Will Marlow is the co-creator of AlumniFidelity, which helps schools and nonprofits improve their online fundraising results. Email him at will@alumnifidelity.com.
Comments [0]
The beta tag is one of Google’s brilliant hallmarks.
The beta phase (it can actually last forever) solves one of the key challenges in software product development. The first challenge (unsolved by the beta phase) is to build software that solves a serious consumer or business problem, which is no small task. But the second challenge (once your software solve a serious customer problem) is that you can never figure out how human beings will actually use your software once they get their hands on it. That is, unless you have a strong beta program and you watch a large number of your users in action, and you learn from them.
Google is the master of using emergent data. Don’t design Gmail. Let your beta testers play with your new email system until the right patterns emerge, and let them design Gmail for you. Same with Twitter. Let the right features emerge, don't airdrop them in from corporate HQ.
Having a strong beta culture is all about knowing when to stop inserting your own preferences and opinions into things, and letting the end users tell you how the product should be designed. That’s when the software gets designed right.
Comments [0]
Comments [0]