“Websites will transition to serving agents, as apps emerge as the primary medium for human engagement.”

That quote from Taneth Evans, head of digital at The Wall Street Journal, raises a question: what makes someone choose your product?

It solves a problem, makes life easier, saves time, keeps them organized or helps them make sense of what they need to know. The strongest products earn a place in someone’s life or work because they make something meaningfully better. They deliver real value.

We explored that question recently with a healthcare client that wanted to do more for its patients. The organization already had trusted expertise, treatment information, videos and practical resources. We could improve how patients found and used that content on the website. But a closer look at what patients were managing during treatment revealed an opportunity to offer more personalized, practical support.

A patient may be managing multiple medications, keeping track of appointments, coping with side effects and preparing questions for their care team, all while trying to understand each stage of their care journey.

That led us to explore a product that could offer tailored support based on each patient’s diagnosis and treatment plan: relevant guidance, timely reminders, clear next steps and an easy way to connect with their care team through MyChart when questions arose.

The product could turn the organization’s expertise into something patients could use day to day: guidance specific to their care, clearer next steps and support that could adapt to what they needed along the way.

How to find the right product opportunity

In the healthcare example, understanding what patients were managing helped us see an opportunity for more personalized support. With another client, the opportunity might be a tool that makes an employee’s day easier, helps a customer make a confident choice or gives people a new way to use a service.

Finding that opportunity means getting close to the people the product is for. What are they trying to accomplish? What matters to them? What do they enjoy, find frustrating or wish they could do? How do they approach those situations today?

I also want to understand why people approach things the way they do. One person may value having more control. Another may want fewer decisions to make. A product could save time, make a task more satisfying or give someone the confidence to do something independently.

That depth of understanding helps us create a product that feels relevant to the people using it. It fits how they live or work, responds to what matters to them and earns their trust over time.

How is AI changing the product development process?

AI is changing both how we bring products to life and what those products can do.

We can use AI to synthesize research, explore concepts, build working prototypes and develop requirements. During delivery, AI tools and agents can support development and testing. Strategy, design and engineering can work together earlier, using a prototype to test assumptions, refine the experience and uncover dependencies that shape the build.

AI can also become part of the experience itself. A conversational interaction might give someone a more natural way to use a service. Personalization could make the experience more relevant. An agent could complete a task with their permission. Each possibility comes with product decisions: what would help the user, what information the experience needs, how much control the person should have and where human review is important.

This is why technical fluency matters more now. Teams need to understand what different AI tools and models can do, where their limitations matter and how to integrate them into both the workflow and the product. That includes understanding the data and context they need, evaluating the quality of their output and making decisions about reliability, privacy, cost and human oversight. Engineering and quality practices need to evolve alongside those choices.

Product strategy gives those decisions direction. It defines what success should look like for users and the business, establishes the KPIs that will help us measure it and sets priorities for the roadmap. As we test the product and see how people use it, that evidence helps us adjust the roadmap: what to improve, what to expand and where further investment is justified.

The tools will keep changing, so the team needs to keep evaluating how it works: testing new approaches, measuring whether they improve delivery or product quality and turning what proves useful into shared practice.

Defining and evolving product success

A product needs a clear reason to earn someone’s time and the organization’s investment. Defining value means being specific about both: what should improve for the people using the product and what that should make possible for the business.

That value can take different forms:

  • A better customer experience may strengthen retention and loyalty.
  • Making expertise more accessible may expand service capacity.
  • An internal tool may reduce repetitive work, freeing people to focus on work that needs their attention.
  • A new digital product may create revenue or give the organization a differentiated way to deliver its services.

What should improve for the person using the product? What should improve for the business because of it? What evidence would show that those improvements are happening?

Those answers define success, establish what we need to measure and give the team a clear basis for deciding whether the product is delivering the value we expected.

Once the product is in people’s hands, we can test those expectations against actual use. We can see where people struggle, what they come to depend on and where their behavior differs from what we expected.

Someone needs to turn that evidence into decisions.

What should improve next? What should be removed? Which new capability is worth introducing? Where does the roadmap need to change, and where is further investment justified?

A product needs more than room in the architecture to evolve. It needs clear ownership, ongoing investment and a way to keep making those choices as customers, technology and the market change.

This is increasingly how we approach product work at Phase2. We bring strategy, design and engineering together early, define the outcomes we are working toward and use AI tools and agents where they help us explore, build or learn faster. Then we use what we learn to keep improving the product and adjusting the roadmap.

4 questions to ask before you build your next product

1. What real value will your product deliver to the people using it?

Be specific about what becomes easier, faster, clearer or newly possible for them. A useful test: would they notice if the product went away?

2. What can your product do that a general AI tool can’t?

If someone can get essentially the same answer from a general-purpose AI tool, information alone may not make your product distinctive. Look at what is specific to your organization: your expertise, services, data, relationships and the actions you can help people take.

This matters even more if agents become a main way people reach information, as Taneth Evans suggests. An agent can pull your content without a visit to your site, so the value has to live in what only you can offer.

3. What business outcome makes the product worth the investment?

Define the result that matters, whether that is retention, revenue, service capacity, reduced support costs, stronger engagement or something else. Then decide what evidence would show that the product is contributing to it.

4. How will you keep delivering value over time?

Watch what people use, what they come to rely on and where the product falls short. Make sure someone owns turning that evidence into roadmap and investment decisions.

The tools will keep changing. The work is knowing where they can make a meaningful difference and turning that possibility into a product people can rely on.

Planning your next product? Phase2's strategy, design and engineering teams work together from the start to define the value, build a working prototype and measure what happens next. Talk to our team.

‍