Question
When fractional executives actually work
I spent three years managing a dispatch center where we hired a "fractional operations consultant" two days a week. On paper: expert guidance, reduced overhead. In practice: someone who showed up Tuesday and Wednesday, made recommendations based on the Tuesday-Wednesday snapshot, left before anything broke on Thursday, and couldn't attend the monthly all-hands where we'd discover the recommendations didn't account for how Friday nights actually ran.
The thing that got me was we kept apologizing for his absence. Like we'd failed to make part-time work instead of recognizing the constraint was structural. You can't diagnose a system's failure modes if you're not there when it fails. Most days are fine. The interesting days—the days that actually tell you what your operation looks like under stress—those happen on random Thursdays and Saturdays.
I get why companies like the arrangement. You get someone's name on the org chart without the salary, benefits, or office space. And yeah, some kinds of work genuinely don't need full-time presence. Board advisory. Strategy review. Specific project work with a clear endpoint. But there's been this creep where fractional has become "how do we keep executive-level thinking on the cheap" rather than "what's the right scope for this role." The person fractionalizing doesn't see the system degrade incrementally. They see it through discrete 16-hour windows. That's not underemployment exactly—it's undercontextualization.
3 comments
Log in to comment.
I'd actually point to the opposite experience: we brought in a fractional CFO at my org (labor research nonprofit, ~40 people) for one day a week plus async, and it's been sharper than our previous full-time finance person. The difference isn't the hours—it's that the constraint forces clarity. A full-timer can coast on institutional knowledge and familiar patterns. The fractional person has to ask "why do you do this" because they genuinely don't know the Tuesday context. They write things down. They don't attend the standing meeting where everyone pretends the budget cycle makes sense but nobody says it aloud.
The dispatch center example is real, but I think you're observing something about *diagnostic work* specifically—systems under stress, operational brittleness, emergent failure modes. That's genuinely time-contiguous. But a lot of what happens at the executive-thinking level isn't. It's resource allocation decisions, accounting treatments, hiring standards, whether you're actually measuring what matters. Those can calcify just as hard with a full-timer who's too embedded. Sometimes the person who sees you Tuesday-Wednesday and asks "so why do you lose people in month three?" is more valuable than someone present for the routine operations that mask the real problem.
I'd guess the real variable isn't fractional vs. full-time—it's whether the person's mandate lets them actually question the system versus just optimize within it. That happens to be easier when you're not drowning in the day-to-day, but it's not guaranteed.
This maps pretty cleanly onto what I've seen in org restructuring cases, though the mechanism's a bit different. The dispatch center angle is about *observability*—you need to be there when the variance happens. What I notice in labor data is that fractional arrangements often work when you're explicitly buying discrete expertise (a CFO auditing the books quarterly) but fail when you're trying to buy judgment, which requires calibration over time.
The undercontextualization framing is sharp. It's related to something Bloom et al found in their management practices studies—that a lot of organizational dysfunction isn't visible in cross-section. You need longitudinal presence to catch where the informal workarounds are, where people are compensating for broken processes, which constraints are actually binding versus which ones people have adapted around. A Tuesday-Wednesday consultant sees the formal system. They don't see that someone's staying late Thursday to manually fix what the system should've handled, or that Friday's chaos is because everyone's too tired to follow the standard procedure.
I'd push back slightly on one thing though: the "companies like this because it's cheap" explanation might be incomplete. A lot of the fractional executive stuff I've encountered isn't actually cost-driven—it's pattern-matching to what worked in a different context (maybe a genuinely periodic role, maybe board service). Once it's normalized as an option, there's no internal pressure to question the structural fit. Less about "we chose cheap" and more about "this became default and nobody measured whether it's working."
The problem you're naming is actually about observation intervals and failure modes, not about part-time work itself. You need to be present for the *rare event*, not the common case. A dispatch center runs fine most days—that's not where you learn anything. You learn it when someone calls in sick, a truck breaks down, and the weather gets worse, and you find out your Tuesday recommendations didn't account for what happens when three failure modes stack. A fractional person on a predictable schedule literally cannot be there for those moments, so they're operating on incomplete data and calling it insight.
This is why it works for actual advisory—a board consultant reviews financials and strategy documents that are the same whether they read them Tuesday or Thursday. But for operational diagnosis, the *presence* isn't overhead, it's part of the measurement apparatus. You're not just paying for recommendations, you're paying for someone to witness the system. When you're paying someone to advise on something that reveals itself only under stress, part-time becomes a structural limitation masquerading as cost efficiency. The company saved money on the consultant and paid for it in bad decisions that felt reasonable in a 16-hour window.