One Job That Became Everything

You hired Wendy because she was exceptional, and not only as a technologist. Wendy could translate from the language of IT to the language of the organization, programs, donors and social impact. She spoke easily to the board and to the program staff about why the technology mattered. She cared about the communities the organization served and about building the digital and data backbone that would help staff serve them better.

For the first three years on the job, it worked. The role was demanding but manageable. Wendy modernized core systems, kept the lights on with a small team and a flat budget, and became the person everyone called upon when something broke. Increasingly, she was also the person everyone called when they had an idea for a new way of doing the work.

That last part is where the story begins to turn.

The increased demands didn't arrive all at once. They accumulated the way water finds its way into a foundation: slowly, persistently, and mostly out of sight until the damage is already done.

Cybersecurity came first. A peer organization was hit with ransomware and the board wanted to know if you were protected. Wendy built the remediation plan and implemented it, on top of everything else.

Data privacy followed. New regulations, evolving funder requirements, organization-wide data mapping and masking. Wendy owned it because there was no one else to own it.

Then came a new CRM for the revenue team. An aging ERP that had been flagged two years earlier was now urgent. An RFP that, done properly, was a six-month project for someone with nothing else on their plate.

And then there was AI.

Staff were already using it: ChatGPT for grant narratives, Claude for data analysis, content generators for communications. No one had asked Wendy. No one had asked anyone.

Wendy saw the opportunity immediately. She also saw the risk: sensitive program and beneficiary data potentially passing through commercial models, no policy, no governance, no guardrails.

She raised it in the leadership team meeting. Everyone agreed it was important. Everyone looked at Wendy to solve it.

She added it to the list.

You saw what was happening. That is the part that stays with you: you were not oblivious.

The small jokes she used to make had stopped. Her peers were coming to you directly with technology frustrations, sensing she was at capacity. You raised the budget question with the board and were told there was no room. You suggested a consultant and Wendy, who had seen consultants disappear after the report, gently pushed back.

Nothing in the management toolkit you had access to felt like the right fit for what she was carrying.

The sick days started in the fall. Then there were two in a week. Then there was a Monday when she simply wasn't there. Things slipped in her absence: a vendor deadline missed, a security patch delayed, a staff member who sent an email containing beneficiary data it shouldn't have, with no one available to manage the response.

And then came the week Wendy wasn't there at all. The message came from her spouse. She was in the hospital. She would be okay. She needed rest.

You sat with that for a long time.

Wendy came back eight weeks later. The ERP was nine months behind. The AI readiness and governance framework still didn't exist. Two members of her team had left during her absence.

The cost in delayed projects, staff turnover, and organizational risk was significant, and far more significant than the investment that might have prevented it.

The problem was never Wendy's capability. It was the ratio between what the leadership role demanded and what one person could sustainably carry.

There was another option. It was not a full-time CTO your budget couldn't sustain, and it was not a consultant who would hand Wendy a report to implement alone. It was a fractional technology leader, someone who had navigated AI governance, legacy system transitions, and cybersecurity strategy in organizations like yours, embedded in your team one or two days a week, carrying genuine ownership of the highest-stakes priorities so Wendy could lead without being consumed.

It would have cost less than the delayed ERP, less than replacing two team members, and less than eight weeks of organizational drift. It would have cost immeasurably less than what it cost Wendy.

If someone on your team is starting to look like Wendy, we would like to talk. We would not offer a report. We would talk about what it looks like to get the right senior leadership capacity into the right place, before the weight becomes too much to carry.

Wendy is a composite character, drawn from the experiences of many technology leaders in the social impact sector.

Fractionals for Impact helps social impact organizations close leadership capacity gaps through fractional executive leadership: senior leaders embedded in your team, driving strategy and execution, at a fraction of full-time cost.

© 2025. Fractional Impact Advisors LLC. All rights reserved.

Contact Us for a Free 30-minute Consultation