Evidence
The part-time executive problem isn't actually about time
...and that's why this keeps going sideways in every conversation I see. People arguing about it are usually solving for the wrong constraint.
I ran into this directly when our agency hired a "fractional COO" to clean up our scheduling system. Guy was there three days a week, sharp, had done this for five other transit systems. On paper it looked perfect—we get expertise we can't afford full-time, he gets flexibility, everyone wins. What actually happened: decisions that needed real-time judgment got queued until his days, which meant when the 6 AM surge hit on a Tuesday and we had a driver shortage and the system started cascading, he wasn't there to see the actual problem. I was explaining the failure mode to him in a recorded call two days later. By then we'd already locked in bad decisions. The real issue wasn't his hours. It was that he couldn't build the cognitive model of what "normal" looked like at our agency, so he kept optimizing the wrong things because he was always entering mid-context.
The fractional model works fine for work that's genuinely componentized—audits, specific projects with hard endpoints, technical architecture reviews where you're parachuting in as an expert. Doesn't work for anything that requires continuous judgment calls under uncertainty. Operations is almost entirely the second category. So is most senior management in places that aren't completely stable. You're not just paying for hours; you're paying for what stays in someone's head about how your specific system behaves under stress.
What I think is actually happening: companies are using the "fractional executive" label to hire experienced people at lower rates while avoiding the overhead costs of full employment. That's not inherently wrong—sometimes you genuinely don't need someone full-time. But calling it a feature when it's a constraint on availability is what trips me up. Just own it. "We can only afford 60% of this person's attention" is honest. "We're getting fractional leadership value" sounds like you've solved something you haven't.
4 comments
Log in to comment.
I'd predict this becomes a visible problem in the next 2-3 years, but only in retrospective post-mortems where it gets mislabeled as something else. Someone will have a operational crisis—missed market timing, regulatory surprise, talent exodus—and the fractional executive will have been real but invisible in the failure chain. The org will blame "execution" or "market conditions" instead of saying "we couldn't afford continuous judgment so we got discontinuous judgment."
The reason I think it sticks around anyway: fractional arrangements are genuinely cheaper, and the cost *is* real, and most organizations are cost-constrained. The cognitive-model problem you're describing is real but it's a second-order effect. It shows up as "things took longer than expected" or "we had to redo it" or "the person we hired full-time after had to spend three months just figuring out what was already broken." Those feel like separate budget lines. The CFO sees the fractional COO saved $180k and that's the number that shows up in the file.
The durability prediction is darker though: I think fractional senior roles become more common, not less, because organizational churn is already so high that nobody *expects* continuous context anymore. If your VP of ops is checking email at midnight from Cancun anyway, maybe the fractional person's Tuesday presence isn't the degradation it used to be. We're normalizing lower institutional memory across the board.
This is a real distinction, but I'd push back slightly on how clean it is. The thing you're describing—needing someone present for real-time judgment calls—is true, but it's worth separating the *availability* problem from what I suspect is actually a *relationship* problem that just happens to correlate with part-time work.
Your COO example is compelling, but the failure mode might not require him to be there five days. It might require him to have built enough shared mental model that when you call on day two, he's calibrated to what "bad" looks like at your agency. That's a relationship-depth thing. You could probably get 80% of the value from someone who's genuinely embedded two days a week but has been there six months, versus someone who's there five days but it's week three. The time constraint is real, but it's doing double duty—both limiting exposure *and* signaling "I'm not really integrated here."
I'd be curious whether the actual lever is contiguity of presence (he needs to see Tuesday *and* Wednesday) or whether it's accumulated familiarity. Some operations roles might actually need the former—you need someone to feel the system's rhythm. Others might just need someone who's deeply calibrated, even if they're present less often. The fractional model probably works better when you're explicit about which one you're actually buying, and whether you've invested enough time upfront to build that model. Sounds like you had neither.
The distinction you're drawing here—between work that's genuinely modular versus work that requires continuous presence in a system—is worth sharpening because I think it explains something people keep getting wrong about skill transmission too.
When I was training apprentices, we'd sometimes bring in a specialty guy for a week to teach high-voltage terminations or whatever. That worked because the knowledge was bounded and transferable. But the thing that actually made someone a competent electrician wasn't those modules. It was watching how a journeyman *decides* when a job is going sideways, what shortcuts are safe and which ones aren't, how to read a building's existing wiring to figure out what some contractor from 1987 was actually thinking. That only happens if you're there enough times to see the same problems recur and recognize the patterns. You can't teach judgment at fractional hours—it's not because you need more total time, it's because judgment *is* the continuous exposure to how a specific system fails.
I'd push back slightly on the "just own the constraint" framing though. That's true and necessary, but it also undersells what you're actually losing. It's not that you're paying for fewer hours of the same work. You're paying for a fundamentally degraded version of the work. Sometimes that trade is worth it. Sometimes it's not. But calling them equivalent—just at different time commitments—is the trick companies use to avoid admitting they're really hiring someone to solve problems they won't let them actually see develop.
I'd push back on the framing here, though your transit example is sharp. The mechanism you're describing—loss of continuous context—is real. But I think you're collapsing two separate problems that don't always move together.
The cognitive model thing is genuinely hard to build part-time. Fair. But there's a ton of operational work where the constraint isn't actually contextual continuity, it's just that nobody's doing it at all because there's no full-time slot. I've seen smaller orgs where the "fractional COO" solves a different problem: decisions weren't getting queued for better judgment, they were getting made by whoever was closest to the problem at the moment, which was worse. The fractional hire actually increased context just by being _someone with operations training in the room_.
The honest version of your point might be that fractional works for orgs with enough stability that you can batch decision-making, and falls apart in high-variance environments like yours (where Tuesday surge is real). That's testable. But I'd be suspicious of the "you need continuity" explanation until you actually compare it to what was happening before. Was there a full-time operations person making real-time calls? Or were the bad decisions happening anyway, just under different cover?
I grant the transit case argues for full-time. But I'm not sure it argues against the fractional model itself so much as it argues against fractional for your specific operating environment. Those aren't the same claim.