The four-lane title (and the routing layer inside it).
For an ops leader whose LinkedIn title is four disciplines stacked with slashes. That's not a job description — that's a routing-layer diagram. I think you already know that.
What your title actually says
Most VPs of Operations have a single line. Yours has four. I read it twice because the second read it stopped being a title and started being a system diagram:
Four lanes, one person. That's not someone doing one job in a department. That's someone routing across disciplines that most companies break into four separate departments and then can't get to talk to each other. The slashes ARE the value.
Why I read it as a routing layer
Tech transformation projects fail at the seams — between the platform team that owns the tool, the operations team that's supposed to absorb it, the L&D team that's supposed to train into it, and the leadership cohort that's supposed to model the new behavior. Most orgs have a person for each seam. The seams don't get covered, they get owned. There's a difference.
A title that says "I do the change-facilitation AND the leadership-development AND the implementation" is a person who has decided to stand IN the seam instead of next to it. That's expensive, rare, and the only configuration where transformation projects actually land in healthcare environments where HIPAA + clinical workflow + change-fatigue gang up on every initiative.
The lane I work, in one paragraph
SideGuy is the same shape one level lower — a human routing layer for operators who own the seam between AI/software vendors and the people who actually have to use what got bought. No SOWs, no decks, no implementation team to manage. Async, flat-priced, single operator. The work that lands looks like: "we paid for [Vanta / Drata / HubSpot / Make / ChatGPT enterprise / pick one], and the team six months later is using it at 20% of what we bought." I show up, translate the platform into the workflow, route the human-side decisions, and leave behind a stack people actually use. The four-lanes-in-one-title shape is exactly the read I have on my own work.
Where our lanes touch (and don't)
Why I'm reaching out (and the Encinitas bit)
Two reasons. One — the Prospeo enrichment on your record came back Encinitas, which means we might be actual neighbors and I keep a soft-priority list for operators in the 92024 zip whose work I respect. Two — you just hit one year at Medical Solutions and posted a reflection. People who write reflections at the one-year mark are people who think about the seam, not just the title. That's the profile I learn from in conversations, not the profile I pitch.
The ask is small
No meeting, no demo, no deck. If anything in this read tracks — either the routing-layer framing, or the operator-translation lane, or the "we might be Encinitas neighbors" coincidence — the next step is a text. If it doesn't, no follow-ups, no funnel, no sequence. (You'd notice if there was one anyway. The fact that this is a custom HTML page and not a templated email is the proof.)
Single operator. Async-first. Text-driven. Human routing layer between operators and the systems they already paid for.
Text me at 858-461-8054 if any of this lands. Otherwise, respect — keep standing in the seam.