Microsoft CPO Aparna Chennapragada on AI, agents, and the future of product building

Executive overview

Most product builders are watching AI change the industry rather than living inside it. Aparna Chennapragada, Chief Product Officer at Microsoft, argues the only way to build well in this era is to prototype constantly and operate one year ahead of where the market is.

The core shift: AI compresses the inner loop of product discovery but raises the bar for what ships at scale. Taste, editorial judgment, and knowing when to solve versus scale matter more, not less, in a world of infinite prototypes.

The product builder who isn't prototyping with AI is already behind.

NLX: natural language as the new interface layer

  • NLX (Natural Language Experience) is the new UX — conversational interfaces are not undesigned, they have grammars, structures, and invisible UI elements.
  • Prompts are a new UI primitive, like dropdowns once were.
  • Editable plans are an emerging construct: agents should surface a plan the user can modify before acting.
  • "Showing the work" requires calibration — too verbose feels like a cron job; too terse loses user trust.
  • Follow-up suggestions must be explicitly designed: too many annoy, too few waste an opportunity to guide users toward a happy path.
  • Personalization of interaction style (TLDR vs. step-by-step) is underexplored and ripe for product investment.

What agents actually are

  • Agents are defined by three properties: autonomy (delegation of higher-order tasks), complexity (multi-step goals, not one-shot requests), and natural interaction (conversation, not just chat).
  • The current era is the "assistance era" — human in the driver's seat with AI co-pilot. Agents increase the autonomy dial as model reasoning improves.
  • Useful example: asking a research agent to review all participants in an upcoming meeting, surface their views on a topic, and draft a persuasion pitch — this surfaces insights a human wouldn't have assembled alone.
  • Asynchronous operation is a defining property: agents work when you're not at the keyboard.

How product development is changing

  • Prototypes before memos: if you're not building to see what you want to build, you're doing it wrong.
  • Prompt sets are the new PRDs — insist on them for any new feature or project.
  • Time to first demo is much shorter; time to full deployment is getting longer. These move in opposite directions.
  • Supply of ideas and prototypes is increasing by an order of magnitude — this raises the floor and the ceiling simultaneously.
  • The editing and taste-making function becomes more important, not redundant. Without it, you get a Frankenstein product.
  • Full-stack blurring at the early-stage is real, but a few tastemakers at the center remain essential.

On coding and the PM role

  • Coding is not dead — abstraction layers keep rising (assembly → C → higher-level languages → natural language), but understanding computer science as a mental model remains essential.
  • "Software operators" may outnumber software engineers, but the discipline of programming thinking persists.
  • PMs who are primarily process managers are at risk. PMs who do taste-making and editing are more valuable than ever.
  • Gatekeeping on ideas is dissolving — smart engineers, designers, and researchers now have an expert in their pocket to round out their pitches.
  • The WWXD (What Would X Do) use case: use deep reasoning plus relevant context to simulate how a specific person would respond to a pitch.

The Frontier Program: living one year ahead

  • Microsoft's Frontier Program institutionalizes "living one year in the future" — giving early adopters access to cutting-edge experimental tools without forcing whole-company readiness.
  • B2B product development requires Van Damme-style splits: compressed AI cycles on one side, slow-moving human habits and change management on the other.
  • Don't hold back early adopters while waiting for the whole org to catch up. Run parallel tracks.
  • The key question the program asks: if you had all AI tools and advanced deep research intelligence available, what would your workday look like?

Framework: three inflection points for zero-to-one products

  • Great new products require at least two of three inflection points:
    1. Tech inflection — a step-function improvement in capability (deep learning for Google Lens, LLMs now).
    2. Consumer behavior shift — a change in how people act that creates new demand (camera-as-keyboard once storage became free).
    3. Business model shift — a new monetization unlock (SaaS, zero-fee trading, outcome-based AI pricing).
  • "Why now?" has a structured answer: identify which two of three are in motion.

Solve before scale

  • Zero-to-one work requires a different posture: wide lurches are healthy, premature fixation on a local hill is fatal.
  • Avoid grown-up metrics too early — CTR and retention with 1,000 users are false precision.
  • Look for the "sound of click": the one or two things the product does remarkably well before claiming it can do everything.
  • Google Now example: great interface, intelligence wasn't there yet. The interface overshot the underlying capability — the opposite of today's problem, where models are powerful but the interface is still dial-up-era chatbots.

On Microsoft vs. cursor and the GitHub position

  • GitHub's advantage is systemic, not feature-level: it's the repository where all code ends up regardless of which coding tool is used.
  • Agent mode in GitHub Copilot is one of the fastest-growing, highest-signal loops in the product.
  • A single product (autocomplete, chat, or agentic coding) isn't the endgame — the Swiss Army toolkit that works as a system is.

Updating priors on AI capability

  • Models couldn't do image generation, data analysis, or deep reasoning a year ago. Priors formed from those failures need to be actively discarded.
  • A Chrome extension that shows "how can you use AI to do what you're about to do right now?" on every new tab is a forcing function for reflexive AI usage.
  • The arbitrage opportunity: builders who don't carry scar tissue from earlier model limitations can set higher expectations and unlock more from current tools.

More like this — when you're ready for early access.

Join the waitlist for a personal account and content recommendations based on what you're working on.

No spam. Unsubscribe at any time.

You're on the list. We'll be in touch before launch.

Get early access to the full library.

Join the waitlist for a personal account and content recommendations based on what you're working on.

No spam. Unsubscribe at any time.

You're on the list. We'll be in touch before launch.

Be among the first to get personalised recommendations tailored to your stage in business.

No spam.

You're on the list. We'll be in touch before launch.

Be among the first to get personalised recommendations tailored to your stage in business.

No spam.

You're on the list. We'll be in touch before launch.