Key Takeaways

  • The bottleneck in product development has moved from technical capability to human ambition. AI tools already let one person write code, build prototypes, and run financial models in minutes.
  • Tara Seshan, product lead for ChatGPT Work and Codex at OpenAI, argues that top operators do not use AI just to automate rote chores. They use it to widen their scope of action.
  • Product managers no longer serve as mere translation layers between engineering, design, and finance. They can directly spin up functional assets across every discipline.
  • Borrowing from economist Tyler Cowen and Stripe co-founder Patrick Collison, Seshan pushes teams to ask what the 10x larger, faster version of their current project looks like.

The Possibility Ceiling Has Moved

For decades, product roadmaps were constrained by bandwidth. If you wanted to test a new product idea, you needed an engineer to write the backend, a designer to build the mocks, and a data analyst to model the revenue assumptions. That meant ideas stayed in backlogs for quarters.

Seshan points out that this constraint no longer exists. When technical barriers fall, execution limits evaporate. As Seshan notes, “We kind of all have that superpower now that I can spin up a set of designs on something and I can go build an initial prototype of it and I can figure out the right pricing model for it and model out all the scenarios. The set of possibilities have widened dramatically.”

The ceiling on what a small team can ship in a week is no longer set by engineering hours. It is set by the scale of what the team dares to attempt.

From Task Automation to Expanding Scope

Most people still treat AI as a faster typewriter. They use it to summarize long email threads, draft routine memos, or clean up meeting notes. Seshan argues that treating AI as a pure efficiency tool misses the entire point.

“The people that we see who are most effective at using AI tools don't simply use it to automate wrote tasks but use it to expand the set of things that they are capable of doing,” Seshan says.

When a single person can build a working prototype, design the interface, and draft the financial projections in an afternoon, the old definitions of functional roles collapse. A product manager who once spent weeks coordinating between four departments can now build and test the first version alone. The value shifts from coordinating workers to choosing the most ambitious direction possible.

Asking the 10x Question

To break out of legacy timeframes, Seshan looks to historical precedents of extreme speed. Patrick Collison keeps a public catalog of fast projects: the Eiffel Tower built in two years, the Apollo program putting a man on the moon in under a decade, JavaScript written in ten days. These achievements happened without modern computing because the teams operated with unreasonable expectations.

Seshan applies the same pressure to modern product teams through a practice popularized by Tyler Cowen. As Seshan explains, “Tyler Cowen has this statement on his site which is that most people underrate the impact of going to someone else and saying hey, what is the more ambitious version of what you're doing, or couldn't you try this faster, or couldn't you try this at a 10x bigger scale?”

When execution speed increases by an order of magnitude, setting modest quarterly goals is a waste of capability. If your team can build a prototype in two hours instead of two weeks, your goal should not be shipping the same roadmap slightly earlier. Your goal should be solving ten times more problems.

What to Do With This

Take the biggest project on your team's sprint board for next week. Open a blank document and write down two answers to these questions: "What would this project look like if we had to ship a testable version by Friday afternoon?" and "What would this look like if it served ten times more users with zero extra headcount?" Build the functional prototype using ChatGPT or Codex before your next standup.