POST applies extremely well to internal-facing collaboration and Information Workplace discussions, which he described in “POST: A Systematic Way To Define Your Collaboration Strategy.”
In the context of collaboration the four step POST methodology consists of:
1. People. Start by understanding what employees actually use and need today. Don’t guess and don’t rely on anecdotal interviews. Instead, start with a quantitative assessment.
2. Objectives. With that baseline of understanding in place, next decide what your business goals are. You will need to build a decision council that includes IT and business to help you do this.
3. Strategy. The strategy part of this planning process means mapping the business goals to specific collaboration scenarios that you can actually improve — no tools yet.
4. Technology. The last step is to figure out which technologies improve your most important collaboration scenarios. Choose cloud services if they make sense; on-premises if not.
IT struggles with a new form of hype. As one Content and Collaboration professional recently told us, “I used to hate constantly meeting with vendors trying to sell me stuff. But now the vendors go directly to the users, convince them they need the tools, and I end up with my own colleagues demanding I buy this “great” stuff that is “exactly what they need.” It’s even worse!”
POST deflects this kind of demand. “You think it’s just what you need? Ok, let’s run the POST methodology and see if this technology is appropriate for our people, objectives, and strategies.” If the answer is yes, you’ve cut through the hype and verified real business benefits. If the answer is no, you’ve demonstrated precisely why, rather than just refusing to give users what they want.
This is a helpful concept to utilise if someone wants you to use something new - run it past this concept and tweak as you need - say in re-designing your intranet to buying iPads for the business. I've been there and worn the T shirt from vendors in the past.
Friday, March 18, 2011
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment