Search This Blog

Showing posts with label System Design. Show all posts
Showing posts with label System Design. Show all posts

Friday, March 18, 2011

Got Hype? You need POST | Forrester Blogs

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.

Monday, January 04, 2010

A failure of intelligence and knowledge management

It is interesting to note that since the recent attempted bombing of the plane in the USA on how failures of intelligence organisations to share knowledge nearly led to tragedy. Since 9/11 the us intelligence agencies have tried to improve this through technology. There has been the well cited case of the use of wikis such as intellipedia as a means of capturing information. I suppose one of the problems is that you can have too much information and you return to the drinking from the fire hose - or as this article puts it sorting the wheat from the chaff.

I think that the article is useful but I think that it needed to look at the people and leadership issues within the intelligence agencies as well as the culture.

Interestingly one of my KM favourites Morten Hansen has a piece in HBR (Click here) he highlights the hoarding barrier where the organisation and its incentives penalised sharing and also the poor ability to search for relevant information. He proposes three areas for improvement and I agree with the one regarding incentives - probably through areas such as the appraisal system and other non monetary inducements - however job rotation may not work in some organisations because of specialisation and recruitment of new people both in public and private sector seems a bit of a no no in the current economic climate.

I've undertaken KM work in the past in that we can provide people with the tools that we think that they need but the problem is that the culture of the organisation needs to be a safe one where people can use the tools and that it is expected that they will use them and that there are no disincentives for people to use them.

We probably also need to look at what is going on in the working environment that the intelligence agencies are working in and the culture - if you are working in a organisation that deals in secrets maybe knowledge sharing amongst other secret organisations is a little more difficult.

I am convinced that a new wave of technology will support improved knowledge management however at best at present it is a marginal revolution with people carrying out work in this area in many cases under the radar - because the organisations that they work for haven't yet caught up or it isn't seen as an organisational imperative in a very competitive and threatening business environment.

It is very easy to snipe from the sidelines when there is a systemic failure - but what current articles fail to look at is the pressure that the intelligence agencies are under and sometimes people don't have the time to share that knowledge even if they wanted to.

Later.... Rosabeth Moss Kanter puts her two pennorth into the discussion - here which talks about the lessons leaders can learn from this - however, there are also lessons that knowledge managers can learn from this.

Monday, December 17, 2007

Imroving your system design

The excellent Matt Hodgson has an excellent post over the weekend on system design. I’ve cut and pasted it in directly as an aide memoire to myself. A number of them such as Content is King I have highlighted and utilised in other organisations. I’d also like to combine this with McAfees SLATES mnemonic which he developed in terms of Web 2.0 applications. These two elements combined don’t make a bad framework to help increase the usability of a system and improve the satisfaction levels of the end user. At the end of the day – be it intranet, CRM internet site the system has to help the user do their job better and quicker and be a pleasurable experience – otherwise your users will slowly ebb away.

Here’s Matt’s Top 10 list.

1. Know your users: Take time to understand the people who are going to use the system, whether its a website or application.

2. Content is King: Design features and content specifically for your users, not for yourself.

3. Make it logical: The organisation of information and how the navigation works has to be logical to those who will use it.

4. Be consistent: Don’t make people constantly adapt to changes layout, language and navigation paradigms — it makes learning about and using the system very confusing.

5. Make it simple: Using systems should require as little mental effort as possible — there’s nothing more frustrating than trying to get the job done and having to work hard to remember how a system works at the same time.

6. Plain English please!: Do the terms and language used in the system make sense to the people who will use it? Don’t make them learn a whole new vocabulary with words that mean one thing to them but another thing when used in the system. Avoid legalese, bureaucratese and organisational jargon.

7. Make the information scanable: Information should be laid out on the screen so that it has a logical flow for the eye. Don’t make people have to remember that one piece of important information is here, while another piece is somewhere else. Similar pieces of information should be as closely associated as possible.

8. Navigation redundancy: People all think about information in different ways, mostly through association rather than categorisation. This means that you need to provide multiple ways of discovering information — and this doesn’t just mean browse and search. If you use taxonomy, make sure information can go in multiple categories, and complement it with a folksonomy.

9. Design by convention: People have an expectation of how systems and their components will work based on previous experience of other systems. This means you need to make your design comply with those design expectations — banners, navigation, search, login, and even cart features all need to appear according to existing design conventions. This doesn’t mean you can’t innovate — just know what your users expect and make it easy for them to learn your system.

10. Make the design clear: This will help people avoid making mistakes when they use your system. Help them recover from errors through providing consistent messaging in the interface itself.