Intranet Portal Guide eBook

    Purchase the full Intranet Portal Guide for $16.88 from Diesel eBooks.














Saturday, December 18, 2004

Stakeholder Analysis and Stakeholder Management


What is a Stakeholder?

Try “define: Stakeholder” in Google and you will be surprised by the huge differences in the way this simple word is defined. It perhaps proves - in a way - just how confused people get about Stakeholder Management and how inconsistent the different approaches to it can be!

My simple definition is “anyone affected by a decision and interested in its outcome”. This can include individuals or groups, both inside and outside your organisation.

Stakeholder Analysis

The first step in Stakeholder Analysis is to assess the Influence and Importance (two different things!) of each individual Stakeholder or Stakeholder group.

Influence is defined as the extent to which a stakeholder is able to act on project operations and therefore affect project outcomes. Influence is a measure of the power of the stakeholder. Factors likely to lead to higher influence include the extent of control over the project funding and the extent to which the stakeholder informs decision-making around investments in technology and business change.

Importance is defined as the extent to which a stakeholder’s problems, needs and interests are affected by project operations or desired outcomes. If ‘important’ stakeholders are not assisted effectively then the project cannot be deemed a ‘success’.

Where Stakeholders are both important and influential, then they are primary stakeholders and must by fully engaged in the governance and steering of the project, if it is to succeed. Where Stakeholders are either important or influential, then they are secondary stakeholders and need to be actively managed during the project.

The second step in Stakeholder Analysis is to understand the current position of each Stakeholder with respect to the project objectives and expected outcomes. For this purpose, a series of Stakeholder Interviews and Surveys should be undertaken, to understand the degree of engagement and the degree of commitment.

Engagement is a measure of how well the Stakeholder understands the challenges the project seeks to tackle and the strategy, plans and outcomes. A low engagement score signals a lack of understanding.

Commitment is a measure of how supportive the stakeholder is. A low score signals hostility, whilst a high score signals strong support.

Ideally, of course, any project wants engaged, informed stakeholders who actively support the project objectives and outcomes. An ill-informed supporter can be just as dangerous as a well-informed objector!

Stakeholder Management

There are many different suugested approaches for Stakeholder Management. In the chapter on influencing (stakeholders) in my (free to access) Intranet Portal Guide, I offer a simple, tried and tested, four-way approach:

1) Partner
Primary stakeholders (with high influence and importance to project success) are likely to provide the project ‘coalition of support’ in planning and implementation. As such, you should partner them to increase their engagement and commitment (revising and tailoring project strategy, objectives and outcomes if necessary to win their support).

2) Consult
Secondary stakeholders with higher influence but lower importance need to be ‘kept on board’. You should consult with them to actively seek their opinions and input for key decisions (and not only those which may affect them directly). It is unlikely you would alter your strategy as a result of such consultation, but you might well alter your tactics (e.g. the who, when or where of project plans) to maintain higher levels of commitment.

3) Inform
Secondary stakeholders with lower influence but higher importance need to be kept informed of decisions taken that may affect them directly. It is unlikely that they would play an active role in making those decisions. However, were they to highlight a particular issue with a decision, it is likely serious consideration would be given to refining the decision made.

4) Control
Control is appropriate where a stakeholder isn’t important or influential and they need help only to respect any decisions taken. Objections to or issues raised are unlikely to be given serious consideration (as they would otherwise divert valuable management attention and resources).

Conclusions

Stakeholders are key to successful Project Delivery in the modern organisation. Both Stakeholder Analysis and Stakeholder Management are vital tools and should be used iteratively throughout a project to keep everyone on the same page. Be aware that different approaches are appropriate for different Stakeholder types. You can't keep all the people happy all the time. Check out my guide for more hints, tips and tools.

About the author:

David Viney (
david@viney.com) is the author of the Intranet Portal Guide; 31 pages of advice, tools and downloads covering the period before, during and after an Intranet Portal implementation.

Read the guide at
http://www.viney.com/DFV/intranet_portal_guide or the Intranet Watch Blog at http://www.viney.com/intranet_watch.

Wednesday, December 08, 2004

Intranet Portal - Business Case ROI


The days of easy money are over

In these post-dot-com days of the 21st Century, the hype attached to IT is well and truly over. The modern Board is deeply suspicious of large IT projects with questionable benefits and a long-term payback period.

The good news is that a world-class portal implementation has the power to completely transform your organisation and touch everyone, from the office of your CEO to the lady in the canteen.

First a little on Costs

Sorry, but the cost of the software is only a relatively small part of the overall bill; with other major costs in hardware, process change and integration activities. Your first (and major) portal project is (in terms of cost) more an infrastructure investment than it is an application.

As a rough rule of thumb (for a user base >10,000), budget for £250 per desktop to put in the essentials (including portal and content management solutions). If you are also integrating to (and exposing) your ERP or CRM systems, add £150.

Direct Benefits

Based on my experience, Direct Benefits (those that you can directly bake into line budgets and make an individual directorate accountable for realising) are only 20-25% of the total prize and will not generally cover the portal implementation costs by themsleves. Direct benefits include reduced printing and distribution costs, decommissioning legacy intranets and FTE savings in operational areas (including IT development & support, Finance & Procurement ledger processing and HR employee services).

Soft Benefits include improved employee satisfaction, better communication and corporate belonging, the importance of which should not be under-estimated in your business case. After all, there is always an emotional, as well as a rational, reason for every purchasing decision.

However, the bulk of portal benefits are Indirect Benefits, where time saved in line areas leads to (for example) reduced call times in call centres, higher sales, faster time to market for new products, fewer failed projects and so on. Benefits realisation is the issue with such benefits. After all, you can't fire 10 minutes of a person a day! The time they have saved is real - ultimately saving cost and driving sales - but it cannot be readily tracked to either.

Making the Business Case: A 10 Step Approach

In
chapter 8 of my (free to access) Intranet Portal Guide, I outline a 10 step approach to making the portal business case.

1) Seek External Legitimacy
Consider using a leading consulting firm to lend weight to the business case. They can bring with them experience (from having done it before elsewhere), a knowledgebase (of facts and figures about the benefits other companies have achieved) and a fresh perspective on your organisation, valued by executives.

2) Benchmark other Organisations
I have included in my guide details of public-domain benefit claims from early UK & US portal adopters, including British Airways, BP, Ford Motors Company, IBM, Bell South, Dow, Cisco and BT. Showing your Board that others have delivered real benefits lessens the feeling that their decision is a ‘leap of faith’.

3) Collect Hard Metrics
Direct benefits may be only 15-25% of your total benefits, so work hard to identify savings in Intranet & Collaborative decommissioning; Print, Postage & Distribution Costs, Processing Manpower reductions; and Third Party expenditure savings.

4) Use a Comprehensive Time Survey
In my guide, I suggest that you survey several hundred (representative) users to establish how much time per day they expect to save by using key portal functionality. This will help you to put a financial value on indirect benefits. I outline 10 sample questions and provide benchmark results you could expect to see.

5) Build a Wall of Benefits
When you are trying to build an ROI based on indirect benefits, you can expect those benefits to be challenged vigorously. By having literally hundreds of individual line items and a big overall total, you improve your chances of surviving the Finance ‘Red Pen’. In my guide, I outline 101 benefit ideas to get you going.

6) Link to the Strategic Agenda
Tie the investment closely to the Strategic Agenda of your organisation. If there is another key initiative currently grabbing all the attention at board level (e.g. CRM or ERP) then make sure your portal case complements, or ideally completes, that strategic picture. Use camaoflague if necessary, as all is fair in love and war!

7) Identify 2-3 Killer Apps...
That will focus the attention (and support) of key sponsors. Look for win-win apps, where the user loves using them but the provider department also extracts key benefits. For example, a self-service HR application where the employee can keep their details up-to-date easily and the company can reduce employee service heads.

8) Use a Cost Avoidance Argument
Your investment will reduce future project costs. After all, a portal is essentially a free infrastructure, a free user interface, a free user client with pre-built security & authentication and a free development framework. HP and others have saved up to 20% on development costs, post-implementation. You could too, so raid the budgets of other approved projects!

9) Consider Larger Scope
Could you make your case if you include internet and extranet in scope? An extranet allows you to securely expose part of your intranet to slected third parties, including B2B customers, suppliers, regulators and government agencies. The incremental cost is quite low, once your intranet platform is there, but the benefits can be large!

10) Use Innovative Phasing
Most companies budget on an annual cycle and are under huge pressure from investors to deliver short-term profitability. The bitter pill of portal costs might be easier to swallow if you spread the implementation over a two year period.

Conclusions

Making the business case for a corporate Intranet Portal will not be easy. You will need all your reserves of patience, cunning and good olf-fashioned hard work. Good luck and don’t forget to check my guide for more detail, help and tools.

About the author:
David Viney (
david@viney.com) is the author of the Intranet Portal Guide; 31 pages of advice, tools and downloads covering the period before, during and after an Intranet Portal implementation.

Read the guide at
http://www.viney.com/DFV/intranet_portal_guide or the Intranet Watch Blog at http://www.viney.com/intranet_watch.