Customer Discovery Across Product Stages, with Ashley Phillips
Customer Discovery Across Product Stages, with Ashley Phillips
[00:00:00] Assumptions Go Stale
Dianna: Products don't need to stop changing just because a team thinks it understands the customer. What I mean by this is an assumption that was true two years ago can quietly go stale as customers' environment or expectations or even the workflows, how they're using the product, how those things change.
That matters when discovery, prototyping, and release carry different levels of risk across startups, hypergrowth teams, and established hardware and software products. The faster the environment changes, the more important it becomes to keep checking what we think we know. Today, Ashley Phillips and I talk about what customer discovery looks like across these stages, how users surprise teams with new uses, and how to keep assumptions connected to real people rather than personas and old reports.
We also discuss why engineers should get closer to customers, how prototypes help reveal what people actually need, and a simple Monday habit for staying honest about what the data is telling you.
[00:01:16] Meet Ashley Phillips
Dianna: Let me introduce Ashley Phillips after this brief introduction
Ashley Phillips is a product leader who's built products at some of the most recognizable names in consumer tech and fintech: Groupon, Venmo, PayPal, and more. Across her career, she's launched B2C and B2B experiences at marketplaces, fintechs, and consumer startups from early-stage teams to hypergrowth companies and big established products.
She's led products through very different outcomes and phases, which gives her a grounded view of product discovery that most of us don't get
Let's jump into my conversation with Ashley
Ashley: you've worked across startups, acquisitions, hypergrowth teams, and established products. What's the one discovery lesson that has held up in every single one?
[00:02:52] Venmo Debit Card Surprise
Ashley: I think one of the biggest lessons, and a thing that I'm, even though it happens over and over again, I'm always pleasantly surprised by, very often, what customers tell you or potential customers tell you during discovery, once you actually get a product out into their hands, as long as it's useful to them, they will find brand-new ways to use it that potentially you weren't even thinking about.
an example of this, um, at Venmo actually, when we were launching the debit card,
you know, six or seven years ago,at the time as we were working on launching it, the hypothesis really was, like, people hold an average amount in in their Venmo balance. It's kind of like found money. They forget that it's there. Like finding 20 bucks in the back pocket of jeans that you wore the previous weekend.
And we wanted to give people a way to spend the found money in real life. So that was the hypothesis going in and we built that product around that. what we saw when we launched it and people did use it that way, we also saw this activity. Venmo has typically been used as sort of like a payback mechanism.
Like, you go to brunch, one person puts their card down, you split it, people Venmo you money. But what we saw happen with the debit card is people would get the bill for brunch, they would pre-pay the person with the Venmo card, and then the person would put the Venmo card down. So they would never be out that cash from their credit card or from their bank however that they were paying for it.
So we saw this sort of pre-pay flow, which was not something that, ... Pre-pay before or Venmoing before they used the debit card, which was not something we had really thought about as a use case, but we saw it again and again which was really cool. one thing I continually love about product working in product management and working in tech, is just this idea that you can build something, you can have some ideas about it, you can then put it in people's hands.
And humans are so innovative they will find new ways to use the tools that you give them
Dianna: I like that because I'm from a risk management reliability background, so my first thought is usually there's gonna be new ways that it's gonna break that we never even thought about. But I like your perspective that people will find new ways to use it or new uses for the things that you develop.
And so I guess there was a, a little bit of a disconnect between any of the pre-work or the conversations you'd have with customers beforehand about it, and then what actually happened in real life?
Ashley: I don't know if there was a disconnect as much as there was maybe like a yes and. and I think listening to what customers tell you with their words but also with their actions within the data that you... If you're looking at product usage or what they're buying or what they're doing.
paying attention to that part after the and can really unlock, let's be idealistic here as, as I am often in this industry right now. But, you know, paying attention to what happens after that and can certainly unlock like new iterations of a feature, new features, but even like new business lines.
[00:06:17] Discovery Never Stops
Ashley: So, um, that's where I think, um, I think a lot of times just like this idea of discovery, we think about discovery as something that happens before like before we work on a product. But really as you're launching, you're continuing to learn, and it's just going on all of the time
Dianna: You would wanna try to do as much upfront discovery as you could, right? Because it's setting the s- the space for the product and everything. So when a Team says customer assumptions they have a certain idea of the who, the problem that this product is serving, the behavior and the intent.
what are they most holding onto when, when they think they've known the customer?
Ashley: I think when we think about teams holding onto those customer assumptions, um, you see it or you can see it play out in different ways at different types of companies. So, multiple times in my career I've gone into places where the product has been around for a while. So let's say, five or 10 years, or the company has been around for a while, five or 10 years, and I think that sometimes you come in and there's a really, obviously there's a really clear idea of who that customer is, but sometimes there's also this idea of, um, I've had this happen several times at different places, where you come in and say like, "Oh," like, "What do we think about this?
What do we think about this?" In terms of feature set or a problem that, you know, you might be hearing from customers from, like, an existing customer base. And you will certainly have people within the company who said, "Oh, we've tried that before and it didn't work." Or, "We've tested that and, you know, several years ago we tested that."
And I think that something that when I hear people say that or think about that sometimes we have this idea of not just who the customer is, particularly if you've been working at a place for a little while, but, like, the the environment and the world in which they're operating in, meaning that just because you tried something two years ago And it didn't work.
There could be a ton of reasons why it didn't work. Execution could have been bad. It might... Or, like, not quite right, or the solution didn't really solve the problem. Um, you know, not the right time. Different things like that. But I think the big thing as we think about particularly the world we live in today, both in terms of product development and just the macro world, the world is changing all the time.
So, like, the demographic of the customer or the customer segment might be the same. But the world in which they're living in from two years ago, as an example, two years ago to now, has completely changed. Like, even thinking about the super nerdy stuff that I I sometimes think about, which is just thinking about, like, the expectation of design interfaces.
what people are used to interacting with five years ago certainly is different than two years ago versus now. Do people want to download an app today? I think most people would say, "No, I do not wanna download another app. I don't need another app." People are used to interacting with technology in different ways today.
A lot of voice, obviously a lot of chat with, with agents proliferating everywhere, and people... A lot of people using, like, ChatGPT or Claude, et cetera, et cetera, or Gemini, on a daily basis.
Some of the assumptions about the, the customer may actually be the same and stable and that demographic over time. But really interrogating this idea, the problems or the needs in the customer may change, and I would expect them to change just because...
Or their expectations may change just because of the world in which they operate. And so their expectations of the product, of the interface, those types of things can evolve and should evolve. And peop- just I think it's important for teams to be aware of that
Dianna: And I, I've seen that happen in other industries that maybe don't move as fast as as the software industry today. And it could even be a, a medical device that's been tried and true and the leader in whatever application that it is. It is still the leader, so it's consistent and it's true, and the customer assumptions have been around for a while, like you said.
It's a, it was a defined product. But the environment in which it operated had changed, and it was the machines that would connect up to it to make it work had changed a lot. Or there were similar procedures that physicians would do that the way that they did those procedures had changed, and so they started to expect different things out of the product, too.
Yeah, en- environment does seem to be a big factor, especially for those products that have been around for a long time. So yeah that's interesting.
[00:11:26] Discovery by Stage and Risk
Dianna: So we talked about products that are around for a long time, but I wanted to ask about your experience between the early stage startup versus the, the hypergrowth of things that you're growing fast and then also this big established product that we've been talking about.
Is discovery the same craft at different speeds for each of these situations, or does it genuinely change? Is it really different depending on what you're working on?
Ashley: Yeah, so I think it's different certainly at stage, It's also certainly different if you're working on software versus hardware, and also hardware and software combined.
Somehow I've been lucky enough to work in all of these, work in all of these situations, so I'll talk about all of them. So, When you're working in that zero to one space, On the software side certainly, and I've done this a couple of times. I did this at a company called Modus that was then acquired by PayPal, and that's how I, I landed into Fintech.
And then also, same founders but much later on, um, at a company called Galactik, a Fintech startup. for both of those companies, what discovery looked like certainly was still talking to customers. But when you don't have like an established or potential customers I should say, or what we thought of as like our target demographic, and like getting things in front of them and like really vetting, trying to vet out those assumptions.
The the benefit certainly of software and the freedom of having very few customers is, uh, is that you can try a lot of things. You can, get things in front of people, and it's very low risk to, um, just push something out and like iterate it, like keep iterating on it like day after day.
Especially with when you're working, you know, with a really small team. Those feedback loops are really tight. Everything can move a lot more quickly, and the risk is super, super low. You're not gonna alienate customers 'cause you maybe don't really have any yet. So , so you're, you know, you're really building and you're figuring it out as you go along.
And you're getting reads from like those potentials of who you think might be that customer, and you're getting reads from things that you know in the industry. Investors are always gonna tell you what they think. Um, so you're kind of getting all this information back. For for bigger products at more, at like, you know, we can talk, uh, we can talk about Venmo again.
Um, and interestingly enough, like I was at Groupon during a crazy growth phase, after it went public and it was kind of like s- what I would think of as like kinda settling in. So that's also kind of interesting to be like from like crazy hyper-growth where everything feels insane In a good way. Like things are so successful, the ground is like changing underneath you as you're going. I mean, it's a, it's heady and a, and a lot of fun. Very different than a place like Venmo where for many reasons it's a lot higher risk. So the discovery, you can take more time with discovery.
You can take more time with user research. And we certainly did. So as an example going into, that, debit card launch, we did in-depth diary studies with potential users about their financial habits, which is really difficult to get people ... Like, doing user research about money and how people spend their money can be challenging to get people to be, like, honest about, how they're spending what they're doing.
So that's a different challenge. But beyond just having, like, an established customer base there, there's also a ton of risk. You can't be really cavalier with the things that you're rolling out to customers. Both because you have this established user base, but also just in fintech in general, there's a ton of compliance.
There, there are a ton of constraints around compliance, around disclosures, around different things that you need to do, about things you need to watch out for, um, in terms of fraud vectors or risk vectors. So there's a lot more that goes into it. I will say that, like, going f- from, um, going from, like, being acquired, being at a, you know, 19-person startup that was, like- You know, zip and zip and zipping, and then getting acquired by PayPal was an amazing experience, and I, I learned so much, but also was, like, a cultural adjustment, um, because you're like, "Oh, we, we work in a different kind of environment now, and there are things about that that we need to adjust to within that environment."
[00:16:14] Hardware Raises the Stakes
Ashley: for the past maybe two and a half years I actually just started a new job about six weeks ago. But prior to that, for the past two and a half years, I was leading product at a company called Aura Frames. Aura makes Wi-Fi-enabled photo frames.
So the idea there is, I don't know if you've ever used one. They're really amazing devices
Dianna: that was last year's Christmas gift to the grandparents.
Ashley: Perfect.
yes, that is the use case we are big at, that, or Aura is big at Christmas with grandparents. It's an incredible gift. It's an incredible piece of hardware. And how kind of the software and hardware go together to make all that magic happen is really great.
So that for me, that was an adjustment in a different way in that was the first time I'd ever worked on a hardware product. I was amazed at the pace at which the company worked to be able to go from idea to this this new device or this new SKU is on shelves was pretty incredible.
But it's still a different, again, like a higher risk which your listeners are obviously very familiar with, but a higher risk release in that with software you can release a new version of the app or, you can make a bug fix. Where something is wrong on the physical device itself, not just the firmware, having something go wrong there is a lot different.
So we did a ton of testing, we did testing and research on the software aspect of it, obviously, and like different delighter features and fun things we were doing between software, like both on the app and on the frame. But also just the physical mechanics of Button press.
Like where do, where should buttons be placed? is this the right spring of the button? Aura hasa touch bar on the top,
And so testing that with people and seeing how like watching them navigate, like how can how can we improve that? So there's a ... it's very different. I actually was on a panel last year and had someone ask me "How is hardware product management different than software?"
And I'm like, it's from my point of view, I think it's, one it's a lot harder because it feels like a, it feels like a higher risk. it's a higher risk release or like release cycle, product release cycle. But the, I think that in the hardware situations or when you're releasing or working on a hardware product, that discovery becomes so much more important.
You really need to be sure or as sure as you can be. You're never sure. But you need to be as sure as you ca- as you can be that what you're putting out into the world is as close to perfect as it can be, which is a very different philosophy of a lot of startups, which is move fast and break things.
You have to have a different balance with hardware products, but also get things out so that they're fast enough and be innovative and all of that. So there's a lot. Hardware's hard.
Dianna: That's also what makes the engineering field so interesting to work in. just to let you know, the Aura Frames I am a mechanical engineer. I'm big into usability and systems, and I loved it. I thought it had great usability for my parents and my in-laws, and then for us to be able to be a part of showing what pictures show up and stuff.
I think the discovery you did for that product was well done. Well done to the Aura team. So yeah, so these different categories or stages of development and business sizes, it seems like it's more to do with the maturity about who your user is. Like how well you know your target user market.
who they are and then also just the, the risks of the changes that you make. Like you mentioned, the regulatory risks and then in hardware, software development combos, just the risks of designing a physical attribute a little too early or not quite in the right way.
[00:20:20] Talk to Users and Prototype
Dianna: So among all of these things, are there any discovery methods that work well across all of these situations, or it all depends on your maturity about your user base and the risks that you're looking at?
Ashley: my viewpoint on it is, or what I always try to bias toward, and part of this is I always want to talk to people. I think that, at many companies, not at many companies, but I think at bigger companies you find that, user research more specifically might be run by another team. And so you might have the user research team who's actually talking to users or a particular audience segment or, potential users.
And they then are distilling these things back. They're making recordings. You could watch the recordings. But for me personally and for my team, like my product managers and designers, and then also the engineers that are on the team, it is so much more powerful to actually talk to people or to hear people in the moment say those things.
even if you're on a Zoom, and usually you are in this day and age with those users. So I think number one is really talk to people. There are really cool to- tools now though, I will say, and we're using them at my new job quite a bit, which is cool, and there aren't many companies that do this, but, like, where you have software that can basically run user interviews. Like user interviews with video asynchronously. So you've given them a script. You've given the software a script, and so it's running through that with real people and responding real time.
And the results that we've seen from some of the tools that we've used have been really, have been pretty good. You can go back and watch the videos. But I still think regardless there is some magic in talking to someone and having them communicate with you directly and being able to respond to that real time.
I think the other thing is just To the extent that you can get something real in people's hands whether that's a piece of software on a screen or on a phone some type of prototype, whether that's hardware or software, I think is kind of the, is the best way to get To get a, a gauge asa good of a gauge as you can about what might happen. And I think part of what makes startups true startups, where you're going like, zero to one, so exciting, is that you can do that in a really low risk way pretty quickly. you're obviously prototyping if you're working in hardware as well,
It might be, like, a harder lift to actually deliver a prototype or deliver a prototype piece of hardware or, it might be a 3D printed something that is not totally representative of the product experience. But getting something to people, and kinda going back to what I was talking about at the beginning, is users always surprise you, and it's I think that's so fun.
And so as much as you can front load that piece of it before you get it out into the real world and learn from them, to me, regardless of stage is kinda the best way to do that.
Dianna: Now speaking to customers and getting a prototype in front of their hands, where do you think that happens the hardest, or at what stage do you think it's the most difficult? Is it when you're developing a new product, when you're pivoting when you're part of an acquisition, a mature product that everyone thinks they understand already?
Ashley: Oh, I think the hardest thing is, the best, the easiest thing and the best thing, the thing you wanna hear is you've built a prototype and you get it into people's hands that are like, "This is awesome," and they're like,
Dianna: Where do I sign up?
Ashley: Yeah, exactly. "How can I pay you for this?" And and I think that what can then be hardest and also disturbing, which we started this with talking about customer assumptions, is what can be hardest is when people don't respond positively.
So essentially, you go into that or you go into, you go in talking to users and you have this idea in your head, you have this hypothesis. You may be clinging to it and you may not actually realize how much you're, like, clinging to it or assuming that it's not a hypothesis, it's a fact.
You know? Like, in your mind you may believe that it's true. And so I think then what is hard is then adjusting. And, it can be hard to adjust to that depending on, like, how much you were clinging to that as real truth. I think it's easier to adjust or it can be easier to adjust early, early stage.
But it can be easier to adjust, again, because of the lower risk. But I think, I think it's really, I think it's, it's really about, like, how willing are you and how open are you, and to a certain extent, like, how humble are you? I, I often talk about product managers as like they, they're like Type A personalities and they wanna get an A on their report card.
Being able... That's just the personality type. I am that personality type. But like, um,it is required that you then be 100% open to what can I learn here?
And like, I am learning here and I am listening, and I'm listening to what I'm hearing from research, what I'm hearing from the market, what I'm hearing from people, what I'm, like, learning through this process. And you're probably, if you're doing it right, you're gonna take a whack to your ego and the things that you thought were true you're gonna learn that they're not and being able to adjust that.
And I think that if, not just product managers, but product managers, designers, engineers, anyone on the team can be in that mindset, what you, and you land on the, you will land on the right answer. You will land on the right solution. You will land on the right feature set. And hopefully be super successful
Dianna: is there a specific signal that it's time to retest something that you thought you know? Or is it based on, like you said, this continuous engagement with the customer
Ashley: So I um, I really like to be continuously engaged with the customer. I had two thoughts about this. So one and we did this at Aura. When I came to Aura, there was research going on, but Aura's small. Aura is a very lean company for kind of the, the size of its brand and the size of its business. Like, the team is very much operating with a lean mindset, like very scrappy and feels very much like a startup even though it's, it's been around for 10 years.
As a result not a ton of research going on or talking to users when I got there. a lot of the user voice was filtered through this really amazing customer experience team, so like a support team. And what I tried to do when I got there, just because I'm like, "I need to understand this customer in a more visceral way than what I'm reading from," you know, marketing decks that, are a year old or what I'm hearing from customer support, and all of that is super valuable, but we just started a a cadence of okay, on Fridays from 11:00 to 2:00, we are going to talk to customers every Friday.
And so design, product research, a- anyone who wants to... And anyone who wants to come can come. We will record them. We will, post them on the company Slack. We will then periodically, roll up insights. And sometimes we had specific things we wanted to, talk to users about. We wanted to get design concepts in front of them.
We had a hypothesis about something and wanted to talk to them about a particular problem set. But a lot of the time, it was just like, "You're an Aura customer," "tell me, like, how did you hear about Aura?" "How do you use it? Where is it in your home?"
Really just trying to keep a bead on that, and I think what was helpful is that, again, and this kind of goes back, and this is also a little bit of my personality too, is that it's really easy to Think about the customer as like this persona as opposed to an actual person. And so that like you have this idea of "Oh, this person..."
And I'm, this is not, "Oh, this person is like this age, they live here, this is their salary, they do X, Y, Z. This is what they care about." And those are, like personas are helpful like as a shorthand, but there, again, like there's just something about like staying in touch with that, and for me like really important to like kind of stay, to in order to stay in touch with that, that is different than reading the persona, on the slide.
So I think that's a thing. Going back to the part about, when do you... I think it's important to always stay in touch, but I also think there's an opportunity to interrogate we have this like long-held belief, when is it time to reexamine that? so I talked a little bit about coming into a new place that's been more established and have, have new ideas.
Or any new employee coming into any new place and say like, "Oh," like, "Oh, I think this would be an interesting idea" or what about this, what about this. Um, I think if you are the employee who has been there for some period of time and new people come in and have all these ideas or new ideas, or maybe ideas that were tried before, and you have a reaction of like, "Ugh, we've already tried that," then it's time then it's time to be like, "Hold on," you know?
Like, "Hold on. Let's pull that apart." I think when you start to feel that, and I have been that person before too, so, you know. So like when you start to feel that, um, inside yourself, like recognize it as a signal for, um, what's happening here? Why am I resisting this? Let's go in and look at this again.
Uh, because I actually think that like people coming in new with fresh eyes, that is the best time to get feedback on what you're doing. And it can hurt. You know what I mean? Like it can be very painful to get that feedback, but I think it's, it's powerful and, it's so valuable
Dianna: I can definitely relate to that too. I think all of us probably can 'cause it's it's also resistance to change or doing it again. but I like looking at that as just a signal to take a look at the assumptions that we've had about this product that might have been out there for a long time, or maybe not very long, uh, because they may have gone stale, right?
[00:31:24] Engineer Closeness and Monday Habit
Dianna: Yeah, I like that so if there's an engineer, uh, working on a product it doesn't matter what kind of company or stage they're in, but they want to get that customer interface. what's the best way that they can go about doing that? Who would they talk to or how could they initiate that?
Ashley: Yeah, so I would say, if you are not involved in that, ask to be a part of it. And I don't think it means, like ... I don't think it means that you need to be a part of it 100% of the time, but it is really powerful to dip in.
One thing that's interesting that Groupon did in the early days, and was for, I think it was, like, one hour a month, engineers would, go and, like, sit with the customer support team.
And one, like, watch them use the tools, some of which, like, some of these engineers had built this internal tools. There was a huge customer support team that was, like, part of the growth. It, like, you know, you can imagine how small that might be at first. Um, when I got there, at some point during my tenure, it was, like, at least 400 people, which is huge, so and then just kept, kept growing.
Just really big. And, you know, one, watch people use these tools. And there were a lot of, like, internal tools, like homegrown internal tools, and a lot of operational teams that are sort of, like, running the machinery of getting things, getting deals up on the site, or working those opportunities in Salesforce.
Like, a huge, like, operational employee base at... or operations employee base at Groupon at the time. So that's one thing. But then two, just, like, listening in... Or mostly email, so not just listening in. But listening in or, like, watching the emails, but looking at the things that are coming from customers.
And, you know, watching what that support team has to do in order to, like, how they answer that, like, what they say, what they're, kind of, like, what they're dealing with. And I had so many engineers who, went through that say, like, that's very powerful for them to just kind of, like, see and feel and know.
So that's not quite, like, capital D discovery, but I think, I think this is less true today than it might have been, like, 10 years ago, or less novel today than it might have been, you know, 10 or 15 years ago. at the time, it it was novel, certainly to the engineers to have engineers as part of that, and to really be more in touch with the customer, not as a, not as a persona or not as more of an abstract entity, but really see what's happening on the ground.
what's powerful about that as an engineer is that- You are also getting distilled all of these, these insights from a product team But to be able to see it, you can develop your own perspective on it that is not just informed by what research is telling you, what product is telling you, but what you are actually seeing happen.
So that would be my advice because I think it can be... I think it can really be a powerful sort of north star and help you potentially as an engineer make better decisions about what you're building.
Dianna: So the closer you can get to the customer's actual feedback, if it's not the actual customer, then what they're actually saying instead of relying on the reports and the distilled information
Ashley: Yeah. I'm not saying don't trust your PMs
Dianna: Yeah.
Ashley: and the, and your researchers and what they're telling you. But I think that it's even... The closer you can get, the more powerful it will be in, in my experience
Dianna: So just to close up here you shared a lot of valuable advice. What's one habit you'd want a listener to try on Monday morning to stay honest about their assumptions about their customers?
Ashley: one thing I do every Monday is there's a set of dashboards that I look at every single Monday, and it's not revenue and it's not it's not business metrics. It is usage metrics. So it is, it is retention. It is, really user activity, which is the, the way that I always think about data and user funnels, like Those things are signals, like data, the metrics are signals.
And then, actually talking to users fills in, like colors in the lines of what you're seeing. And gives it a little more substance. You know something is happening. The metrics will tell you that something is happening. Talking to users about it will tell you precisely what is happening and why.
it's easy to do every, every Monday, and making it a weekly habit
Dianna: Yeah, I was gonna say because when I was working as a project engineer, that wasn't necessarily a task I was thinking about. But making time, just carving out some time to intentionally look at that every week to keep your finger on the pulse, so to say. Yeah, that's great advice. Ashley, where can people find you and is there a place we should point them toward for your work?
Ashley: Yeah, so where they can find me for my product work this is very boring, but I'm always posting on LinkedIn about all sorts of things related to product. And right now I talked about, joining a new place six, six weeks or so ago, and that's at DoubleGood.
DoubleGood is a fundraisingwe build fundraising software for youth sports and schools. So if you are somehow involved in that and have feedback about the product or just wanna talk to me about fundraising, please hit me up. I also have a podcast. It has nothing to do with product or software engineering.
It has everything to do with Chicago. It's called Notes From Chicago. You can find it anywhere you listen to podcasts or also on YouTube. And we're at notesfromchicago.com. And if you have guest ideas I would love to hear them if you are in Chicago.
Dianna: That sounds great. Ashley, thanks for joining us today. I really appreciate your insights
Ashley: Dianna, thanks so much. This was really fun
Track 1: That concludes the interview. Ashley and I talked about why discovery doesn't end before development begins. Customers may use a product in ways the team didn't anticipate, and the assumptions around a product can become stale as the surrounding environment changes. We also talked about how discovery changes across startups, hypergrowth teams, and established products, and why hardware and software require different balances between speed, learning, and release risk.
The common thread was staying close to real people and treating what we think we know as something that may need to be examined again. So here's your Monday morning move. Choose one customer assumption your team is relying on. Look at one current usage metric, support pattern, or piece of direct customer feedback and ask whether it confirms the assumption, complicates it, or suggests that the environment has changed.
Then, if you can, get closer to the source. Ask to join a customer conversation, listen to a support interaction, or review the actual words people are using. Data can show you that something is happening. Talking to users can help you understand what is happening and why. You can find Ashley on LinkedIn.
I'll include her contact information and the resources mentioned in the show notes.
If this conversation helped you think differently about customer assumptions, discovery, or how products change over time, subscribe to Quality During Design and share this episode with someone who is working to stay close to the people who use what they build.
You can also find more reflections in the monthly digest at newsletter.deeneyenterprises.com. This has been a production of Deeney Enterprises. Thanks for listening