How to Build a High-Performance IT Culture: The New CIO's Most Important — and Most Overlooked — Job
You can hire the right people, define the right processes, and build the right strategy. If the culture does not change, IT will still fail. After 30+ years leading IT organizations, this is the pattern I see consistently — and the approach that actually fixes it.
The Problem Nobody Prepares New CIOs For
A new CIO steps into a struggling IT organization. The expectations are clear: turn it around. Fix the delivery problems. Rebuild trust with the business. Get IT performing like it should.
They do the right things. They conduct a thorough assessment of the people and their skills. They identify the process gaps and define new governance structures. They build a technology roadmap aligned to the business strategy. They bring in strong people for the key roles.
Six months later, the CEO is still asking: "Why are we not making progress?"
The CIO — who has done everything right on paper — is watching their reputation erode in real time. Projects are still late. Commitments are still missed. The business still does not trust IT. And despite all the structural changes, the organization feels fundamentally the same.
The missing variable is almost always culture.
Culture is the operating system that runs underneath every strategy, process, and org structure. And in IT organizations that have operated without accountability for years, it is the most powerful — and most resistant — force in the building.
What a Low-Accountability IT Culture Looks Like From the Inside
The symptoms are consistent across industries and organization sizes. In IT departments where accountability has never been established — or has been systematically avoided — the culture develops a set of deeply embedded behaviors that resist structural fixes.
The team is not lazy. They are not incompetent. They are operating exactly as the culture has trained them to operate. They have learned that due dates are approximate. That "almost done" is an acceptable status indefinitely. That problems surface when they become crises, not when they first appear. That meetings end without clear owners or follow-through. And that nobody will be held accountable for any of it in any meaningful way.
Diagnostic signals of a low-accountability IT culture:
Deliverables are consistently 'almost done' — for weeks
Due dates are treated as suggestions rather than commitments
Problems are reported when they become crises, not when they first appear
Meetings end without clear owners, actions, or dates
IT defines success as 'we delivered the code' rather than 'the business outcome was achieved'
High performers are quietly demoralized or actively leaving
Business stakeholders have stopped expecting IT to deliver on time
The IT team spends more energy explaining why things are late than preventing lateness
Nobody can define what 'done' means for a given deliverable
Accountability conversations are avoided because they feel 'personal'
Meanwhile, the CIO is absorbing the organizational failure. The CEO does not see the team's behavior — they see the CIO's results. And when results don't come, the CIO's credibility takes the hit. This dynamic plays out in organization after organization: a capable executive failing not because of their strategy, but because the culture they inherited had more momentum than the strategy they introduced.
6 Mistakes New CIOs Make That Let Culture Win
1. Announcing the strategy before diagnosing the culture
New CIOs are under pressure to show vision quickly. They produce roadmaps, reorganize teams, and launch initiatives within weeks of arriving. But without understanding the cultural environment first — how decisions actually get made, what accountability actually looks like, where the resistance lives — even a technically sound strategy will stall. The org chart changed. The culture did not.
2. Confusing activity with execution
IT organizations that have never been held accountable for outcomes become expert at looking busy. Meetings are full. Status reports are detailed. Everyone is working hard. But nothing ships. The new CIO sees the activity and mistakes it for progress. Weeks pass. Milestones are missed. By the time the CEO asks why nothing has moved, the CIO's credibility is already damaged.
3. Not defining 'Done Done' on day one
'Done' in a low-accountability IT organization means something different than 'done' in a high-performance one. In the low-accountability version, done means 'I finished my part.' In the high-performance version — 'Done Done' — it means tested, documented, deployed, confirmed working, and handed off with the next person equipped to use it. Until this definition is explicit, universal, and enforced, the organization will continue to produce work that is technically complete and operationally useless.
4. Tolerating missed commitments without consequence
The first time a deadline is missed and nothing happens — no conversation, no root cause review, no acknowledgment that a commitment was broken — the culture receives a signal: commitments are not real here. This signal is received loudly and remembered long. Every subsequent missed deadline is easier to rationalize because the precedent was set. New CIOs often tolerate early misses out of graciousness. The culture interprets it as permission.
5. Underestimating how long culture change takes
A culture of low accountability and poor execution took years to build. It will not change in 90 days. CIOs who expect rapid cultural transformation become frustrated, take shortcuts, or abandon the effort when initial resistance is high. The ones who succeed treat culture change as a multi-year program — with clear milestones, consistent reinforcement, and the patience to let new behaviors compound.
6. Fixing processes without fixing mindset
New governance frameworks, project intake processes, and delivery methodologies are only as effective as the mindset of the people executing them. An IT team with a low-accountability mindset will find ways to game a new process just as efficiently as they gamed the old one. Process changes must be accompanied by explicit culture work — or they are theater.
The Right Approach: People, Process, Technology — and Culture
The framework most CIOs use to assess a new IT organization covers three dimensions: people, process, and technology. It is the right framework — as far as it goes. But culture is the fourth dimension, and it is the one that determines whether the other three actually work.
People
Skills assessment, role alignment, talent gaps, leadership capability, key-person dependencies. Who are the stars? Who is misaligned? Who needs to grow and who needs to go?
Process
Governance, project intake, delivery methodology, change control, vendor management. What processes exist? Which ones are followed? Where does execution break down?
Technology
Application portfolio, technical debt, infrastructure modernization, security posture. What does the technology estate enable? What does it constrain?
Culture
Accountability norms, execution standards, communication behaviors, relationship with the business. How does this organization actually operate — not on paper, but in practice?
Culture cannot be fixed by changing the org chart, deploying a new project management tool, or writing a new governance policy. It is changed by leadership behavior, accountability structures, and the consistent, visible enforcement of a new standard over time. This requires a deliberate program — not a memo.
The 6-Step Approach to Building a High-Performance IT Culture
This is the approach I have used and refined over 30+ years of leading IT organizations — and the framework I bring to every engagement where culture is the root cause of IT underperformance.
Weeks 1–4: Diagnose Before You Prescribe
Understand the Culture You Are Actually In
Before announcing anything, observe. Sit in status meetings and watch what happens when something is late — is there a direct conversation, or is it absorbed without comment? Review recent project history — not the official status, but the actual timeline of missed commitments. Interview team members individually. Ask them what gets in the way of getting things done. Ask what happens when someone misses a deadline. The answers will tell you more about the culture than any org chart or process document.
Key Actions:
- ▸
Shadow two to three team leads for a week — observe how they run their teams
- ▸
Review the last six months of project status reports — find the pattern in the misses
- ▸
Conduct one-on-ones with every IT leader — ask what they need to be more effective
- ▸
Interview three to five business stakeholders — ask what IT does well and what it doesn't
Weeks 4–6: Define the New Standard
Make the New Expectations Explicit and Non-Negotiable
Culture change begins with a clear statement of what the new standard looks like — not in a memo, but in person, directly, with enough specificity that nobody can claim they didn't understand. Host an IT all-hands — a town hall — within the first 60 days. Share what you found in your assessment honestly. Describe the gap between where IT is and where it needs to be. Define the new expectations with concrete, specific language.
Key Actions:
- ▸
Host an IT town hall — present current state honestly, describe the future state specifically
- ▸
Define 'Done Done' in writing — post it, reference it in every project meeting
- ▸
Establish a commitment framework: every deliverable gets an owner, a date, and a definition of done
- ▸
Announce that performance evaluations will assess execution and accountability — not just effort
Months 2–3: Establish Accountability Structures
Build the Mechanisms That Make Accountability Real
Accountability is not a value — it is a system. The new culture requires structures that make commitments visible, misses impossible to ignore, and consequences consistent. This does not mean punishing people. It means making execution the default expectation — and making the conversation about a missed commitment as normal and professional as any other business conversation.
Key Actions:
- ▸
Implement weekly delivery reviews — every commitment from last week reviewed, every miss discussed
- ▸
Create a visible project dashboard accessible to the CEO and executive team
- ▸
Establish a root cause process: every missed deadline gets a written root cause, not an explanation
- ▸
Tie the first quarterly performance reviews to the new execution standard
Months 3–6: Win Early and Make It Visible
Create Proof That the New Culture Delivers
Culture change requires evidence. The IT team needs to see that operating by the new standard produces better outcomes — for the business and for them personally. Pick two or three high-visibility initiatives and drive them to 'Done Done' with relentless focus. Celebrate the delivery publicly. Connect the outcome to the cultural change explicitly: this is what execution looks like. This is what we can accomplish when we hold the line.
Key Actions:
- ▸
Identify two to three quick wins — initiatives that can be completed in 60 to 90 days
- ▸
Assign your best people and give them everything they need to succeed
- ▸
Communicate progress weekly to the CEO and executive team
- ▸
When the wins land, celebrate them publicly and explicitly connect them to the new culture
Months 6–12: Reinforce, Recognize, and Remove Obstacles
Sustain the Culture Through Consistent Leadership
The culture will be tested. There will be a project under pressure where it is tempting to cut corners, skip the root cause review, or excuse a missed commitment because the context was complicated. These moments define whether the culture is real or performative. Every time the CIO holds the line under pressure, the culture becomes stronger. Every time the CIO makes an exception, it weakens.
Key Actions:
- ▸
Recognize high performers publicly — name the behaviors you want to see more of
- ▸
Address chronic underperformance directly and formally through the performance review process
- ▸
Run a 6-month culture retrospective — what has changed, what has not, what is the next frontier
- ▸
Revisit the IT town hall format quarterly — keep the communication direct and honest
Ongoing: Performance Management as Culture
Performance Reviews Must Reflect the New Standard
Nothing signals what an organization truly values more clearly than what it rewards and what it tolerates in performance reviews. If the new culture demands accountability, execution, and business orientation — and the performance review still rewards effort, tenure, and technical expertise without measuring delivery — the culture message is contradicted every review cycle. Rebuild the performance framework to measure what actually matters.
Key Actions:
- ▸
Revise performance criteria to include delivery accountability, quality of execution, and business impact
- ▸
Establish measurable performance indicators for every IT role, not just management
- ▸
Use the performance review to have direct conversations about culture fit — not just technical skills
- ▸
Make it clear: high technical skill combined with low execution accountability is not a sustainable combination
The IT Town Hall: Your Most Important First Move
Within the first 60 days, every new CIO leading a cultural transformation should host an IT all-hands meeting. Not to celebrate the team. Not to present a vision deck. To have an honest conversation — in person, with the whole team — about where IT stands, where it needs to go, and what the new expectations are.
This meeting should cover five things:
Current state — honestly
Not brutal, but not sanitized. If IT has a credibility problem with the business, say so. If projects have been consistently late, acknowledge it. The team already knows. What they need to know is that leadership sees it too.
Where we are going — specifically
Not 'we are going to be a world-class IT organization.' Specifically: what outcomes we are committed to delivering in the next 12 months, and why they matter to the business.
What the new expectations look like — concretely
Define Done Done. Define what it means to own a commitment. Define how problems should be communicated. Give people the specific language of the new culture, not just the values.
How people will be evaluated — transparently
Performance reviews will change. Execution, accountability, and business impact will be measured. Make this explicit and early, so nobody can claim they were surprised.
What support is available — generously
Culture change is hard. People need to know you are invested in their success, not just in judging their performance. What training, tools, and leadership support will be available to help them meet the new standard?
Defining "Done Done": The Single Most Impactful Cultural Shift
One of the most damaging cultural patterns in low-accountability IT organizations is an undefined — and therefore inconsistent — definition of done. In these organizations, team members complete their piece of the work and declare it done. The next person in the chain finds it incomplete. Rework happens. Time is lost. Frustration accumulates. And nobody is clearly accountable because everyone did their "part."
"Done Done" is not done until:
The deliverable meets the defined acceptance criteria — not the developer's interpretation of it
It has been tested in an environment that reflects production conditions
Documentation is complete and accessible to the people who need it
The receiving party has confirmed they can use it
Any downstream dependencies have been notified and are unblocked
The outcome — not just the output — has been verified
Post this definition. Reference it in every project meeting. When someone says a task is done, ask which of these criteria have been verified. Within weeks, the team's behavior around completion will shift — because the definition of done is now visible, specific, and shared.
How Full On Consulting Helps
Full On Consulting provides interim CIO services, IT assessments, and transformation program leadership for organizations where IT culture is the root cause of underperformance. We have led this work in organizations across multiple industries — assessing the cultural landscape, establishing the new operating framework, and staying engaged through execution long enough to ensure the change takes root.
Culture change is not a 30-day consulting engagement. It is a sustained leadership program. We bring the experience, the framework, and the willingness to have the hard conversations that make it real.
Interim CIO Services
Step in as IT leader during a transition or transformation — with the mandate and the experience to drive cultural change from the top.
Learn more →IT Health Check
Independent assessment of IT culture, people, process, and technology — with a prioritized roadmap for getting IT to high performance.
Learn more →First 90 Days Playbook
Read our insight on the First 90 Days as CIO — the proven playbook for establishing credibility, diagnosing the organization, and setting the foundation for cultural transformation.
Learn more →Is Your IT Culture the Root Cause?
If your IT organization has the right people, the right processes, and the right strategy — but is still not delivering — the answer is almost certainly culture. And culture does not fix itself. It requires deliberate leadership, consistent accountability, and the willingness to have uncomfortable conversations early enough to matter.
If any of what you have read here sounds familiar, let's have a direct conversation about what is actually driving the underperformance — and what it would take to fix it.
Frequently Asked Questions
How do you change the culture of an IT department?
Changing IT department culture requires five things working simultaneously: a clear and visible statement of new expectations from leadership; accountability structures that make performance measurable and consequential; early wins that demonstrate the new standard is real; consistent modeling of the culture from the top; and time. The most common mistake is announcing a new culture without changing the consequences for operating by the old one. If employees see that missing deadlines, avoiding accountability, and producing low-quality work still has no consequences, the announcement is noise. Culture changes when the consequences change.
What is the biggest mistake new CIOs make in their first 90 days?
The most common mistake new CIOs make is focusing exclusively on technology strategy and organizational structure while underestimating — or ignoring entirely — the cultural work required to execute it. A new CIO can produce a compelling three-year IT roadmap, restructure the org chart, and identify the right enterprise platforms. None of it delivers results if the IT organization does not have the execution culture to follow through. The organizations that get stuck are almost always stuck on culture, not strategy. The second most common mistake is moving too fast — announcing major changes before building the trust and credibility that makes change stick.
What does a high-performance IT culture look like?
A high-performance IT culture is characterized by: clear accountability — every deliverable has an owner and a date, and both are taken seriously; a shared definition of 'done' — the team understands that 'done' means tested, documented, deployed, and confirmed working, not just code-complete; proactive communication — problems are surfaced early, not hidden until they become crises; business orientation — IT team members understand the business impact of their work, not just its technical specifications; and continuous improvement — the team consistently examines what went wrong and why, and applies those lessons to the next initiative.
How long does it take to change IT culture?
Meaningful IT culture change — moving from a culture of low accountability and reactive execution to a high-performance delivery culture — typically takes 12 to 18 months of consistent, deliberate leadership. The first 90 days establish the foundation: assessment, expectation-setting, and early accountability. Months 3 through 6 test whether the new standards are real or performative. Months 6 through 12 are where the culture either takes root or reverts. The single most important factor is consistency — the CIO must model the culture they are building, hold the line on expectations in every interaction, and never excuse the old behavior in exchange for short-term convenience.
How do you hold IT teams accountable without destroying morale?
Accountability and morale are not opposites — in fact, a culture of low accountability is usually a culture of low morale, because high performers are demoralized by carrying the weight of colleagues who are not held to the same standard. The key is to make accountability structural rather than personal: define what done looks like, make commitments explicit and visible, and address misses through process improvement conversations before they become performance conversations. When accountability is consistent, transparent, and applied equally, most employees respond positively — because they finally understand what is expected of them and have a clear path to be recognized for delivering it.