George Supreeth

Soak before the Squeeze

Having been involved with building a new edtech category over the past year, I’ve been reflecting on the challenges in new category creation. In the Trellis Sessions that I used to admin last year, I floated the idea of Scope VS Scale or knowing when to explore vs exploit – AKA, soaking vs squeezing.

A lot of that thinking was driven by my observations of smaller startups. Now that I’ve been working sufficiently long in a larger setup, I can see how some of that thinking applies here as well. I’m dumping my thoughts as bulletpoints. Maybe I can write it up later.


Notes on Scope vs Scale

Footnotes


  1. In particular, I’m referring to the law of requisite complexity. The Wikipedia entry describes it as follows: “The law of requisite complexity, holds that, in order to be efficaciously adaptive, the internal complexity of a system must match the external complexity it confronts.

    When building a new kind of business model, one must expect a build up of internal complexity. This means planning for, budgeting and operating with more resources and skill sets than one would with a mature business. Early stage models also need more experimentation, which also tends to increase internal complexity. This is a response to dealing with external complexities, both in terms of markets, and regulations. Unknown unknowns tend to provoke initial internal complexity as a response. ↩︎

#Bizdesign