Effective Persuasion

Effective persuasion is a negotiating and learning process through which a persuader leads colleagues to a solve a problem through a shared solution. Persuasion requires careful preparation, constructed arguments, evidence, and emotional match
Four ways not to persuade:
  1. State a position at the outset, and then by process of persistence, logic, and exuberance try to push the idea!!
  2. Resisting compromise or middle-ground
  3. Believing that arguments and logic always win
  4. Believing that persuasion is an one-shot effort
Effective Persuasion:
Involves phases of discovery, preparation, and dialogue; dialogue happens before and during the persuasion process. Before the persuasion process, use dialogue to learn about the opinions, concerns, and perspectives. During the persuasion process, you invite people to discuss, even debate, the merits of your position, and then to offer honest feedback and suggest alternative solutions.

Most effective persuaders seem to share a common trait: they are open-minded, never dogmatic

Four essential steps in persuasion:
  1. Establish Credibility
  2. Identify common grounds with audience
  3. Use vivid language and compelling evidence
  4. Connect emotionally with audience
Establish Credibility:
In the workplace, credibility grows out of two sources: expertise and relationships; people with track record and who are known to be honest, steady, and reliable have an edge when going into any persuasion situation.

Evidence:
Supplement numerical data with examples, stories, metaphors, and analogies to make their positions come alive

Comments

Post a Comment

Popular posts from this blog

No Non-Sense Transformation

‘Context’ Many years ago, when we first started setting up shared services in a major technology firm, we embarked on a journey that had many unknowns. Whether it was scope of work, projects, technology, or processes – nothing was clearly outlined. We had few excel sheets to guide us through the process of setting up shared service organization. It was no more than a simple ‘lifting’ of processes from each entity into a regional centre. The initial days were tough – It was about power, control, and other hidden aspects in organization. The lower end resources who managed the day-to-day operations struggled to meet the expectations from the internal clients. We had ‘all fingers pointing at one direction: shared services’, and always for the wrong reasons. ‘No defined parameters’ Now, when I look back to the unwieldy phase – it appears that there were number of interventions that could have been employed to mitigate the organizational resistance. In my experienc...
Read more

Patrick Pichette and Art of Corporate Finance in IT Industry

I was reading through Patrick Pichette's interview with Mckinsey Quarterly last week, and it was perhaps one of the few interview reports that made me sit back, read, read, and read through again. Its quite an old interview, but worth looking given its relevance in today's fast changing IT landscape. The report certainly made me to think about many aspects of corporate finance and strategy. Patrick's  ideas are certainly commendable and thought provoking - From managing Short Term metrics to Start-Up culture. Here are some excerpts and my thoughts... 'Managing Short Term/Tactical metrics' Managing short term metrics is part of corporate life once an organization goes public. There is a general expectation from investing community to meet/beat analyst estimates and that puts a lot of pressure on C-Level executives. Nevertheless, it is required of C-Level executives to meet short-term goals as well as long-term vision. In the report, Patrick suggests that short...
Read more

The RASSP in IT Architecture

The QUALITY Attributes are those that defines how the system should perform over a business cycle/Time Period. Fundamental to good IT design is forecasting the business peaks and troughs and how the system should behave over the business cycle. When there are peak loads, systems should automatically be able to scale and perform with consistent service level agreements. However, there are several cases in the past where such quality attributes were ignored leading to loss of revenue. Quality Attributes can be either run-time or non run-time attributes. Clearly, from a business standpoint, the run-time consideration is of prime importance as no one would want to lose business because of a system downtime or a performance lag. The blog post focuses on the run-time considerations an architect should adhere when making architecture decisions. The following attributes are considered the most important run-time attributes when designing new systems. Reliability (R), Availability (A), Sca...
Read more