There is a lot of fuss around on the on-line networking sites at the moment that is basically asking 'what's the the point of networking'. Here's the response I gave to a LinkedIn question on this subject...
"...The point of networking in my view is to build trusted relationships, providing a support and 'friendship' infrastructure - you have to give, give, give and occasionally you get to 'take'. Building these relationships might lead to sales, but it may not be direct sales, rather leads and referrals from folks that trust you to deliver. "
If we apply this to managing change, answering the question of 'what's the point of networking in managing change', I wouldn't change my answer much...
"The point of networking IN MANAGING CHANGE in my view is to build trusted relationships, providing a support and 'friendship' infrastructure - you have to give, give, give INFORMATION and occasionally you get to 'take' THE DESIRED (BEHAVIOURAL) CHANGES. Building these relationships might lead to CHANGE, but it may not be direct, rather STEPS ALONG THE PATH from folks that trust you to deliver. "
The point is that we need to build relationships with people, and build a network of colleagues, suppliers, partners etc that can help us achieve the ultimate goals of our projects - the enduring change that creates the value required. When I worked for a major corporate it was clear that my network helped me deliver, and working on a shorter-term assignments still requires these relationships to be built-up, only more quickly.
I deliberately left the term 'stakeholders' off of my list above - depending upon what you need to achieve, the stakeholder groups that are most affected by the change are probably those where your networking skills will be most valued. You need to nurse those affected by the change, whether as the sponsoring community (who might get fired if it fails!) or those directly impacted through the new systsem, company acquisition, outsource or whatever. It is ultimately 'people that stop change', so you need to ensure that you understand their fears, worries, crises and how you might steer them in the direction of accepting and embracing the change.
There are of course a lot of techniques to help you do this, but that is for another day!!
Managing change in your organisation is a real challenge - lets talk about it, develop ideas, and rant and rave. Let's remember that change in people's business lives affects their real lives too.
Showing posts with label value creation. Show all posts
Showing posts with label value creation. Show all posts
Thursday, 24 May 2007
Tuesday, 27 February 2007
How important is being a 'trusted adviser' to clients?
I was asked this a few days ago, so thought I would quickly articulate my views here.
Without trust, it seems to me that relationships are ineffective. Individuals will never achieve optimum performance and the benefits from the relationship will not achieve their full potential.
As a consultant, one strives to become a 'trusted adviser' - as a professional person a consultant strives for client satisfaction as well as personal satisfaction - in a change environment one would gauge this as benefits delivered (exceeding those required if possible) along with the behavioural and process changes that ensure that those benefits endure. As a trusted adviser the consultant is taking the client relationship to the next level - not necessarily for mercenary reasons - endeavouring to use their skills and 'wise counsel' to support their client through whatever challenges faces them.
It seems to me that this is critical to development of a long-term professional relationship, with potential benefits to the consultant of further work and referrals.
Without trust, it seems to me that relationships are ineffective. Individuals will never achieve optimum performance and the benefits from the relationship will not achieve their full potential.
As a consultant, one strives to become a 'trusted adviser' - as a professional person a consultant strives for client satisfaction as well as personal satisfaction - in a change environment one would gauge this as benefits delivered (exceeding those required if possible) along with the behavioural and process changes that ensure that those benefits endure. As a trusted adviser the consultant is taking the client relationship to the next level - not necessarily for mercenary reasons - endeavouring to use their skills and 'wise counsel' to support their client through whatever challenges faces them.
It seems to me that this is critical to development of a long-term professional relationship, with potential benefits to the consultant of further work and referrals.
Labels:
change consultant,
change management,
value creation
Wednesday, 24 January 2007
Managing the financial impacts of change
I've had a few discussions lately about financial control in a change and project environment. Too much to discuss in detail here, but here's a 'top of my head' list of the things that you might do to keep financial control of your project;
- Build a narrative business case, and detailed plan;
- Align that to detailed numbers - implementation (revenue) expenses, capital expenses phased to show cashflow (cash is king!), and benefits case - what will be delivered when and what will the real impacts be;
- Develop a risk weighted NPV - use factors such as 'do we know how to do this?', 'do we have the resources?', 'budget?' to show an NPV - over time improve the NPV by adjusting the risk factors as you satisfy yourself that you can achieve it. The NPV (or ROCE) is a great measure to show expected financial outcomes.
- use qualitative measures to support your numbers (which of course you will monitor in detail weekly/monthly!) - are deliverables being completed or is there a bow-wave of activity building up with consequent cashflow impact, are the numbers and criticality of open issues/risks increasing etc
- Use graphs to compare measures - see the relatives as well as the absolutes.
- Make sure any numbers that you use are reconciled to source data (ie; are accurate), and preferably 'triangulated' to two sources
With proper (basic) systems and processes, much of this monitoring can be automated!
Enough for now!
Wednesday, 17 January 2007
Why do we deliver change...to create value
We deliver change to create value - that's it. I've written on this subject before but given one or two discussions I've had recently thought it worth reiterating the point.
Change is a difficult thing. But it must always have an ultimate goal - in corporate life we deliver change because it creates shareholder value (it is difficult to see any other reason), and in the social and governmental sectors we might go through a change programme to establish some social or environmental improvement. Why would you go through potentially gut-wrenching change for no good reason?
Change is a difficult thing. But it must always have an ultimate goal - in corporate life we deliver change because it creates shareholder value (it is difficult to see any other reason), and in the social and governmental sectors we might go through a change programme to establish some social or environmental improvement. Why would you go through potentially gut-wrenching change for no good reason?
Tuesday, 16 January 2007
Facilitation for change - tools to support us through change
I've been along to a meeting today - these folks are all professional facilitators based in central England, and much of what they do is help groups of people achieve their change goals (as well as mediation, public policy and loads of other things). It is a long time since we could rely on things to 'just happen', and facilitated workshops, conferences, meetings etc help in ensuring that objectives are achieved.
This got me thinking - as change consultants/change managers what do we have in our armoury to help us through some really tricky people-related change activities. Here's my list off the top of my head...
This got me thinking - as change consultants/change managers what do we have in our armoury to help us through some really tricky people-related change activities. Here's my list off the top of my head...
- processes to support change analysis
- project and programme management approaches
- Communications expertise; and
- Professional facilitation of course
....but other than experience and common sense probably not a lot else.
If you want to get in contact with any of the UK Facilitators let me know.
Thursday, 4 January 2007
Project Management and Change Management
There is a debate going on in another forum about the use of structured project management methodologies (eg; Prince 2) versus the management of change. We need to be clear that project management is not the same as change management - managing the project is part of managing the change, but it is a relatively mechanistic process, providing the assurance of technical delivery and to some extent the delivery of the benefits. Change management is about delivering the behavioural change that ensures that the benefits endure, that the technical changes are accepted, and that the expected outcomes are achieved.
Another way of looking at this is that there are many more people involved in delivering the change (the sponsor, Board, managers etc), whereas the project processes can be delivered by the Project Manager (who, if they are enlightened/experienced will be focussed on delivering the change as well as the technical delivery).
One thing that annoys me is where some third party suppliers/partners (in IT particularly) tend to come along after winning a contract and expect that they can simply implement their bit of technology and it will work and be accepted - they often get a shock and then cost overruns etc, and consequently relationships start to fail between supplier and customer....the real world is difficult!
Here's a link to a basic project/change role comparison from the change management learning center if you're interested.
Another way of looking at this is that there are many more people involved in delivering the change (the sponsor, Board, managers etc), whereas the project processes can be delivered by the Project Manager (who, if they are enlightened/experienced will be focussed on delivering the change as well as the technical delivery).
One thing that annoys me is where some third party suppliers/partners (in IT particularly) tend to come along after winning a contract and expect that they can simply implement their bit of technology and it will work and be accepted - they often get a shock and then cost overruns etc, and consequently relationships start to fail between supplier and customer....the real world is difficult!
Here's a link to a basic project/change role comparison from the change management learning center if you're interested.
Friday, 8 December 2006
Big business - talking about the importance of people
Well, well, well. On today's BBC 'Working Lunch' programme (I do not spend all day watching television, honest), Ben Verwaayen CEO of BT spoke about the importance of people in this FTSE 100 company - watch the video. Mr Verwaayen was excellent, and tied BT's business strategies into the 100000 people globally who have to deliver them. He clearly has a grip on what makes companies tick, and the need to get BT's people behind him. What amazed me, was that it is rare that you hear a big-company CEO talking like this (and the interviewer's preamble outlines Mr Verwaayen's credentials from a people point of view).
Excellent interview if you're interested in change in the real world!
Excellent interview if you're interested in change in the real world!
Thursday, 7 December 2006
The whole point is to deliver value
I'm an accountant - but I'm not boring! I've admitted it, owned up to it. Done.
This admission is important - the reason that we implement projects and programmes is to deliver value......isn't it? So you would expect me to say nothing matters other than the financial impacts of the change activity. What will implementation expenses be, when and how are benefits realised, how can costs be capitalised, who has got the budget etc...
OK I would say all of those things - in the business world we have to deliver value to all our stakeholders, but we also have to think that there may not only be a financial business case that we need worry about, but all of the other impacts of our projects. Take the petrochemicals sector for instance - a project that develops relatively environmentally-friendly biofuels (see the UK Chancellor of the Exchequer's comments on this in yesterday's pre-budget report) deliver value in other ways, not just financial. This is important - selling the change on the basis of environmental benefit may be more relevant to some stakeholders than 'we save £xm over 10 years'. We need to determine all of the benefits and make sure that they're sufficiently developed to get people to accept the change. It may be possible to tweak a programme of work to (cheaply) gain additional benefits that make the change more palatable. Whichever way, it is critical that the benefits case is worked up in detail at the beginning of the project rather than the end!
This admission is important - the reason that we implement projects and programmes is to deliver value......isn't it? So you would expect me to say nothing matters other than the financial impacts of the change activity. What will implementation expenses be, when and how are benefits realised, how can costs be capitalised, who has got the budget etc...
OK I would say all of those things - in the business world we have to deliver value to all our stakeholders, but we also have to think that there may not only be a financial business case that we need worry about, but all of the other impacts of our projects. Take the petrochemicals sector for instance - a project that develops relatively environmentally-friendly biofuels (see the UK Chancellor of the Exchequer's comments on this in yesterday's pre-budget report) deliver value in other ways, not just financial. This is important - selling the change on the basis of environmental benefit may be more relevant to some stakeholders than 'we save £xm over 10 years'. We need to determine all of the benefits and make sure that they're sufficiently developed to get people to accept the change. It may be possible to tweak a programme of work to (cheaply) gain additional benefits that make the change more palatable. Whichever way, it is critical that the benefits case is worked up in detail at the beginning of the project rather than the end!
Subscribe to:
Posts (Atom)