Skip to main content

Notes to Self: How to save good ideas.

When it comes to ideas, experience has taught me that there is lot of work to be done even to get a hearing and lot more if it has to be taken to the implementation stage. Just having a good idea alone is just not enough. Experience has also Taught me that human beings aren't exactly as rational as they think of themselves to be. This is even more evident when it comes to approaching new ideas. People have hidden biases, anxieties, contrary opinions and a constant fear of what the idea would do to them or their standing.

With the above in mind, I was thrilled when i came across an article in HBR titled 'How to save good ideas'. This is basically a sales pitch for the book 'Buy in - how to save good ideas from being killed'. I find the article very interesting and could relate a lot to it. I have given below are some interesting points from the HBR article. Please note that this is not a review of the book, but more of a points to remember from the HBR article. The book is still in my ‘to be read’ list. 
  • Human beings have basic skepticism about new ideas.
  • Getting buy-in for good ideas is a basic human issue; it’s a life skill.
  • While people may get ideas in a jiffy, formalizing the idea is an analytical task.
  • Gaining support for the idea means getting into the human nature and group dynamics territory
  • Due to information overload, getting people's attention within a short span of time is very important.
  • The real question is' How do you get people's attention so that they understand and embrace a really good solution to a problem?’.
  • Most of the people respond to attacks on ideas with data and logic.
  • Respond to counter attacks/arguments with respect. Keep responses short, simple, clear and filled with common sense.
  • The motives of the people who oppose the ideas doesn’t matter.
  • When responding to attacks on your idea, take the role of a statesman.
  • It helps since people will be sympathetic to your idea, listen and move sympathetically towards you.
  • There are four ways in which people can kill your ideas
    • Fear Mongering
    • Delay
    • Confusion
    • Ridicule
  • The above four ways manifests itself through 24 different queries. Some of them, I could relate to, are given below
    • Money [or some other problem a proposal does not address] is the only real issue.
    • What’s the hidden agenda here?
    • What about this, and that, and this, and that...?
    • It’s too simplistic to work.
    • No one else does this.
    • Aha! What about THIS? [“this” being a worrisome thing that the proposers know nothing about and the attackers keep secret until just the right moment]
    • People have too many concerns.
    • Tried that before—didn’t work.
    • It’s too difficult to understand.
    • Good idea, but the timing is wrong.
    • It won’t work here. We’re different.
    • You’ll never convince enough people.
    • We’re simply not equipped to do this.
  • Broad rule of thumb for responding to attacks
    • Let the trouble makers in and treat them with respect
    • Communicate in ways that are simple, clear.
    • Don’t make it personal.
    • Watch the whole group and not focus on the person attacking your ideas.
    • Don’t short cut your preparation.
Kotter has the following to say about how great leaders sell ideas.

Great Leaders
  • Know how to communicate in simpler and clearer ways ( this is not dumbing down)
  • Use short stories about something that people could relate to, to sell your ideas.
  • Know selling ideas is not about just intellectual stuff.
  • Know selling ideas is not just about pounding people with data.
  • Know it is all about hitting at an emotional level. and engaging people
I find the article very interesting and it has got me thinking. I definitely recommend the article and the book to anyone who has ideas to sell. For me, getting people to listen to my ideas and ensuring that the idea gets implemented, is one of the most pleasurable moments in life :). I am sure the book will help me learn some tricks. Beyond that it is just a matter of practice, practice and more practice in selling ideas.

Comments

Popular posts from this blog

Kano Model of Customer Satisfaction - Notes to Self

Note: What follows is the notes taken from my study of Kano's model of Customer Satisfaction. I came across this model when i wanted to know if there was a structured approach that would help me prioritize features for software product development. 

To evaluate a product or service, following parameters are very important

The value provided - this helps attract customersThe Quality offered - This earns customer respectProduct or Service innovation - This helps differentiate from competition
But these are not perceived directly, but indirectly through the product and it's features. Kano's model help to group product features into 3 categories ( 6 categories, but only 3 are important) and there by makes it feasible to deliver value at a promised quality while offering innovation. 

The 3 important feature categories are 
Basic featuresLinear featuresExciters or DelightersBasic features are that must be present in the product to be successful. They are also referred to as must have…

Knowns, Unknowns and Project Management...

This article is a draft of a paper i started to write in september 2007 and left it where you see it today.  The purpose is to to come out with a conceptual framework through which “the knowledge needed to successfully execute a project” can be viewed and gauged and presents a brief outline of the same. As always comments are most welcome...
Financial Resources, Domain, Technology, Communication, Cultural Differences, Organizational Structure, Organizational Culture and Power Play within an organization are some of the factors that have an ultimate bearing on the success of a project.
All projects come in shades of grey is a fact that has to be acknowledged. For example, when we start a project, very rarely do we know everything about Project Requirement, Scope and other factors that impact the project. There will be lot of ambiguity and this ambiguity has to be accepted and put to proper use.
But the problem is that people usually look at these factors in black and white. This may be ac…

Aggressive Schedules - Few thoughts...

During my early years in the software industry, i used to look at people who worked in projects with aggressive schedules, in awe. The people working in such projects talked about, long hours, working week ends and heroic endeavors in their projects. The people who worked in such projects were given more awards and rewards, compared to others. i thought that this was the way to be.

After working in projects with aggressive schedules, I realized that what I saw was only the silver lining and there was a big dark cloud behind this ( talk about what experience can do for you). The common thread that linked all the projects was that all of them exhibited one or more of the following.
Project ended up delayed by more than 100% Project got cancelled Project got de-scopedProject has a high cost of maintenance.  Having been burnt up by working in projects with “Aggressive Schedules’, (henceforth denoted as AS), I understand that projects with aggressive schedules cause more damage than what we …