The Triangle™ Model

The Triangle™ model offers a clear way to understand where friction begins and how digital delivery can flow more predictably.

In organisations, as digital delivery challenges show up in different ways depending on the role:

  • Leaders see unpredictable costs, shifting priorities and unclear decision-making
  • BIM managers and coordinators experience rework, inconsistent inputs and design workflows that don’t connect

Even though the symptoms differ, they often come from the same underlying issue:
the three core parts of the organisation - leadership, engineering, and finance/risk - are not aligned in how digital work should flow.

The Triangle™ makes this connection easy to understand.
It highlights how misalignment in one corner creates pressure in the others, and how shared clarity between these areas leads to smoother projects and better outcomes for everyone.

The Triangle™ is a framework developed and owned by Pasi Joensuu, based on extensive field experience in infrastructure digitalisation.

The Three Corners of the Triangle™

Digital delivery challenges often appear differently depending on the role.

For some, the pressure shows up as shifting priorities or unclear decisions.

For others, it appears as rework, inconsistent inputs, or workflows that don’t connect.

Even though the symptoms vary, they frequently point to the same underlying structure. The Triangle™ describes this structure through three domains that influence every project’s clarity, flow and predictability.

Looking at these domains together helps organisations understand where friction begins, how it spreads across teams.

Leadership

Defines priorities, responsibilities and the pace of decisions.
When leadership signals are unclear or change frequently, both design and execution teams feel the impact immediately.

Engineering

Produces the models, data, designs and technical coordination that projects rely on.
When expectations, inputs or workflows are inconsistent, rework and delays grow quickly.

Finance & Risk

Guides budgets, approvals and the level of predictability expected in the project.
When financial or risk-driven decisions are made without full technical context, friction appears across teams.