Sanjay K Mohindroo
A practical CIO 90-day plan for building board trust, reducing enterprise risk, prioritizing investments, and delivering measurable business value from day one.
A new CIO does not have 90 days to understand the technology. They have 90 days to establish why the business should trust their judgment.
That distinction can determine whether the next three years deliver measurable business value or become another expensive exercise in transformation theatre.
After nearly three decades working across industries, geographies and executive leadership environments, I have learned that the most consequential decisions a CIO makes early in their tenure are rarely technology decisions.
They concern capital, people, risk and priorities.
The conventional advice is familiar: spend the first 30 days listening, the next 30 developing a strategy and the final 30 presenting a roadmap.
I disagree.
The first 90 days are not an extended orientation programe. They are a test of executive judgment under imperfect information.
A successful CIO must diagnose the business, challenge assumptions, establish accountability and demonstrate progress, often simultaneously.
Here is the approach I would recommend.
Why the Traditional CIO 90-Day Plan Falls Short
Most organizations already have a technology strategy, an investment portfolio, and a long list of initiatives described as critical.
What they often lack is clarity about which investments are actually producing business outcomes.
Consider a global manufacturer operating across multiple markets.
Its technology leadership might inherit dozens of active projects, a substantial annual technology budget and competing requests from regional business heads.
The instinctive response is to review every project, commission an architecture assessment and develop a comprehensive transformation roadmap.
That may appear disciplined. It can also consume the entire first quarter without changing a single business outcome.
The more important questions are different.
Which initiatives directly support revenue, margin or customer retention? Which systems represent unacceptable operational exposure? Which investments continue because nobody has challenged their original assumptions?
A CIO who cannot answer these questions is not yet in control of the technology agenda, regardless of how detailed the roadmap looks.
The Five Decisions That Define the First 90 Days
I use a simple framework: Understand, Prioritize, Align, Deliver, and Build for Scale.
These are not five sequential phases. They are five executive responsibilities that overlap throughout the first quarter.
1. Days 1–15: Understand the Business Before Assessing the Technology
The priority is to establish where the organization creates value and where it is vulnerable.
Meet the CEO, CFO, business unit leaders, risk leadership, and selected customers where appropriate.
But avoid the predictable question: "What do you expect from IT?"
Instead, ask:
· What are the three business outcomes we cannot afford to miss this year?
· Where is technology currently constraining growth, productivity or customer experience?
· What operational failure would cause the greatest financial or reputational damage?
· Which technology investments would you reconsider if capital became scarce?
These conversations expose the difference between stated priorities and actual business needs.
Alongside them, examine four facts: technology spending, critical operational dependencies, major delivery commitments, and leadership capability.
By day 15, the CIO should have a preliminary business-risk map, not a technology wish list.
It should identify where value is being created, where money is being absorbed, and where the enterprise is exposed.
2. Days 15–30: Prioritize Ruthlessly and Challenge Existing Commitments
One of the most difficult responsibilities for an incoming CIO is deciding what not to do.
Technology portfolios accumulate commitments over time. Projects survive leadership changes, business cases become outdated and sunk costs are mistaken for reasons to continue.
A new CIO has a narrow window in which to challenge this inertia.
I recommend assessing significant initiatives against four criteria:
1. Business value: What measurable financial or operational outcome will this deliver?
2. Risk reduction: What exposure does this eliminate or materially reduce?
3. Time to impact: When will the business experience a meaningful benefit?
4. Execution confidence: Do we have the leadership, capacity and organizational commitment to deliver?
Every major initiative should receive one of four decisions: accelerate, continue, redesign or stop.
Stopping a project is not evidence of failure. Continuing an unjustified investment because it is politically convenient is.
Imagine a portfolio containing 40 active initiatives.
A structured review might reveal that 10 have weak business ownership, five duplicate capabilities, and several depend on assumptions that no longer hold.
These numbers are illustrative, but the underlying issue is common: portfolio activity is not the same as portfolio value.
The objective is not indiscriminate cost reduction. It is better capital allocation.
By day 30, the CEO and CFO should know which technology commitments deserve continued investment and which require intervention.
3. Days 30–45: Align Accountability, Not Just Stakeholders
Business-IT alignment is one of the most overused expressions in enterprise technology.
In many organizations, alignment means holding meetings, establishing steering committees and securing agreement on a presentation.
That is insufficient.
Real alignment means the business and technology leadership jointly own outcomes.
If an initiative promises a reduction in customer onboarding time, the business executive responsible for onboarding must share accountability for achieving it.
If an automation programe promises productivity gains, the relevant operational leader must own the process changes required to realize those gains.
The CIO cannot deliver business transformation while the business remains a spectator.
I recommend establishing a compact accountability charter for every major initiative.
It should identify the executive sponsor, expected business outcome, investment envelope, decision rights and success measures.
The measures must be intelligible to the board.
Revenue contribution, cost-to-serve, operating resilience, working capital and customer retention are meaningful.
The number of applications migrated, or features deployed, may be useful operational measures, but they are rarely sufficient measures of business success.
By day 45, every material technology investment should have a named business owner and an agreed definition of success.
4. Days 45–75: Deliver an Early Win That Actually Matters
The pressure to demonstrate early success is understandable.
Unfortunately, it can encourage cosmetic victories.
A new dashboard, an internal chatbot demonstration, or a highly publicized pilot may generate enthusiasm without improving enterprise performance.
The right early win should satisfy three tests.
It must address a recognized business problem, produce measurable evidence and create confidence in the organization's ability to execute.
For example, reducing a recurring order-processing bottleneck may be more valuable than launching a new digital platform.
Eliminating a material control weakness may create more enterprise value than announcing an ambitious AI programe.
Improving the reliability of a revenue-critical process can establish credibility faster than a polished technology vision.
The early win should also be proportionate.
Do not destabilize a critical operation to prove that the new CIO is decisive.
A useful target is to demonstrate a measurable improvement within 60 to 75 days, supported by a credible baseline and verified by the business owner.
Where the outcome takes longer, demonstrate that a material risk has been removed or a previously stalled decision has been resolved.
Early wins should build institutional confidence, not personal publicity.
5. Days 75–90: Build for Scale and Establish the Next 12 Months
By the final month, the CIO should be able to explain the technology agenda without relying on technical terminology.
The CEO and board need answers to five questions.
Where are we investing? What business outcomes will those investments produce? What risks remain? What capabilities must change? Who is accountable?
The resulting 12-month agenda should distinguish between three categories:
Protect the enterprise: Cybersecurity, resilience, regulatory obligations and critical operational dependencies.
Improve enterprise performance: Productivity, process simplification, customer experience and cost efficiency.
Create future advantage: Data capabilities, AI, differentiated digital services and new business models.
The balance will vary by organization.
A regulated financial institution facing material resilience concerns may need to emphasize protection. A consumer business facing declining customer loyalty may prioritize experience and differentiation.
The mistake is to assume every organization needs the same transformation agenda.
The final deliverable should be a concise, financially grounded investment plan with milestones, owners, dependencies, and explicit trade-offs.
What the Board Should Expect by Day 90
A board should not judge the incoming CIO by the number of meetings conducted or the sophistication of a technology presentation.
It should expect evidence of improved executive control.
Dimension Evidence by Day 90
Business understanding: Agreed enterprise priorities and constraints
Capital discipline: Investment decisions with clear rationale
Risk management: Material exposures identified, owned and addressed
Accountability: Named business and technology owners
Execution: At least one verified improvement or material risk reduction
Future direction: A credible, funded 12-month agenda
These are not administrative deliverables.
They establish whether technology leadership is becoming an effective instrument of enterprise performance.
The Counterargument: What About Listening and Building Trust?
Some leaders will argue that 90 days is too short to challenge established investments or make consequential decisions.
There is merit in that concern.
An incoming CIO who begins cancelling projects without understanding the organization's history can destroy trust and overlook critical dependencies.
But listening and acting are not mutually exclusive.
The solution is to distinguish between reversible and irreversible decisions.
Clarifying accountability, challenging business cases and stopping unnecessary new commitments can often happen quickly.
Major platform replacements, structural reorganizations and irreversible capital commitments require deeper evidence and appropriate governance.
Decisiveness is not the same as haste.
The best CIOs know when to act, when to investigate and when to resist pressure for a premature announcement.
The Real Test Begins on Day 91
The first 90 days will not transform an enterprise.
They should, however, change the quality of decisions the enterprise makes about technology.
By then, the CIO should have earned the confidence to challenge priorities, redirect investment, confront uncomfortable risks, and hold both technology and business leaders accountable.
That is the foundation of sustained transformation.
The CIO who spends the first quarter trying to impress the organization with a grand vision may leave the underlying problems untouched.
The CIO who uses that period to establish clarity, discipline and measurable progress creates something far more valuable: the ability to deliver.
The first 90 days are not about proving that the CIO understands technology. They are about proving that technology leadership understands the business.
For CEOs, board members, and CIOs: what is the one decision a new CIO must get right in the first 90 days, even if it creates uncomfortable conversations?
Share your perspective in the comments, or subscribe to TechnologyTrends for more practical insights on technology leadership and enterprise transformation.