When IT Management Becomes Executive Work

An IT manager acting as CTO may be keeping your systems running while also being expected to develop technology strategy, manage major investments, oversee suppliers and advise the executive team. What began as a manageable operational role can gradually become two demanding jobs, often without additional time, authority or support.

For a growing business, the challenge is deciding whether your IT manager can reasonably carry these responsibilities. As someone who has progressed from technical roles through IT management to CTO, I believe the answer starts with understanding the work, supporting the person and identifying which leadership responsibilities the business genuinely needs.

Takeaways

  • Growth changes technology responsibilities. An IT manager may inherit executive duties without the role being formally redesigned.
  • Separate capacity from capability. A lack of time requires a different response from a lack of experience.
  • Make accountability clear. The IT manager, senior technology leader and executive team need agreed decision-making responsibilities.
  • Support existing capability first. Mentoring, delegation, specialist advice or independent leadership may be better than replacing a capable manager.
  • Review the arrangement as the business grows. Recurring strategic decisions may justify ongoing Fractional CTO or executive technology support.

Table Of Content

How an IT Manager’s Role Changes With Growth

In a smaller organisation, the IT manager may be responsible for maintaining systems, managing support requests, overseeing infrastructure and coordinating technology suppliers.

Their main responsibility is keeping technology working reliably so employees can do their jobs.

As the business grows, technology becomes more closely connected to commercial decisions.

A manufacturer introduces an enterprise resource planning system. A healthcare provider considers replacing its patient management platform. A retailer invests in eCommerce integration, warehouse automation and customer data.

Each decision affects budgets, employees, customers, suppliers and future operations.

The IT manager naturally becomes involved because they understand the existing systems. Over time, they may find themselves responsible for:

  • Developing technology strategy and investment priorities.
  • Assessing major software and infrastructure proposals.
  • Advising the CEO on technology risks and opportunities.
  • Managing complex projects involving multiple departments.
  • Challenging supplier recommendations and commercial arrangements.
  • Reporting technology performance and risks to executives.
  • Planning technology capabilities needed for future growth.

These responsibilities can be appropriate for an experienced IT manager.

The difficulty arises when they are added to an already demanding operational role without changing its structure or expectations.

More Responsibility Is Not Always a Promotion

Consider an IT manager who has successfully maintained the organisation’s technology for years.

They understand its systems, employees and suppliers. Senior management trusts them, so important technology decisions naturally come their way.

Eventually, they are asked to prepare a three-year technology roadmap while still managing the service desk, handling incidents and resolving daily operational problems.

They may welcome the opportunity to contribute strategically.

But unless something changes, they now have less time for both responsibilities.

The business may have expanded the role without formally recognising it.

This is not automatically a performance problem. It may be an organisational design problem.

IT manager reviewing technology plans while handling daily operational responsibilities
Expanding IT Manager Responsibilities

IT Management and CTO Responsibilities

The difference between an IT manager and a CTO is not simply seniority or technical knowledge.

It is primarily about the nature of the responsibilities.

IT management commonly focuses on operating and improving the technology services the organisation already uses.

Executive technology leadership focuses more heavily on deciding what technology the organisation needs, where to invest, which risks to accept and how technology supports business objectives.

These responsibilities overlap, especially in established businesses without a large technology department.

A CIO may also perform the executive technology role, particularly where technology primarily supports internal operations rather than being part of the product sold to customers.

The titles matter less than establishing clear accountability.

Comparing the Three Levels

The following table distinguishes operational IT management, technology leadership and executive governance.

ResponsibilityOperational IT ManagementTechnology LeadershipExecutive Governance
Daily IT servicesManage service performance, incidents and supportOversee operational capability and prioritiesMonitor material service risks
Technology strategyProvide technical input and operational requirementsDevelop strategic options and a technology roadmapApprove direction and investment priorities
Major investmentsAssess technical requirements and implementationEvaluate options, costs, dependencies and business fitApprove investments within delegated authority
SuppliersManage service delivery and operational relationshipsEvaluate strategic suppliers, performance and dependenciesOversee major commercial commitments
Technology riskIdentify and manage operational risksEvaluate material risks and recommend treatmentSet risk expectations and approve risk acceptance
Technology projectsCoordinate technical work and implementationOversee delivery priorities, dependencies and accountabilityMonitor outcomes and approve material changes
People and capabilityManage staff, skills and daily workloadsDevelop leadership capability and future team structureApprove organisational direction and resources

This is a practical responsibility framework, not a rigid job description.

An experienced IT manager may already be capable of performing several technology leadership functions. A CTO may remain involved in operational decisions, particularly in a smaller technology team.

The important distinction is between doing the work, directing the work and being accountable for the business decisions.

Frameworks such as ISACA’s COBIT recognise the importance of distinguishing technology governance from management.

Your organisation does not need a complicated governance structure to apply that principle. It needs clarity about who recommends, who decides and who is responsible for following through.

Signs Your IT Manager Needs More Support

An expanding role does not automatically create a problem.

The warning signs appear when the responsibilities exceed the time, experience or authority available to manage them effectively.

Strategic Work Is Always Delayed

Your IT manager agrees that the business needs a technology roadmap, but operational problems repeatedly take priority.

There is always another urgent support issue, security update, supplier problem or infrastructure change.

The roadmap remains unfinished, and major technology decisions are made individually without an agreed long-term direction.

The manager may understand the importance of strategy but lack the uninterrupted time required to develop it.

Every Major Decision Reaches the CEO

Your IT manager can explain the technical options but struggles to recommend which best serves the business.

As a result, decisions about systems, architecture, vendors and investment keep returning to the CEO.

The CEO may not have the technical knowledge needed to assess the options confidently.

Neither person is necessarily doing a poor job.

The organisation may be missing the executive technology experience needed to translate technical alternatives into business decisions.

Suppliers Are Setting the Direction

Your organisation may rely on managed service providers, software developers, cloud specialists and technology vendors.

These suppliers can provide valuable expertise.

However, each naturally views your requirements through the services and products they provide.

An IT manager might be capable of managing individual supplier relationships without having the wider experience needed to challenge a major architectural decision, commercial commitment or proposed development investment.

Without independent oversight, supplier recommendations can gradually influence the technology direction of the business.

The concern is not that suppliers are necessarily giving poor advice. It is whether the organisation has someone capable of evaluating that advice against its broader objectives.

Projects Lack Executive Oversight

Your IT manager may be coordinating several technology projects while managing daily operations.

Progress reports might focus on technical activities without providing a clear picture of business outcomes, financial exposure or delivery risks.

When delays occur, the manager must manage the technical response while also explaining consequences to senior management.

This can become especially difficult when projects involve several business departments or external suppliers.

Where the main concern is struggling projects, focused Project Delivery support may be more appropriate than changing the entire technology leadership structure.

Important Risks Are Not Escalated

The IT manager may understand weaknesses in infrastructure, ageing applications, supplier dependencies or recovery arrangements.

However, identifying a technical risk is different from explaining its commercial consequences and obtaining an executive decision.

A business might repeatedly postpone a security investment because the risk has not been clearly connected to potential operational disruption or customer consequences.

The Australian Signals Directorate’s guidance on cyber security roles emphasises clear responsibilities, alignment with business strategy and executive reporting.

This reinforces an important point: executives retain responsibility for appropriate governance even when technical work is delegated to an IT manager.

The Manager Becomes a Bottleneck

When every incident, supplier question, project decision and executive request reaches one person, work starts to slow down.

Employees wait for approvals. Suppliers wait for instructions. Strategic initiatives compete with urgent operational tasks.

The manager may respond by working longer hours or becoming involved in even more detail.

That can temporarily keep things moving, but it does not solve the underlying dependency.

If your business cannot operate effectively when its IT manager takes leave, responsibilities and delegation deserve attention.

Is It a Capacity or Capability Problem?

Before deciding how to address the situation, distinguish between capacity and capability.

They can produce similar symptoms but require different responses.

A capacity problem occurs when someone has the skills and experience to perform the work but insufficient time, resources or management support.

A capability problem occurs when the responsibilities require knowledge, experience or judgement that the person has not yet developed.

A third issue is authority. Someone may have the ability and time to make a decision but lack the formal responsibility or organisational support to do so.

How to Identify the Difference

SituationLikely underlying issuePotential response
Strategic work is repeatedly interrupted by operational incidentsCapacityDelegate operational work or provide additional resources
The manager struggles to evaluate major technology investment optionsCapabilityMentoring, specialist advice or senior technology leadership support
Suppliers seek executive approval for routine decisionsAuthorityClarify decision rights and approval limits
The manager understands the strategy but cannot deliver it alongside daily responsibilitiesCapacity and structureReallocate responsibilities and review the team structure
Important technology risks are identified but not explained to executivesCapability or communicationImprove reporting, coaching and executive engagement
The CEO expects outcomes the manager cannot approve or resourceAuthority and governanceClarify executive accountability and agreed priorities

The assessment should involve the IT manager directly.

Ask what consumes their time, which responsibilities they find difficult, where they need support and what decisions they believe should sit elsewhere.

You may discover that the manager is frustrated by the same issues as the leadership team.

Why the Distinction Matters

Imagine an IT manager who has strong technical judgement and understands the organisation’s commercial priorities.

They are perfectly capable of preparing a technology roadmap, but operational support takes up most of their working week.

Sending them on another leadership course will not create the time needed to complete the work.

The better response may be to delegate support responsibilities or strengthen the operational team.

Now consider a manager who has plenty of time but little experience evaluating a multimillion-dollar software programme involving several suppliers.

Giving them additional time will not automatically provide the commercial and executive experience required.

They may benefit from mentoring, independent advice or a senior technology leader working alongside them.

The right intervention depends on what is missing, not simply what is going wrong.

Why Leadership Expectations Need to Change

As a business grows, expectations often change faster than reporting structures and job descriptions.

An IT manager who was originally responsible for keeping systems operational may suddenly be expected to contribute to the executive team’s commercial decisions.

That transition requires more than technical expertise.

Operational Success Is Different

Operational IT management often rewards responsiveness, reliability and technical problem-solving.

Success may mean resolving incidents quickly, maintaining availability, supporting employees and managing suppliers effectively.

Strategic technology leadership requires a different balance.

The leader must consider future business requirements, investment trade-offs, organisational capability and the consequences of decisions that may affect the company for years.

Sometimes the right strategic decision involves accepting a short-term operational inconvenience to achieve a more important long-term outcome.

That is not always an easy transition for someone whose career has rewarded resolving today’s problems.

Executive Communication Matters

A technology manager may be comfortable explaining technical risks to developers, engineers and suppliers.

A CEO needs a different conversation.

For example, an IT manager might report that an application uses an unsupported database version.

The executive team needs to know what that means for business continuity, the likely consequences of leaving it unchanged, the available options and the investment decision required.

The technical explanation still matters, but the business decision must be clear.

Good communication is not about simplifying everything. It is about giving decision-makers the information they need.

People Leadership Becomes More Important

As responsibilities expand, the manager may need to spend less time personally resolving technical problems and more time developing others.

This can be challenging for highly capable technical people.

They may have built their careers by being the person who knows how to fix difficult issues.

But leadership means creating a team that can operate without depending on one person’s knowledge or constant intervention.

My guiding principle is people before technology.

If someone is becoming the organisation’s senior technology leader, they need the opportunity to develop people, delegate effectively and create the conditions for good decisions.

That requires support from the business as well as effort from the individual.

IT manager discussing technology strategy and investment priorities with an executive
IT Manager Developing Strategic Leadership

Who Should Own Technology Decisions?

Giving an IT manager more responsibility without matching authority creates confusion.

They may be expected to deliver results while lacking control over budgets, project priorities or supplier decisions.

Before changing the leadership structure, I would establish which decisions should be made by the IT manager, which require experienced technology leadership and which belong to the CEO or board.

Define Decision Rights

A practical starting point is to agree who has authority to:

  • Approve routine technology expenditure.
  • Recommend major technology investments.
  • Select and manage technology suppliers.
  • Approve changes to project scope and delivery priorities.
  • Accept material technology and security risks.
  • Set technology strategy and investment priorities.
  • Escalate issues that affect business objectives.

For each decision, identify who recommends the action, who approves it and who is responsible for implementation.

The distinction matters.

Your IT manager may recommend replacing an ageing business application, but the investment decision may belong to the CEO or board.

Similarly, the manager may identify a cybersecurity risk and recommend treatment, but the organisation’s authorised leadership must decide how that risk is addressed or accepted.

Improve Executive Reporting

A concise technology report can help make accountability visible.

I would begin with five questions:

  1. Which technology priorities are progressing?
  2. Which projects or services need attention?
  3. What significant risks are unresolved?
  4. How is technology expenditure tracking?
  5. Which decisions require executive approval?

The report should be understandable without requiring the CEO to interpret technical language.

It does not need to become another complicated management exercise. Its purpose is to support timely decisions and clear accountability.

Five Ways to Support Your IT Manager

When the existing manager is capable and trusted, replacing them should not be the first option.

There are several practical ways to strengthen technology leadership without unnecessarily disrupting the organisation.

1. Develop the Existing Manager

If the IT manager has the interest and potential to grow into a more strategic role, provide a clear development path.

That might include mentoring, executive meeting participation, training, responsibility for selected investment decisions and structured feedback.

Start with areas where the manager already demonstrates sound judgement.

Give them meaningful opportunities to lead while maintaining appropriate oversight.

Development takes time, and not everyone wants an executive technology career. That preference should be respected.

Some excellent IT managers prefer operational leadership. The business still needs their expertise.

2. Strengthen Operational Support

If capacity is the main problem, redistribute some daily responsibilities.

This might involve developing a senior technician, appointing a service delivery lead, changing the distribution of support work or using an external provider for clearly defined operational services.

The objective is to create enough space for the manager to focus on higher-value responsibilities.

However, outsourcing operational activities does not automatically resolve leadership gaps.

Someone still needs to manage the provider, evaluate performance and maintain accountability.

3. Add Specialist Expertise

Some decisions need expertise that the organisation does not require every day.

For example, a major cloud migration, cybersecurity assessment or complex software architecture decision may justify engaging a specialist.

This approach works when the need is clearly defined and the IT manager can retain ownership of implementation and operational consequences.

The limitation is that specialist advice may address an individual question without solving broader leadership and governance problems.

4. Introduce Technology Leadership Support

Where the business has an ongoing gap in strategic judgement, governance or executive communication, independent Technology Leadership support can work alongside the existing manager.

This can include helping clarify responsibilities, improving technology reporting, providing leadership coaching, evaluating supplier decisions and strengthening accountability.

The aim is to improve the effectiveness of the existing team.

I see value in working with an IT manager rather than positioning independent advice as a judgement on their competence.

A manager who has access to experienced support can develop new skills while continuing to contribute their valuable knowledge of the organisation.

5. Add an Ongoing Fractional CTO

Sometimes the business needs someone to take continuing responsibility for CTO-level leadership functions.

There may be multiple projects, important investment decisions, significant supplier dependencies or technology risks requiring regular executive oversight.

An ongoing Fractional CTO can provide senior leadership without creating a permanent full-time executive role.

The existing IT manager can remain responsible for operational delivery, technical teams and systems.

The Fractional CTO can focus on agreed executive responsibilities, technology strategy, governance, investment decisions, supplier oversight and leadership development.

The exact division of responsibilities must be agreed.

Without clear boundaries, introducing another leader can create confusion rather than solve it.

Comparing the Options

OptionBest suited toMain consideration
Develop the IT managerStrong potential with identifiable experience gapsRequires time and meaningful opportunities
Strengthen operational supportCapable manager overloaded by daily responsibilitiesMust preserve clear operational ownership
Engage specialistsDefined technical decisions requiring particular expertiseDoes not necessarily provide continuing leadership
Technology Leadership consultingGaps in governance, communication, structure or leadership capabilityScope and decision rights must be clear
Ongoing Fractional CTORecurring need for senior strategy, governance and executive oversightRequires an agreed leadership relationship

There is no universal best choice.

The business should choose the smallest effective change that addresses the actual problem while supporting its longer-term needs.

A 90-Day Leadership Improvement Plan

Before making major structural changes, I would consider a 90-day improvement plan focused on expectations, responsibilities and practical progress.

The following is an illustrative approach. It can be adjusted for the size of the organisation and the complexity of its technology environment.

Days 1 to 30: Assess the Responsibilities

Begin with a discussion between the CEO and IT manager.

Review the current role, competing priorities, operational workload and strategic responsibilities.

Identify the decisions that have become difficult, projects that are not progressing and risks that are not receiving sufficient attention.

Agree on the most important business outcomes technology needs to support over the next 12 months.

By the end of the first month, aim to have:

  • A clearer description of the manager’s responsibilities.
  • An initial view of capacity and capability gaps.
  • A list of important technology decisions requiring leadership attention.
  • Agreed executive responsibilities and escalation arrangements.

Do not try to redesign the entire technology organisation immediately.

Focus on understanding the constraints.

Days 31 to 60: Make Targeted Changes

Use the assessment to address the most pressing issues.

If operational workload prevents strategic progress, delegate selected tasks or provide additional support.

If investment decisions are unclear, introduce a practical approval process.

If executive communication needs improvement, establish a regular technology leadership meeting with a short report covering priorities, costs, delivery and risks.

Where specialist judgement is missing, arrange appropriate mentoring or independent advice.

The objective is to create a more effective operating arrangement rather than simply adding meetings and documentation.

Days 61 to 90: Review the Results

Assess whether the changes have made a meaningful difference.

Can the IT manager now dedicate time to strategic responsibilities?

Are technology decisions progressing with clearer ownership?

Does the CEO have a better understanding of costs, risks and investment priorities?

Are suppliers receiving more consistent direction?

Has the manager gained confidence and capability in areas that previously caused difficulty?

Look for observable improvements, not just additional activity.

If the manager is progressing well and the arrangement appears sustainable, continue developing the internal capability.

If major leadership gaps remain, consider whether ongoing independent support or a different structure is required.

The outcome of the 90-day process should be a better-informed decision about the organisation’s technology leadership, not a predetermined recommendation to hire another executive.

IT manager and executives reviewing a 90-day technology leadership improvement plan
Technology Leadership Improvement Planning

When Do You Need Ongoing Leadership?

A short improvement programme can solve some organisational problems.

Others require continuing executive involvement.

If the business regularly makes substantial technology investments, manages complex suppliers or depends on several technology teams, senior leadership needs may not disappear after the initial changes.

Ongoing support becomes more relevant when the business requires regular decisions about:

  • Technology priorities and investment.
  • Major software development or systems projects.
  • Supplier performance and commercial commitments.
  • Cybersecurity and operational risk.
  • Technology architecture and future capacity.
  • Team leadership and organisational capability.

A capable IT manager may be able to contribute strongly to all these areas while still benefiting from experienced executive guidance.

The question is whether the responsibilities are substantial and frequent enough to require continuing leadership.

Consider the Total Cost of the Arrangement

Hiring a full-time CTO is not simply a salary decision.

The organisation also needs to consider recruitment, onboarding, executive responsibilities, supporting resources and whether there is sufficient ongoing work to justify the role.

On the other hand, leaving the strategic responsibilities with an already overloaded IT manager has a cost too.

Delayed decisions, weak supplier oversight, unclear project priorities and unmanaged dependencies can consume resources without appearing as a separate line in the technology budget.

White Internet Consulting offers ongoing executive support through three engagement models:

EngagementMonthly price
Advisory$7,500
Governance$10,500
Embedded$14,500

These provide different levels of continuing executive involvement, depending on the organisation’s requirements and existing leadership capability.

For a business with a competent IT manager, an Advisory or Governance arrangement may be worth considering where independent strategic judgement or ongoing oversight is needed.

An Embedded arrangement may be more appropriate when executive technology responsibilities require closer involvement with the management team, projects and suppliers.

The decision should follow an assessment of the responsibilities involved.

There is little benefit in creating another leadership role if the real problem is that your IT manager needs an additional technician or clearer approval authority.

Frequently Asked Questions

Can an IT Manager Act as a CTO?

Yes. An experienced IT manager may be capable of performing CTO responsibilities, particularly in a smaller organisation. The important questions are whether they have sufficient capability, capacity, authority and support to perform both operational and executive duties effectively.

When Has an IT Manager Outgrown Their Role?

An IT manager may have outgrown the original role when strategic decisions, executive reporting, major investments and supplier oversight become regular responsibilities. This may indicate that the role needs to evolve, rather than that the manager is underperforming.

Should We Promote Our IT Manager to CTO?

A promotion may be appropriate if the manager demonstrates the required leadership capability and wants the responsibility. Before changing the title, clarify the role, business expectations, decision-making authority and operational responsibilities that may need to be delegated.

Can a Fractional CTO Support Our IT Manager?

Yes. A Fractional CTO can work alongside an existing IT manager, providing senior technology strategy, governance, mentoring and executive oversight. Clear responsibilities and reporting arrangements help the relationship support the internal team rather than create competing authority.

How Do We Assess the Leadership Gap?

Review the manager’s workload, responsibilities, experience, decision-making authority and the technology decisions facing the business. A structured assessment can help distinguish capacity constraints, capability gaps and weaknesses in organisational governance.

Conclusion: Support the People You Have

An IT manager taking on CTO responsibilities may be a sign that your business has grown beyond its original technology leadership structure, not that your manager is failing. Before introducing another executive role, identify the responsibilities, assess the gaps and consider how to strengthen the existing team. If you would like an independent perspective, book a free consultation to discuss the leadership support your business needs. The goal is to create a sustainable arrangement when your IT manager is acting as CTO, with clearer decisions, stronger capability and better support for the people responsible for delivering results.

Share This Post

Need stronger technology leadership?

Good technology leadership gives your business clearer direction, stronger accountability and better decisions.

If your technology team lacks direction, leadership responsibilities are unclear, or you need experienced support strengthening how technology is led, take a look at my Technology Leadership service or Contact Us to start the conversation.

Iain White Technology Leadership Adviser

Strong technology leadership is about more than technical knowledge. It means setting clear direction, making sound decisions and helping people do their best work. 

Iain White has spent decades leading technology teams, supporting technology leaders and helping businesses improve how technology is managed.

He works with founders, executives, CTOs and technology managers to clarify responsibilities, strengthen decision-making and improve accountability across technology teams.

His experience spans technology strategy, software delivery, governance, cybersecurity and risk, giving him a broad view of the challenges technology leaders face.

Through White Internet Consulting, Iain helps organisations build stronger technology leadership so their teams have the clarity, support and direction they need to deliver.