This week’s letter features five essays that can be explained using the theme of the first essay, which is using the right amount of force to navigate a situation. Starting and building a business, in many ways, is a calibration challenge—being able to make the right intervention at the right time and applying it in the right measure.
On to this week’s updates.
“There is a theory in organizational research that partly explains this. It's sometimes called the zone of proximal development in learning. The idea is that the most effective development happens in the space just beyond what you can already do, where the challenge is real but not overwhelming. In that zone, the learner is stretched but not broken. In that zone, adaptation occurs.
Organizations work much the same way. The most effective growth happens in the space just beyond what you've already mastered. Close enough that your systems can handle it, far enough that you're genuinely building new capacity.
The hard part is finding and staying in that zone. Because the zone is not a fixed coordinate, it moves as you grow. And you can't see its edges from the inside. You only know you've crossed into the wrong territory when the pain arrives, sometimes weeks after the decision that caused it.”
“The company tried to address a capability gap by hiring junior headcount for a role that nobody senior fully understood. It didn't work twice. First, with the unspecified earlier sales hires, and second, implicitly with how long it took before anyone identified the actual mechanism.
Finally, bringing someone who already possessed the relational capital the company lacked, at a seniority level matched to the size of the gap, solved the bottleneck for the company.
It also helped solve the company’s structural challenge in building a sales operation. On the one hand, it brought in someone who fills an important gap in terms of expertise. At the same time, that same hire helps the company eventually build out the processes and structures for an eventual sales operation so that when someone new comes in, they know what their job is.”
“The third is the gap between when a company starts and when it becomes a company, and how little the gap matters in hindsight. By any formal measure — registration, a name, a bank account, a lease — Kaz Software did not exist for the first six to eight months of its own founding story. What existed was three people, a contract, and a converted bedroom. The decision to formalize came only once the original bet had already paid off once (the contract was extended) and the administrative load of staying informal had become heavier than the cost of dealing with the RJSC.
This suggests a sequencing worth checking against other cases: structure, in this telling, isn't something a business needs to start; it's something a business needs once continuing to operate without it becomes more expensive than the paperwork. Even then, the registration itself was handled with the same loose, reactive style as everything before it — forgotten mid-process, then re-attempted under a different name almost by accident.”
One of the most difficult problems in many areas of life is generating good ideas. In this article, we compile some of our favorite canonical essays on coming up with ideas, particularly startup ideas.
“By the company's own numbers, it has served under 1% of an addressable market of 38 to 40 million students in Bangladesh. That is either a modest result for fourteen years of work or an enormous amount of room to grow, depending on how you choose to look at it.
Whatever your take, both readings are correct.
Trust takes time to compound. There are no shortcuts to verify half a million tutors. The moat here was never technology. It is the accumulated, unglamorous work of getting thousands of small transactions right, consistently, for over a decade, until families started trusting the platform by default.
These lessons are easy to underrate.
Solve for trust before you solve for scale, because scale without trust in a market like this collapses the moment something goes wrong.
Validate demand before building a new category, rather than betting on what customers might eventually want.
Keep the burn low enough that a bad year, and there will be more than one, doesn't kill the company.
Hire for appetite over credentials, and give people years to grow into the role rather than expecting them to arrive finished.”
