Maslow and socio-dynamics: winning team buy-in for BIM

I am Mickael Quinart, BIM/CAD Consultant at PALLADION. Here is an enriched version of the article, transformed into a definitive educational guide.

Change Happens in Minds

A BIM deployment alters habits, status, and sometimes the sense of competence among employees. To succeed, it is essential to understand what motivates each individual and how stakeholders position themselves concerning the project. A BIM deployment is not just a technological undertaking; it is, first and foremost, a human project, a paradigm shift that disrupts established working methods. Ignoring the human dimension risks resistance, demotivation, and ultimately, deployment failure. The key lies in supporting and understanding the psychological drivers of each individual when faced with the unknown and novelty.

Maslow's Hierarchy Applied to BIM

Maslow's Hierarchy of Needs provides a valuable framework for understanding your teams' motivations when facing BIM-induced change. Each level must be satisfied before the next can be addressed.

An employee concerned about their job security will not be receptive to discussions about innovation (self-actualisation). It is crucial to address needs in order. This means that before discussing the long-term benefits of BIM or innovation opportunities, it is imperative to ensure that basic conditions (equipment, training, job security) are met and clearly communicated. Inadequate training on outdated hardware, for instance, can generate frustration that extends far beyond simple technical inconvenience.

Sociodynamics: Mapping Stakeholders

The sociodynamic approach classifies stakeholders along two axes: their synergy (positive energy towards the project) and their antagonism (resistance). This yields a stakeholder map, essential for developing a targeted communication and support strategy:

• Allies / Engaged: These are the drivers of change. They are enthusiastic, proactive, and see the benefits of BIM. They should be mobilised as key contacts and "BIM champions".
• Hesitants and Passives: This category often represents the majority of employees. They are not against change but are waiting to see concrete proof of its effectiveness. They need to be convinced by example and quick successes.
• Torn: These individuals are interested in innovation but are concerned about the consequences for their role, skills, or workload. They require particular attention and personalised assurances to reassure them.
• Opponents: This group expresses active resistance to change. Their objections may be based on negative past experiences, lack of knowledge, or a sense of threat. It is crucial to listen to them carefully, as their objections often reveal real risks or weaknesses in the deployment strategy. However, energy should not be exclusively spent on convincing them, but rather on understanding and, if possible, defusing their fears.

The strategy involves leveraging allies to engage the passive ones, rather than exhausting energy trying to convince opponents. By showcasing concrete successes and valuing "champions", a positive dynamic is created that makes change more acceptable to the majority.

Practical Case in a Design Office

Imagine a structural engineering design office that has decided to embark on its BIM transition. Management, aware of the importance of the human approach, appoints an internal BIM Manager to lead the project.

This manager begins by observing existing practices. They quickly identify a young engineer highly motivated by new technologies (an ally), who has already proactively researched BIM. They also notice a group of experienced draftspersons/designers, attached to their traditional working methods, but curious about potential efficiency gains (some hesitants). Finally, a senior engineer, highly respected for their technical expertise but sceptical about the added value of BIM, raises doubts about model reliability and loss of control over calculations (a potential opponent, or at least a "torn" individual with strong objections).

The BIM Manager then organises a series of information meetings. To address physiological needs, they ensure that future users' workstations are upgraded and software licenses are available. For safety, they clearly communicate that there will be no redundancies due to BIM and that a "right to make mistakes" will be in place during the learning phase. They then propose that the motivated young engineer become the internal technical reference for structural modelling software (Revit Structure, Tekla Structures, etc.), thus mobilising them as an ally.

With the help of this ally, they set up short, practical training sessions focused on concrete case studies from the design office. Initial models are created in pairs, allowing hesitant individuals to feel supported. Even small successes (a quick 3D visualisation, simple clash detection) are communicated internally to demonstrate the concrete value of BIM. The sceptical senior engineer is invited to targeted demonstrations, showing how BIM can improve coordination and problem detection before construction, without undermining their calculation expertise. Their objections are listened to carefully and transformed into specifications for implementation (e.g., rigorous verification of structural data export).

Over the months, the hesitant individuals begin to engage, seeing their colleagues progress and initial pilot projects showing time savings. A sense of belonging to an emerging "BIM team" develops. Successes are celebrated, reinforcing the esteem of those who embraced the change.

Best Practices / Common Mistakes

Step-by-Step Method

1. Initial Human Assessment and Mapping (3 months prior): Conduct an internal audit to map stakeholders according to sociodynamics (allies, hesitant, torn, opponents) and identify the priority needs of each group using Maslow's hierarchy. This can involve individual interviews, anonymous surveys, and observations.
2. Define Support and Training Strategy (2 months prior): Based on the mapping, develop a communication plan, an adapted training programme (with introductory modules, practical workshops, etc.), and identify the necessary hardware and software resources. Appoint "BIM champions" and define their roles.
3. Pilot Launch and Close Support (Day 0): Start with a modest-sized pilot project, primarily involving allies and a few hesitant individuals. Establish constant technical and methodological support (internal key contact, hotlines, Q&A sessions). Celebrate early successes to create positive momentum.
4. Progressive Deployment and Knowledge Capture (3 to 12 months post-launch): Expand deployment to other teams and projects. Continue training, targeting specific emerging needs. Implement regular feedback sessions, communities of practice, and an internal knowledge base to capture lessons learned and best practices.
5. Continuous Evaluation and Adjustment (every 3 to 6 months): Regularly re-evaluate stakeholder mapping and the level of needs satisfaction. Adjust communication strategy, training, and resources based on feedback and developments. Human support is an iterative process.

Watch Points

• The role of middle management: This is crucial. If local managers are not convinced or sufficiently trained, they can become major obstacles, even if not direct opponents.
• Change fatigue: A BIM deployment is a marathon, not a sprint. Constant support efforts are needed to prevent demotivation due to initial workload or unforeseen difficulties.
• Managing expectations: It is important to be realistic about timelines and immediate benefits. BIM is not a magic bullet, and significant gains may take time to fully materialise.
• Recognition of existing skills: The transition to BIM should not devalue expertise acquired through traditional methods. It is an evolution, not a clean slate. Existing skills should be seen as a foundation upon which to build.
• Digital ecosystem: Ensure that IT infrastructure (network, servers, storage) can support BIM requirements (heavy models, real-time collaboration). Tools like Revit, ARCHICAD, Tekla Structures require high-performance workstations.
• Interoperability: The ability to exchange data between different software is fundamental. Using open formats like IFC (Industry Foundation Classes) is a solid foundation, complemented by structured communication tools like BCF (BIM Collaboration Format) for managing comments and conflicts. The Navisworks platform is often used for multi-software clash detection.

Action Plan

1. Map employees according to the stakeholder map.
2. Identify priority needs (Maslow) for each group.
3. Assign a visible role to allies (key contact, pilot).
4. Communicate concrete and rapid successes.
5. Re-evaluate the map every three to six months.

Key Takeaways

• Motivation depends on unmet needs: address them in order.
• Sociodynamics identifies allies, hesitant individuals, and opponents.
• Allies drive the majority; objections illuminate risks.
• BIM is a human project before it is a technological one.
• Normative frameworks like ISO 19650 provide information management principles that must be accompanied by a robust human strategy.

Article based on the professional thesis "BIM transition and optimised deployment, applied in an engineering firm".

Mickael Quinart, PALLADION