What a Fractional IT Director Does in the First 30 Days

One of the most common questions from organizations considering fractional IT leadership is what the engagement actually looks like in practice. What does someone do when they show up part-time to lead a function they don't yet know?

The first thirty days are mostly about understanding what's there before changing anything. That sounds obvious, but it's worth being specific about, because the organizations that get the most from fractional IT leadership understand what to expect and what not to expect in the early weeks.

Week One: Understanding the Environment

The first week is inventory and orientation. Not just technology inventory -- everything that touches the IT function.

What systems are running and where? What vendors are under contract, and what are the terms? Who are the internal IT staff or managed service providers, and what do they actually do day to day? What are the open issues, the active projects, and the things that have been deferred?

The goal by the end of week one is a clear picture of what exists. Not an assessment of whether it's good -- just what's there. In organizations that have been running informal IT for a while, this inventory surfaces things that surprised even the organization. Software that nobody knew was still running. Contracts that have been auto-renewing for years. Vendors who haven't been actively managed in a long time.

Week Two: Understanding the Business

IT leadership that doesn't understand the business it supports makes the wrong decisions. Week two is about understanding how the organization works, what its priorities are, and where IT is currently creating friction.

This means talking to people who aren't in IT. Operations leadership, clinical or service line leadership, finance, whoever is experiencing IT problems or depending on IT to work well. Their perspective on where IT is falling short is usually different from the IT team's perspective, and both are useful.

It also means understanding the organization's direction: growth plans, upcoming changes, strategic priorities. IT decisions made without that context tend to optimize for the current state rather than the state the organization is moving toward.

Week Three: Triage and Quick Wins

By week three there's enough information to prioritize. Not everything -- a prioritized list of the issues that are most urgent, most impactful, or easiest to address without disrupting other things.

Quick wins matter disproportionately in a new engagement. They build credibility with the team and with executive leadership. They demonstrate that the engagement is producing results, not just producing analysis. And they're usually available -- most organizations that haven't had senior IT leadership have obvious problems that haven't been addressed simply because nobody with the authority or expertise to address them was paying attention.

Typical week-three quick wins: a vendor contract that can be renegotiated before an upcoming renewal, a recurring incident with an obvious fix that's been accepted as normal, a process change that makes something meaningfully faster or more reliable.

Week Four: First Reporting and Forward Plan

By the end of the first month, executive leadership should have a clear picture of where IT stands. Not a status report -- a real assessment: what's working, what isn't, what the highest-priority issues are, and what the plan is to address them.

This report is the foundation for the ongoing engagement. It establishes the baseline that future progress gets measured against. It also surfaces decisions that need to be made at the executive level -- budget questions, vendor decisions, staffing questions -- so that leadership can make those decisions with real information.

The forward plan that comes out of this month is usually a mix of near-term fixes, medium-term projects, and strategic questions that need more time to answer. That's normal. The first thirty days produce clarity, not completion.

What Not to Expect

It's worth being direct about what the first thirty days don't produce. They don't produce a fully transformed IT function. They don't produce a complete technology roadmap. They don't resolve every problem that's been building for years.

What they produce is understanding and prioritization. A clear picture of what's there, what matters most, and what order to address things in. That foundation is what makes everything after it faster and more effective.

Organizations that have been without senior IT leadership often have an understandable urgency to see things fixed quickly. That urgency is valid. The first thirty days are designed to channel it productively rather than reactively -- to make sure the things that get fixed first are the ones that most deserve to be fixed first.

After Thirty Days

Month two is when the real work starts. The priorities are set, the relationships are established, the quick wins have demonstrated what's possible. The engagement moves from understanding to execution.

What that looks like depends on what the first thirty days found. Every organization is different. But the pattern of the first month -- inventory, understanding, triage, reporting -- is consistent across engagements because the sequence works.