The Startup Ecosystem Wasn't Built for You.

You got a message from a stakeholder at 9pm last night. They want a report by Friday. The format they asked for doesn't match the data you have — so you'll spend Thursday rebuilding a spreadsheet that already exists in a different form.

This morning, a mentor canceled. Twenty minutes before the session. You found out when a founder forwarded you the WhatsApp.

Somewhere in your task manager there's a thing you were supposed to do two weeks ago. You're not sure what it is. You haven't looked.

A founder pinged you last night — not about the program. About their co-founder. You're not a therapist. You answered anyway.

There are four people editing the same spreadsheet. You're not sure who has the latest version. You're not sure it matters.

You're behind on something. You're not sure what. And you haven't had a real conversation with a founder about their actual business in... you'd have to check.

Sound familiar?

The Invisible Operator

That's not a hypothetical. That's a composite portrait of every program manager I've ever worked with — including myself in earlier roles. The person running the program. The operational spine of every accelerator, incubator, and startup program in the world.

The person who recruited the founders, designed their journey, matched them with mentors, managed the stakeholders, navigated the politics, and kept the lights on.

Here's what I've noticed after ten years in this industry:

Founders get a thousand podcasts. There are entire media companies built to celebrate the startup journey. Investors get five hundred more. Every fund has a content strategy. The person running the program? Almost nothing.

That invisibility isn't accidental. It's structural. The startup ecosystem was built to celebrate the startup. The operators who make those startups possible — who design the programs, absorb the chaos, and hold the whole thing together — were never part of that story.

That's what I'm trying to correct.

Why Programs Break Down (The Same Way, Every Time)

After ten years working with accelerators — running them, advising them, building systems for them — I've seen the same six places where programs fall apart. Not because the operators are bad at their jobs. Because nobody ever gave them a system.

I call these six components the Program Operating System. Not a product. A mental model. A way of seeing where programs break and why.

Component 1: Purpose Architecture

Most programs start by designing activities. They book the workshops, schedule the mentors, build the curriculum — before anyone has agreed on what success actually looks like for a founder. Then at the end of the cohort, a stakeholder asks: did it work? The honest answer is: we don't know, because we never defined what "work" meant.

Purpose Architecture means theory of change first. What outcomes do you want for founders? What would those look like in 6 months, 12 months, 3 years? You work backwards from the answer, not forwards from the calendar. Without it, everything in the program is theater.

Component 2: Founder Selection

Walk into most selection processes and you'll find a Google Form, a panel interview, and gut feel. The problem isn't that people are making bad calls — it's that the process doesn't produce a decision you can explain. You can't tell a rejected founder why they didn't get in. You can't improve next cohort's process because you don't know what you were optimizing for.

Structured selection means a rubric. Explicit criteria. Scores you can compare. A process you could run without you in the room.

Component 3: Program Infrastructure

I call this tool soup. Airtable for applications. Spreadsheets for tracking. Email threads for decisions. Notion for documents. A Slack that nobody uses consistently. None of it talking to anything else. The symptom isn't that the tools are bad — it's that the program lives in five different places and only you know which one has the current version.

Program Infrastructure means a single source of truth. One place where the program lives. Not five. This is the thing people try to fix first and usually do wrong. They buy a new tool. The problem isn't the tool. It's the architecture.

Component 4: Founder Journey Design

Most programs are built around modules. Week 1: ideation. Week 2: market research. Week 3: pitch deck. The curriculum looks good on a slide. Then cohort starts and founders drift. They attend every session, go through the motions, and at the end of week 8 you're not sure what actually changed for them.

Modules are passive. Founder Journey Design means milestones — deliverables, not reflections. Every week ends with something the founder built, decided, or validated. An artifact. When you design around deliverables, founders don't drift. They either hit the milestone or they don't, and you know immediately who needs attention.

Component 5: Ecosystem Activation

Most programs treat the mentor network as a feature. "We have 200 mentors." Pull on it and you'll find: 200 people who said yes to an email, 40 who showed up to orientation, 15 who ran a session, and 3 who stayed engaged.

The bench isn't the problem. The activation system is. Ecosystem Activation means treating mentors, investors, and alumni as a system with onboarding, matching logic, structured session prep, follow-through, and feedback loops. When this works, you stop chasing mentors. They stay because the program is worth their time.

Component 6: Impact Measurement

At the end of every cohort, someone needs a report. The funder. The board. The corporate sponsor. Every time it's a four-day scramble to pull numbers from spreadsheets that don't agree with each other — because measurement was never built into the program. It was always something to figure out at the end.

Impact Measurement means building data collection into the program from day one. By the time the cohort ends, the report is 80% written. You're not building the measuring stick after the race.

You're Not Behind Because You're Bad at Your Job

Six components. That's the Program Operating System. Each one is a specific place programs fail, and each one has a fix. Not a generic fix — a real system, built for the person running the program in the actual conditions they're working in.

Here's what I want you to hear, if the opening of this article described your week:

You're not behind because you're bad at your job. You're not struggling because you don't care enough. You're running a program that nobody gave you a system for. You're doing real work that the ecosystem doesn't have language for yet. You're the person who makes the whole thing function, and you are almost entirely invisible in every conversation about innovation.

That's what Season 2 of The School of Innovation is for. Every Monday, one practical idea for the operator. Solo episodes, 25–30 minutes, one thing you can actually use. Occasional guests when there's an operator with a story worth telling — someone who built something, fixed something, or failed at something instructive.

One idea per week. That's it.

Want The Full Story?

Listen to the full episode: Coming soon...

And if you want the written version — I write a newsletter called The Ops Brief, every Thursday. Short, practical, for the same person this podcast is for. Subscribe here. It's free.