It's not about winning the debate...

Despite its "Trump" headline, this article from the Harvard Business Review is a good guide on how to encourage someone to change their mind about something. The suggestions would be useful for all sorts of arguments - whether Trump or Clinton now, or closer to home the Brexit controversy or more mundanely for issues in any office or workplace.

Calling people names, pretty obviously, doesn't work. It may vent our frustration, or reaffirm our affinity to our group, or even stake a moral claim (e.g. calling someone a bigot is also claiming that we're better than them); what it won't do is get the victim of the name-calling to change their mind . f anything, it will strengthen their resolve.

Arguing through logic sounds more reasonable, but often doesn't work. This is partly because people don't work 100% on logic, and partly because a debate becomes a contest in which we want to win (and, possibly, be seen to win). Losing a contest isn't a good motivation for someone to change their mind; they want to make a positive choice, not to feed the winner's ego.

It's not about winning the debate; it's about encouraging someone to change their mind. As the old quote says, "It's amazing what you can accomplish if you don't care who takes the credit".

Comments

Webinar: Powering your business with Cloud Computing

On October 14th, I will be hosting a Grid Computing Now! web seminar on the topic of Cloud Computing. We have lined up two very interesting speakers who are using Cloud now to make businesses work. Ross Cooney had a good technological solution to sell but couldn't make it economic until Cloud Computing allowed him to pay for his computation only when he needed it. He will discuss the instant benefits and long term impact of cloud computing to the development, competitiveness and scalability of your application. Alan Williamson created the BlueDragon Java CFML runtime engine that powers MySpace.com. He advises several businesses and will give an overview of the different types of services available and how to avoid being locked-in to a single supplier. You can register for this event here .

Business Model Canvas

A Business Model Canvas is a tool for mapping the core functions and capabilities of an organisation. Compared to the Core Diagrams that I described in an earlier post , the business model canvas attempts to present more aspects of the business, starting with the value proposition – a statement of what the organisation offers to its users (in the business world, to its customers). It shows the activities and resources, as Core Diagrams do, but also shows user relationships & channels, and also benefits and costs. I’m not aware of any universities that have used this tool but you can find examples from elsewhere on the web. We are considering business model canvases as a tool for mapping the strategic capabilities of units at the University of Edinburgh. Phil Taylor, our EA contractor, sketched an outline of what a business model canvas might begin to look like for HR: This is only intended to be suggestive: the real canvas would need to result from in-de...

Changing Principles

In EA, architecture principles set a framework for making architectural decisions. They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects. Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community. Many organisations take the TOGAF architecture principles as a starting point. These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure. These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure. See for example the principles adopted at Plymouth University and the University of Birmingham . Recently though, I encountered a different way of looking at principles. The user experience design community tend to focus more on how we should do things. E.g. we should...

Distributed Thinking

Search This Blog