The Hidden Roles That Make or Break a Digital Project

When industrial digitalisation projects stall, it’s rarely because of the technology. The more common reason is that the right people weren’t in the right roles from the start. We’ve seen this pattern many times: capable teams, good intentions, solid tools but no clear ownership or alignment between the operations and management layers.

Digital transformation in operational environments isn’t just about data and software, it’s about people and how they work together. The difference between a project that delivers real value and one that drifts quietly into irrelevance often comes down to a few key roles that are easy to overlook.

I’ve been delivering digital projects in industrial environments for over 20 years now and here are my reflections on what those essential, but often overlooked, roles are.

Close collaboration between the Technical sponsor, users, subject matter experts and those delivering digital projects is essential

The Technical Sponsor: Owning the Problem and the Progress

Every successful project needs a technical sponsor who truly feels the pain the project is meant to solve. This isn’t someone in IT or at board level, but someone in the business, from the operational side, who understands both the day-to-day challenges and the business outcomes that matter.

A good technical sponsor bridges the gap between technical detail and business context. They have enough authority to control the budget or a direct line to someone who does. They’re close enough to the work to sense when the project is drifting off course. Most importantly, they take ownership of the project’s budget and schedule, making informed decisions about trade-offs and priorities.

When this role is missing or filled by someone too detached, projects tend to lose focus. Teams optimise for the wrong outcomes, budgets balloon, and progress becomes hard to measure.

The Management Sponsor: Providing Air Cover

If the technical sponsor is the project’s engine, the management sponsor is its shield. Their job is to make the project official, visible, and supported across the organisation. They provide “air cover” for the team, clearing the way when other departments like infrastructure or networking need to contribute time or resources.

A management sponsor understands the organisation’s internal processes well enough to anticipate where they might add friction or cost. They can also set realistic budget expectations without relying entirely on external vendors. Their backing signals to everyone involved that this is a serious initiative, not an experiment.

Without that top-level endorsement, even the best technical sponsor can struggle to gain traction or maintain momentum.

The Unsung Heroes: SMEs, Administrators, and Adoption Catalysts

Beyond the sponsors, a few less visible roles quietly determine whether the project takes root.

Subject Matter Experts (SMEs) provide the technical truth. They know how systems behave in practice, what data really means, and what will or won’t work in the operational environment. Their input is essential, but they also need time and permission to engage. They can be the same person as the Technical Sponsor, but often they shy away from the limelight or project politics and just want to focus on getting things done right. That’s where the management sponsor’s support is crucial.

Project administrators keep the work moving. They schedule meetings, track progress, and help clear roadblocks but they shouldn’t own the budget or schedule. Those belong with the sponsors, leaving the administrator free to focus on coordination and communication.

Then there’s the project adoption catalyst, a role many organisations overlook. This person understands how to get people excited about the change, whether through lunch-and-learn sessions, internal webinars, or simply helping users see how the new tools make their jobs easier. Adoption doesn’t just happen because the technology works; it happens because people are brought along for the journey.

Culture Matters as Much as Structure

Even the best-defined roles can fail if the culture isn’t right. The most successful projects we’ve seen have a short chain of command, a no-blame culture, and a healthy acceptance of uncertainty.

Industrial digital projects are complex by nature. There will be surprises, data quirks, and moments where assumptions don’t hold. That isn’t failure, it’s discovery. The most cost-effective approach is to start delivering early, learn fast, and refine along the way.

When people feel safe to surface issues and experiment, progress accelerates. When they don’t, projects stall in meetings trying to predict every possible problem in advance.

Building Digital Projects That Deliver

Getting these roles and relationships right doesn’t just make delivery smoother; it makes success measurable and repeatable. At Eigen, we’ve found that clarity of ownership and culture often matter more than the choice of technology stack.

If your organisation is planning its next digital initiative, it’s worth asking: do we have the right people in the right roles to make this succeed?

To learn more about how we help industrial teams build connected, intelligent systems that actually get adopted, visit eigen.co.