Key Takeaways

  • Unreasonable deadlines counter internal sandbagging: teams naturally set lower expectations for themselves unless pushed with intense urgency.
  • Technical excellence fails on its own; a pure engineering focus must pair with aggressive sales and marketing distribution.
  • Birdwatch, developed under Agrawal at Twitter, proved durable enough to become the backbone of Community Notes under Musk.
  • Technical leadership requires placing bets on the next two or three architecture hurdles before the current problem is fully resolved.

Unreasonable Urgency Beats Self-Imposed Limits

Most employees protect themselves by sandbagging. When asked for an estimate on a project, engineers and product teams add padding to guarantee they hit the target. It feels rational, but it silently slows companies down.

Reflecting on his time working directly with Elon Musk at Twitter, Parag Agrawal points to Musk's habit of setting extreme expectations as an effective tool against this dynamic. As Agrawal observed: “The urgency and the ability to compress time and I think having unreasonable expectations of people is mostly a good thing because most people don't understand what they're capable of and kind of implicitly sandbag themselves and implicitly set lower expectations of themselves than they're capable of.”

Demanding an impossible deadline changes the entire problem-solving framework. When an engineer is told to ship a three-month project in four days, they cannot just work longer hours. They have to strip out unnecessary scope, eliminate bureaucracy, and question core assumptions. Agrawal noted: “So when simultaneously inspired and pushed with urgency, people can do more than they thought. And I think he can sometimes extract that from people.”

Why Pure Engineering Is Never Enough

Early in his career as a technical leader and researcher, Agrawal believed that product quality was the only variable that dictated success. Build the best system, run the fastest models, and the market will take care of itself.

Building his new search company, Parallel, changed his mind. Technical supremacy without distribution is a dead end. “I started with a very pure technical and product focus like the only thing that matters is building the best technology and the best product. Nothing else matters. And now I see week on week value of having highly competent sales and being good at marketing.”

Product builders often treat sales as an afterthought or a necessary evil. In practice, great sales and marketing provide the feedback loop that prevents engineers from building features nobody buys. Even good internal systems require alignment with clear distribution. Agrawal pointed to Twitter's Birdwatch as an example of durable product architecture: “Listen, I always liked what we called birdwatch. uh which is now community notes rebranded.” Good technical foundations endure, but only if the organization survives commercial realities.

Preempting Technical Bets

Building scalable systems requires looking past the immediate blocker. Agrawal emphasizes keeping “technical intuition, centering a lot of what you do towards a longer term technical aspiration and as soon as you solve one problem trying to place bets on the next two or three preempting technical bets.”

If you wait until a technical bottleneck is completely fixed before designing the next architecture shift, your velocity stalls. High-performing engineering teams operate in parallel: while one group executes on the immediate deliverable, leadership tests the structural bets required for the next order-of-magnitude scale.

What to Do With This

Look at your roadmap for next sprint. Pick the project with the longest estimated timeline, cut the deadline by 60 percent, and ask your team what they would need to cut to ship by Friday. If they argue it cannot be done, ask them to identify the single dependency slowing them down and eliminate it immediately.