Closing Keynote · 16:30 · 39 min

Move Early, Commit Carefully

Simina PasatFormer VP of Product, GitHub

AI made building cheap but promising did not get cheaper, so build to learn and commit only to what deserves a promise.

Simina Pasat
Chapters
Highlights

The moments worth replaying.

Short clips, each a complete thought. Share them, or jump to the spot in the full talk.

Punching the wall harder is not progress

The Eileen Gu analogy that frames the whole talk, landing on the line that it has never been easier to build something nobody wants.

5:21 IN THE TALK · 73 S
Xbox saw Twitch coming and never committed

A vivid story of a company that had the prototypes but lacked a top-level commitment, and why AI still does not fix that.

11:06 IN THE TALK · 83 S
The bank that chose a ten-person startup

Her biggest learning from Copilot Enterprise: a regulated customer took a risk because the pain was that big, so build ahead of the models.

19:03 IN THE TALK · 71 S
Building got cheap, promising did not

The core argument plus her personal US and Europe synthesis: move fast, then decide what you commit to.

21:31 IN THE TALK · 90 S
Trader Joe's: 4,000 products, four times the sales

A surprising number that makes the case for taking features away instead of adding them.

31:29 IN THE TALK · 72 S
Push it until it breaks

Her closing advice, made credible by her own new chapter of building hands-on after leaving GitHub.

36:11 IN THE TALK · 69 S
In short

What Simina argued.

Simina Pasat closed the day with a homecoming. Fifteen years ago she came to Munich for a master's at TUM, worked at hybris, then moved to Seattle for Xbox and GitHub, where she was most recently VP of Product for GitHub and Copilot. She opened with Olympic skier Eileen Gu's line that hard work is overpraised and direction underrated: working harder means punching the wall harder, direction means noticing you can walk around it. Translated to product, hard work is building and direction is deciding what to build, for whom and why. Her warning: it has never been easier to build something nobody wants. The old cost of engineering forced product teams to ask the boring questions early. That forcing function is gone.

Her advice is to build to learn, not to commit. Write down the hypothesis and what success looks like first. Customers loving a demo is not success, because they can love ten other products like it. Two stories showed the gap between a demo and a product. At hybris labs her team built a digital wine shelf that lit up recommended bottles in the store. Retailers loved it, but moving it from the lab into the business was the hard part. At Xbox she worked on Game DVR while Twitch took off. The team built prototypes, but a bet that size needed someone at the very top to commit, and nobody did. AI does not fix that: you can build Twitch overnight, but not the distribution and network effects.

At GitHub she joined Special Projects, formed after the Microsoft acquisition to win back developer trust. In one year they shipped over a hundred changelog improvements, and betas drew tens of thousands of developers. One fast team stress tested the whole organization. Release processes, reviews and a comms team needing days for copy on something built in an afternoon started to break. AI now gives every team that speed, and when judgment cannot keep up, you build the wrong thing faster. Atlassian surveyed about 1,000 product people: 80 percent ship faster with AI, customers see no more value. Customers also stopped waiting. Banks, German carmakers and healthcare companies want to try a demo the same day. IBM found two thirds of CEOs invest before understanding the value.

Her sharpest story came from launching GitHub Copilot Enterprise. While her team was still prototyping AI code review, a financial institution that never ran betas was already piloting pull request reviews with a ten-person startup. Two lessons: build ahead of what today's models can do, and startups may make mistakes a large vendor cannot afford. GA still means security reviews, compliance, SLAs, support, docs and pricing, plus a promise to keep it working for years. She then asked where product advantage still holds. Adoption starts bottom-up, as GitHub and later Cursor, Claude Code and Codex spread from personal accounts into companies, while commitment happens top-down. Value moved from access to usage to impact, and pricing followed from per seat to per token to Intercom's 99 cents per resolved ticket.

If outcomes are what matters, only features that drive the outcome deserve to exist. Anyone can add now; the skill is knowing what to take away. Trader Joe's stocks 4,000 products against a typical supermarket's 50,000 and sells about four times as much per square meter because customers trust the selection. Agents are becoming the customer, and they do not see your onboarding or landing page, only whether the tool call worked. The advantage goes to whoever learns fastest, compounded through context, trust and community. Simina left GitHub this summer and is building hands-on again, running a Friday retro with Claude on what pushed the limits and what she learned. Her closing line: move early enough to learn, and commit carefully enough to endure.

Key takeaways

8 things to take back to your team.

  1. Before building anything, write down the hypothesis, what you want to learn and what success looks like; customers loving it is not success.
  2. Ask the boring questions while the demo is still exciting: does it solve a real problem and will anyone pay for it?
  3. Build ahead of what today's models can do, because the model you are using today is the worst one you will ever use.
  4. When one team speeds up, check release, review, documentation and comms processes, because they were built for a slower pace and will break.
  5. Launch with the outcome, not the feature: show measured impact from internal use and pilot customers, like review time dropping from days to hours.
  6. Define one impact metric tied to the problem statement, because boards and CFOs now ask for ROI rather than activation or adoption rates.
  7. Spend as much judgment on what to remove, combine or kill as on what to add; users and buyers cannot absorb more.
  8. Pick one thing each week that pushes the limits with the goal of learning fast, and run a Friday retro on what you learned.

For a product team, AI made building cheap. But promising didn't get any cheaper.

You can copy features, but you cannot copy where people are.

Move early enough to learn, and then commit carefully enough to endure.

Slides

The slides that carry the argument.

Download the deck (PDF, 32 slides)
Slide 3Slide 4Slide 12Slide 16Slide 21Slide 23Slide 28Slide 32
Show all 32 slides
Slide 1Slide 2Slide 3Slide 4Slide 5Slide 6Slide 7Slide 8Slide 9Slide 10Slide 11Slide 12Slide 13Slide 14Slide 15Slide 16Slide 17Slide 18Slide 19Slide 20Slide 21Slide 22Slide 23Slide 24Slide 25Slide 26Slide 27Slide 28Slide 29Slide 30Slide 31Slide 32
Mentioned on stage

Names, numbers, sources.

About the speaker

Simina Pasat

Simina Pasat was VP of Product at GitHub, where she led product management for the developer platform and took GitHub Copilot Enterprise to general availability. Before GitHub she was at Microsoft, with earlier stops at Xbox Live, SAP hybris and 4PSA. She holds a Master's from TU Munich and now builds again hands on in Seattle.