How Great Product Owners Get to Know Their Customers

At a lot of large companies, our customers are so far out of reach that we don’t know anything about them. We don’t have any direct access to customers either, so by the time we get any real information, it’s several layers removed. It’s really common for companies to protect access to customers, but getting to know our customers likes, dislikes and preferences is a great way to ensure the products we are delivering meet their needs.

If you want to go from being a good to great product owner, we have some tips and tricks for you to better understand and empathize with your customers.

Identify User Roles

The first step in understanding the different types of customers that use your product. This should be done as a collaborative effort with your Scrum team. You may want to also invite representatives from sales, marketing or customer service who may offer a different perspective.

The first step is to brainstorm any possible users of your product. Let’s say that you’re creating a mobile application for teachers to communicate with students. Set a time box, such as 10 minutes and have everyone submit as many possible ideas as they can. Remember, there are no bad ideas in brainstorming!

Some potential users for this app could be:

  • Teachers
  • Parents
  • Elementary Students
  • Secondary Students
  • School Staff
  • School Club Organizers
  • Coaches

Next, the team should organize these roles into categories that are similar such as “Staff” or “Students”, while eliminating any duplicate roles.

Finally, the team will discuss which roles are relevant to the product. The team may need to program the app differently between parents, teachers and students, but maybe there is no need to differentiate types of students.

Write Personas

Once you’ve determined the user roles that are relevant to the development of your product, a persona is a great technique for going one step deeper into understanding that customers. Personas should also be done with your team and representatives from marketing sales and customer service, if possible.

A persona is a way to bring to life the customer by thinking about typical characteristics. Some elements that you’ll want to put into the persona are:

  • Name
  • Description
  • Demographics
  • Personal
  • Goals
  • What does a day in their life look like?
  • Attitudes and feelings

Here’s an example for the persona of an elementary school teacher:

Tina the Teacher

Tina the Teacher works at a public elementary school. She lives in the suburbs in a middle class neighborhood and is a mother of young children herself. She loves working with children and relates better to kids than adults. She gets up really early every morning to make healthy lunches for her kids and to prepare her lesson plans for the day. She’s frustrated that she can’t see her students face-to-face and finds it difficult to effectively communicate to kids and parents with online learning.

While it may feel a bit fictional, base this persona on what you already do know about your typical customer. Some of it may be stereotypical or guesswork, but a lot of it should come from historical evidence in working with your customers in the past.

Personas should be done for all of your major user roles, and should be visible to everyone on the team and updated often as you learn more about your customers.

Create an Empathy Map

An empathy map is a way for your team to go another level deeper into understanding what your customers are thinking and feeling. To get started, you’ll want to focus the map on a specific persona. Once again, this should be done collaboratively with your team, not alone at your desk. Here are some questions to think about:

  • What do they think and feel (what really counts, major preoccupations, worries and aspirations)?
  • What do they see (environment, friends, what the market offers)?
  • What do they say and do (attitude in public, appearance, behavior towards others)?
  • What do they hear (what friends say, what boss’ say, what influencers say)?
  • Pain (fears, frustrations, obstacles)
  • Gain (wants/needs, measures of success, obstacles)

The empathy map activity is really helpful for product considerations and really understanding what your customers may find valuable.

Get Access to Customers

The best thing you can do, of course, is actually observe customers interacting with your product. Nordstrom did a great job of this when they built a sunglasses app in real time by talking to customers in the store. Wells Fargo nailed this when their execs went to bank branches and talked and observed customers using the ATM machine. Apple does most of its product development by talking to customers in the store.

At many companies your customers may be out of reach, but the closer you can reach them, the better you’ll be at creating products that are exactly what your customers need and value.

Lance Dacy is a Certified Scrum Trainer who’s passionate about applying Scrum beyond technology to all areas of business and life. If you’d like to become a Certified ScrumMaster®, check out the upcoming class schedule.


Related Articles

Reach-Impact-Confidence-Effort (RICE)

Welcome back (or just welcome) to our series on prioritization techniques. As I work with teams and organizations, I notice a huge component of planning missing in their endeavors; prioritization. I often say that a Product Owner's job is to maximize the amount business value delivered of a Scrum Team...

Read More

Impact mapping: Business goals to product backlog

Are you struggling with how to create your product backlog? You have a business goal but you are still unsure how to continue? Let me introduce you to impact mapping and why this is beneficial for building a backlog based on your business goals in no time. Impact mapping is...

Read More

Understanding Customer Needs

In the ever-evolving world of product development, understanding what your customers truly want stands as a cornerstone for success. This crucial insight not only shapes innovative products but also ensures they resonate deeply with your target audience. Let's dig a bit deeper on a few of the best practices for...

Read More

Product Owner Certification

Who is a Product Owner? The product owner is a key role in an agile software development project. They are responsible for defining the project vision and bringing that to the scrum team. The product owner creates the product backlog and sets the priority of the backlog items. They focus...

Read More

Eisenhower Decision Matrix (The 4D's)

Dwight Eisenhower was one of the greatest military minds and responsible for countless decisions during one of our world's most dire times (WWII). When I was in leadership training at FedEx (many years ago), I was exposed to the 4D's of prioritizing my tasks as a leader (Delegate, Delay, Discard...

Read More

How To Lead Innovation Workshops

As a product owner, it’s important that you’re always leading the team through product innovation ideas or your product can quickly become stale and boring! Without true innovation, your team just builds and builds, but doesn’t get to use their brains creatively, which can stagnant product innovation. In this article...

Read More

Story Mapping to Prioritize

As we continue on our series through the end of the year (the one that focuses on prioritization techniques for our Product Teams), we land on Story Mapping in this post. I normally wouldn't think of Story Mapping as a prioritization technique, but in certain situations, I think it's perfect...

Read More

Introducing the Top 10 Challenges of Product Delivery

Product Development is an exciting space and the sky is the limit on the products we can choose to develop. Naturally, the market for your product determines its success. You always have to have a great product idea, but then have to have a plan to execute better than your...

Read More

Anti-patterns of the Product Owner

Welcome back! In this session, we will focus on Product Owner anti-patterns. There is no doubt that the Product Owner is a critical role in Scrum. Essentially, they are accountable for maximizing the value that the Scrum Team collectively delivers. They straddle both worlds of Development and Business/Stakeholder Management. While...

Read More

RVCE Prioritization Matrix

For product managers working in Agile/Scrum organizations, featuring and task prioritization is important for effective roadmap planning. Out of all the features you consider, prioritization helps identify the order of importance and drives the delivery of the work that achieves organizational goals. We are continuing our series this year on...

Read More

How Getting to Small Helps Teams Get to Done

I recently visited with Brian Milner over at Mountain Goat Software to discuss some tips you might not be thinking about with Product Backlog Refinement and Team Design. Check it out here!

Read More