Idea vs Ideating!!
Cricket being most spoken sport in India, I thought
of taking cricket as an example for explaining the above subject. Anyway
language of cricket is easily understood by all...
From "My thoughts" i categorized a normal pitch into different
parameters which we encounter in our day-day business... Have a look at
the below picture... Here,
Ball is issue which needs to be tackled.. If the
ball misses batsman and hits the wicket then the ground rules commands batsman to leave the ground...
The distance of 22 yards is constant, however depending on the pace of ball,
the time is decided to tackle the issue.... Therefore, the time is
defined to tackle the issue... By the time the ball arrives, the batsman
needs to be ready with the strategy (shot) to tackle
the issue..
Thought process of batsman will calculate desired result of shot, time available to play the ball and placement of shot to reduce competitors (fielders).... This is the idea of batsman to play particular shot... And not always does the same shot suit and yield the same result... Therefore, historical data is good, but need to analyse the present situation first...
Thought process of batsman will calculate desired result of shot, time available to play the ball and placement of shot to reduce competitors (fielders).... This is the idea of batsman to play particular shot... And not always does the same shot suit and yield the same result... Therefore, historical data is good, but need to analyse the present situation first...
What happens if the batsman (organization) gets into ideating
(continue to keep coming up with different shots and not clear which
shot to adopt) mode even after the ball pitches and is very near to the
batsman ? This is a pure case of ideating within organization... that is
we continue to improvise on particular shot / strategy even when
deadline to resolve issue is near...
While ideas are good for solving / tackling an issue, ideating
becomes dangerous as it results that batsman misses the ball
(probability is high)... More misses would act pressure on batsman
and thus probability of getting out would be high....
Imagine now we have two balls coming at the batsman at the same
time, (this is a common scenario, where we deal with many issues at same
time). The only way to tackle is to play the ball which might be
directed towards wicket and this is an example of prioritizing
issues... If we try hitting a wide ball and leave the one on the
wicket, we are out... therefore, prioritizing is such an important thing
for employees...
Analogy:
Ball: Issue
Fielder : Competitor (stopping runs)
Pace of ball : Time available to resolve issue
Batsman : organization
Shot selection : Strategy adopted
This was "My Thought", and am eager to know "Yours"... Can we draw
more analogy out of this wonderful game of cricket and try to apply to
our business ?
Do share your thoughts.....
Comments
Post a Comment