Culture in the project environment

Culture in the project environment

There is a growing awareness of the impact that culture has on the success of any large group of people trying to work together. The limited research that has been done tends to focus on culture change in existing businesses, companies, or institutions. There is no blueprint for how to approach culture on a project. With people at the heart of projects, we recognise that creating the right culture is  important, so how do we adapt what we know about organisations to suit the project environment?

First, we must understand the key differences between projects and organisations that impact the way the culture presents and develops. Projects are often set up as temporary organisations and have some distinct features that need to be considered when thinking about the culture. Through our experiences with project teams, we have been able to develop some foundational principles that can be applied to existing models and used to build an approach to culture that is relevant for the project environment.

Project culture or organisational culture?

It would not take too much searching to find a useful definition of organisational culture:

  • a set of shared behaviours and assumptions,
  • collective beliefs and attitudes,
  • the written and unwritten rules of conduct,

or simply ‘the way we do things around here’.

Many decades of research and development have produced robust approaches to building and maintaining successful organisational cultures. The importance of having the right culture in an organisation is rarely disputed. The question is, how does this apply to project teams? There are key features of project teams which make them different to permanent organisations.

Project teams are intentionally finite.

A team will come together to work on a specific task over an extended period, as short as several months or as long as several years. Once the outcome is achieved and the project is complete, the team is usually disbanded, and individuals join up with others on another task or project. In a traditional long-term organisation, the vision (or outcome) for the organisation is usually aspirational, with the intention of driving corporate behaviours through connecting to personal values. Due to the task-oriented nature of projects, a project organisation naturally has a much more tangible, shorter-term outcome that is not so obviously connected to personal values. Individuals may connect to the overall goal of the project in different ways.

The project environment is often high in uncertainty, complexity, and change.

Particularly in the infrastructure delivery environment, where alongside the technical motivation, projects have social and economic drivers to deliver on, uncertainty, complexity and change are the order of the day. Characteristics such as agility and team resilience become core to the success of the team. Collaboration across traditional boundaries must happen, requiring trust, transparency and sharing of information, and speed of response and decision-making.

Within a long-term business environment that is not so changeable, though these are desirable characteristics and skills to have, the stability of the organisation is not dependent on them. The culture of the organisation – ‘the way things are done around here’, can be set and embedded over time without having to respond to constant shifts in the environment.

Project teams are usually made up of people from multiple organisations.

This seems like an obvious point to raise! However, teams engaged in a major project or a collaboration of some kind are often made up of people from different organisations, coming from perhaps similar but not the same organisational culture. The assumed values, beliefs and behavioural expectations may not be aligned or even discussed before the team is put together. This can lead to differences in expectations regarding behaviour and challenges in deciding which values are right for the joint organisation, and whether individuals are expected to disconnect, completely or in part, from their home or parent organisation and develop a new identity for the duration of the project.

How can you build and sustain the desired culture in the project environment?

In this setting, another definition of culture is useful:

“…the general customs and beliefs, of a particular group of people at a particular time… especially as shown in their ordinary behaviour and habits, their attitudes toward each other.”

(Cambridge Dictionary)

For a project team, it is still important to have consistency in values, beliefs, and behaviours – the things that we might describe as the components of culture. The complex nature of the project environment can make this more challenging, and although traditional models can be applied, we must view them through a different lens. The approach is built on three foundational principles.

  1. Communicate what is important.

Particularly where there are multiple organisations involved, spending time together to understand different drivers, desired outcomes, and what is important to each person or organisation is key. Identifying and communicating areas of alignment (and difference) right from the start ensures that the effective functioning of the team does not rely on assumptions. Where expectations are assumed instead of communicated, the team can fall into dysfunction rapidly, putting energy into getting back on track rather than progressing towards achieving their task. Developing a set of joint objectives or values enables team members to bond around a common goal while still working towards their personal and organisational objectives.

  1. Provide support and enablers.

Once expectations around behaviour have been set and communicated, there are some important questions for project leaders to work through to ensure the team have access to the tools that will help them succeed.

  • What systems and practices are in place that empower or inhibit the desired culture?
  • How are people rewarded and recognised? Which behaviours does this drive?
  • Where can team members go to find help when things go off course?

Without defining the support available, people default to the systems, practices, and behaviours that they already know. These are usually learned from past projects, differing sometimes even from person to person. They may or may not be aligned with the intentions of the project and it can take significant time and effort away from the project to reconcile everyone to one way of working.

  1. Measure the cultural development.

As with any form of measurement, this requires data capture and assessment against defined metrics on a regular cycle over time. Although this relies on qualitative data, there are key areas of focus that can demonstrate the development of the culture, for example: measuring alignment of behaviours with values, measuring the consistency of practice, measuring the relationship between cultural components and performance, and so on. Measuring the development will ensure that as the environment changes, the support provided is appropriate to suit the needs of the team at the time. Measurement also ensures that what is important remains in focus throughout the duration of the project.

Getting the right culture in place will have a significant impact on project performance. It will shape how the teams involved connect, communicate and collaborate. Culture is therefore just as important within a project as it is in any organisational setting. If we take the time to creatively think through the unique features of the project environment, it is possible to use existing models to support teams in developing and sustaining their desired culture. So, a parting question to you; what are you going to do to shape the culture on your next project?

Kelachi Amadi-Echendu

The Collaboration Fallacy – Part 2

The Collaboration Fallacy – Part 2

In Part One of this article I introduced a concept I called the Collaboration Fallacy, which is an inaccurate assumption that multiple teams engaged in a major project will automatically work together in the best interest of the project. My purpose in articulating the idea of the Collaboration Fallacy is to nudge project leaders to recognise that humans do not naturally work as happily integrated units. The project culture in which they operate must encourage them to do so. The concept is an extension of the more widely acknowledged phenomenon known as the ‘planning fallacy’, initially identified by Daniel Khaneman and Amos Tversky. Khaneman and Taversky observed that humans continually underestimate the time needed to complete a project despite the information being available to them that would lead to a more accurate answer.

The key point that I tried to emphasis in the first article is that if project leaders were to take the time to look more closely at the factors that bind or disrupt inter-team relationships, they would take a different view as to what was needed to build a successful team of teams. This is particularly important when stepping up into complex project environments where the interactions between groups of people become one of the most troublesome variables. I have noticed however, a high level of complacency in many senior teams at the start of a large project, where the predominant belief is that everything will be fine, and any problems that arise will work themselves out. Once the behavioural norms are set however, they are very difficult to change.

The challenge, therefore, is to find some mechanisms that will help project leaders avoid this naïve tendency and look more closely at the challenges ahead. Logically, we should start with learning from our past experience and that will help avoid making the same mistakes again. There are thousands of project case studies in the public domain which identify the problems created for teams when working in projects with high levels of ambiguity and frequent change. Auditors and analysts often identify a lack of planning or forethought which might have avoided significant difficulties downstream. I have found, however, that stories of past failure often carry little weight when thinking about future projects and programmes. The prevailing view is that ‘this project is different, so those problems will not occur’. In my research, I have found a richer source of knowledge and learning to come from asking my interviewees to describe a project that went well, rather than one that went badly. This is often an interesting challenge, as successful large projects are much less common than one would think.

The question as to what went well, and why, is intended to draw out the factors that actually turned out to be important to success, rather than the more superficial elements that are more commonly used when planning a project. I have found almost without exception that when a project is considered in hindsight to have been successful, time and resources were spent focusing not just on the technical and commercial challenges but also the social components of team development and interaction.

One simple solution to avoid falling prey to the Collaboration Fallacy is for the senior team to set some time aside in their planning sessions to ask each other to tell a story of what made a past project a success and then crucially, what learning might be taken into the current project. Stories are immensely powerful in helping humans learn; they resonate at both an emotional as well as a cognitive level, so that we remember more of the detail, and attach greater meaning to the experiences of the protagonists.  As human beings we are more likely to react to someone else’s story than we are to bullet points in a PowerPoint presentation.

The beauty of this approach is that it diverts the discussion away from the instinctive focus on technical planning which tends to dominate most early senior team meetings. Instead, the question allows each person to slow their thinking and reflect on the past. Once everyone has had a chance to contribute, the session could move onto another crucial question; “What has to go right for this project to be successful?” (It is important to note that what needs to go right is very different to the question of what could go wrong.)

Setting time aside to plan for building positive relationships and interpersonal trust can be distracting when a newly formed team really just want to press on with the process of delivery. The payoff downstream is however potentially huge, particularly when trying to work in a complex environment. So, as you move into your next project, one of the key questions to ask your team is ‘are we in danger of falling for the Collaboration Fallacy here, and if so, what are we going to do about it?’

Tony Llewellyn

Social Intelligence – The Critical Ingredient to Project Success

Social Intelligence – The Critical Ingredient to Project Success

Delivering projects is a human activity. Generating something new from ‘thin air’ requires groups of people who are able to conceive, plan and then execute a series of complicated activities that will, in some form or other, enhance the lives of other human beings. Large projects require the input of many highly specialised skills, which are of limited value in themselves, but are of significant worth when combined with the skills of others. It is this combination of applied skills that lead to success. Project teams need intelligence, or more particularly three distinct types of intelligence.

  • Technical intelligence – the knowledge and awareness of how to find the solution to a particular problem or opportunity.
  • Commercial intelligence – the knowledge and awareness of issues around money, contracts and the identification and management of risk.
  • Social intelligence – the knowledge and awareness of how humans behave in groups and teams.


Large projects require lots of people. Despite advances in automation, we remain a long way from having robots to design, manage and deliver complex engineering software, logistics or construction projects. These enterprises require human expertise and ingenuity to make them happen. As illustrated in the diagram below, there is a sweet spot at the centre of the Venn diagram where these three elements combine to form the rounded capability to lead and manage a major project. When assembling a project team, we tend to value specialist technical and commercial skills in others because they cover for gaps in our own skill or knowledge set. Adding social intelligence to the group, however, tends to be seen as much less important.


 Social intelligence

We often use the word ‘dynamics’ to describe how people interact when they are together in a group or team. The word dynamics actually means ‘forces of change’. We tend to use the phrase ‘human dynamics’ when talking about how people interrelate when they come together as a group or a team. So human dynamics are essentially the forces that create or destroy the momentum of interaction between groups of individuals.

The problem is that people are messy.  Humans are driven by a complex series of emotional reactions that are genetically hardwired into us to thrive and survive. Our behaviours are driven by motivational factors that are often not visible to others and can often be difficult for others to comprehend. To understand others and then have them understand you is an essential human skill. The ability to first understand others and then be understood by them is often referred to as Social Intelligence. This is a term used to describe a degree of awareness of the human interactions between oneself and others and also between others.

The concept of Social Intelligence has a variety of possible definitions but at its simplest, it is ‘an ability to get along well with others and to get them to co-operate with you’ . Daniel Goleman (2006) argues that whilst IQ is something that you are born with, social intelligence is regarded more as a learned skill, than a genetic trait. This leads us to the question that if social intelligence is an essential component of project success, then why do professional bodies pay so little attention to its development?

My observation is that there tends to be a tacit assumption in many teams that everyone on the team will automatically have the social skills needed to get along well with each other. This often turns out to be a significant misjudgement. Whilst humans have evolved to work in groups, left to our own devices we also have an amazing capacity to find reasons to disagree and dislike other people or groups. As projects have got bigger and more complex, it is clear that future generations of project leaders are going to have to take the development of their social intelligence more seriously.

Positive social interaction in project teams cannot therefore be left to chance. In just the same way as the technical and commercial competencies, there are methodologies for building strong social bonds. Those methodologies need to first be understood, learned and then practiced.


Learning and development

So if Social Intelligence is a learned skill set, the next question is how and where to acquire it.

The prevailing belief in universities and colleges appears to be that the development of social skills should be left to future employers. The problem in deferring the development of these skills is that too much effort is spent in remediating bad habits and rebuilding confidence, rather than providing the more advanced social competences needed to help individuals and teams thrive in a complex environment. It is interesting to note the outcome of a survey of teachers, reported in an article in the Times Literary Supplement dated 30 August 2017. The article highlighted the statistic that 91 per cent of respondents felt that schools should be doing more to help their pupils develop teamwork and communications skills.

There is a tendency to call the ability to understand and communicate a ‘soft’ skill, the implication being that learning how to connect with other people is an imprecise art rather than a precise process. I believe this is an outdated description emanating from a time when managers lacked both the knowledge and the need to recognise the practice and process of efficient and effective team development. The other argument for degrading social skills to the category of ‘soft’ is a belief that they cannot be measured and therefore cannot be managed. This again is simply lazy thinking. There is no difference in my mind in assessing someone’s technical, commercial or social capabilities. It is simply a matter of choosing the metrics and then making the effort to collect the data.

Organisations will periodically invest in soft skills training in areas such as presentations, negotiation, time management and communication.

These are active elements which reflect the ‘tell’ mindset predominant in western organisations. Social intelligence is a wider concept, which involves more than just what one person says or does.  To be able to influence what happens in a team, you need to understand what is going on, not only when the individuals react to each other and how they collectively respond to events that impact on the team. Social intelligence learning therefore includes areas such as:

  • Systemic thinking. Seeking to identify all of the different factors that have created a situation. It involves techniques to look at a problem or issue from a number of different perspectives.
  • Understanding group dynamics. Learning how to ‘read the room’ to gauge what is happening underneath the surface behaviours of the team.
  • Influential enquiry. Controlling and steering conversations through the use of skilled questions.
  • Conflict management. Managing difficulties and problems by creating an atmosphere that encourages dialogue rather than heated debate
  • Psychometrics. Understanding others by learning to recognise their motivations and preferences and adapting your messages so they recognise your point of view more quickly.
  • Sensory awareness. Knowing how to really listen to what others are communicating not just in words but in posture, eye movement, facial expression and pace of voice.
  • Reflection. The habit of methodically taking time to think about recent experiences and consider what happened, why it happened, and what to do the next time a similar situation occurs.

The skills set out above can be taught but as with any skill, must be practiced to become proficient. These skills must be learned and developed in the same ways one acquires technical and commercial skills. The initial information can be acquired in the classroom, or from books. A good place to start would be to check out my website, The real learning only comes however, when trying to apply this knowledge in a real-life situations.


Managing Behavioural Risk

This article has focused on the need for project leaders to pay attention to the social or people based factors in addition to the technical and commercial challenges that every project must deal with. Successful projects almost always feature successful teams where collaborative behavioural norms had been embedded early in the project life cycle. Ineffective teams will always struggle to deliver on their promises and so anyone studying the risk of default must pay attention to the dynamics present within the core team.

As projects continue to grow in size and complexity paying attention to the level of social intelligence in you team may well be the difference between success and failure. I would therefore urge any leader looking for a better way of reducing the risk of project failure to explore the investment in developing the social competences outlined above. A team with the full range of strong technical, commercial and social skills is much more likely to build a success story.

Tony Llewellyn



  • Golman, D (2006) The new science of human relationships, Random House
  • Ward H, (2017) Teachers rate soft skills as more important than good grades. Times Educational Supplement, 30 August 2017. (accessed on 5 Jan 2018)
The Collaboration Fallacy – Part 1

The Collaboration Fallacy – Part 1

The benefits of developing collaborative relationships between teams working on large projects are easy to recognise, particularly when operating in a complex and uncertain environment. Studies of successful projects almost always identify the creation of strong social bonds between sub teams who rely on each other to complete their tasks. And yet I continually encounter stories of project leaders declining to invest the time and resources needed to establish the processes, structures and behavioural norms that are needed to create a collaborative environment.

For example, I recently came across a project that is about to make the transition from the design stage into mobilisation for delivery. The project is complex and the early stages have been difficult, but the original project leader had the foresight to employ a specialist firm to help the different teams work as a collaborative unit. Moving into the delivery stage, a new project director has been appointed, who has decided not to carry this specialist support through into the delivery phase. The stated reason given is because there is no budget, but I have heard stories on a similar theme so often, it is worth looking a bit deeper. In the course of my research into successful and unsuccessful projects, it has become apparent that a large proportion of project leaders and their advisers are prone to a concept that might be called the Collaboration Fallacy.

This is a phenomenon in which senior decision makers involved in large projects make an assumption that despite the evidence of their own experience, all of the teams and groups involved in the enterprise will naturally work collaboratively together in pursuit of a single collective goal. It then comes as an unpleasant surprise when project performance starts to deteriorate and the project agenda becomes derailed by inter team conflict and blame.

Most project management professionals are aware of the concept known as the ‘Planning Fallacy’, whereby humans continually underestimate how long an element of a project is likely to take to complete. The term was coined by David Khaneman and Amos Trevisky in 1979 and is an extension of our tendency towards optimism bias. The primary insight Khaneman and Trevisky offered was that we often make such errors of judgement in forecasting the future, even when the evidence that would predict of a more realistic outcome is readily available to us.

Over the past eight years, I have collected enough evidence to show that project teams are likely to be more effective when they invest in establishing the processes, systems and behavioural norms that encourage the different sub-teams working on a major project to communicate, cooperate and collaborate. The problem is that this requires time and resources to be used at the start of a project just when everyone is under pressure to immerse themselves into the technical detail. The prevailing belief is that project professionals

should be able to behave logically and rationally and that cooperation and collaboration should automatically happen irrespective of circumstances. This is a flawed assumption. The reality of human behaviour in groups should lead us to the opposite assumptions for the following reasons:

1.    Tribal tendencies – whilst humans are wired to work with others, our preference is to stay in small groups, usually of between 3 and 10 people. Grow beyond that number and we will instinctively start to form sub-groups. Whilst humans are wired to work cooperatively with each other to find food and safety, we are also instinctively tribal. Once we have formed into a satisfactory group, we begin to define our team by its differences to others. We are also naturally competitive so will seek to gain small advantages over other teams within the same organisation.

2.    Organisational siloes. If human nature was not enough, organisations habitually structure themselves into departments, grouped by random factors such as skillset or geographic location. The prevailing obsession with control often means that communication is designed to move up and down the vertical ‘siloes’ shown on the org chart so that all important (as well as a lot of unimportant) information moves to the top of the hierarchy and directions are passed down. Any communication between vertical siloes is limited to senior leaders who are often competing with each other for influence.  Cross team communication is consequently limited to random individual relationships between people who happen to know each other.

3.    Systemic barriers. The vast majority of organisations put structural barriers in place between themselves and their supply chain, where procurement teams and their consultants insist on the use of transactional mechanisms. These inevitably send the parties onto a course where each is battling to protect their own position, rather than working in partnership to solve collective problems.

These barriers exist to a greater or lesser extent in every major project, both within internal teams and external contractors. The more people involved in the project, the more likely one is to find evidence of miscommunication, non-cooperation and dysfunctional behaviour. Anyone who has been involved in a project involving many groups of people knows this to be true.

So why despite the evidence of own experience, do we continue to expect that people will instinctively, systemically and culturally collaborate? The answer of course lies in the misplaced optimism, which brings us back to the concept of the Collaboration Fallacy where we make an unrealistic assessment of the future scenario without thinking through what is likely to happen if we take a past experience into account.

The bottom line is that large projects fundamentally rely on effective communication between teams who are dependent on each other to deliver their component of the project. The challenge for project leaders is to decide how to create a project environment where the different sub-teams build the right relationships at the right time. The positive news is that the above barriers can be overcome through the use of a set of processes, and methodologies, which can successfully counter our tribal and transactional tendencies to build a collaborative environment.

Just how these processes work will be the subject of the part 2 or this article, but to close this piece off, I would like to reinforce the core message that collaboration and co-operation are not natural or instinctive habits in teams working in complex projects environments. If you recognise the need for your teams to work together to resolve the vast array of problems and difficulties that are likely to arise on your next project, then don’t succumb to the Collaboration Fallacy, and take time to make sure that the problems your teams have experienced in the past do not continue in the future.

Any discussion on teams is often multi faceted, generating many different views. So what are your thoughts on the Collaboration Fallacy?

Tony Llewellyn

Peripheral vision

Peripheral vision

The COVID-19 crisis has forced teams to continue working together using electronic media. Many organisations are finding that at least temporarily, they can operate on a virtual basis, giving much credence to the argument that remote working is at least as effective as office-based operations. However, a question that has been playing on my mind over the past three weeks is; how much knowledge are we missing from the part of natural communications process that might be called our ‘peripheral vision’? Peripheral vision is how I would describe what enables us, often accidentally, to discover that someone else has found a solution to a problem we are struggling to solve, or those moments we find a connection to an option which we were previously unaware of. A couple of simple questions highlight my point:

  • How often do you gain the most valuable insights while having a conversation over making a coffee prior to a planned meeting, rather than during the meeting itself when following a pre-set agenda?
  • How often within an office environment do you hear a snippet of a conversation which makes you stop what you are doing and go and find out more?

I sense that this information gap is going to increasingly impact our ability to move projects forward as the return to working in an office environment looks even more distant. My concern is whether the working habits we are developing at this time are nudging us unintentionally into siloes, where connection and communication across sub-team boundaries become limited. So, what mechanisms could we try and develop to help replace this missing source of information in a distributed team? I can think of three potential areas:

  1. Behavioural – Part of the answer might be to become more expansive in our thinking about our current work and how it might be used. Who else might find it useful to know what we are working on and the challenges we are struggling with?
  2. Becoming a ‘learning team’ – The benefits of recycling learning back into a team are a well understood feature of high performance. Adopting the habit of regular review of what has happened and what could we do to improve, will push a team to extend their peripheral vision. By pausing to reflect, team members increase their chances of thinking laterally to explore new connections.
  3. Explore technology – One example that I am interested in exploring further is the use of software to analyse communications and connect people within an organisation who are not already connected but are having conversations with others about similar topics. The increase in the availability of free-text theming software could really support knowledge management in a new way.

My purpose in writing this short article is not to prescribe the answer, but to try and stimulate some discussion about how we continue to adapt our working practices to ensure we can be as effective working in distributed team. I would therefore love to hear your thoughts and opinions on this issue.

Edward Moore