How Much More Can We Do With the Same?

AI is software that can infer from data and context to produce predictions, recommendations, content, decisions, or actions that previously required human judgment.

That is my practical definition. It is not perfect, but it is useful because it gets us past two unhelpful extremes. AI is not science fiction, and it is not automation with better branding. It is a new capability layer. It can help systems perceive, predict, generate, reason, decide, and act with varying levels of autonomy and adaptiveness.

For product teams, the biggest shift is not just that AI helps us move faster. It is that AI collapses the distance between idea, prototype, evaluation, and launch. That does not make judgment less important. It makes judgment more important.

The risk is not that everyone can generate more ideas.

The risk is that we confuse speed with strategy, output with quality, and demos with durable product value. AI can make weak thinking faster, or it can make strong teams more powerful.

Our job as leaders is to make sure it does the second.

AI changes the altitude of product work

Historically, a lot of product development has involved translating ideas from one format to another. Strategy becomes a PRD. The PRD becomes a design. The design becomes tickets. The tickets become implementation. The implementation becomes analysis. The analysis becomes another round of strategy.

AI compresses that translation layer. A product manager can prototype earlier. A designer can explore interaction models faster. An engineer can move through boilerplate, debugging, and implementation alternatives faster. A data scientist can turn analysis into product-facing insight faster. Researchers can synthesize customer feedback more quickly. Editorial and merchandising teams can experiment with positioning, curation, and audience targeting in more dynamic ways.

That changes the altitude of product work. We do not have to debate every idea abstractly. We can prototype it, test it, inspect it, and evaluate it much earlier in the process.

But AI will not automatically tell us which ideas are strategically right, brand-appropriate, customer-worthy, technically sound, or operationally safe. It gives us more options. It does not tell us which ones deserve organizational energy.

That is still our job.

Product teams need to think about AI in three layers

The first layer is AI as a productivity tool. It helps with synthesis, prototyping, research summaries, competitive analysis, design variations, copy, test plans, debugging, and documentation. This is where many teams start, and it is useful. But it is only the beginning.
The second layer is AI as a product capability. AI can power better search, personalization, recommendations, content understanding, conversational interfaces, creative tooling, experimentation workflows, and operational systems. This is where AI moves from helping us build the product to becoming part of the product itself.
The third layer is AI as a change in user expectations. Customers are going to expect products to understand more context, require less friction, feel more adaptive, and help them get to the right outcome faster. Product experiences that feel static, generic, or overly manual will start to feel increasingly dated.

That means the better question is not, “Where can we add AI?” The better question is,

“What customer decision, workflow, or pain point can now be rethought because AI exists?”

Where can intelligence reduce friction, improve relevance, or create a better experience? How do we make these capabilities feel useful, trustworthy, explainable, and human instead of magical, confusing, or intrusive?

Those are product questions, not just technology questions.

The disciplines are getting closer, but accountability still matters

AI is bringing product, design, engineering, research, data, and editorial disciplines closer together, especially in the exploration phase.

A PM can build a rough prototype. A designer can explore product logic more deeply. An engineer can evaluate implementation paths faster. A researcher can synthesize patterns more quickly. An analyst can make insights more actionable. Editorial and merchandising teams can test how curation and positioning might change the customer experience.

That shared ability to make ideas tangible is powerful. It means teams can reason together around something closer to the actual experience instead of debating abstract requirements, static mocks, or long documents.

But there is also a risk. We can blur the difference between prototype and production.

Just because a PM can build a demo does not mean we can skip engineering discipline. Just because design can generate many variations does not mean we have a coherent experience. Just because engineering can move faster does not mean the product problem was worth solving.

The disciplines are getting closer at the exploration layer, but we still need clear ownership at the production layer. Product owns the customer and business problem. Design owns the experience quality and interaction model. Engineering owns system integrity, scalability, reliability, security, and maintainability. Research owns the depth of customer understanding. Data and analytics own measurement discipline. Editorial and merchandising bring taste, context, business priorities, and cultural judgment.

AI should reduce unnecessary handoffs. It should not erase accountability.

AI should become part of the product decisioning layer

In a streaming product, AI fits across the full customer lifecycle, but it shows up differently at each stage.

At acquisition, AI can help us understand audiences, position content, personalize messaging, and connect the right customer to the right promise.
At onboarding, it can reduce cold-start friction. Instead of asking users to do a lot of work upfront, we can infer preferences, ask lighter questions, and adapt quickly.
But discovery is where this becomes especially important. Search, personalization, recommendations, artwork, rails, summaries, trailers, metadata, and conversational discovery are all places where AI can help customers decide what to watch. During playback and engagement, AI can help with recaps, next-best-watch decisions, end-card recommendations, short-form discovery, sports moments, live events, and contextual experiences around franchises.
For retention, AI can help us understand churn signals, content affinity, household behavior, and the moments where a customer is losing value.

The larger point is this:

AI should not be a separate surface sitting off to the side. It should become part of the product’s decisioning layer. It should help the product become more adaptive, more contextual, and more useful throughout the customer journey.

In streaming, the job is not just to have a large catalog. The job is to turn that catalog into a personal, relevant, and valuable experience. AI gives us new ways to do that, but only if we connect the technology to real customer problems and real product strategy.

Faster ideation makes judgment more important

AI makes ideation cheaper. That means the bottleneck moves from idea generation to idea selection.

My bar is not, “Can we make a demo?” My bar is whether the work solves a real customer problem, improves a measurable business outcome, fits the product strategy, can be operated responsibly, and can be evaluated honestly.

I think we need to separate three different types of quality.

Prototype quality asks whether we can show that something is possible.
Product quality asks whether it is reliable, usable, fast, safe, accessible, and coherent with the broader experience.
Strategic quality asks whether this is the right thing to spend organizational energy on.

AI helps us generate more paths, but it does not remove the need for taste, prioritization, experimentation, and leadership judgment. In fact, the faster ideation gets, the more disciplined the release gate has to become.

Policy matters.

Every company adopting AI has to create rules that are clear enough to protect the company, customers, partners, IP, employees, data, privacy, and trust, but practical enough to help teams move.

Good policy should not only be a list of things people cannot do. It should create safe lanes. It should make clear what teams can do, what requires review, what is prohibited, which tools are approved, how to handle sensitive data, how to handle copyrighted material, how to evaluate outputs, and where to go when something is unclear.

If we only focus on risk prevention, we will move too slowly. If we only focus on speed, we will create avoidable risk. The goal is speed with guardrails.

AI changes leverage before it changes the org chart

I do not think the right frame is simply, “AI replaces jobs.” The more immediate and practical frame is that AI changes the leverage of every function.

The PM role becomes less about writing documents and more about judgment, problem selection, product strategy, experimentation, and driving clarity.
The design role becomes less about producing static artifacts and more about shaping intelligent, adaptive, trustworthy experiences.
The engineering role becomes less about manually producing every line of code and more about architecture, systems thinking, reliability, integration, review, security, and production quality.
Research becomes even more important because faster product cycles still need a grounded understanding of real people.
Analytics and data science become more important, not less, because we need to know whether AI-driven experiences are actually improving outcomes.
Editorial and merchandising judgment becomes more important because AI can generate and optimize, but it does not automatically understand taste, cultural context, franchise value, or brand strategy.

Over time, team size and structure may change. Smaller teams may be able to do more. Some coordination layers may become lighter. Some work will become more automated. But I would be careful about jumping immediately to headcount conclusions.

The first-order effect should be higher leverage. The second-order effect may be different org design.

The smart companies will not look at AI and ask, “Can we do the same with less?”

They will ask, “How much more can we do with the same?”

What success looks like

Successful AI adoption means AI stops being a novelty. It becomes embedded into how we work and how the product creates value.

Internally, success means teams use AI to move faster, think more clearly, prototype earlier, evaluate more rigorously, and reduce repetitive work. Product reviews become more prototype-driven. Research synthesis becomes more continuous. Experiment setup and analysis become faster. Content operations and metadata workflows become more intelligent.

In the product, success means customers find something they love more quickly and more often. Search works better. Recommendations feel more relevant. The homepage feels more adaptive. The product understands context better. We use content metadata, behavioral signals, creative assets, and editorial judgment in smarter ways.

At the company level, success means we build an AI operating model that is fast, safe, measurable, and differentiated. Not just lots of pilots. Not just demos. Not just activity. Real customer impact. Real team leverage. Real business outcomes.

AI will not make judgment obsolete. It will make judgment more visible.

When teams can generate more ideas, prototypes, analyses, and product paths than ever before, leadership becomes less about asking whether something is possible and more about deciding what is worth building.

AI gives companies a chance to create more customer value, more experimentation, more learning, more relevance, more creativity, and more leverage.

But only if we lead it that way.

AI is not magic, and it is not only a threat. It is a new capability layer. AI can make weak thinking faster, or it can make strong teams dramatically more powerful.

That is the leadership challenge in front of us.

This article reflects my personal perspectives on product management, AI, and content discovery. It does not represent the official position of my employer or any affiliated organization.