Pure gut
[...] The story of the Nano started nine months ago, when Jobs and his team took a look at the iPod Mini and decided they could make it better. On the face of it, that wouldn't appear to be a fantastically smart decision. The iPod Mini was and still is the best-selling MP3 player in the world, and Apple had introduced it only 11 months earlier. Jobs was proposing to fix something that decidedly was not broken. "Not very many companies are bold enough to shoot their best-selling product at the peak of its popularity," Gartner analyst Van Baker says. "That's what Apple just did." And it did that while staring right down the barrels of the holiday retail season.
It was a gutsy play, and it came from the gut: unlike almost any other high-tech company, Apple refuses to run its decisions by focus groups.
Time Stevie's Little Wonder (2005-09-19) [min emfas]
Fan vad jag ska citera det där vid något bra tillfälle.
Uppdatering (16.53)
Apropå det så borde jag skicka med det här på samma ställe, så jag kommer ihåg det (och ja, det är ett långt citat):
Don't ask staff what they need
A common trap to fall into is to ask staff what they need. This involves asking questions such as:
- What is most useful on the intranet?
- What are the problems with the current intranet?
- What features are missing from the intranet?
- What additional information do you need?
- How else could the intranet help you with your job?
The key problem with these questions is that they require staff to have an understanding of intranets, and how they can support day-to-day work in an organisation.
In general, however, staff have little understanding of intranet technologies or approaches. Instead, they have in-depth knowledge relating to their job role and activities.
Asking these questions therefore generates one of two possible responses:
- "I'm not sure. Can you give me some examples of how an intranet could help me?"
- "I think it would be great if the intranet provided feature xyz!"
In the first case, staff are unable to provide meaningful input into intranet design or strategy. In the second, a 'wish list' of features and tools is collected, but without ensuring that these ideas will actually be useful (or used) in practice.
In either case, attempting to gain intranet ideas from staff in this way will not generate a clear and concrete roadmap for how to improve the intranet.
KM Column Conducting intranet needs analysis (2005-09-05)
Kategori: Användbarhet, Teknik
Kommentarer
Ja det där fick mig att le brett när jag läste det. Gör mer fundera mindre.
Kommenterat av: ph den 2005-09-14 kl. 15.50 #
Kommentera