Archive

Posts Tagged ‘strategy’

Telling stories – fairy tales, case-studies & scenarios….

April 14, 2011 5 comments

Telling Stories - At the ICI/Atelis competitive intelligence conference that took place last week (April 6-7, 2011) in Bad Nauheim, Germany there was a panel discussion on story-telling as a method of reporting intelligence. At about the same time, the Association of Independent Information Professionals (AIIP) held their 25th annual conference in Vancouver, Washington in the USA. Mary-Ellen Bates described how stories can help information professionals market themselves by showing how their skills can solve client problems. The fact that both conferences looked at story-telling shows how businesses are adopting the technique as a way of addressing complex issues.

Story telling is an ancient art-form that might seem strange as a business tool. However, often stories will be an excellent approach for solving business questions as they allow people to look at a situation objectively, remove themselves from the scene and take an outside view. The trick is to tell the right story, catching the imagination and making people think. During the ICI / Atelis conference I suggested a framework for when different story styles can be used.

The first story type is the “fairy-tale” – the “Once Upon a Time in a Kingdom Far Away” type of story. Fairy-tales are possibly the most abstract example of a story that can be applicable to business. The danger is that they can be seen as childish and far-removed from real-world business realities. In fact, they can be a powerful way of highlighting deep-seated organisational problems, as management refusal to see such problems can be illustrated with stories. Such stories can help managers recognise their own situation, and so identify the problems and think of possible solutions.

Consider a company where the CEO or other senior management refuse to see that their business has changed.  Often such management grew up in the industry and believe that they know it inside out. Accepting that things have changed is anathema to them. A standard comment given by such managers when asked why things are done in a particular way is “We’ve always done it that way“. Essentially such management suffers from corporate denial – or what Ben Gilad called a business taboo in his book “Business Blindspots“.

Telling such managers a fairy-tale story can help them see the problem (assuming that you can arrange a session they will be willing to attend).

Once upon a time, in a far-away country there was a king who loved to sing. He loved to sing so much that he made laws that all his people were to learn his favourite songs.

Every Sunday, the people were to gather in the town squares and village greens and sing the songs the king loved.  The people were happy as they also loved the music and they prided themselves as being the most musical people in the world.

One day, a travelling minstrel sailed into the the kingdom from across the sea – singing a new song. Soon, children started to sing this new song, followed by their parents, and word reached the king that the people were no longer singing the king’s songs but were singing something different.

The king flew into a rage, and put the minstrel into a deep and dark dungeon. However this didn’t stop the minstrel singing – and soon the guards started to sing the new song. The king then made laws saying the new song lacked harmony, was discordant, and that anybody caught singing it would be severely punished.

Gradually the people became unhappier. They liked the new song and wanted to sing it along with the old songs. Instead they stopped singing – and the king got angrier and angrier that his songs were no longer being sung. He tried to force people to sing, but they just sang out-of-tune. He made new laws that said they had to sing on Sundays and Mondays, but found that lots of people said they’d lost their voices from singing so much and so couldn’t sing on Sundays or Mondays. And so the king also got unhappier as he no longer heard his songs being sung as in the past….

The basic lesson for a story such as this is to accept and embrace change – rejecting change is likely to be self-defeating. There are many companies and industries that fail in this – the music industry being a classic example, that lost out by refusing to recognise the impact of music downloading, Napster, iTunes and peer-to-peer file sharing. A fairy-story can help highlight the problems – although the solution will need to come from full discussion and management acceptance.

The second story-type is the traditional case-study. Case studies should be used where the organisation knows the problem, but not the solution. Finding the solution directly is difficult as management is too close to the situation. The case-study serves as a way of examining the problem dispassionately, by looking at a parallel situation involving a company or organisation, from another industry, or market. The aim is to analyse the problem and work out appropriate strategies to solve the problem and apply them to the real situation. The key for a case-study is to find one that matches the organisation’s problems. There is a vast bank of case-studies for a range of industries, topics and problems at the Case Study Clearing House.

A third story-type are future scenarios, generally generated as part of a scenario-planning exercise. Such stories attempt to answer “what if” questions by looking at external factors and their correlations and impacts, and then considering how these could play out in the future. It is essential that such scenarios are internally consistent and that there is a clear line of development from the current situation to the future scenario. This can then allow for strategies to be put in place that take into account what could happen. Such strategies need to be adaptable to changing situations and allow for organisations to prepare for any eventuality.

As a reporting approach, telling stories is one way of putting across ideas that stimulate the imagination, and so can help organisations develop strategies that lead to success. There is a common theme to all three story types: problem identification, its acceptance and the need for strategies to cope with change. They differ in their perspective on the world. The fairy-tale approach looks at understanding problems and overcoming blindspots that relate to the past imposing on the present; case studies look at solving present problems; scenarios are aimed at preparing organisations for the future.

Delicious humbug and monitoring News stories

December 20, 2010 Leave a comment

Effective competitive intelligence monitoring means keeping up with the news, and where news is likely to impact you, drawing up strategies to take into account changes.

The problem with instant news via twitter, blog posts and various other news feeds is that news updates sometimes happen too quickly, before the snow has even had a chance to settle. That’s fine – just so long as the source for the news is 100% reliable, and the news story itself is also totally accurate. (I’m using snow as a metaphor here – rather than the more normal dust – as outside there is around 15cm of the stuff with more promised during what looks like being the coldest winter in Europe for over 20 years).

Unfortunately, more often than not, one of these two aspects fails: the source may not be reliable, or the story may not be true, or may be only half-true. Typically however people pick up on the story and it spreads like wildfire (so not giving that snow a chance to settle before it gets melted all over the web).

An example of this has been taking place this last week – with numerous posts reporting the demise of the web-bookmarking service Delicious.

Delicious (originally located at http://del.icio.us) was founded in 2003 and acquired by Yahoo! in 2005. By 2008 (according to Wikipedia) it had over 5 million users and 180 million bookmarked URLs. This makes it an important source for web-searching as, unlike with a search engine such as Google or Bing, each URL will be human-validated and valued.

Apparently, during a strategy meeting held by Yahoo! looking at its products, Delicious was named as a “sunset” product.

Slide from Yahoo! strategy presentation - on plans for various products

An image of this slide was tweeted – and after Yahoo! failed to deny that Delicious was to be closed, posts quickly appeared denouncing the company for the decision. Nobody really cared that sites like AltaVista and AlltheWeb were going – as they were to all intents and purposes dead anyway. (Their search features have long been submerged into Yahoo!’s own – although I for one, still miss some of the advanced features these services offered. Alltheweb allowed searching of flash content, and AltaVista had a search option that nobody now offers: the ability to specify lower/upper case searches).

The problem is that many of the sources posting the story are normally extremely accurate and reliable so when they post something, it is reasonable to believe what they say. This then compounds the problem as the news then gets spread even further – and when the story is corrected, the news followers often fail to spot the corrections.

The example of Delicious is not isolated. There are many news stories that develop over time – and when making strategy decisions based on news it is important to take into account changes, but also not rush in, if a news item hasn’t been fully confirmed.

Ideally check the source – and if the source is a press item (or blog post) then look to see if there is a press release or where the original item came from, in case there is a bias, inaccuracy or mis-interpretation. Only when the news has been confirmed (or where there are no contra-indications) should strategy implementation take place (although of course, the planning stage should be considered immediately if the potential impact of the news is high).

In the case of Delicious their blog gives the real story. The slide leaked to twitter was correct – Delicious is viewed as a “Sunset” product. However that doesn’t mean it will be closed down – and Yahoo! states that they plan to sell the service rather than shut it down (although it is noticeable that they don’t promise to keep the service going if they fail to find a buyer).

There is, in fact, another lesson to be learned here, relating to company awareness on the impact of industry blogs and twitter. It is important to not only monitor what is said about your company, but also to anticipate what could be said.  In a world where governments can’t protect secrets being leaked via Wikileaks, it would be surprising if high-impact announcements from companies didn’t also leak out to industry watchers. Some companies constantly face leaks – Apple is notorious in this regard – and part of their strategies involve managing potential leaks before they do harm. In this Yahoo! failed. As a media company that depends on the web for its business this is a further example suggesting how Yahoo! seems to have lost its way. This is not negated by evidence such as the leaked slide mentioning Delicious, showing they are thinking about their future and product/service portfolio.

%d bloggers like this: