The Ultimate Leadership Development Plan for Startup Executives

Three executives left the same Series B company within eighteen months. Not for money. Not for title. They left because the founder had promoted them into roles that didn't exist before the round closed, handed them a scope nobody had defined, and then wondered aloud in board meetings why the results weren't there yet. I watched this happen from the inside — I was one of the three.

That's the thing about a leadership development plan for startup executives: most of them are written for a world that doesn't move this fast. The corporate playbook assumes a stable org chart, a defined ladder, a manager who has time to coach you. In a startup, the org chart redraws itself every nine months, and the person who's supposed to develop you is usually the same person drowning in their own job.

So what actually works? After building and rebuilding leadership plans across three startups — two of which survived, one of which didn't — I've landed on a framework that holds up when everything else is on fire.

Why generic leadership development plans fail startup executives

Here's the uncomfortable part. Roughly three out of four companies judge their own leadership programs as ineffective. I don't need a survey to believe that number — I lived it. At my second startup, HR rolled out a "leadership excellence" initiative borrowed from a Fortune 500 template. Twelve weeks of workshops. A 360-feedback tool nobody trusted. By month four, attendance had dropped by half and the VP of Engineering had started calling it "the Tuesday thing we skip."

The root problem isn't the content of these programs. It's the assumption underneath them: that leadership is a stable set of competencies you develop gradually. In a startup, leadership is a moving target.

The startup-versus-corporate mismatch

At a large company, a director promoted to VP typically inherits a team, a budget, and a mandate that mostly resemble what they had before. The delta is manageable. At a startup, a Head of Sales promoted to VP might suddenly own hiring, forecasting, a new go-to-market motion, and board reporting — all in the same quarter. The skill set required isn't an incremental improvement. It's a different job.

I made this mistake personally. When I moved from leading a five-person product team to running the entire product org at a Series A company, I assumed my job would scale. It didn't. It inverted. My first three months were spent doing what I'd always done — shipping, reviewing, deciding — when the actual job was hiring people who could ship without me. I didn't figure that out until a board member asked, bluntly, why my calendar looked identical to the year before.

That's the mismatch in one sentence: your calendar is the honest version of your development plan. If it doesn't change, nothing else did.

What a usable plan actually needs

A plan for a startup executive needs three things a corporate template won't give you:

• A stage anchor — which funding round you're preparing for, and what that round demands of you.
• A scope delta — the specific responsibilities you don't yet have but will in twelve months.
• A kill criterion — the condition under which you abandon part of the plan. Without one, you'll cling to a development goal long after it stopped being relevant.

Everything else — the workshops, the coaching, the reading list — is optional.

What is the 70-20-10 rule for leadership development?

The 70-20-10 rule says that roughly 70% of leadership growth comes from doing the work, 20% from relationships and observation (mentors, peers, feedback), and 10% from formal training like courses or coaching. It's a rough heuristic, not a law — the exact ratios are debated — but the underlying claim is sound: you get better at leading mostly by leading, not by studying leadership.

Why the 70% is where most startups cheat

Most people nod at this rule and then spend 90% of their development budget on the 10%. Workshops. Courses. A coaching package. All of it useful in small doses, none of it where the growth actually happens.

The hard part of 70-20-10 isn't believing it. It's making the 70% deliberate. Doing more work isn't the same as developing. You have to pick assignments that stretch a specific capability, then reflect on them. Otherwise you just accumulate experience without learning from it.

Concretely: if your weakness is difficult conversations, don't "work on communication." Take on the task of restructuring one underperforming team — and commit to having every hard conversation in person within a defined window. I did this once with a design lead who was on the verge of being managed out. Thirty days, five conversations, one of which I rehearsed out loud in my car. She stayed and improved. The lesson stuck because I was in it, not reading about it.

How to structure the 70 in practice

Pick one stretch assignment per quarter that maps to a specific gap. Not two. Not three. One — because if it's a real stretch, one is already too much. The other 80% of the framework fills in around it:

1. One stretch assignment tied to a named capability gap.
2. One mentor or peer who's already done the thing you're trying to learn — outside your company if possible.
3. One formal input, capped at a few hours a month. A course, a book, a coaching session. Not all three.
4. A weekly fifteen-minute reflection, handwritten. This is the part everyone skips and it's the part that makes the rest stick.

The reflection piece matters more than it sounds. When I started writing three lines every Friday — what I did, what I'd do differently, what I avoided — patterns emerged within about six weeks that I hadn't seen in a year of just working harder.

What are the 5 C's of leadership?

The 5 C's — commonly listed as communication, collaboration, credibility, confidence, and curiosity — are a shorthand for the core qualities strong leaders tend to share. They're a useful checklist, not a development plan. Treating them as the plan is one of the most common mistakes I see in startup executive development.

Which C matters most at which stage

The 5 C's aren't equally important at every stage. They shift:

Stage	Dominant "C"	Why
Seed	Curiosity + Communication	You're figuring out what the company is. Adaptability wins.
Series A	Credibility	You're now selling a story to hires, customers, and investors who weren't in the room at the start.
Series B/C	Collaboration + Confidence	The org is bigger than you can personally see. Your job is enabling, not doing.
Late stage or pre-exit	All five, in balance	You're a public-facing leader now. None of them can be weak.

Notice that "confidence" — which most people read as a personality trait — actually becomes a requirement at scale. Not the loud kind. The quiet kind: the ability to make a call with incomplete information and then defend it without needing everyone to agree.

I've watched brilliant operators get stuck at the Series A-to-B transition because they couldn't make decisions without consensus. Consensus worked when the team was eight people. At forty, it just produces paralysis. That's a C-gap that no workshop fixes — only reps do.

What is the 30-60-90 rule in leadership?

The 30-60-90 rule is a structured onboarding framework: the first 30 days for learning and listening, the next 60 days (days 31-90) for diagnosing and forming hypotheses, and the final 30 days (days 61-90) for acting and delivering early wins. It was originally popularized for new executive hires, but it works just as well for a leadership development sprint.

Using it for development, not just onboarding

Most people apply 30-60-90 to a new job. I use it for any capability I'm trying to build, treating the whole thing as a ninety-day cycle:

• Days 1-30: observe the current state without trying to fix anything. Talk to people. Ask "what would you do in my position?" I've collected some of my best ideas from people who had no authority to implement them.
• Days 31-60: form one strong hypothesis about what needs to change, and pressure-test it with two or three people whose judgment you trust.
• Days 61-90: ship one visible change and measure the result.

One visible change in ninety days. That's the bar. Not a transformation, not a strategic pivot. One thing you can point at.

Why ninety days? Because startups operate in roughly quarter-sized chunks, and anything longer loses momentum. I once let a development goal drag across two quarters and by the end, the original problem had shifted enough that the goal was obsolete. I finished the plan out of stubbornness. It accomplished nothing.

What should a leadership development plan include?

A usable plan fits on one page. If it doesn't, it won't get looked at — I've tested this. A three-page plan gets referenced twice and then forgotten. A one-pager that lives at the top of a notes app gets referenced weekly.

What has to be on that page:

1. The stage you're developing for. "Series B readiness" or "post-Series A scale" — something concrete.
2. One capability gap, stated in behavioral terms. Not "improve leadership." Instead: "make difficult personnel decisions within two weeks instead of dragging them out for months."
3. The stretch assignment that will close it — one task, with a real owner and a deadline.
4. The support structure: a named mentor, a coach if you're using one, and the peer group you'll be honest with. Names, not categories.
5. The measurement — a specific, observable signal. Not a self-rating. Something another person could confirm without asking you.
6. The kill criterion. Under what condition do you abandon this plan and start over?

Two more things, both optional but worth it for me: a template you actually fill in (I use a simple table, dates in the left column, capability in the right), and a single accountability partner. Mine is a former COO at a company that went public — we talk every three weeks, and she has blanket permission to call me out when I'm avoiding something.

How to review without drowning in process

Quarterly reviews, not annual. Fifteen minutes, three questions: what stretched me, what stalled, what changes next quarter. That's it. The trap is building an elaborate review ritual that becomes its own job.

What if my company won't fund any of this?

Most of what matters costs almost nothing. The stretch assignment is free. A mentor outside your company is one coffee conversation to set up. A peer group is five people and a recurring slot. The expensive stuff — external coaching, formal programs — is the 10% layer, not the 70%. You can build a genuinely effective plan for the cost of a few hours a month.

Do I need a coach?

Not necessarily, but if you do hire one, hire for the stage you're moving into, not the stage you're in. A coach who's only worked with seed-stage founders will give you seed-stage advice. Ask specifically about the transitions they've helped someone through, not the frameworks they use.

Making it survive contact with reality

The plan will break. That's not a failure mode — it's a feature. A startup's needs change fast enough that any plan designed to last a full year is designed for a company that probably won't exist in that form. Build it in ninety-day chunks and rebuild it every quarter. That's the whole methodology, really: small cycles, ruthlessly reviewed, thrown away when the world moves.

The three executives I mentioned at the top? One of them is now a CPO at a later-stage company, one runs a small consultancy, and one — this is the part that still bugs me — went back to a big corporate job and told me it was a relief to have a ladder again. Three different outcomes, same starting point: a founder who never built a development plan for them because nobody had built one for him either.

You don't have to inherit that pattern. Pick one capability. One stretch assignment. One person who'll tell you the truth. Start on Monday.