The Hidden Risk of AI: Building Transformation Programs for a Future That May Not Exist
For decades, enterprise transformation followed a familiar model: define a future state, build a multi-year roadmap, and execute with discipline. That model is now under pressure—not because transformation is no longer necessary, but because the assumptions behind it are rapidly breaking down. Large transformation programs rely on a core premise: that we can reasonably predict the future operating model. In an AI-driven environment, that premise is increasingly fragile. Capabilities are evolving faster than planning cycles, and organizations are designing multi-year programs against a moving target. McKinsey & Company has highlighted that while generative AI could create significant economic value, organizations are capturing impact fastest through incremental deployment embedded in existing workflows, not large, monolithic transformations. Value is emerging in shorter cycles, not long-duration bets. At the same time, execution risk was already high. Boston Consulting Group estimates that 70% of digital transformations fail to meet their objectives, even in more stable environments. AI does not reduce that risk—it amplifies it. But there is a more fundamental issue emerging—one that is still underappreciated. We are designing transformation programs without a clear understanding of what AI will actually be capable of in two to three years. This introduces a new form of exposure. Not just whether a program will be delivered successfully, but whether it is solving the right problem at all. Entire layers of functionality being built today—workflow orchestration, decision support, even elements of system integration—may be simplified, automated, or eliminated as AI capabilities mature. The risk is no longer just execution failure. It is design risk leading to solution irrelevance. Programs that are delivered on time, on budget, and exactly as designed—but no longer aligned with the business or technology landscape by the time they go live. This is why we are seeing leading organizations shift away from “big-bang” transformation toward more adaptive models. Composable architectures, incremental modernization, and shorter investment cycles are becoming the preferred approach—not as a compromise, but as a strategic response to uncertainty. The question is no longer, “What should our business look like in five years?” It is, “How do we remain adaptable over the next five quarters?” For CEOs, CIOs, and private equity leaders, this has direct implications for capital allocation and risk management. Transformation programs must be structured with optionality—designed to evolve as capabilities evolve, rather than locking into a fixed future state. In many cases, the right answer is not to stop transformation—but to deconstruct it. Rob Purks is a Founding Partner at Lumerai Advisors, a technology strategy advisory firm. Lumerai Advisors provides an unbiased perspective which is not influenced by vendor relationships. With over 150 years of CIO and technology experience, the founding partners bring an honest and complete perspective on technology strategies and challenges. #Telecom #DigitalTransformation #PrivateEquity #ITStrategy #CIO #EnterpriseArchitecture #OPEX #AI #Cloud Lumerai Advisors
The AI ROI Panic Is About to Create the Next Legacy System
By Rob Purks, Founding & Operating Partner, Lumerai Advisors There is a quiet panic spreading through boardrooms right now, and it has nothing to do with whether AI works. It has to do with whether anyone can prove it. The numbers behind that panic are real. Hyperscalers are on track to spend roughly $675 billion on AI infrastructure this year alone. Meanwhile, MIT’s Project NANDA found that 95% of enterprise AI pilots deliver no measurable P&L impact. S&P Global reported that 42% of companies abandoned most of their AI initiatives last year which is more than double the rate of the year before. Forrester is now predicting a market correction with enterprises deferring a quarter of their planned 2026 AI spend into 2027. Even the debt markets have weighed in: Citi identified a measurable credit spread penalty for companies classified as AI adopters without evidence of return. Spending without proof is now literally priced into the cost of capital. I am not here to argue with the data. The data is right. I am here to argue with the response. Key Takeaways The Control Reflex: Why AI Governance Backfires When boards see numbers like these, they react the way boards have always reacted: with control. AI steering committees and per-use-case business cases. ROI attestation before funding. Approval gates between pilot and production. Governance councils that meet monthly to review initiatives that move weekly. Every one of these mechanisms is individually defensible. That is exactly what makes them dangerous. I have spent my career on both sides of this dynamic, as a CIO running technology for telecom operators in Latin America, and later advising enterprises on transformation at Accenture, IBM, and Ericsson. And I can tell you what happens next, because I have watched it happen with every major technology wave: the control structure built to manage today’s uncertainty becomes tomorrow’s constraint. It outlives the problem it was created to solve. Nobody is ever promoted for dismantling a governance committee. I learned this the hard way by inheriting the aftermath of one. At a Latin American operator a major CRM transformation had been put in front of a review board and killed on grounds that were individually hard to argue with: the projected budget was steep, the internal skills weren’t fully in place, and the business wasn’t deemed ready. Every objection was reasonable. The board did exactly what it was designed to do. And while we sat on a defensible “not yet” a competitor moved, modernized its customer platform, and took ground we never fully recovered. The control worked perfectly. The company lost anyway. That is the trap: the most dangerous governance failures don’t look like failures at all, they look like prudence. We have seen this exact movie before. Cloud and agile both promised speed. In most enterprises they delivered something closer to “the same speed with more meetings.” The technology arrived, the operating model absorbed it, neutralized it, and carried on. The gains didn’t disappear, they were quietly strangled by slow decisions and diffused accountability. The ROI panic is now rebuilding that machinery, at speed, with the best of intentions. Except this time there is a difference that should worry every executive: when the constraint is a legacy system you can eventually migrate off it. When the constraint is a legacy operating structure there is no migration project. It just becomes how the company works. I call this Governance Debt: the accumulated drag of controls that outlast the uncertainty they were built to manage. Like technical debt it compounds quietly and like technical debt the interest is paid in speed. The Wrong Diagnosis: It’s Not an AI Adoption Problem Here is the tell that we are solving the wrong problem. In one of the most striking findings of this cycle 97% of executives report personally benefiting from AI yet only 29% see significant organizational ROI. Read that gap carefully. It is not an adoption problem. It is not a model-quality problem. And it is emphatically not a control problem. It is a compounding problem. Value is being created at the level of individuals and teams and the organization has no mechanism to aggregate it, redirect it, or build on it. Adding oversight to that situation does not create compounding. It adds friction to the one place value actually exists. Look at what the successful 29% actually have in common: AI tied to revenue outcomes, business teams owning the workflows, and the whole effort treated as organizational redesign rather than technology deployment.[1] Notice what is not on that list: more approval gates. The organizations seeing returns did not out-govern their peers. They out decided them. What to Build Instead: A Velocity-First AI Operating Model If the answer isn’t heavier oversight, what is it? Three structural moves none of which require a committee: Replace approval gates with kill cycles. Don’t make initiatives prove their worth before they start, make them prove it on a clock. Every AI initiative launches with pre-agreed kill criteria and a fixed time box. The discipline shifts from “may we begin?” to “did we learn enough to continue?” That is governance measured in velocity, not meetings. Measure ROI at the portfolio level, not the use case. Demanding a business case from every individual experiment guarantees you will only fund the safe, incremental, and ultimately unimportant. Venture and private equity investors figured this out decades ago: the portfolio carries the math so the individual bets can take real risk. It is the same logic that drives value creation across a portfolio of companies, you manage the aggregate, not the average. Boards should hold leadership accountable for portfolio-level return and learning rate, not for the survival of any single pilot. Put a sunset clause on every control. Any governance mechanism created to manage AI uncertainty should carry an expiration date and a renewal test: what decision did this body accelerate this quarter? If the honest answer is none, it isn’t governing, it’s accumulating. This is how you keep
AI Isn’t Your Competitive Advantage; Better Decisions Are
Organizations don’t compete on technology. They compete on the quality and speed of their decisions. Introducing the Enterprise Decision Stack™, a new executive framework explaining why strategy, governance, operating models, trusted data, and AI must work together to create sustainable competitive advantage.
The Missing Stage in Every Technology Investment
McKinsey estimates that approximately 70% of digital transformations fail to meet their objectives. Why? Most technology decisions don’t fail because organizations choose the wrong technology. They fail because they begin by solving the wrong problem. After more than three decades helping executives make major technology decisions, I’ve noticed something: the best executive teams don’t necessarily have better answers. They ask better questions. It often starts with a statement like: Most organizations immediately begin discussing vendors. A different conversation begins by asking, “What business problem are we actually trying to solve?” Technology requests are rarely the problem. They are hypotheses about the solution. Executive leadership begins by validating the problem before validating the technology. Exceptional leaders separate business problems from proposed solutions. That’s why I believe the quality of every technology investment is determined long before technology is ever selected. Better decisions begin with better questions. Executive Takeaways Where Most Investment Processes Break Down Imagine building a new corporate headquarters. No executive team would approve the full construction budget before understanding the business requirements, evaluating alternative designs, assessing the site, and validating the long term operating model. Yet organizations routinely approve technology investments with an equivalent level of uncertainty. Not because they’re careless. Because the investment process encourages certainty before sufficient understanding exists. Business cases are often written while assumptions still outweigh evidence. Benefits are estimated before outcomes are fully defined. Budgets are approved before organizations truly understand the problem they are trying to solve. Then implementation begins and the organization spends months learning what it could have discovered before approval. We’ve normalized learning after approval. Instead of learning before commitment. Technology Investments Should Mature Like Executive Decisions One of the lessons I’ve taken from working with executive teams is that confidence isn’t something you create. It’s something you earn. The best investors understand this instinctively. They don’t commit all of their capital on day one. They invest in reducing uncertainty. Every conversation. Every discovery session. Every customer interview. Every piece of evidence either increases confidence or challenges assumptions. Technology investments should work exactly the same way. As knowledge increases… Decision confidence should increase. As decision confidence increases… Investment commitment should increase. Instead, many organizations reverse the sequence. They commit significant capital first. Then spend months validating assumptions they could have challenged before funding was approved. The Lumerai Technology Value Realization Framework™ After seeing this pattern repeat across hundreds of technology decisions, we developed the Lumerai Technology Value Realization Framework™ to help executives improve decision quality before major investments are made. At its core is a simple principle: investment confidence should increase before capital commitment. Rather than viewing technology investments as a single approval event, the framework treats them as a progression of executive decisions. Each stage is designed to answer one critical question before additional resources, executive attention, or capital are committed. It begins with a Business Opportunity. Not a technology request. Not a vendor presentation. A business opportunity. From there, each stage progressively reduces uncertainty while increasing executive confidence. Each stage exists for one purpose: replacing assumptions with evidence before increasing commitment. Every stage earns the right to unlock the next investment decision. Warning Signs You’re Investing Too Early The Role of the Modern CIO Is Changing For decades, CIOs were measured by operational excellence. System availability. Cost management. Project delivery. Those responsibilities remain essential. But executive leadership increasingly expects something more. Boards, CEOs, CFOs, and investors increasingly expect CIOs to improve the quality of enterprise technology investment decisions, not simply the quality of technology delivery. That requires a different leadership mindset. One that values curiosity before certainty. Business outcomes before technology features. Questions before answers. The CIO of the future won’t be defined by the systems they implement. They’ll be defined by the quality of the decisions they help their organizations make. A Question Worth Asking Before approving your next major technology investment, ask one simple question. Are we solving the right problem? It sounds obvious. Yet it may be the most valuable question an executive team can ask. Technology alone doesn’t create business value. Better decisions do. Those decisions come from solving the right problems, executing with confidence, and replacing assumptions with evidence. And every one of those things begins with asking better questions. Coming Next: The Most Expensive Technology Mistake You Can Make Most technology requests arrive disguised as solutions. “We need AI.” “We need a new ERP.” “We need to move everything to the cloud.” But what if those aren’t business problems at all? In the next article, we’ll explore why organizations so often mistake technology requests for business needs, and how a disciplined discovery process can dramatically improve technology investment decisions before a single dollar is committed.
The Architecture of Authority: Why AI Is Reshaping Enterprise Leadership
For decades, the enterprise power dynamic was absolute and unchallenged: systems provided the data, and humans provided the judgment. Organizations termed themselves “data-driven” if an executive glanced at a dashboard before making a call, but the dashboard was a passive participant. It never actually changed who held the steering wheel or who was accountable when things went wrong. Technology was a silent partner—a repository of record that executed instructions only after the human “go” signal was given. That boundary has not just blurred; it is being erased. We are moving from an era of “Systems of Record” to an era of “Systems of Action,” and most organizations are fundamentally unprepared for the shift in authority that follows. The challenge isn’t the technology itself; it’s that we are attempting to run 21st-century intelligence on top of 20th-century governance. The End of the Dashboard Era The newest generation of AI has moved beyond recommending a course of action to initiate it. This is the critical pivot point where “support” becomes “participation”. In many modern enterprise stacks, the machine is already making high-stakes calls in milliseconds—isolating network devices, blocking multi-million-dollar transactions, or rerouting global shipments—often before a human analyst even sees an alert. When a system functions at this speed, the traditional “human-in-the-loop” model becomes a bottleneck or, in some cases, a myth. At this point, the system is no longer informing a decision; it is determining the outcome. This creates an immediate crisis for traditional governance. Most corporate frameworks are built on a 1990s-era assumption: that humans make judgments and systems implement them. When the system itself begins to determine what happens next, the separation between decision-making and execution—the very foundation of corporate oversight—becomes impossible to maintain. The Conflict of Logic vs. Intuition The most overlooked risk in AI implementation isn’t a technical failure—it’s the moment of disagreement. What happens when a machine’s data-driven recommendation contradicts a veteran manager’s years of intuition? In a traditional hierarchy, the senior leader wins by default. But in an AI-integrated environment, that “win” might come at the cost of operational speed or accuracy. Conversely, if the machine wins, who owns the liability? In regulated industries, these aren’t just philosophical debates; they carry significant legal and operational consequences. A system that blocks a transaction or flags a customer is taking an action that has traditionally required a signature and a clear chain of custody. If we haven’t designed the “Decision Architecture” to handle these conflicts, we aren’t innovating; we are simply creating a new type of organizational chaos. Decision Architecture: The Invisible Layer As decisions begin to emerge from within the technology itself, the structure of decision-making becomes an architectural question, not just a management one. This is the concept of Decision Architecture: the intentional design of how authority flows between people and software. Historically, authority evolved through hierarchy: information flowed up, and decisions moved back down through operational silos. Core platforms, like ERP systems, were built specifically to reinforce this “step-by-step” approval logic. These designs work perfectly when systems are executing predictable transactions. But they fail when an intelligent layer begins to evaluate context and trigger responses across those same processes. The friction we are seeing today isn’t a technical glitch; it is an organizational collision. Decisions are bypassing the management chain entirely and emerging from the “intelligence layer” of the stack. Without dedicated architecture to govern this flow, the CIO is no longer managing a technical stack—they are managing a fragmented, automated bureaucracy. The Danger of Accidental Authority Perhaps the greatest risk to the modern enterprise is “Accidental Authority.” This happens when AI capabilities are developed in isolated silos—one team building a fraud model, another implementing automated customer service, and a third deploying AI-driven cybersecurity. Each of these teams is essentially handing over “micro-slices” of corporate authority to different algorithms, often without a central registry of what decisions have been automated. Without coordinated architecture, you wake up to a fragmented environment where your systems have inconsistent levels of authority, lack oversight, and offer no clear way to override them when they go off the rails. We must stop building AI as a series of features and start building it as a unified decision-making ecosystem. The Practitioner’s Mandate: Designing for Authority For the modern CIO, the challenge is no longer the deployment of AI; it is the management of authority. The most dangerous path is allowing this authority to emerge accidentally, hidden within isolated teams or embedded deep inside individual platforms. To lead this transition, technology leaders must move toward three strategic imperatives: From Tool to Participant The organizations that survive this shift will be the ones that stop viewing AI as just another tool in the shed and start viewing it as an active participant in the business. The role of the leader is no longer to “sign off” on the data, but to architect the logic that governs the machine’s behavior. Success in the AI era won’t belong to the companies with the fastest algorithms or the biggest data lakes. It will belong to the leaders who treat decision-making as something that must be intentionally designed, rather than something that happens by accident as a byproduct of new technology. Frequently Asked Questions How is AI changing corporate hierarchy? Artificial intelligence is reducing the need for organizations to rely solely on traditional management layers to coordinate work and distribute information. As AI systems become capable of analyzing data, recommending actions, and executing routine decisions, authority increasingly shifts from information control to judgment, governance, and accountability. Organizations will need to redesign leadership structures to ensure humans remain responsible for strategic direction and oversight. What is the Architecture of Authority? The Architecture of Authority is the framework that defines how decisions are made, delegated, governed, and monitored within an organization. In the age of AI, it extends beyond traditional reporting structures to include intelligent systems that participate in decision-making. A well-designed Architecture of Authority ensures AI augments human judgment without weakening accountability or governance. Will AI
The question isn’t whether your organization will be transformed by AI. That ship has sailed.
The question is whether your workforce will become a competitive advantage in an AI-powered economy or whether AI will simply expose capability gaps that already exist. Your AI strategy is only as strong as the people expected to execute it. Most organizations are measuring the wrong thing. They track AI licenses, adoption, training completion rates, and prompt engineering workshops. Yet despite billions of dollars invested in AI, only a small percentage of organizations are realizing meaningful business value. The reason is simple. AI transformation is not primarily a technology problem. It is a workforce capability problem. The question leaders should be asking is not whether employees can use AI. It is whether they can make better decisions because of it. Do your people actually know how to work in an AI-powered world? Not “have they attended a webinar” or “did we roll out Copilot.” I mean: do they fundamentally understand how to think alongside AI, direct it, interrogate its outputs, and apply judgment where the machine falls short? That’s a very different bar — and most organizations have no honest answer. Executive Takeaways The Numbers Are Damning The data is in, and it’s unambiguous. According to IDC, 94% of CEOs and CHROs identify AI as their top in-demand skill for 2025, yet only 35% of leaders feel they’ve actually prepared their employees for AI-driven roles. Meanwhile, a 2026 DataCamp/YouGov survey of 500+ enterprise leaders found that 59% admit their organization has an AI skills gap, even though most are already spending on AI tools. Think about that: majority investment, minority readiness. PwC’s 2025 AI Jobs Barometer adds another dimension: AI-exposed roles are evolving 66% faster than other positions and command a 56% wage premium. That means the gap isn’t just an operational inconvenience — it’s a competitive liability that compounds every quarter you don’t address it. We’ve Been Asking the Wrong Question Most workforce AI assessments are built around the wrong mental model. They ask: “Can this person use the AI tool?” That’s like evaluating a surgeon by whether they can hold a scalpel. The right question is: “Can this person make better decisions because of AI?” Working effectively in an AI world requires a fundamentally different skill architecture than what most job descriptions, competency models, and performance reviews are built to measure. It’s not about prompt engineering. It’s about something deeper. The World Economic Forum’s Future of Jobs Report puts it plainly: employers anticipate that 40% of core skills will change by 2030. Not augmented — changed. That’s not a training program. That’s a reinvention of what “qualified” means. What “AI-Ready” Actually Looks Like After 35 years leading technology transformation across global retailers, manufacturers, and PE-backed companies, I’ve seen many skill paradigm shifts. This one is different in a critical way, it cuts across every function, every level, and every geography simultaneously. True AI readiness requires capabilities across three dimensions, yet most organizations focus exclusively on the first. The Lumerai AI Readiness Model Level 1: Tool Fluency Can employees effectively use AI tools? Level 2: Critical Reasoning Can they challenge and validate AI outputs? Level 3: Human Edge Can they apply uniquely human judgment, creativity, and leadership? BCG research found that companies successfully addressing AI talent shortfalls achieve 2.3x faster AI adoption and 67% higher AI ROI. The skill assessment isn’t a HR box to check, it’s a value creation lever. Warning Signs Your Workforce Isn’t AI Ready Why Most Assessments Miss the Mark Here’s the uncomfortable truth, most organizations are confusing activity with capability. Deploying Copilot is not an AI strategy. Sending people to a LinkedIn Learning course is not workforce transformation. And asking employees to self-report AI comfort level is not an assessment. The DataCamp report reveals the paradox in stark terms, most enterprises are offering some form of AI training, yet only 35% have a mature, workforce-wide upskilling program. The organizations with that mature program are nearly twice as likely to report significant AI ROI. The rest are spending money and just making noise. Effective assessment requires measuring against a defined target, not a generic “AI skills” list, but a role-specific, business-context-specific model of what AI-assisted performance actually looks like in your environment. A Framework Worth Building If you’re serious about knowing where your workforce stands, here’s where to start: Map your role exposure: Not every role is equally disrupted or equally enabled by AI. Start with a realistic heat map of AI exposure across your organization — which roles are most automatable, which are most augmentable, and which create the highest risk if AI is used without adequate oversight. Define role-specific AI competency profiles: A CFO who needs to interrogate AI-generated financial models requires a different skill profile than an operations manager using AI for demand forecasting. Generic frameworks produce generic results. Assess with scenarios, not surveys: Self-assessment is unreliable for novel skill domains. Scenario-based evaluations present a realistic AI-assisted decision situation worth observing. Close the loop with your technology roadmap: Your AI skills strategy needs to anticipate where your tools are heading, not just where they are today. Agentic AI is arriving faster than most teams realize. If your workforce isn’t prepared to work alongside autonomous AI agents, you’ll be wasting time and money rebuilding capability. The Leaders Who Act Now Will Define the Gap McKinsey estimates that 88% of organizations now use AI in at least one business function. Only 1% have achieved true AI maturity. The distance between those two numbers is, in large part, a human capability problem. The CEOs and CIOs who understand that AI tools without AI-ready people produce expensive mediocrity will act differently in 2026. They’ll treat workforce AI assessment not as a one-time initiative, but as an ongoing strategic process as embedded in their operating rhythm as financial reviews and technology audits. The question isn’t whether your organization will be transformed by AI. That ship has sailed. The question is whether your workforce will become a competitive advantage in an AI-powered economy or whether AI will
The Tech Leaders First 100 Days
The first 100 days of a new IT leadership role are a critical window. This playbook breaks down how to assess your team, identify the right opportunities, review the portfolio, and build a strategy that earns trust and sets the stage for lasting impact. You have been handed the keys. New title, new organization, new expectations, and a clock already running. Whether you are stepping into a CIO role for the first time or taking the helm of a technology function at a company you are still learning, the first 100 days are crucial. Those first 100 days are all about learning what the organization needs most, and positioning yourself and your team to deliver it. This is not a sprint, it is a structured reconnaissance. The leaders who move fastest in their first months are often the ones who stumble hardest by month six. The ones who invest early in listening, assessing, and aligning, deliberately and without ego, are the ones who build the foundation for durable change. The first 100 days are not about what you know. They are about learning what the organization most needs, and earning the right to change it. Executive Takeaways The Lumerai CIO First 100 Days Framework Phase Focus Objective Days 1-30 Listen & Learn Understand the organization before making changes Days 31-60 Assess & Prioritize Evaluate team, portfolio, and opportunities Days 61-90 Align & Act Build stakeholder alignment and begin execution Days 91-100 Commit & Communicate Finalize roadmap and establish accountability The most successful CIOs resist the urge to prove themselves immediately. Instead, they follow a structured progression from understanding to assessment, alignment, and execution. Section 1: Assessing Team Maturity Your team is your first and most important operating context. The tech team’s maturity is critical and that team must provide near flawless execution before you have earned the right to drive the organization where it needs to go. Now is the time to engage them and fairly assess the current maturity and the path to improve. You need an honest picture of where it actually stands, not where it thinks it stands, and not where your predecessor reported it to be. The Lumerai Team Maturity Model Team maturity is not simply a question of technical skill. It encompasses four overlapping dimensions: A technically brilliant team that cannot align to business priorities is just as limiting as a business-savvy team that cannot execute. The most capable IT organizations are both. Team maturity is a stronger predictor of transformation success than technical capability alone. How to Conduct the Assessment Resist the temptation to deploy a formal survey. The data gathered through direct conversation in the first 30 days is richer and more revealing than any survey. Structure your early 1:1s around a consistent set of open questions: Suggested Questions for Early 1:1s: Listen for patterns across these conversations. Recurring themes about process gaps, leadership behaviors, budget constraints, or talent deficits are more diagnostic than any individual answer. Maturity Levels: A Practical Framework Once you have completed your listening tour, work with your direct reports to score the organization across the maturity levels. The goal is not to render a verdict, it is to create a shared baseline that informs your strategy. Your first 100 days should give you enough data to know where you are and your first year’s strategy should have a clear line of sight to where you are going. Section 2: Identifying Strategic Needs and Opportunities Every new leader’s arrival creates an inflection point where people are more open to change. Your job in the first 100 days is to identify the best opportunities before the window closes and the organization settles back into its existing patterns. Quick Wins versus Long-Term Plays Not all opportunities are created equal. One of the most common mistakes new IT leaders make is chasing a large, visible transformation initiative in their first months before they have earned the trust or gathered the context to sustain it. A far more durable approach is to sequence deliberately: Where to Look for Opportunities The highest-value opportunities tend to cluster in a small number of recurring patterns: The highest-leverage opportunities are rarely technical. They are cultural, the invisible friction that slows decisions, creates rework, and keeps good people from doing their best work. Section 3: Navigating Your Own Assimilation The most overlooked dimension of a new leader’s first 100 days is internal. How you show up, how quickly you build trust, and how effectively you read the political and cultural landscape of your new organization will determine how much of your actual agenda you get to execute. The Assimilation Traps Experienced leaders fall into predictable patterns when they are new. Recognizing them in advance is the first step to avoiding them: The Four Assimilation Traps to Avoid: With your new team, a facilitated new leadership assimilation exercise can dramatically speed up the “getting to know each other” process. Warning Signs Your First 100 Days Are Going Off Track Building Trust Across Stakeholder Groups Your stakeholder map in the first 100 days should include at least four distinct constituencies, each with different needs, different definitions of success, and different levels of trust to build: The Working and Listening Tour In your first 30 days, conduct a structured listening tour across the organization. This is not a performance review of the IT function, it is your chance to understand the business through the eyes of the people it serves. Walk the walk and learn how the business operates and how technology either supports or hinders those processes. Work in a plant, warehouse, store of function to learn the end to end of the business. What you will learn will shape every strategic decision you make in the coming months. Section 4: Conducting a budget and ecosystem review A portfolio review is one of the most important and most frequently skipped activities in a new leader’s first 100 days. It is the process of systematically inventorying and evaluating every active