The Longer Game - and Why Reputation Is the Only Governance Asset That Compounds
If you have missed out the articles in this series, glance through these for a quick recap:
The Green Dashboard Trap: Why ERP and MES Projects Fail Long Before Anyone Reports Red
What a Steering Committee Actually Is, and Why You Are Using It Wrong
The Trap That Feels Like Safety
Why Scale Changes Everything and Why Your Dashboard Lies at a Different Altitude
The Cascade Nobody Saw Coming
Otherside - The View Nobody Talks About
When the Committee Turns Over and the Programme Pays the Price
Fear Factor — When the Committee Makes Fear the Rational Choice
Five Disciplines - What Good Actually Looks Like
There is a specific kind of professional respect that exists in the programme management community that is never formally awarded, never written on a certificate, and never announced in a meeting.
It is the respect that attaches to a PM whose Green means Green.
Not the PM who always reports Green. The PM whose Green you believe. The PM who, when she says the programme is on track, you do not feel the need to verify independently, because her track record of honest reporting has made verification unnecessary. The PM whose Amber you take seriously the moment it appears, because her Amber has never been a managed signal. The PM who, when she asks for something, gets it quickly, because the committee has learned from experience that she does not ask unless the ask is real.
This is a form of professional capital that takes years to build and can be destroyed in a single steering meeting. And it is, in large programmes, not a soft asset. It is a hard governance asset that has direct, measurable delivery consequences.
This is the longer game. And it is the only game worth playing.
What Reputation Actually Does in a Programme Governance Context
Most discussions of professional reputation treat it as a career asset: something that helps you get the next role, the next client, the next programme. That is true. But in the context of a live programme, reputation operates as something more immediate and more consequential. It determines how quickly the committee responds when response is needed.
Consider two PMs, each managing a workstream in the same programme. Each surfaces an Amber in the fortnightly steering review. The Amber is of similar severity. The escalation is structured similarly. The options presented are similarly well-prepared.
The first PM has a track record of honest, early, structured escalation. Her previous Ambers were real, resolved through committee intervention, and closed with documented outcomes. The committee knows her Green means Green and her Amber means Amber.
The second PM has a track record of managed reporting. Her previous Ambers have occasionally resolved themselves within a fortnight without visible committee intervention, in ways that the committee could not fully trace. Her Greens have occasionally turned out to be less Green than reported.
The committee’s response to these two Ambers will be different. Not because the committee is consciously applying a credibility weighting. But because the committee members are human beings who have had different experiences with these two PMs, and those experiences shape how the next piece of information is received.
The first PM’s Amber triggers immediate engagement. The committee chair asks what they need. Decisions are made. Action items are assigned.
The second PM’s Amber triggers a different set of questions. How serious is this really? Is this going to resolve itself like the last one? Should we wait until next fortnight to see whether this is a real escalation or a managed one?
These are not unreasonable questions. They are the rational response to an information track record that has not been consistently reliable. But they consume time that the programme cannot spare, delay interventions that would have been more effective earlier, and produce a governance environment in which the committee’s authority is deployed more slowly and less precisely than the programme needs.
The credibility deficit of the second PM is costing the programme in every review, not because anything dramatic is happening, but because the fundamental trust that makes governance efficient is absent.
The Steel Plant Dimension: Why Credibility Matters More Here
In a steel plant ERP, MES, or APS implementation, the PM’s credibility with the steering committee carries additional weight for three specific reasons.
The plant’s operational leadership has limited tolerance for ambiguity.
Steel plant operations are managed with precision. The blast furnace campaign is planned to the hour. The rolling schedule is optimised to the minute. The maintenance shutdown window is non-negotiable. The people who lead these operations have spent their careers in an environment where information needs to be accurate and decisions need to be made on the information available, not on what the information might be after a further assessment.
When these leaders sit on an implementation programme’s steering committee, they bring this disposition with them. A PM who reports accurately, even when the news is bad, is recognised and respected by plant operational leaders. A PM who manages her reporting is not trusted by them, because they have spent their careers developing the ability to distinguish between a process that is performing within specification and a process that is being represented as performing within specification.
The plant operational leader on the steering committee is often the committee’s most discerning reader of programme reporting. And the PM who earns her trust earns the most valuable governance ally she can have: a committee member who will advocate for rapid intervention when the PM asks for it, because she has learned from experience that the ask is real.
The vendor ecosystem is small and reputationally interconnected.
As noted earlier in this series, the steel plant implementation vendor community is compact. The same vendors appear across multiple plants and multiple programmes. The PM who develops a reputation for honest, clear, timely escalation is recognised not only by her own committee but by the vendor community that operates across multiple client programmes.
Vendors, as rational actors, prioritise their resources toward clients who are applying the most visible and credible pressure. A PM whose credibility with her steering committee is high is a PM whose committee-level escalations are taken seriously by vendors. A vendor that has experienced the consequences of being formally escalated by a credible PM to a credible committee will respond differently to the next escalation from the same PM than a vendor that has learned that the PM’s escalations produce lengthy committee discussions without decisions.
The PM’s reputation for honest governance is, in the vendor management context, a commercial asset for the programme.
The domain complexity means the committee relies heavily on the PM’s assessment.
A steel plant ERP and MES implementation involves technical complexity in both the software and the industrial operations that most committee members cannot independently evaluate. The committee is relying heavily on the programme team’s assessment of what is on track and what is not, because the committee does not have the domain knowledge to perform its own independent assessment in the steering meeting.
In this environment, the PM’s credibility is the committee’s only reliable signal. A committee that trusts the PM’s assessment can govern efficiently: they receive the assessment, they ask the right questions, they make decisions. A committee that does not trust the PM’s assessment must either accept the risk of governing on information it suspects is managed, or invest time and energy in independent verification that is slow, expensive, and disruptive to the delivery team.
Neither option is as good as simply having a PM whose assessment can be trusted. The value of that trust, in a domain-complex programme, is larger than in a context where the committee can more readily verify the programme’s real state independently.
The Scar Tissue Disposition: What Experienced Committee Members Learn
The most experienced steering committee members in large programme governance share a disposition that is not born of cynicism or distrust. It is born of specific, expensive, personal experience of governance failures. It is the disposition of someone who has sat in a room where a programme revealed itself to be something other than what it appeared, understood with precision what options were no longer available, and made a commitment to themselves that they would not find themselves in that position again.
The disposition is specific: they are more attentive in smooth reviews than in difficult ones.
In a difficult review, where the dashboard has an Amber or Red, the committee is appropriately engaged. The difficult review is doing its job: it is surfacing a problem for committee attention. The committee responds. Decisions are made. Actions are assigned.
In a smooth review, where every workstream is Green and the programme manager is confident and the meeting is running eight minutes ahead of schedule, the experienced committee member is watching more carefully, not less. She is asking herself a question that she has learned, at cost, to ask: is this smooth because the programme is genuinely performing, or is this smooth because the programme has been prepared?
She knows these two things can look identical from the outside. She has learned that the way to distinguish them is not to accept the smooth review at face value but to probe the areas where a managed review would be least prepared for a genuine question.
The question about the interface register. The question about what the PM is most uncertain about that has not yet reached the formal escalation threshold. The question about the vendor that has been “being monitored” for three consecutive fortnights. The question about whether the simulation results have been validated against the live data environment.
None of these questions are aggressive. None of them imply distrust. They are the questions of someone who has learned that the smooth meeting is worth more scrutiny than the difficult one, because the difficult meeting is already doing the governance work and the smooth meeting may not be.
This disposition is the accumulated scar tissue of governance failures. It is earned through the specific experience of finding out late, of sitting in a crisis meeting and understanding with clarity that the intervention available six weeks ago was no longer on the table, and of asking the question that follows every such experience: why did I not know sooner?
It is also, in a well-governed programme, completely unnecessary. The PM who surfaces problems early, structures her escalations clearly, maintains the integrity of her RAG reporting, and builds a track record of honest governance gives the committee no reason to apply the scar tissue disposition to her programme. The smooth meeting is genuinely smooth. The committee can engage with it as accurate information rather than treating it as a performance to be evaluated.
The goal of good governance is not just to handle problems well when they arise. It is to make the experienced committee member’s instinct to distrust the smooth meeting an instinct that this particular programme never gives her reason to exercise.
A Tale of Two Programme Reputations
The PM Whose Green You Believe
There is a programme manager who has worked in steel plant implementation for fourteen years. She has delivered three large MES programmes and two ERP programmes. She has a reputation in the implementation community that is difficult to describe precisely and impossible to manufacture: when she says a programme is on track, it is on track.
This reputation was not given to her. It was built, over fourteen years, through a consistent set of choices in specific moments.
The moment in her first programme, in month eight, when she identified a data migration risk that she could probably have managed internally but chose to escalate because it had cross-workstream implications, and watched the committee resolve in fifteen minutes what would have taken her six weeks to navigate alone.
The moment in her second programme, in month fourteen, when the vendor missed a significant commitment and she filed a formal vendor performance notice the same week rather than managing it bilaterally, and watched the committee-level escalation produce a vendor response that the bilateral management had not produced in four weeks.
The moment in her third programme, in month six, when she told the committee that the go-live date they had publicly committed to was no longer achievable with the current resource plan, and watched the committee make a difficult decision in the room rather than defer it until the situation was unmanageable.
Each of these moments was uncomfortable. Each of them produced a short-term cost: a difficult meeting, a challenging conversation, a reputation for being the person who surfaces bad news. And each of them contributed to a long-term asset: a committee that learned, one programme at a time, that her Green means Green and her Amber means Amber.
By her fifth programme, the dynamic in her steering meetings had a different quality from anything she had experienced in her first. When she raised an Amber, the committee chair’s first question was always “what do you need from us?” When she reported Green, nobody felt the need to probe. When she asked for something, it was provided quickly, because the committee had fourteen years of evidence that she does not ask unless the ask is real.
This is the governance compact at its most efficient. Information flows upward honestly. Decisions flow downward clearly. The committee’s authority is deployed precisely and rapidly, because it is deployed in response to an accurate picture of the programme’s real state.
The programme completed ahead of schedule and under budget. Not because it encountered no problems. It encountered significant problems, including a vendor failure that required a committee-level escalation to the vendor’s regional leadership, a data quality issue that required a three-week remediation, and a plant operations constraint that required a replanning of the go-live sequence. All three problems were surfaced within seventy-two hours of identification. All three were resolved through committee intervention. The programme absorbed each one without material impact on the overall delivery.
The PM Whose Green You Check
There is another programme manager in the same implementation community. She is technically capable, commercially astute, and genuinely committed to delivery. She also has a reputation that is less useful than the one described above.
Her Green is not disbelieved. But it is verified. Committee members who work with her programme feel the need to probe the smooth meetings. Vendors who know her programme from the implementation community have learned that the committee’s escalations arrive later than the underlying situation warrants. Incoming committee members who review her programme histories find dashboards that look clean but leave questions unanswered.
She is not dishonest. She is optimistic. She manages risks that she believes she can manage, and she manages them with genuine skill, and she is sometimes right. But she is sometimes wrong, and when she is wrong, the committee finds out later than it should, with fewer options than it would have had, and with the specific experience of discovering that the smooth meeting was a managed performance rather than an accurate report.
I want to be precise about this, because it is easy to read the two portraits as a simple story of one good PM and one bad one. That is not what I am describing. The second PM is not a bad PM. She is an optimistic one. The difference is narrower than it sounds, and it has consequences that compound across every programme she manages.
Over time, this experience accumulates into the committee’s default posture toward her programmes: cautious engagement, independent verification where possible, a slight delay in committee intervention while the committee assesses whether the escalation is real.
That slight delay is the cost. Not dramatic. Not catastrophic. But real and consistent across every programme she manages, compounding in every steering meeting, producing programmes that are slightly slower to respond to problems than they should be, slightly more expensive to resolve crises in than they would need to be, and slightly less effective at deploying the committee’s authority at the moment when authority is most valuable.
The Programme That Earns Its Reputation: A Complete Picture
The reference case that closes this series is not a fictional programme invented to make a point. It is the composite of several real programmes, described by senior practitioners when asked to name an example of governance working as it was designed to work.
What they describe, consistently, has the same characteristics.
The programme director stated her operating principle explicitly to the workstream leads at programme inception, in the first all-hands session of the programme. Not in a governance document. In the room, in conversation: “I will never ask you to manage a programme-level risk alone. I will never penalise you for surfacing a problem early. I will ask you to manage it correctly, with a structured escalation and a clear ask. And I will penalise you for surfacing it late. Not because I want to punish you, but because late escalation costs us all options we cannot afford to lose.”
The committee chair made a complementary commitment at the first steering meeting: “If you bring us a problem with options, we will make a decision in this meeting. If we cannot make a decision in this meeting, we will tell you why and commit to a specific date. We will not interrogate the problem without deciding about it. Our job is to decide. Bring us decisions to make.”
These two commitments, stated explicitly, in the first week of the programme, established a governance compact that shaped the information culture for the entire delivery.
The workstream leads heard the programme director’s commitment and understood it as a genuine promise. When they identified risks, they escalated them within days, not weeks, because they had been told directly that early escalation would not be penalised. The programme director kept her promise: when Ambers arrived early, she thanked the workstream lead in the review, named what was right about the timing, and moved immediately to the committee decision.
The committee heard its chair’s commitment and understood it as a standing instruction. When escalations arrived, they made decisions. They did not ask root cause questions before the forward decision was made. They did not request written analyses before acting. They made decisions, assigned action items, and followed up on them at the next review.
The governance compact was honoured on both sides. And the result was an information environment in which every problem was surfaced within seventy-two hours of identification, every escalation was structured with problem, options, and ask, every committee intervention was timely and effective, and every action item was tracked and closed.
The programme encountered two events that, in a less well-governed programme, would have become cascades. A material master data quality issue in month seven that affected three workstreams. A vendor resource gap in month twelve that affected the MES scheduling module’s configuration timeline.
In both cases, the escalation arrived within seventy-two hours of identification. In both cases, the structured escalation gave the committee a clear decision to make. In both cases, the committee made the decision in the meeting. In both cases, the problem was resolved before it reached the downstream workstreams.
The programme completed six weeks ahead of its planned go-live date, with a final cost 4% below the approved budget.
The six weeks early and the 4% below budget were not the result of favourable conditions. The conditions were not favourable: the plant was in a period of operational pressure, the implementation partner had resource turnover in month fourteen, and one of the key committee members changed roles in month eighteen. All three of these events would have been significant governance challenges in a less well-governed programme.
They were manageable in this programme because the information environment was honest, the committee’s response was timely, and the governance compact was honoured by both sides consistently enough that when the challenges arrived, the machinery to address them was already working.
What the Longer Game Requires
The longer game in programme governance is not a strategy that delivers results quickly. It is a compound investment that delivers results over time, across programmes, across careers, and across the industry communities in which programme professionals work.
For project managers and workstream leads, the longer game requires the consistent practice of the five disciplines from Part Nine, maintained across every programme regardless of whether the committee rewards them consistently. The PM who practices honest escalation in a Programme B environment, where the committee interrogates rather than intervenes, is investing in a reputation that she will carry into her next programme, where the committee may be more receptive. The habit, once built, is more valuable than any individual programme’s governance environment, because it produces the same information regardless of the environment it operates in.
It also, over time, changes the environments it operates in. The PM who consistently practices honest escalation and structures her escalations clearly is demonstrating, in every programme she works in, what good governance behaviour looks like. Committee members who work with her over multiple programmes learn what good escalation looks like and begin to respond to it appropriately. Other programme managers who observe the outcomes she produces begin to understand why the practice produces those outcomes.
Reputation is contagious in the programme management community. The PM whose Green means Green elevates the standard for every PM who works alongside her.
For committee members, the longer game requires the consistent practice of the governance behaviours described in Part Eight: the thank-you that is specific and public, the decision made in the meeting rather than deferred, the follow-up on committee commitments, the distinction between accountability and blame maintained in every review. These behaviours, practiced consistently, produce governance environments that attract honest information rather than managed information.
And for the programme community as a whole, the longer game is about building an industry norm in which the five disciplines of Part Nine are the expected standard rather than the exceptional practice. Where the PM who escalates late is the exception rather than the rule. Where the committee that interrogates rather than intervenes is recognised as a governance failure rather than a management style. Where the smooth dashboard that never shows Red is read as a signal to look harder rather than a cause for comfort.
This is not a utopian aspiration. It is the observable state of the best-governed programmes in every industry and every context. Those programmes exist. Their reputations are known in the communities where they operate. The people who worked on them carry the experience forward into the next programme. The practices spread.
A Final Note: The Governance Compact and Why It Matters Beyond the Programme
This series began with a simple observation: there is a phrase that echoes through programme review rooms across the country, spoken with the confidence of someone who has not yet opened the envelope.
Sab theek hai, sir.
Everything is fine.
Everything is not always fine. In large, complex, multi-workstream programmes implementing sophisticated software in industrially complex environments, things go wrong. Data quality is worse than expected. Vendors underdeliver. Interface specifications diverge from the live data environment. Capital expenditure approvals take longer than planned. Business process owners change roles at critical moments. Plants have operational constraints that were not fully understood in the design phase.
These things happen. They are not governance failures. They are the normal complexity of delivery in the real world.
The governance failure is not that these things happen. The governance failure is when these things are known to the programme team but not to the committee, because the information environment has been shaped by incentives that reward managed reporting over honest reporting.
The governance compact is the agreement that makes honest reporting the rational choice. The programme team’s half of the compact is to surface information early, structure escalations clearly, and maintain the integrity of the RAG system. The committee’s half is to respond to that information with decisions rather than debriefs, interventions rather than interrogations, and the consistent distinction between accountability and blame.
When both halves are honoured, programmes deliver. Not without problems. With problems that are caught early, surfaced clearly, and resolved while the options are still good, by committees that have the authority and the information to act at the moment when action is most effective.
When either half is broken, programmes drift. Problems accumulate in the space between the reported state and the real state. The committee makes decisions based on a programme that does not exist. The delivery team manages risks that the committee could have resolved in fifteen minutes with authority it has but has not been given the opportunity to deploy.
And at some point, the gap closes. Reality asserts itself. The crisis arrives. And in the post-mortem, someone asks the question that follows every such event, in every programme, in every industry, across the entire history of large-scale delivery:
“Why are we only hearing about this now?”
The answer to that question is always some version of the same thing: because the governance compact was not honoured, and the information that should have reached the committee in week seven reached it in week fourteen, and the options that were available in week seven were no longer available in week fourteen, and the programme paid the difference.
The compact is the thing worth protecting. The five disciplines of Part Nine are the practices that protect it on the delivery team’s side. The governance behaviours of Part Eight are the practices that protect it on the committee’s side. The credibility built through honest reporting over the longer game is the asset that makes the protection self-sustaining, because a committee that has learned to trust a PM’s Green creates the conditions in which honest reporting is not an act of courage but simply the obvious thing to do.
That is the programme worth building. That is the reputation worth earning. That is the governance compact worth honouring.
And none of it begins with a framework, a methodology, or a governance document.
It begins with one PM, in one fortnightly review, looking at a dashboard that should read Amber, and making a choice.
Looking back across ten parts of this series, that is the only sentence that needed to be written. Everything else was context for it.
This series has been a long conversation about something that most governance frameworks discuss in abstractions and most PMs learn the hard way. If something in these ten parts resonated with an experience you have had, on either side of the table, I want to hear it. The comments are where this conversation has always been heading.
And if you have worked on a programme where the governance compact was genuinely honoured, on both sides, and where the result was something you were proud of, tell me about that too. Those stories are rarer than they should be. They deserve to be heard.
#ProgrammeGovernance #ProjectManagement #ERPImplementation #MESImplementation #APSImplementation #SteelManufacturing #HonestLeadership #DeliveryExcellence #GovernanceCompact #IndianManufacturing #SteeringCommittee #ProgrammeReputation #LongerGame #RiskManagement #DigitalTransformation
Disclaimer: The incidents, characters, projects, and organisations referenced in this article are fictionalised composites drawn from recurring patterns observed across complex transformation programmes. Their purpose is to illustrate leadership and governance lessons rather than describe any specific organisation, project, customer, or implementation. The lessons, however, are very real.