From BIM to Product Management: Rethinking the Role of Digital Engineers

A Better Frame: Think Like a Product Manager

To better understand this role, it helps to look beyond construction. In many ways, the closest parallel to a Digital Engineer is a Product Manager.

At first glance, the two roles appear unrelated. However, in practice, they share a common core.

Both:

• Operate across disciplines

• Align stakeholders

• Define systems and workflows

• Drive outcomes without direct control

The difference is not capability, it is mindset.

What Digital Engineers and Product Managers Share

1. Process Oversight

• Digital Engineering: Oversees BIM standards, workflows, and delivery processes

• Product Management: Oversees product lifecycle, roadmaps, and feature delivery

2. Stakeholder Coordination

• Digital Engineering: Aligns architects, engineers, contractors, and clients

• Product Management: Aligns designers, developers, and business stakeholders

3. Tools and Standards

• Digital Engineering: Defines modelling standards, CDE structures, and workflows

• Product Management: Defines tools, systems, and development processes

4. Quality Assurance

• Digital Engineering: Ensures model integrity, coordination, and data quality

• Product Management: Ensures product quality, usability, and performance

5. Information Flow

• Digital Engineering: Facilitates data exchange across disciplines and project stages

• Product Management: Ensures clear communication between users, teams, and systems

6. Strategic Alignment

• Digital Engineering: Connects delivery workflows to project and business goals

• Product Management: Aligns product direction with business strategy

7. Problem Solving

• Digital Engineering: Resolves coordination breakdowns and workflow inefficiencies

• Product Management: Removes blockers and resolves cross-team conflicts

8. Not Direct Creators

• Digital Engineering: Enables delivery without directly modelling or building

• Product Management: Enables delivery without directly designing or coding

Both roles act as integrators of complex systems. They don't build the asset. They ensure it gets built well.

Why This Shift Matters

Many Digital Engineers operate like technical support:

• Reactive

• Tool-focused

• Measured by compliance

But Product Managers operate differently:

• Outcome-driven

• User-focused

• Measured by impact

When I started applying product thinking in Digital Engineering, the shift was immediate:

• Solutions became simpler and more usable

• Teams engaged earlier and more consistently

• Executives understood the value faster

• Digital Engineering became part of delivery, not documentation

What Changes in Practice

When Digital Engineers think like Product Managers, the approach changes:

• Treat digital initiatives like products, not policies

• Focus on user needs, not tool capabilities

• Iterate based on feedback, not assumptions

• Measure success through outcomes, not adoption

• Align workflows with real delivery conditions

This moves Digital Engineering from managing systems to driving outcomes.

Where This Leads

If Digital Engineering evolves in this direction, we start to see:

• Clearer ownership of delivery outcomes

• Better alignment between strategy and execution

• Faster adoption of digital workflows

• More meaningful engagement from project teams

Most importantly, we stop asking, "Are we following the standards?" and start asking, "Is this improving delivery?"

A Shift in Identity

Digital Engineers are not custodians of process. They are:

• System designers

• Workflow architects

• Outcome drivers

We sit at the centre of delivery systems, connecting people, data, and decisions. That position carries responsibility. Not just to define how things work, but to ensure they work better.