Stakeholder

One of the more difficult management decisions is how hard to pursue a contract claim. The claim will inevitably have a deleterious impact on a key stakeholder relationship and any significant claim will have proportionally high costs associated with legal and other expenses. Balancing the inevitable costs against the possible gains is a difficult but necessary decision before moving forward. Usually, the potential yield of a claim is given as a subjective assessment based on experience.

Dr. John Lancaster of Hill International has recently published a paper that seeks to remove the subjectivity from the assessment of which claims are worth pursuing (see 1 below). Lancaster proposes using a risk assessment approach to determine the likely range of outcomes and which claims contribute the most to the likely settlement. He suggests using the following factors:

• Entitlement confidence:
  • The strength of the contractual argument for entitlement; and
  • Contractually compliant notices.
• Magnitude confidence:
  • The quality and quantity of supporting records;
  • The quality of the project schedules (and any necessary corrections and/or repairs), cost records, etc; and
  • The certainty with which the effect/s of each event is known.

Applying a percentage weighting to these factors and using Monte Carlo analysis the likely range of cost and time outcomes can be assessed and the key claims identified.

It is important that the right people complete this assessment: the entitlement confidence categories should be assessed by counsel and the magnitude confidence categories assessed by the domain experts with input from the project staff.

The results of this analysis will identify:

• The likely outcomes under the prevailing entitlement and magnitude confidence ratings;
• The probabilities of securing different outcomes; and
• Identifying the claims that are the most important to the overall claim and which ones require more work.

Based on this assessment and after factoring in the costs and consequences of making the claim, pragmatic decisions can be made on:

• whether or not to pursue a claim;
• where to set negotiation limits (see 2 below); and
• which of the claims, with more work on establishing entitlement and/or substantiation, could contribute the most to a robust claim.

In an ideal world effective stakeholder relationship management would remove the need for contractual claims. When they become necessary, Dr. Lancaster’s ideas will help remove much of the unnecessary ‘heat’ from the assessment process and provide a pragmatic baseline for managing any claim in a professional and business like way.

1. Lancaster, John, “The use of risk analysis techniques to evaluate potential delay claim outcomes,” Project Control Professional: The Journal of the Association of Cost Engineers, February 2010. The full article is available on request from johnlancaster@hillintl.com.
2. For more on dispute management and negotiating see: http://www.mosaicprojects.com.au/WhitePapers/WP1049_Dispute_Management.pdf

My original thesis has recently been published as a book by Lambert Academic Publishing AG & Co (www.lappublishing.com).

Details of the book are:
Project Relationship Management and the Stakeholder Circle [Paperback]
ISBN-13: 978-3838398167
Available from Amazon at: http://www.amazon.com/Project-Relationship-Management-Stakeholder-Circle/dp/3838398165/ref=sr_1_1?s=books&ie=UTF8&qid=1282809735&sr=1-1

The research described in my thesis underpins the Stakeholder Circle methodology and tools which led to the publication of Stakeholder Relationship Management: A Maturity Model for Organisational Implementation and the SRMM maturity model available from Gower Publishing at http://www.gowerpub.com/isbn/9780566088643

One of the key skills required by project managers, in fact all managers, is the ability to motivate team members and the wider stakeholder community.

Most business approaches to motivation are based on extrinsic motivators – if you achieve ‘A’ we will reward you with ‘B’ and if you are really good and make ‘2A’ we will give you ‘2B’. The theory used by business is based on the assumption the larger the reward the greater the motivation; provided basic principles such as fairness are applied and the reward is commensurate with the effort needed and expectations of the person being motivated. It is assume the increase in motivation will flow through to increased performance.

Management scientists way back to Henry Gantt had established that in the ‘carrot-and-stick’ approach to motivation, fear and the ‘stick’ had little effect, the ‘carrot’ and reward had measureable effect. However, these studies were applied to manual workers.

More recent work by researchers such as Hertzberg in his ‘Hygiene Theory’ (1959) and Maslow’s pyramid of need (1943) placed salary (wages/reward/income) relatively low down the list of motivators. As long as the ‘pay’ was what was expected it had little extra value; inadequate rewards could quickly de-motivate, but once adequate levels were reached ‘pay’ simply came off of the table. This is a basic part of our PMP courses, hardly new or exciting….

However, I have just watched a fascinating video on TED, by Dan Pink, on the surprising science of motivation: starting with a fact that social scientists know but most managers don’t: Traditional rewards aren’t always as effective as we think.

A brief summary of the presentation is that traditional rewards do work for simple manual tasks. However, as soon as creative thinking is needed extrinsic rewards have the opposite effect by focusing effort in a narrow band and stopping the more creative thinking needed to solve the problem. The results are measurable negative performance, increasing as the reward increases.

According to Pink, the motivators that do work are intrinsic:

• Autonomy: control and self-direction over the work.
• Mastery: the ability to excel at the work by getting better and better at difficult tasks.
• Purpose: the work contributes value to the organisation and others (in the service of something larger).

These motivators are very similar to the ideas of Maslow and Hertzberg briefly discussed above, and McGregor (Theory X, Theory Y – 1960). What’s fascinating in Pink’s presentation is the fact most organisations reward their senior decision makers with huge pay bonuses to solve some of society’s most difficult problems (and wonder why they fail so often…).

To see the presentation, go to the TED website at: http://www.ted.com/talks/lang/eng/dan_pink_on_motivation.html – whilst there it is well worth browsing, there are dozens of other fascinating presentations.

Methodologies define a step-by-step process for delivering projects. Each methodology will describe each step in adequate depth, so that the project team understands what has to be done to deliver their project. This is quite different to a standardised knowledge framework such as the PMBOK® Guide (for more on this see: PMBOK -v- Methodology).

By using the same steps for every project the organisation undertakes risks and uncertainty are minimised and there is likely to be an overall saving of time and effort on projects.

Defining ‘your’ methodology

The key steps to follow are:

• Define what it is that you want from your methodology, the type of content it should contain and the way in which it will be used.
• Create a set of specific requirements. Some options include defining:
  • How much of the project lifecycle needs to be incorporated
  • How much detail should be included? What practical templates and examples are needed to help to complete the step quickly and easily?
  • Should it follow one of the worldwide project standards such as the PMBOK® Guide?
  • Can/should the system be easily customised suit all project types and sizes?
• Determine the best methodology to use:
  • Review the methodologies used currently by your organisation and compare them to your requirements to see if there is a good fit.
  • Review the commercially available methodologies to see if there is a good fit.
  • Select the option with the best fit to your requirements
• The best methodology is still only likely to have a 90% fit (or less), this is normal. Make sure you can customise the remaining elements to meet your requirements.
• Ensure adequate flexibility for the range of projects in your organisation.

Implementing the methodology

The key steps are:

• Create an Implementation Plan supported by a change management plan. Implementing a methodology is a significant organisational change.
• Run the implementation as a change management program, including customising the methodology for your environment. Stakeholder engagement is vital to the overall success of the initiative.
• Train the users and support staff in the methodology and ensure ongoing support.
• Ensure the methodology is followed.
• Start improving the methodology (for more on measuring and improving the organisations project management maturity see Mosaic’s OPM3 home page).

Improving the methodology

Processes are always capable of improvement. Observing the actual implementation of the methodology will define actions and outcomes within the following matrix.

Unauthorised, unproductive activities need to be stopped and authorised productive processes supported. The two zones for process improvement are refining or removing elements of the methodology that do not add value to the overall management of the project and incorporating unauthorised processes that are not in the methodology but that are being used add value.

The easiest and most important area for action is rectifying the unproductive processes already in the methodology. Care need to be taken to ensure the definition of ‘unproductive’ is understood. Most planning processes don’t produce anything and consume effort; superficially they can be classified as ‘unproductive’. In reality, effective planning contributes significantly to the efficient delivery of the project and its value to assist in the efficient execution of the work being planned is significant.

Excessively detailed planning though is usually counterproductive. Value judgements are needed to assess the point at which adding more detail or rigour becomes ‘planning overkill’ reducing the overall value of the process and conversely, how much detail can be safely removed from a planning processes to improve overall productivity before insufficient planning starts to cause problems.

Adapted from Firdman, H. E. (1991). Strategic information systems: Forging the business and technology alliance. McGraw-Hill, New York.

Adapted from Firdman, H. E. (1991). Strategic information systems: Forging the business and technology alliance. McGraw-Hill, New York.

Ensuring the methodology is seen as ‘productive’ is essential for it to be generally accepted and supported by your stakeholders.

Once the existing methodology is optimised and firmly in the ‘authorised and productive’ segment, the next area is to examine unauthorised processes that aid productivity and progressively incorporate these into your methodology. The ‘unauthorised and productive’ quadrant is where you find genuine innovation and opportunities for organisational gain.

Summary

No methodology works ‘out of the box’ they all need customisation and tailoring. However, the effort is worthwhile. OPM3 has demonstrated standardised processes that incorporate best practices can provide significant benefits to an organisation (see more on OPM3).

The challenge is balancing systemised processes with the need for adequate flexibility to deal with the circumstances of each unique project. An effective project management methodology needs core components, scalable components and optional components designed to meet the needs of your organisation.

The military doctrine of ‘command and control’ heavily influenced the structural approach to management characterised as ‘Scientific Management’ and the works of Taylor (1911). Scientific management assumes, amongst other things, that ‘supervision must be achieved through a clear chain of command and through the application of impersonal rules’ and that ‘only those at the top have the capacity and opportunity to direct the enterprise’. This philosophy has strongly influenced the development of project management (see: The Origins of Modern Project Management). But does this represent effective military management?

Following the defeat of the Prussian armies by Napoleon at the battles of Jena and Auerstedt in 1806, the concept of ridged process-oriented command and control structures has been progressively replaced by the concept of ‘auftragstaktik’, or directive command. These ideas were originally championed by Major General Gerhard von Scharnhorst and were formalised by German Generalfeldmarschall Helmuth von Moltke who was the chief of staff of the Prussian Army for thirty years from 1857.

The core concept of auftragstaktik is ‘bounded initiative’. Provided people within the organisation hierarchy have proper training and the organisational culture is strong, the leader’s role is to clearly outline his/her intentions and rationale. Once this is understood, subordinate personnel can formulate their own plan of action for the tasks they are allocated and design appropriate responses to achieve the objectives based on their understanding of the actual situation, exploit opportunities and mitigate problems.

The investment necessary to achieve this capability is not simply a question of financial and material resources – time is critical both for the training of individuals and the development organisations. In von Moltke’s army, a junior Prussian commander exercising his initiative on the battlefield was most likely drawing upon a variety of resources at his disposal including:

1. his understanding of his commander’s explicitly stated directive that would have provided him with an appreciation of the situation, a specific task, and a description of the commander’s intentions;
2. his beliefs about his organisation, his role within that organisation, and the degrees of freedom available to him in the exercise of that role;
3. his expertise in the technical aspects of the military profession and
4. his understanding of his commander and his peers.

These latter aspects are captured in the notion of ‘implicit intent’, would provide him with the basis for his course of action and bound the solution space available to him.

A General may wish to defend a city, a Brigade Commander defend his designated sector and within the sector, a Platoon Commander may be tasked with establishing a road block which involves one of his NCOs establishing a strongpoint. The General does not need to instruct the NCO on how to site the strong point, camouflage it or man it. At each level, good leaders will think ‘two levels up’ and provide oversight ‘one level down’. The process is not random, Standard Operating Procedures (SOP) define how specific tasks should be accomplished and ‘bounded initiative’ allows the individual leader to optimise the SOP for the specific circumstances he or she encounters to best support the overall intent of the commander. Von Moltke emphasised that he wanted to ‘steer’ initiative in the right direction.

These concepts are closely aligned with the human resources approach to management, which developed in the 1950s and 60s and emphasise a symbiotic relationship between individuals and organisations where ‘democratic leadership is the most effective means of managing’ and ‘openness and participation are the most effective means of demonstrating democratic leadership’.

On very small projects, a project manager may be capable of directing and controlling the work of everyone in the team. However, as soon as the team or the technology grows beyond a relatively simple system direct ‘command and control’ becomes impossible and attempting to impose a ridged hierarchy based on formal instructions will lead to inefficiencies. Effective leaders need to establish clear guidelines and a system of protocols, chain of command, and standard operating procedures so that everyone in the project team knows what they to do and who is accountable. The overall action of the team is unified by the leader’s intent; within this space sub-teams and smaller work groups are allocated their individual missions and tasks within that higher intent. Once this framework is in place, properly trained team members can go straight into the performing stage of their activity.

This alternative to ‘command and control’ developed by the Prussian military in the 1860s allows a far more effective and efficient use of resources. Auftragstaktik is not an easy option, the team needs better leadership, better training and the willingness to engage in taking ‘bounded initiatives’ but overall it offers a much better way of achieving the project’s objectives.

Applying these concepts does not reduce the importance of the normal project management artefacts such as the schedule and cost plan; what changes is the way these artefacts are used. In a decentralised management structure, the Project Plan defines the guidelines and framework the team will work within rather than attempting to prescribe how they will work (for more on this see: Project Controls in the C21 – What works / What’s fiction).

I have just finished a week in Shanghai; the main purpose of my trip was to participate in a panel session at the CIOB International Construction Conference. For more on this see Patrick’s post CIOB Shanghai Meetings. However, the highlight of the trip was a day spent at World Expo.

The Expo is simply enormous. The site covers a total area of 5.28 square kilometres spread along both sides of the Huangpu River in downtown Shanghai; it includes gardens, wet lands, paved walkways and 100s of new and renovated buildings.

In the two months since opening the Expo has hosted over 20 million visitors and expects over 75 million before closing in October. On busy days over half a million visitors are on the site. Everywhere you look on the site there are queues but the organisers keep things moving, the officials are polite and helpful and the crowd rubs along without friction, maybe even enjoying the experience. From a stakeholder management perspective, expectations are managed and information is readily available, particularly if you speak Mandarin – international visitors are not likely to exceed 5 million.

The China Pavilion dominates the site and is a wonderful experience. For locals to visit the pavilion, someone has to join the queue outside the gates at 6:00am to so when the gates open at 9:00am they can be near enough to the front of the next queue at the China Pavilion to receive some of the 50,000 tickets issued daily to allow them join another queue for 2 to 3 hours to get inside to see and experience the exhibits.

I was more fortunate, the hosts of the CIOB conference were able to arrange VIP access but I can understand why the Chinese pavilion is worth the wait. Its exhibits really are wonderful. There are over 200 countries and international organisations represented, ranging from Tuvalu to the USA; the World bank to the International Council of Museums, as well as numerous major corporations and most Chinese provinces. Almost every pavilion had its queue! In a long day I only managed to see a small section of the total experience but could start to appreciate the overarching purpose of this great festival.

My visit to the Expo was a once in a lifetime experience. If you can’t make the trip personally, you can be a virtual tourist on line at http://en.expo.cn/. Either way World Expo 2010 is well worth the visit.

I never cease to be amazed by the number of people holding leadership roles in the project management community who denigrate ’soft’ skills. The latest attack on ‘soft’ skills is in a letter to the editor in the May edition of Project Magazine published by the APM, UK.

The Honorary Secretary of the APM Contracts and Procurement SIG, Gerry Orman states ‘soft skills are merely a form of manipulation’; and suggests including them in the knowledge framework for the project management profession will result in the dumbing down of our emerging profession. He also asserts the role of the project manager is to fulfil a contract, not deliver the project so apparently people leading the delivery of internal projects within organisations are not project managers!

Apart from the difficulty of defining projects in terms of one sourcing methodology, writing contracts, Orman seems to conveniently forget the thousands of contracts that end up in the courts each year because of the breakdown in relationships within the contract. Stakeholder management is a key skill for project managers, including identifying, prioritising the project’s stakeholders, and then developing effective communication within relationships that work (for more on this see WP1007 The Stakeholder Cycle). The success of the construction phase of Terminal 5 at Heathrow was largely due to BAA’s focus on the ‘soft’ skills needed to develop and sustain the integrated delivery teams that created the success. This was a revolution in procurement and supply chain management and led to this project being celebrated as the most successful construction project in the UK (for more on this see my presentation to the CIPS Australasia Strategic Procurement Forum in Auckland).

The same argument applies to most project management artefacts. The most perfectly developed schedule is totally useless if the information it contains is not communicated to the people who need to work to the plan; communication is a ‘soft’ skill. But communication on its own is not enough! The people receiving the communication need to understand the message and agree to use the schedule in the coordination of their work. This is unlikely to happen if the people have not been involved in the schedule development which requires more stakeholder engagement and communication, consensus building and a range of other ‘soft’ skills (see: Communication in organisations: making the schedule effective).

Putting it another way, developing an effective schedule that is useful because it is actually used to manage time on the project demands the project manager and/or project scheduler engage effectively with the people who will be responsible for implementing the schedule. This requires interpersonal, contextual and behavioural competencies.

Orman also states professional skills should be unique to the professions, examinable in a written exam and uses the medical profession as an example. Two members of our family recently completed a multi year journey to become qualified anaesthetists. Over the years there were many written examinations but there were also searching interviews and clinical assessments along the way and years of ‘apprenticeship’ under the direction of more senior professionals to ensure they were competent as well as knowledgeable. If medical professionals need more than book learning and written examinations why should project managers be any different?

Project success is achieved by persuading people in the project team to enthusiastically and collaboratively work together to achieve the contracted output. Developing a motivated team capable of achieving this requires a range of ‘soft’ skills including leadership, motivation, communication and conflict management to name a few. Organisations cannot do work; it is the people within the organisation that do the work and management is about directing and leading people!

Answering the question, what is more important, the ‘hard’ skills of scope management, scheduling and cost planning or the ‘soft’ skills of motivation, communication and leadership, is difficult. My feeling is the synergy of ‘hard’ skills powered by ‘soft’ skills will create a far more powerful engine for success than the sum of the two parts in isolation. Successful project managers need both capabilities either within their person or within their leadership team.

If we ignore stakeholders and the ‘soft’ side of our project management skill set we severely reduce our ability to meet our client’s requirements for on time on budget and on scope delivery. ‘Soft’ is not a synonym for easy!

Your project will only be considered successful if its key stakeholders perceive the project’s outcome as a success. These perceptions of success or failure are heavily influenced by the effectiveness of the project’s communications, and relationships, with its stakeholder community, particularly senior managers. Communicating effectively is both a science and an art framed within a relationship.

The starting point if you wish to be taken seriously is to develop a reputation for credibility. Senior management need to recognise that if you say something, it is backed up by facts, and if you commit to something, it is delivered. Credibility is earned by performance, but there is no harm in quietly making sure your performance is noticed in the right places. Your reputation is a general underpinning to all internal organisational relationships. Developing a specific relationship needs a specific, culturally appropriate focus before you can expect to communicate effectively.

Also, the last few years have seen significant changes in people’s understanding of acceptable behaviours and have forced a re-evaluation of the way Project and Program managers need to communicate to influence their stakeholders; particularly when ‘advising upwards’ and dealing with difficult people. The first key to building any effective relationship is to avoid stereotyping. Upwardly mobile managers with a focus on being promoted, frequently have a different life focus to project managers. These differences are not uncommon in successful senior executives and need to be respected as a component in the relationship, not denigrated.

The second key is to recognise that in every relationship there is a power dimension. How a senior manager uses his or her power is to an extent a generational issue. As long as they understand their purpose, many younger managers would see nothing wrong in a more junior manager setting reasonable boundaries and procedures to the relationship and communication. Older managers used to operating in a command and control environment are likely to react negatively to a ‘junior’ pushing rules upwards.

The solution is mutuality. You need to understand what you need from the relationship (support, resources, backing) and also what the senior manager needs from the relationship. Then, work within the relationship to negotiate mutually beneficial outcomes that meet both sets of requirements. It is by linking your needs to the achievement of the senior manager’s requirements; you can start to achieve real communication.

As already mentioned, crafting advice to senior management to achieve effective outcomes from the communication is as much an art as a science. Communicating for effect requires a clear understanding of the objective of the communication and the skills to create messages that are focused:

• On the right people
• At the right time and carry
• The right information in the right format.

Mutuality and credibility are the two keys to advising upwards, but in the end, all relationships depend on the situation. If you are seen as a serious contributor to the organization’s success and can link your needs to the needs of senior management, there’s a high probability of achieving your desired outcome and benefiting the organization at the same time.

My next book, Advising Upwards: A Framework for Understanding and Engaging Senior Management Stakeholders, will be published by Gower in 2011. For more on the book see: http://www.mosaicprojects.com.au/Books.html#AdvisingUpwards

In the meantime, our popular workshop, The science and art of communicating effectively will be run in Sydney and Melbourne over the next few weeks. For more information see: http://www.mosaicprojects.com.au/Training-Comms.html

Research by Dr. Brian Hobbs, University of Quebec at Montreal, Quebec, Canada published in a White Paper prepared for the Project Management Institute (PMI) highlights the precarious existence of the majority of Project Management Offices (PMOs). Approximately half of the PMO’s in existence are seeing their relevance or very existence questioned.

Whilst PMOs have been popular since the middle to late 1990’s and new PMOs are being created at a relatively high rate; PMOs are also being shut down or radically reconfigured at a similar rate. As shown in the figure below most PMOs in existence today are rather recent creations. The sample suggests more than half the PMOs in existence today (54%) were created in the last two years and only 17% have been in existence for more than five years.

This data suggests a PMO often has only a short time to demonstrate its ability to fit into the organisations culture and create value before it is restructured or closed down. We have looked at some of the issues and challenges associated with PMOs in a Mosaic White Paper ‘PMOs’.

Based on years of observation, the key to achieving an effective start up for a PMO has more to do with the PMO’s management being able to effectively manage their key stakeholders, particularly in the executive suites than any methodology or reporting processes the PMO may import or develop. For more on this see the numerous papers we have published [paper listing]. The key message is technical competence is never going to be enough to justify the existence of a PMO.

Cost performance is a symptom of other management functions. It is impossible to ‘manage costs’. The only way to change cost outcomes is to change the other processes that incur costs.

The three key areas of business operations and project management that incur costs and where a change in the process will cause a change in costs are:

1. Changing the procurement / purchasing / supply chain processes that acquire the required inputs to the process being managed.
2. Changing the way the work that transforms inputs to outputs is undertaken through enhanced management and leadership including skilling, motivating and directing the people involved in the work and ensuring they have the correct resources and equipment to undertake the work.
3. Focusing on the quality of the outputs produces to ensure the ‘right scope’ has been delivered at the ‘correct quality’. Too low and there are cost consequences in rectification, too high and you may have spent money unnecessarily.

These three elements exist in a risk frame. Whilst risk management will not ‘control’ the future, it will allow opportunities to be identified and grasped and threats mitigated and avoided by changing the way the work is undertaken and as a consequence optimise cost outcomes.

The two key facets that permeate all of the above are stakeholder management and time management.

• Stakeholder management both within the team and externally, (including effective communication) is central to achieving a successful outcome at the best price. Stakeholders are in the supply chain, include the project team and contractors and can have a major impact on the risk profile of the work. For more posts on stakeholder management see: http://www.stakeholder-management.com/blog/?cat=5
• Time management focuses on ensuring the right people are in the right place at the right time, with the right resources and equipment to do the work in the optimum sequence. For more posts on time management see: http://mosaicprojects.wordpress.com/category/project-controls/scheduling-project-controls/

Both of the above need regular reviews and adjustment within the overall frame of the emerging risk profile.

Where ‘cost management’ adds value is via techniques such as Earned Value (EV). Applying EV effectively allows the symptoms of a deviation from the expected performance to be highlighted through Cost Variances and other reports.

As with medicine and diseases, it is capability to recognise and correctly interpret symptoms that allows diagnosis that leads to the effective treatment of the under-laying problem. In project and business management space, this should translate to the requirement for managers not only to report a cost variance, but also to identify the cause of the variance and to recommend and/or implement corrective actions.

Whilst it is impossible to directly manage or control costs; timely and accurate information on cost performance can be a valuable diagnostic tool to remedy the real issues. What’s needed is for senor managers to stop focusing on ‘cost’ and start asking deeper questions about performance and risk.  I know many readers of this blog will say this already happens in their organisations, but I also know that far too many other managers focus on the symptom of cost performance rather than the under-laying problem to the detriment of their businesses.