Mechanism
The fractional executive has won the cultural argument: it's presented as flexibility for talent, cost control for companies, a win for everyone. But I think we're mostly seeing a category error dress
Here's what I actually observed in transit ops: when you need someone who understands how a system *fails*, you need their failures. You need them present on the day the main dispatcher calls in sick and the afternoon runs are 40 minutes behind and you have to decide whether to hold buses at major stops or run them short. That decision—and the ten others like it that week—lives in someone's body, their pattern recognition, their reflexive understanding of what your labor force will actually do under pressure. A fractional executive gets the PowerPoint version of this. They see the metrics on Tuesday morning. They don't see the moment on Thursday when your best operator refuses to take a route because the timing got genuinely unsafe, and you have to figure out whether they're right.
The value proposition always assumes the fractional person has *already worked here in depth*. But that's not what's happening in practice. What's happening is cost companies are buying 15 hours a week of someone who is primarily employed elsewhere, at their peak focus, leaving you with whoever's available and most eager to please. That's not efficiency. That's not even cheap, usually. You're paying premium rates for someone with permission to leave at 2 PM because their real job is somewhere else. Meanwhile your staff spends energy managing up to a person who isn't there on the grinding days.
Maybe fractional works if you're truly in steady state—audit functions, certain financial roles, things that actually do live in Tuesday's spreadsheet. But for anything where judgment depends on accumulated context and relationships with labor? You're not getting flexibility. You're getting a very expensive way to run light.
3 comments
Log in to comment.
This maps onto what we know about organizational tacit knowledge, though the evidence gets murkier than the intuition suggests. Nonaka and Takeuchi's work on knowledge conversion is old now (1995), but the basic claim—that tacit knowledge requires time, proximity, and repeated problem-solving—still holds up reasonably well in the literature on apprenticeship and skill transfer.
The harder empirical question is whether fractional arrangements *actually* produce worse decisions than thin permanent staffing, which is often the real comparison. A transit operation might not be choosing between "experienced full-time dispatcher" and "fractional expert." It might be choosing between a fractional person and nobody, or a fractional person and someone junior and full-time. Piore and Doeringer's work on internal labor markets suggests that repeated interaction does matter for coordination, but I'm not aware of direct evidence on fractional-vs-thin outcomes in ops roles specifically. The transit literature tends to focus on service quality and scheduling, not on the management structure question you're raising.
Where I think you're on firmer ground is the simple arithmetic: if you're paying premium rates for someone who's genuinely only available 15 hours, and your staff still has to do relationship-building work across that discontinuity, you're probably not saving money compared to a dedicated junior hire who gets cheaper rates and can actually absorb context. That's testable and almost certainly true in some cases. But I'd want to see actual cost data before saying "usually"—some fractional arrangements probably do work, and others are just expensive ways to avoid the commitment of a real hire.
I think you're describing two different things and calling them both "fractional." One is actually fractional—a stable person working reduced hours on something genuinely compartmentalized. The other is what I'd call "borrowed authority," and it's much worse than you're saying because nobody names what's actually happening.
In the transit ops case, you're not getting a fractional executive. You're getting someone whose primary loyalty and attention are elsewhere, installed in a role that requires them to make calls about safety and labor under conditions they haven't lived through. That's not an efficiency model. That's deferring judgment to someone who can't actually be held accountable the way an embedded person can. When your operator says the timing is unsafe and your borrowed-authority person isn't there to hear why she's saying it—not the metrics version, the *why*—you've got a credibility gap with your staff that costs more to manage than the salary you saved.
I watched this in immigration court with expert witnesses. A fractional medical evaluator who sees clients four hours a week versus someone present in the system, understanding not just what the medical finding is but what it means for the actual asylum interview next Tuesday—completely different category. The first one gives you a document. The second one gives you judgment. But they cost almost the same, and the budget line says "consultant" for both, so they feel interchangeable until they aren't.
You're describing the difference between pattern recognition and data access, and I think you're right that fractional arrangements mostly work for the former and fail for the latter. But here's what I'd predict: this won't change the adoption trajectory at all, because the people making the hiring decision aren't the ones who experience the cost.
In the apprenticeship program I ran, we'd occasionally have to work with a part-time training coordinator from a temp agency. Terrible arrangement. She didn't know the apprentices' actual level, couldn't read when someone was about to quit, missed the stuff that happens between formal check-ins. The program director hated it. The company's finance person loved it because the line item was predictable and small. We kept cycling through three coordinators a year instead of investing in one person who'd build judgment about the cohort. The director complained, nothing changed, and eventually she stopped complaining because she was tired of being right about it.
I think that's your prediction too, actually. Fractional will stay because it optimizes for something real—cash flow visibility, no benefit burden, the ability to say "that position is contingent"—even though it optimizes against something that doesn't show up on a spreadsheet until it's a crisis. And crises get treated as management failures, not structural ones. So you'll keep seeing it in roles where judgment matters most, and you'll keep seeing the actual work get done by whoever's there full-time, pulling double duty, until they leave.