Why BIM initiatives fail

Why BIM Initiatives Fail to Meet Expectations

In BIM Modelling & Revit Production, Standards & Delivery (ISO 19650 / BEP) by Bauministrator

Most BIM problems don’t show up on day one.

They show up a few weeks in — when deadlines start to bite, feedback loops get noisy, and someone asks the question every team eventually asks:

“Which version is the right one?”

At that point, it’s tempting to blame the tools. Or the model. Or “BIM complexity”.

To see the root cause of BIM underperformance, it helps to start with traditional CAD delivery.

CAD delivery: drawings-first

(Information stays behind the “CAD gate”)

In a traditional CAD approach, the workflow often looks like this:

  • CAD operators author drawings (and sometimes 3D models)
  • Engineers and reviewers receive published outputs (PDFs / paper)
  • Feedback happens via markups, emails, meetings, and re-issue cycles

Only a small group touches the “source”.
Most of the team works from published copies.

This traditional style has been effective on traditional projects.
But on complex projects with more stakeholders and organizations, it creates familiar friction:

  • Decisions get scattered across emails and markups
  • It’s hard to see what changed, when, and why
  • Coordination issues arrive late (or in the field)
  • A lot of project knowledge becomes trapped inside the documentation workflow
  • Big ‘rush’ or shortcuts taken when the contractor teams send a change request.

The quiet shift BIM introduces

BIM/DE changes one thing that doesn’t get talked about enough:

It shifts the project from published snapshots to a shared reference point.

It shifts the design vehicle from static circulated drawings to an information-enriched model where everyone on the project has sufficient access to facilitate their level of engagement.

The shift isn’t just technical — it changes how people collaborate, who is involved, and where decisions live.

BIM-oriented delivery: model-first

(pulls stakeholders into the same conversation)

A BIM-oriented approach changes the centre of gravity.

The model becomes the shared reference point — not a CAD department artefact.

And that pulls more stakeholders into the delivery loop:

  • BIM technicians / modellers build and maintain the model (and may generate drawings)
  • Engineers use the model for review, measurement, design discussions, and issue resolution
  • Project managers engage with the model for planning, sequencing conversations, and risk discussions
  • Clients can review intent and raise issues earlier with better context
  • Construction teams use the model information for better buildability discussions (where appropriate) and even set-out automation
  • Everyone can participate more directly in coordination conversations and clash investigations

This doesn’t mean everyone has to become a modeller.

It means fewer decisions happen in isolation, and fewer surprises appear late.

The surprising part: you probably already have enough tools

This is what catches many teams off guard:

Most engineering companies already have most of the tools they need to get meaningful value from BIM.

What’s usually missing isn’t another software purchase — it’s the way of working around:

  • responsibilities
  • approvals
  • issue handling
  • version control
  • and what “done” actually means

Why BIM still fails: the model becomes another silo

Here’s the failure mode that feels like a technology problem, but isn’t:

The model becomes a new “gate” because the project is still being run like it is drawings-first.

People start treating it like “the BIM team’s thing”, instead of the project’s shared reference point.

You’ll recognise the symptoms:

  • Engineers and PMs avoid the model because it feels like someone else’s domain
  • The model becomes a last-minute drawing machine again
  • Coordination happens late, under deadline pressure
  • People don’t trust what they’re seeing, so they revert to PDFs and gut feel

That’s not because BIM is bad.

It’s because the project never set the human rules that make BIM usable.

The Heart of BIM/DE.

Counter-intuitively, the first focus of BIM isn’t “What tools do we need?” or “What skills do we train?”
It is:
How does this fit into our culture and delivery process — and what needs to change for people to actually work differently?”

The BIM Manager’s real job: tying it together

This is where a good BIM Manager (or BIM Lead) earns their keep.

Not by being the best at software — but by turning “we have a model” into “we have a process”.

A good BIM Manager helps by:

  • making expectations explicit: what “done” means for models, drawings, and information
  • documenting the way of working: simple standards people actually follow
  • facilitating collaboration: meetings, coordination rhythm, issue workflows
  • bridging departments: keeping engineering, delivery, and documentation aligned
  • protecting delivery under pressure: preventing the workflow from collapsing near deadlines

In other words: BIM becomes valuable when someone owns the collaboration mechanics.

A simple starting point for decision makers

If you want BIM to reduce risk rather than add risk, don’t start with a shopping list.

Start with a few practical agreements:

1) Define what you’re delivering (and what you’re not)

  • What are the deliverables?
  • Who uses them, and for what decisions?
  • What is out of scope?

2) Assign ownership

  • Who owns coordination setup?
  • Who owns approvals and sign-off?
  • Who owns issue tracking and close-out?

3) Create a lightweight review rhythm

  • How often do reviews happen?
  • How are issues raised and closed?
  • Where is the single source of truth?

4) Train for outcomes, not buttons
Training sticks when it’s anchored to your actual deliverables and workflow — not generic features.

Once those pieces are in place, you’ll often find your existing toolset goes a lot further than you expected.


Related Services:

  • For team coaching and capability → Skills
  • For deliverables and workflow setup → Process

Want a second set of eyes?

If you’re trying to make BIM feel calmer, clearer, and more predictable — send me your situation and I’ll help you identify the smallest practical next step.

Send your Situation

  • Include: what your deliverables are, who the stakeholders (roles) are, and where it’s getting messy (versions / approvals / responsibilities / coordination).