Scaling Companies Up Requires Some of The Startup Phase Scrappiness


Founders know that scaling their company to Unicorn status requires extending beyond a singular focus.

Launching a product extension.

Complementing your established Go-to-market motion.

Entering new markets (Different ICP, Geography, etc. )

Often, companies approach these extensions using the same processes they use for their established Products/Markets.

They approach a new product opportunity with unwarranted conviction.

They go into a new market using established/scaled revenue operations.

They implement new motions using "big design up front"

They often spread too thin by working on multiple extensions simultaneously.

They work on them using the same processes and structures that are tuned for "efficiency" and "margin expansion"

That often turns out to be an expensive mistake.

Because unlike your established Product/Market, these extensions are often bets.

They often require multiple departments to collaborate tightly to find the extension's Product-Market-Motion Fit.

They require an experimentation mindset (like the same company had in its pre-PMF days...)

Whether it's new leaders brought in to "scale" the company, or the same leaders who were around during the initial leaner days, running a dual operating system - efficient and scrappy side by side - is hard.

I find it helpful to be explicit about your portfolio of activities - which can benefit from efficiency-focused operating systems, and need agile scrappiness.

Here's one technique that can help you improve organizational traction on these strategic bets:

  • Reflect on your goals (e.g. OKRs or items on your company Kanban board)
  • Categorize them based on the level of bet they represent
  • Decide what the right operating model is for them - Scrappy or Efficient?
  • Manage the riskier Bets like VCs manage their startup portfolio

NOTE: This post is inspired by a Science of Selling Podcast episode on Extending to Multi-Product Selling.

Yours,

Scaling w/ Agility

Are You Struggling to Scale Your Organization ? Need agility but dubious of process BS/dogma? I share reflective, pragmatic, principled takes on how to approach scaling your organization leveraging the essence (rather than theater) of product operating models, agile practices and frameworks, and business operating systems such as EOS and OKRs.

Read more from Scaling w/ Agility

Hey Reader, Before you fix teams, fix the system they operate in. Most organizations focus their improvement efforts at the team, program, or product level while maintaining the same organizational operating system—how they make decisions, fund work, and measure success. These teams might be using the latest and greatest processes (Agile, Product Model, Lean Startup, take your pick) but they still need to manage countless dependencies. The funding and GTM processes are still following classic...

When Vered and I got married, my father-in-law gave me a very nice watch as a wedding gift. I didn’t wear a watch that often at the time. I wore the watch, but it didn’t transform me. It provided the service of telling the time, but even back in 2004, we had phones that had clocks. And I was and am pretty punctual so didn’t need that transformation. (And when you’re in Engineering/IT leadership, nobody cares about the watch you wear… at least in Israel… ) Don’t tell Eli, but that watch spent...

“GenAI can enable cheaper, faster experimentation / discovery (it compresses the truth curve by reducing the cost of pretotyping style product experimentation techniques)” (Yours truly, in yesterday’s insight on how AI can really help you build better products) This statement seems to have hit a nerve with reader Elad, who is product leader at a cybersecurity scaleup: “Not everyone can do this… New companies, sure. Larger, established companies are knee-deep in mountains of code,...