Bladewatch.com

The more barriers to entry with the technology, the more people will think about it before deploying it.

We need to remove the barriers to entry with the technology, not just in terms of how difficult it is to use, but also:

• How it will benefit my business operationally or technically – it’ll make it faster
• What I need to consider if thinking about adopting the technology
• What process steps, go-live requirements or issues others have had with the platform
• What sites/blogs/documentation or whitepapers there are to make deployment, support and evolution easier

The more we surround the product with community, with dialog, debate and support, the more we can achieve from the product, the more we can manage failure, manage expectation and get genuine free feedback for product evolution or improvement.

How wonderful would it have been had there been a blog saying, if you’ve got a problem with your HP P-class enclosure, take the backplane bit off for 5 minutes, plug it back in and that will reset the enclosure’s ILO connections and should fix that red light issue. The first line stuff, the easy stuff, with obviously the generic, be careful what you’re doing clauses, need to be more accessible to reduce vendor support costs and improve knowledge of the platform or product, in doing so, changing the situation from, that’s a hardware thing to a, oh pop down press these two tabs and then if it doesn’t work call support.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.