Skip to main content
Start free

Becoming a Digital Troublemaker · Lesson 3 of 11

Why Some Great Ideas Still Fail

Video5 min

This video explores why digital change is so difficult in construction and project delivery, examining how habits, disconnected priorities, fragmented systems, and the lack of shared structure prevent even the best intentions from turning into lasting transformation. The written guide below covers why teams rarely move together even when they all want improvement, how disconnected priorities across design, construction, FM, and ownership create friction, why BIM problems are often really process and communication problems, how many digital leaders start as technical problem-solvers before becoming change leaders, and why lasting transformation needs three things: connected processes, practical training, and leadership support.

Why digital change fails in construction and what it takes to make it stick

Change sounds simple in theory. You see a better way of working. You suggest a smarter workflow. You might even build a prototype or a pilot. But in practice, making real change across teams and departments is one of the toughest challenges in the construction industry. The reason is not that people do not want to improve. It is that organisations are built on years of habits, shortcuts, and survival tactics, and those patterns are deeply embedded in the way projects are delivered. Even when teams agree that change is needed, they rarely move together. One group pushes ahead, another hesitates, and another stays focused on today's deadlines regardless of what has been proposed. Without a shared structure, the old habits pull everyone back.

The pattern is familiar to anyone who has tried to introduce new workflows. You kick off with big energy and ambitious plans. Early adopters get excited. There is momentum for a few weeks. Then gradually, the pace slows. Deadlines take priority. People revert to what they know. The new workflow quietly disappears, and frustration replaces the initial enthusiasm. This is not a failure of willpower or competence. It is a structural problem. New ways of working cannot survive real project pressure unless they are supported by connected processes (opens in a new tab), proper training, and genuine leadership backing.

One of the biggest sources of friction is that different stakeholders on a project have fundamentally different priorities, and those priorities rarely align without deliberate effort. The design team is focused on drawings and models. The construction team is chasing coordination deadlines and task coordination. The facilities management team is thinking about asset data and long-term operations. The owner is thinking about the big picture but is often disconnected from project milestones and makes changes too late. Everyone is pushing towards their own goals, but very few are working towards the same outcome at the same time. When information requirements (opens in a new tab) are not defined upfront in a structured way, each party fills the gap with their own interpretation, and the result is conflicting expectations, rework, and missed deliverables.

The problem compounds when systems do not align either. A common scenario is sharing models through a common data environment (opens in a new tab) while approvals are still happening over email. Two systems running simultaneously means two different versions of the truth. Confusion about which version is current, who approved what, and what has actually been agreed leads to misapprovals and unnecessary blame. The same issue plays out with documents. The project brief sits buried in someone's inbox, never to be referenced again. The contract agreement is ignored until someone needs a scapegoat. Compliance certificates are only chased down when the client refuses to make final payment. Handover documents are scrambled together the night before practical completion. These are not isolated failures. They are symptoms of a system where document management (opens in a new tab), approvals, and workflows are not connected.

Many people in BIM and digital delivery roles recognise this description. The video makes an important observation about how today's digital leaders typically got started. Most did not begin as change management strategists. They started as technical problem-solvers: the person everyone called when files would not open, when software was not working, or when a model needed fixing. They solved the small problems first and helped make projects run smoother. Then one day, someone handed them the challenge of implementing BIM (opens in a new tab). "You're good with systems. Can you sort this out?" That moment is where real leadership begins, because the challenge is no longer just technical. It is about changing how people work, how decisions are made, and how information flows across an entire project.

The realisation that follows is a turning point. The BIM execution plan (opens in a new tab) that nobody reads is not just a BIM problem. It is the same problem that affects every document, every approval, and every communication on the project. The project brief, the contract, the compliance records, the handover certificates: they all suffer from the same disconnection between how information is created and how it is used. When these processes are driven by emails, PDFs, informal approvals, and disconnected spreadsheets rather than a structured database (opens in a new tab), even the most experienced teams face duplicate effort, rework (opens in a new tab), and missed deadlines. It is not the people who are the problem. It is the system.

Good ideas alone are not enough. Without three essential elements working together, new workflows will always fade under pressure. The first is a connected process that links requirements, documents, contracts, approvals, tracking, and verification in a single structured workflow rather than scattered across disconnected tools. The second is practical training (opens in a new tab) that goes beyond software skills to build understanding of why the workflows matter and how every role connects to the bigger picture. The third is a business case that leadership can get behind, articulating the value of connected workflows in terms of reduced risk, less rework, and better project outcomes. The upcoming lessons in this course break down exactly how to build each of these three pieces and how to turn your efforts into real, lasting transformation.

Why digital change loses momentum and how to prevent it

  1. Recognise that habits are structural, not personal - Teams revert to old ways of working not because they are resistant to change but because the existing structures support those habits. Without a shared, connected system, individuals will default to what they know under deadline pressure. The solution is not more persuasion but better process structure (opens in a new tab).
  2. Align priorities across stakeholders - Design, construction, FM, and ownership teams all have different goals. Define information requirements upfront so that every party understands what is expected, who is responsible, and how their work connects to the project outcome.
  3. Eliminate dual systems - If models are shared through a CDE but approvals happen over email, you have two versions of the truth. Bring approvals, documents, and agreements into a single connected system where contracts, requirements, and documents are linked and traceable.
  4. Treat BIM problems as process problems - When people do not read the BIM execution plan, the issue is rarely about the document itself. It is about how every document, approval, and communication on the project is managed. Address the wider system, not just the modelling workflow.
  5. Build the three pillars of lasting change - Connected processes, practical training, and leadership support. Without all three working together, new workflows will fade under pressure. The Digital Troublemaker's toolkit provides the framework for building each of these pillars in a structured way.
  6. Move from technical problem-solver to change leader - If you started as the person who fixed files and helped with software, recognise that your role has evolved. You are now leading a shift in how your organisation works. The digital leader path is about understanding people, processes, and culture as much as technology.
  7. Create the business case for leadership buy-in - Use the digital transformation business case template to articulate why connected workflows matter in terms that leadership can act on: reduced risk, fewer delays, less rework, and stronger project delivery.

What you'll learn

  • Why change sounds easier than it is - How years of embedded habits, shortcuts, and survival tactics create structural resistance to new workflows, and why even well-intentioned teams revert to old patterns under project pressure without shared structure and support.
  • Disconnected priorities create friction - How design, construction, facilities management, and ownership teams each focus on different goals, and why the lack of aligned information requirements means everyone pulls in different directions rather than working toward a shared outcome.
  • Dual systems cause confusion - Why running models through a CDE while managing approvals through email creates two versions of the truth, leading to misapprovals, blame, and wasted effort that undermine trust in the new way of working.
  • BIM problems are process problems - Why the BIM execution plan that nobody reads is just one symptom of a wider issue where every document, every approval, and every communication on a project is managed through disconnected, informal systems rather than a structured workflow.
  • The path from problem-solver to change leader - How many of today's digital leaders started as technical fixers before being asked to lead BIM implementation, and why that transition requires a shift from solving software problems to changing how organisations work.
  • Three things lasting change needs - Why connected processes, practical training, and leadership backing are the three essential pillars that determine whether new workflows survive real project pressure or quietly disappear within months.

Common questions

Why do new workflows often fade after a few months?

New workflows fade because they are introduced without the structural support to sustain them. When deadline pressure hits, teams revert to the habits that feel safe and familiar. The new way of working only survives if it is embedded in a connected process that is easier to follow than the old approach, backed by training (opens in a new tab) that builds genuine understanding, and supported by leadership who champion the change rather than just approve it.

Is the problem with BIM adoption really about process, not technology?

In most cases, yes. The technology works well. The challenge is that BIM is often adopted as an isolated modelling tool while the rest of the project, including documents, contracts, approvals, and handover, continues to run on disconnected manual processes. When the BIM execution plan (opens in a new tab) is ignored, it is usually because every other document on the project is also being managed informally. Fixing BIM adoption means fixing the wider information management system.

How do I get leadership to support digital change?

Leadership responds to business outcomes, not technical features. The business case template helps you articulate the value of connected workflows in terms that matter to decision-makers: reduced project risk, fewer delays, less rework, stronger compliance, and better client outcomes. When the argument is framed around business value rather than software capabilities, leadership is far more likely to support and champion the change.

What is a Digital Troublemaker and how does it relate to leading change?

A Digital Troublemaker is someone who sees what is not working in how projects are delivered and steps up to lead the solution. It is not about being disruptive for its own sake. It is about having the awareness to identify process failures and the drive to put structured, connected alternatives in place. The Digital Troublemaker course provides the framework, tools, and community to help you lead this shift effectively.

What are the three things needed for lasting digital transformation?

The three pillars are: a connected process that links requirements, documents, contracts, approvals, and verification in one structured workflow; practical training that builds understanding of why the workflows matter and how every role connects to the bigger picture; and a business case that gives leadership the confidence and rationale to back the change. The upcoming lessons in this course break down each of these in detail, with tools and templates to help you build all three.

Explore further

Finished this lesson?Mark it complete to save your place, take the quizzes and earn your free certificate. It's your Plannerly account - no new one needed.

Discussion

6 comments

Sign in to read the 6 comments and join the conversation.

Sign in

Sign in to keep your progress

Use your Plannerly account - the same email and password as the app. Every lesson stays open either way.

New to Plannerly? Create a free account · Forgot your password?

Used a different email for training than for the app? Sign in with either - you can bring them together afterwards.

Learned with a different email? Sign in to that account here and we'll bring its courses, progress and certificates into the one you're signed in with. Certificate links and QR codes keep working.

Forgot that password? Reset it first, then come back. Want to keep the other account instead? Sign out and sign in with that one.