Instagram's team viewed the 'stories' format not as a proprietary feature, but as a new, universal primitive for mobile sharing, akin to the 'feed.' They believed denying users this powerful format would be a disservice, so they adopted it and improved upon it for their specific user base.

Large companies like Rippling and TripActions maintain innovation velocity by creating "carved out" teams for new, "zero to one" initiatives. This organizational strategy provides singular focus, empowering a small group to execute with the intensity and speed of an early-stage startup without corporate distractions.

Inside Instagram, engineers frequently discussed a thought experiment: if half the company vanished, would things improve? They often concluded "yeah, maybe." This reveals a deep-seated belief among product builders that organizational bloat, communication overhead, and excessive code were creating more problems than the extra headcount was solving.

Contradicting the common startup goal of scaling headcount, the founders now actively question how small they can keep their team. They see a direct link between adding people, increasing process, and slowing down, leveraging a small, elite team as a core part of their high-velocity strategy.

Near the launch of Instagram Stories, the team was in a bind after losing their drawing tools engineer. Co-founder and CTO Mike Krieger exemplified a "lead from the front" mentality by personally jumping in to code the remaining features, like the neon brush, and review diffs at 2 AM. This hands-on leadership from the top inspired the team.

To adapt to AI-driven productivity, Block abandoned large, static feature teams for small squads of 1-6 people that can flexibly move between products. This structure, combined with cutting management layers by over 50%, allows for faster information flow and rapid, AI-powered development cycles.

When the Instagram Stories project was churning, leadership made a counterintuitive move: they significantly cut the team size. This resulted in clearer ownership, less communication overhead, and faster decision-making, allowing a tiny core team to build and ship the massive feature in just a few months.

Staying lean is a deliberate product strategy. Bigger teams may build more features and go-to-market motions, but smaller, focused teams are better at creating simpler, more intuitive user experiences. Focus, not capital, is the key constraint for simplicity.

Anthropic's product teams abandoned formal specification documents for simple bullet-point lists. This minimal approach to planning reduces overhead, enabling them to build and ship entire features in days, not the weeks or months required by traditional spec-driven development.