What a Director of Strategy & Ops actually owns at Via.
A research note on the role. Where the function sits in 2026, what the first ninety days should look like, the three metrics that matter, the questions worth asking in the interview, and the risks worth naming out loud.
Via's Director of Strategy & Ops seat is not a planning role. It is a portfolio operator seat across partner cities. The right operator runs it like a multi state P&L: cohort the cities by maturity, instrument the leading indicators of non renewal twelve months early, and build the architecture that lets each city compound rather than improvise its way through the first ninety days.
Each partner city is a P&L. That changes the operating math.
Four observations from the public record. Each is the kind of thing the team running the function thinks about every Monday morning.
Via is no longer just on demand transit
The platform now spans paratransit, school transportation, microtransit, fixed route optimization, and increasingly AI driven dispatch. The product surface has grown faster than the operating model that supports it. Each new module a partner city activates is a new operating variable to manage at the city level and at the platform level. That is a strategy and ops problem, and it is the function this role exists to own.
The portfolio is multi jurisdictional
Via partners with cities, transit agencies, school districts, universities, employers, and healthcare networks. Each has its own procurement cycle, its own compliance regime, its own definition of success. A partner that renews in year one for the right reasons is structurally different from a partner that renews because nothing went wrong. The strategy function gets to define which kind of renewal counts.
School routes are a different operating animal
The expansion into student transportation is one of the highest leverage growth surfaces and one of the most operationally unforgiving. Safety regulations are stricter, schedule tolerance is tighter, parent visibility is total. The operating playbook that wins in microtransit does not automatically port to school routes. Building the bridge between the two is operational discipline, not algorithmic insight.
Operating margin compounds at the city level
Every partner city has a contribution margin curve. The first 90 days set the trajectory. The next 24 months pay the bill. The strategy and ops function is the one place inside Via where the launch playbook, the city level KPI architecture, and the cross city benchmarking sit together. Three points of margin improvement applied across a 100 city portfolio is a different size of business than the same improvement in one flagship market.
What the first ninety days actually look like.
Three things any Director of Strategy and Ops owns from day one. A portfolio level operating dashboard, a launch readiness framework, and the standardized governance that lets each city compound rather than improvise.
Stabilize.
days 1 → 30- Operating audit on three partner cities. One mature, one mid stage, one recent launch. Sit with the city ops lead. Read the renewal docs. Walk the dispatch room. Document the operating signals that diverge from the platform level metrics. That divergence is the strategy roadmap.
- Stakeholder map across functions. Strategy lives at the intersection of city ops, product, partnership management, finance, and legal. Build the map of who owns what, where the handoffs break, and which decisions currently take 14 days that should take three.
- Read the renewals that didn't happen. The platform level retention number is real but lagging. The cities that did not renew, or renewed at reduced scope, are the leading indicator. Talk to the partnership managers who lost them. Document the cause taxonomy.
- Inventory the launch playbook. What exists, what is tribal knowledge, what gets reinvented at every new market. The next launch should not be the eighteenth time someone solves the same week one driver onboarding problem.
Compound.
days 31 → 60- Standardize the launch readiness framework. A staged go or no go gate at week minus 6, week minus 2, and day of launch. Each gate is keyed to operating signals, not vibes. The team that has launched 100 markets should not be flying without instruments on the 101st.
- Build the city level operating dashboard. Twelve metrics per city, instrumented at a weekly cadence, benchmarked against the portfolio. Contribution margin trajectory, on time performance, complaint volume per 1,000 trips, driver retention, dispatch utilization. The dashboard is for the city ops lead first and the executive review second.
- Cross city operating playbook. Eight chapters covering the things every city ops lead has to do regardless of market: driver supply and retention, schedule density and waste, partner side reporting cadence, compliance and audit readiness, complaint triage, vehicle utilization, demand seasonality, and the city renewal narrative. Operating leads use it as a curriculum, not a manual.
- Renewal risk early warning model. The cities most likely to walk in 12 months are predictable today. Build the leading indicator model, instrument it, hand the alerts to partnership managers with a defined intervention playbook.
Scale.
days 61 → 90- Quarterly Via Operating Index. Anonymized cross city benchmarking shared back with partner cities. Each city ops lead and partner agency sees where their numbers sit relative to peers. The transparency lifts the floor without naming names. It also becomes a sales tool for the partnership team.
- Module launch readiness handoff. The framework for activating a new module inside an existing partner city. Most platform companies treat module launch as a product marketing problem. It is also an operational problem and should have an operating gate.
- Strategic review cadence with the CEO and exec staff. Monthly portfolio of cities review, quarterly strategic pivot review. The strategy and ops function should be the single place where "should we keep this market" gets a clean answer, not a defensive one.
- Hand the operating model to the city ops leadership. Documented, instrumented, repeatable, and owned by the field. The Director's job is not to run cities. It is to make sure every city can be run by the lead in that market, with the right architecture behind them.
The three things I'd watch from day one.
Not a dashboard of fifty KPIs. Three numbers that, if they move, the rest of the portfolio moves with them.
Where Via wins and where it has to fight.
Four competitors, four dimensions. The strategy and ops function defends or expands on each axis depending on the partner city, the module, and the procurement cycle.
| Via | Spare | HopSkipDrive | Routematch / Ford | |
|---|---|---|---|---|
| Multi modal platform depth (on demand + paratransit + school + fixed route) | strong | building | school only | legacy transit |
| AI dispatch + routing sophistication | strong | strong | mid | legacy |
| US partner city scale | advantaged | growing | specialty | incumbent base |
| School transportation product | building | limited | specialist | none |
Hypothetical contribution margin by city cohort (year)
Six questions I'd want answered in the interview.
The point of these is not to demonstrate that the JD got read. The point is to surface where the team thinks the function is weakest, so the first 30 days do not get spent rediscovering what leadership already knows.
Which partner cities are most likely to walk in the next 12 months, and what is the team's current confidence level on those predictions?
If the answer is precise, the function has a working early warning system. If the answer is vague, that is the first 60 day build.
What does the standard launch playbook look like today, and where does it break?
Every transit launch has a 200 item checklist. The interesting question is which 12 items, if missed, predict a partner relationship that never recovers.
Where does product end and operations begin in the city ops conversation?
The cleanest org charts have a sharp line. The most effective city ops conversations cross it constantly. Knowing which is true at Via shapes how the strategy function partners with both sides.
What is the current cause taxonomy for non renewal, and how confident is the team in it?
If the taxonomy has six causes and four of them are "other," that is a research project. If the taxonomy is precise but the predictive accuracy is low, that is an instrumentation project. Different problem, different fix.
How does operating margin actually compound at the city level today?
The thesis is that margin compounds. The reality may be that it compounds in some cities and decompounds in others. Knowing which is which shapes where the strategy function leans first.
What does success at the 12 month mark look like for this specific role?
Not the OKR. The team change, the cadence change, the leading indicator that says the function compounds even if quarterly results miss by a few points.
Four risks worth naming out loud.
Honest read on what could trip the function. The point of writing these down is to be ready for them, not to talk anyone out of the bet.
Procurement cycles in transit are long
Municipal procurement runs on government timelines, not platform company timelines. Revenue is loaded toward the back of the contract, and the operating cost is loaded toward the front. A strategy function that does not understand this rhythm will optimize for the wrong quarter.
Operational complexity scales nonlinearly
Doubling the partner count does not double the operating complexity. It triples it, because the interactions between cities and modules and partner types compound. The function has to design for the 200th partner from the moment it stands up the framework for the 50th.
Authority over launch readiness
Strategy and ops functions only work if they have real authority to push back on launches that aren't ready. Without that authority, the function becomes a documentation team that watches preventable problems happen. The role needs an explicit go or no go vote on new market activations, or it becomes advisory.
Module sprawl fragments discipline
Every new module Via launches inside an existing partner city is operating exposure on top of existing operating exposure. The temptation is to treat module attach as a sales metric. The operating reality is that each module has its own SLA, its own cost structure, and its own failure mode. The function has to keep the portfolio view tight as the product surface grows.
The fuller portfolio at kiyonglee.com is the canonical record of how I think about operating businesses, multi market portfolios, and the architecture that lets the field run.
$ cat ~/kiyonglee.com →Twenty minutes is enough to see if this lands.
If the diagnostic reads true to how the strategy and ops function feels from the inside, a working call is worth setting up. If it reads wrong, that is also useful information.
Start the conversation// sources
- Via Transportation · company positioning, modules, and partner city portfolio
- Via news room · partner city announcements, module launches, school transportation expansion
- Industry coverage on TransitTech, microtransit, and paratransit operating models in US municipalities
- Public procurement filings from partner agencies on transit service contracts and renewal terms
- Operating discipline references from sixteen years running multi state franchise portfolios under audit governance