Managing stakeholders
Enterprise projects succeed or fail through people. The technical work can be excellent and still stall because the budget holder lost interest, security wasn't consulted, or frontline users quietly refused to change how they work. Managing stakeholders deliberately is part of the engineering.
Map the people
| Role | What they care about | What they need from you |
|---|---|---|
| Executive sponsor | Business outcome, risk, their own reputation | Clear progress against the metric; no surprises |
| Champion | Making the project succeed (often their idea) | Ammunition: results, stories, materials to share internally |
| Economic buyer | Return on spend | The business case and evidence |
| End users | Their daily work getting easier, not harder | A tool that fits their workflow; a voice in the design |
| IT and security | Risk, compliance, operational load | Early involvement, documentation, respect for their process |
| Sceptics | Often valid concerns about disruption or risk | To be heard, and to see evidence |
The same person can hold several roles. In smaller customers, the champion may also be the sponsor.
Find and grow a champion
A champion is an insider who wants the project to succeed and can navigate the organisation for you. Give them reasons to keep championing: early wins they can show, credit in front of their leadership, and materials that make them look good. Projects without a champion tend to drift; if yours doesn't have one, finding one is a priority.
Win over sceptics
Sceptics usually have a reason — a past project that failed, fear for their team's jobs, or a real technical concern. Meet them one to one, ask what worries them, and invite them into the pilot. A converted sceptic is your most credible advocate.
Clarify responsibilities
For anything with several parties, a simple RACI avoids "I thought you were doing that":
| Activity | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|
| Provide data access | Customer IT | Data owner | FDE | Sponsor |
| Build and deploy pipeline | FDE | FDE lead | Customer IT | Sponsor |
| Label evaluation set | Claims SMEs | Claims lead | FDE | Sponsor |
| Approve go-live | Sponsor | Sponsor | Security, IT | All users |
Set a cadence
- Weekly working session with the core team: progress, blockers, decisions needed.
- Weekly written status to a wider group (see below).
- Stage-gate or steering review with the sponsor at each lifecycle transition.
A predictable rhythm prevents the ad-hoc "where are we on this?" messages that signal eroding confidence.
A status update that gets read
**Status: On track / At risk / Off track** — <one-line reason>
**Progress this week**
- <result, ideally with a number>
**Next week**
- <planned outcome>
**Decisions / help needed**
- <specific ask> — <who> — <by when>
**Risks**
- <risk> — <mitigation>
Put the status colour and the asks at the top. Executives read the first three lines; make sure those lines are the ones that matter.
"Your champion leaves the company mid-project. What do you do?" Identify a new champion quickly, re-confirm the sponsor's commitment with a short results summary, and make sure the decision log and documentation let a newcomer catch up.
Senior Full-Stack Engineer · AI & AWS. I turn ambiguous customer problems into production systems — cloud, data and AI.