Rigorous user research was not enough to win over her own colleagues
A new product backed by data, user testing and rigorous research still triggered panic and fear inside her own company, because it changed what had made the business successful. Corina Dumanovschi, Senior Product Manager at OLX Group, led that build from scratch in a payments domain she had never worked in. For any product person driving big change, the question is how to bring a whole organization on board.
Learn the do's and don'ts she uses to navigate stakeholder storms and keep a new product moving
Corina Dumanovschi, Senior Product Manager at OLX Group, shares what it took to build a new remote-transaction product from scratch inside an established company. She argues that rigorous discovery and data are not enough on their own: product people also need empathy for internal stakeholders, comfort with discomfort and the resilience to keep learning, iterating and repeating.
“So, the value for the user backed by data and rigorous research is not enough.”
“This is not a soft skill. This is a core skill.”
What you will learn
Plan product discovery with a cross-functional group, opportunity trees, user testing, surveys and A/B tests to validate hypotheses.
Spot misleading user testing results where participants finish a flow without really understanding it.
Anticipate fear and resistance from internal stakeholders and position a new product as an extension, not a threat.
Prepare executive summaries, demos and worked-out alternatives for different audiences before you are asked.
Expect discomfort and imposter feelings so you can navigate them and build resilience.
Details
Level
Intermediate
Format
Talk
Technical depth
Non-technical
For
Early career, Mid-career, Senior individual contributor
Length
19:14
Published
July 2020
Questions this talk answers
Why is strong user research not enough to get stakeholder buy-in for a new product?
A big change triggers fears about how it will affect people, so you also need empathy for where internal stakeholders are coming from. Her rule is: don't assume, ask and analyze.
How can you tell whether user testing results are trustworthy?
Participants may push through a flow just to finish the task or to avoid hurting the team's feelings. Unpack each step and never dismiss problems as only one or two users.
How should you position a new product inside an established company?
Frame it as an extension of the current experience rather than a replacement or threat, and keep reframing the argument until people come on board.
What should a product manager always have ready?
Executive summaries for different audiences, presentations, demos or user manuals, plus alternatives already worked out in case leadership asks you to change course.
How can a product manager prove their value in a job interview?
Back up every claim with a concrete example from past experience showing what you did and how it worked out, and prepare a clear structure for your points.
About this talk
Building a new product is one of the most equally difficult and exciting journeys a product person can embark on. When doing it inside an established company, things tend to become a lot messier. This talk is about resilience, the costs of this turbo-boosting career opportunity, the weird and, sometimes uncomfortable situations that come up, and how to embrace them.
Data is not enough: don't assume, ask and analyze (52 s)
Caring deeply is a core skill (76 s)
Let's get started. So we only have 20 minutes today. While I want to talk about my journey building a new product from scratch, I will be focusing on some of the struggles since I feel that we rarely call them out publicly. And they do make us stronger product people and enhance the culture of our companies, not to mention the customer centricity.
So let's begin our story. Once upon a time, right? That's how all stories begin. I had just joined the company. And following an organizational change, I landed in an area where I did not have any domain expertise. A week in, I met my new manager, and I was very upfront about where I was coming from. She was, however, trusting and optimistic. And she decided to empower me to embark on a learning journey, to look for a fresh perspective and come up with how I can bring value to our users in the company, figure out something new, take the greenfield approach and think outside the existing status quo.
This was super exciting. So obviously curiosity invaded the realm. The beginning was particularly intense. There was so much information to absorb and so many sources and avenues to get it from. When I say information, I mean domain knowledge. In my case, it was very specific around the payment area. But I also mean user research that was already available out there, qualitative, quantitative data, people, some of the user experience history in the company.
So I used a lot of ways, why, anything, everything, yes, no, what was happening. And imposter syndrome kicked in. I think this is this tends to be a problem, particularly as a woman in tech. I made myself look as if I was uncertain or I was not confident enough, maybe not strong enough due to the cautious approach that this imposter syndrome triggered for me.
Of course, I was excited, but I also felt a fear of failure. And it took me a while until I realized that that was OK. So what I had to do was step back and do some internal reflection, get to know myself better and define my compass. Another word of warning here. If you don't sound confident, people will doubt your skills.
That's a sad reality. OK, so let's do this. Right. Product discovery time. If you've been working as a PM for a while, you're probably going to say, yes, yes. We know about the tools and processes and all of that. But do let me summarize some of them briefly. You gather the cross-functional group of people. You look at an opportunity tree.
If you don't follow Teresa Torres, I highly recommend you do. You do a design spread, qualitative, quantitative research, which includes testing, user testing, surveys, A/B tests. How might we answering all of these questions. So in a nutshell, validate those hypothesis to make sure that we understand the market, the users, the costs, the risks. Me and the team, because as I mentioned, this takes a lot of effort and a lot of people have to be part of it, make sure we cover our bases.
And it turns out that something new was taking shape and it was transforming our in-person meetup core business and expanding it to a bigger footprint. One where we have facilitated transactions, remote ones. Mind our biases. This is a super important one. So we're putting some serious cognitive load on some of our users and we're convinced it was super intuitive.
But remember that this was new to them and our users do not like to read information on a screen or a page, nor were they paying attention to our various attempts to tell them about next steps. This was something that we had to change and try different approaches to so many times. On the product side, you may love the idea because you're excited and you're invested and you're thinking, oh my God, this has such an amazing potential.
But be careful about it. Be careful about the hypothesis that you test. This might not be the last one that you do have to test. And it may be that you build on certain ideas and hypotheses or it may be that you have to discard them and really move on. An example that I like to bring to emphasize this. Some users in user testing were going through the flow without understanding it.
So they had their eyes on the prize. Build this castle. Get it done super fast. And there we go. Success, right? That doesn't mean that they would have used it in real life. They were after all in a user testing session. So they might even think about not hurting our feelings and so on. So do make sure to unpack the different steps. That's super important.
And never, ever blame it on the users or take the easy way of saying, oh, it's just one or two people. You really have to pay attention and work through these things. Okay, so this is the part that you might have encountered more frequently. I want to talk about the moment when the first internal storm hit. In my team's happy product discovery bubble, I thought that by doing things the right way, stakeholders and colleagues will buy into the vision and what we're trying to solve and achieve.
It turns out that we were, as I mentioned previously, starting at something that was perceived as a huge change. We knew it was change, but this was apparently a huge one. It was a change in direction, something different than what had made the company successful up to the present day. And a good amount of people took panic and fear as their first reaction.
It was becoming real. It was no longer a mood shot. It went to roof shot. It went to palpable reality. So, of course, everybody's fears and insecurities and worries about how this might affect them kicked in. The aha moment here is that change, we expect it to be hard, but we do not have a sense about how hard it will actually be.
So, the value for the user backed by data and rigorous research is not enough. A strong sense of empathy and understanding both the users, but also where the internal stakeholders and collaborators in your company are coming from is super important. Don't assume, ask and analyze. And another anecdote that I want to share here. Without a sense of real urgency, people will choose comfort informed habits over taking a risk towards the future.
And when I mean people, I mean your users, but I also mean your collaborators, team, internal stakeholders. You know, in our case right now, we are living through a pandemic, right? So, of course, with social distancing measures in place, we cannot think of doing any sort of in-person trade. We cannot meet strangers, we can barely meet our families and friends.
And this kind of approach of offering an alternative to the in-person meetup makes perfect sense and it's super important. But if you go back a couple of years, this was not the case then. So, there was no real sense of urgency that this might be necessary. We had to work quite a bit to get this off the ground and also to move past the first storm.
Good news is that we reached a place where we're in this ship together. It takes time and we kept updating our approach and framing the argument in multiple different ways to get people on board. We made sure to position the product as an extension and not as a replacement or a threat to the current experience. This builds a lot of resilience.
And in the end, we're all human. So, it's important that we are mindful of this. And if you ever are put in this kind of situation to make sure that you are careful about and aware of egos, maybe agendas, particularly loud voices and how to navigate around them. They don't come from a place of bad intentions, but they can have serious consequences if you leave them unchecked and unknown.
In my case, it was exactly like that. I had to dig a lot deeper to understand why certain fears and concerns inside the organization, because we're no longer a startup, right? We're coming. And what exactly was the biggest barrier for people to get on board? And in the end, it happened. We got in that ship together. And things started picking up again.
They did get better after the first few storms and failures. This doesn't mean that we stopped facing challenges. I want to be very clear about it. It means that we became a lot stronger at facing the challenges together. It may also sound cliche, but it's super important to have the different perspective and to have people sharing and voicing their concerns and also supporting your effort in the direction that you're going.
The end? No, definitely not. When you think about stories and how we present them and how we think about the experience that we've been through, we might say, okay, and at some point, everything ends. Well, no. In product, things do not end. You learn, iterate, and repeat. That's the reality. I think when we embark on a mission and we have this awesome opportunity to build a new product or even a new feature or build something and make a change for the better in the world, we think that we're going to go down the road and we're going to have some highs, some ups and downs.
As you can see in the picture on the left side, there's a road with ups and downs, but the road keeps going, when in reality, it's a junction. You have multiple roads. They can go up, down, left, right. You can take three, five routes to reach the same destination. So it's super important to be mindful of that and always have the comparison in your mind.
It's the same thing when you learn, iterate, and repeat for your users, but then also for your stakeholders, your collaborators, your team. Always keep improving. That's something that you learn the hard way sometimes and never think that, okay, there's just an end. Unless, of course, there are certain moments in a product lifecycle where it reaches its end.
That's it. Okay. I want to summarize a few points for you to remember from this talk. The takeaway don'ts, which is don't fall in love with your ideas. Don't underestimate emotions and habits of your users and stakeholders when making big changes. I say on the B side, be exceptionally mindful of this. Don't ever let entitlement or blame creep up.
What I mean by this is sometimes in organizations, you can see silos popping up. This is not my problem or it's this other departments. No, it's not. If what you're building and what you're solving for the users such as different areas, different teams and different departments, then it's part of your mission. And it's part of your responsibility to take that in and to address it.
You cannot just say, hey, I don't care if this adds so much operational complexity. I'm releasing my MVP, which is a very good example, a minimum viable product. And well, it will be a lot of manual work, but it will be for somebody else. No, no, please don't do that. That's definitely not going to set you up for success.
And you're not going to get that buy-in and alignment and that motivation and purpose in your team and your organization to continue and be truly customer centric. And the positive side of things, the takeaway do's have strong opinions held loosely. Make sure that you allow yourself to change your mind as much as you like a certain idea or you're very confident about it.
It can change and it will change. It will evolve as your experience and your learnings evolve. Care deeply about how your work impacts your users and everyone around you. This is not a soft skill. This is a core skill. Caring deeply about what you do is a core skill. And it's something that you cannot build. You cannot do without.
You cannot have that curiosity and empathy to do product and build things first and solve problems for other people if you don't care about them. Be comfortable with getting uncomfortable. The reality is that you don't have that beautiful road with ups and downs. Sometimes you have multiple roadblocks along the way and the path takes you in unexpected places.
So recognize as early as you can that you will feel uncomfortable. You might have imposter syndrome kicking in. You will not be convinced about things or something will make you feel queasy. This will happen. So just expect it. I think you can more easily navigate it when you expect it. Stand your ground. Motivation and purpose translate into resilience.
Sometimes in certain domain areas, depending on the company, things take time. And for you to go through the things take time, you have to be resilient and you have to keep questioning why with empathy and respect. On the even more practical side of things, be prepared. Always have material ready for various audiences. Have an executive summary on hand or multiple executive summaries on hand if you can.
Those will help you. And also presentations or demos or sometimes user manuals have all of this ready. I don't know about you, but to me it happens so frequently that somebody that I've never spoke with just sends me a message on Slack and asks me about that. And it's so easy when I have something on hand to share with them or when a super urgent meeting with your management team pops up and you have to be present and you have to be able to show the data, show an executive summary and talking about everything related to your product.
So all different types of communication options, alternatives, risks when they say, OK, maybe they tell you that you need to stop what you're doing and do something else. Make sure you have some sort of alternatives prepared and already worked out in your mind. And remember that a smooth sea never made a skillful sailor. I think we learn so much by going through uncomfortable and tough situations, by having to deal with difficult situations, people by having to try 10 times before finding a certain experience that works.
So, yeah, you're not going to jump on the ship and go from point A to point B and cross the cross the ocean while you're crossing the ocean. You're going to have a storm, a tornado, a vortex, maybe you see an iceberg along the way. So, yeah, embrace these things as learning opportunities and keep your curiosity and wits about you.
OK, that is all from my side. I will talk about this for so much longer, but we do not have the time. Do reach out to me. I'm going to try and have a look at the questions here. I'm on Twitter. If you have follow up questions for this, you can also find me on LinkedIn. But I am the person that will reply to you faster on Twitter.
Thank you for coming to my talk today. And let's see if we can, if you have some questions. OK, I'm scrolling. What are your thoughts on the pandemic affecting the tech industry? I think it will lead to a new normal in the in the tech industry. Also for us, it will create that sense of urgency depending on the domain you're working in.
Exactly how? Well, the first example is that we're going digital with everything, even even for government services. Up until now, you had to, for example, in Berlin, where I live, you had to go and pick up a certain parking permit in person and fill in a form. Well, that's no longer happening. Thanks to the pandemic, the digitalization is accelerated.
So you do everything, all of that online. I think we're also going to become a lot more data privacy and security concern, or at least I'm hoping we will, because this is another super important topic, seeing how we are reacting to the pandemic and how we're looking at different apps to help support us live with it. Hopefully that answers.
Okay, I don't think we have additional questions. How to prove your value as a product manager in a selective process for a new job. Have examples on hand all the time. Be prepared to back up everything that you're saying. So don't only say product discovery, but say, did this exact, with this exact example from your past experience, and this is how it panned out and worked.
Prepare structure. To make sure that your points come across. And yeah, those would be my initial points.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Article based on this talk
Why rigorous research alone will not win stakeholders over to a new product
Corina Dumanovschi on the internal storms of building a new product inside an established company, and the habits that carried her through them.
In short
Building a new product inside an established company is as much about people as it is about users. Corina Dumanovschi, Senior Product Manager at OLX Group, explains that solid discovery and data got her team a validated idea, but not internal buy-in. What moved things forward was empathy for colleagues, patient reframing and the resilience to keep learning, iterating and repeating.
Key takeaways
Plan product discovery with a cross-functional group, opportunity trees, user testing, surveys and A/B tests to validate hypotheses.
Spot misleading user testing results where participants finish a flow without really understanding it.
Anticipate fear and resistance from internal stakeholders and position a new product as an extension, not a threat.
Prepare executive summaries, demos and worked-out alternatives for different audiences before you are asked.
Expect discomfort and imposter feelings so you can navigate them and build resilience.
Starting from zero in an unfamiliar domain
Dumanovschi's story begins just after she joined the company. An organizational change landed her in the payments area, where she had no domain expertise. Her new manager trusted her anyway and gave her room to take a greenfield approach and think beyond the existing status quo. The first weeks meant absorbing domain knowledge, existing user research, qualitative and quantitative data and the company's user experience history.
Excitement came with imposter syndrome and a fear of failure, which she describes as a particular problem for women in tech. Her answer was to step back, reflect and define her own compass. She is also candid about the cost of looking uncertain: "If you don't sound confident, people will doubt your skills." (2:01)
Discovery done right, and its blind spots
Dumanovschi briefly runs through the discovery toolkit: a cross-functional group, an opportunity tree (she recommends following Teresa Torres), a design sprint, qualitative and quantitative research, user tests, surveys, A/B tests and "how might we" questions. The work showed that something new was taking shape: extending an in-person meetup core business into facilitated remote transactions.
She warns that teams fall for their own ideas. Her team believed a flow was intuitive while putting serious cognitive load on users who did not read on-screen information. In user testing, some participants completed the flow without understanding it, focused on finishing the task and perhaps on sparing the team's feelings. Her rule is firm: "And never, ever blame it on the users or take the easy way of saying, oh, it's just one or two people." (5:14)
When the internal storm hits
Inside the discovery bubble, Dumanovschi assumed that doing things the right way would bring stakeholders along. Instead, the product was seen as a change in direction away from what had made the company successful, and many colleagues reacted with panic and fear once it became real.
Her lesson is that everyone expects change to be hard, but nobody knows how hard. "So, the value for the user backed by data and rigorous research is not enough." (6:39) Product people need empathy for internal stakeholders as well as users, summed up in her repeated advice: "Don't assume, ask and analyze." (6:39)
She adds that without real urgency, people stick with familiar habits. Years before the pandemic made remote transactions obvious, there was no such urgency, so the team had to work hard to get the product off the ground.
Getting into the same ship
The turnaround came from repeatedly updating the approach and framing the argument in different ways. "We made sure to position the product as an extension and not as a replacement or a threat to the current experience." (7:52) She also urges attention to egos, agendas and particularly loud voices. They rarely come from bad intentions, but left unchecked they can have serious consequences. Digging into the real barriers eventually got everyone on board, and while challenges continued, the team became much stronger at facing them together.
She rejects the idea of a tidy ending. "In product, things do not end. You learn, iterate, and repeat." (9:51) The road, she says, is less a single path with ups and downs than a junction with many routes to the same destination.
The do's and don'ts
Her don'ts: do not fall in love with your ideas, do not underestimate the emotions and habits of users and stakeholders, and do not let entitlement or blame creep in. Shipping an MVP that dumps manual work on another department is, in her words, not going to set you up for success.
Her do's start with strong opinions held loosely and caring deeply about how your work affects users and everyone around you. "This is not a soft skill. This is a core skill." (13:09) She advises expecting discomfort and imposter feelings, standing your ground with empathy and respect, and being prepared: executive summaries, presentations, demos, user manuals and worked-out alternatives ready for whoever asks. Her closing image gives the talk its name: "And remember that a smooth sea never made a skillful sailor." (15:36)
In the short Q&A, she predicts the pandemic will create new urgency and speed up digitalization, and advises job seekers to back every claim about their product work with a concrete example.
Watch the talk
Product Sailor Caught in a Storm, Corina Dumanovschi, 19 minutes: https://www.womentech.net/video/corina-dumanovschi-product-sailor-caught-in-storm
About the speaker
Corina Dumanovschi is a Senior Product Manager at OLX Group and an organiser of Women Techmakers Berlin who advocates for education, diversity and inclusion. She has a degree in Computer Science Engineering and has worked across e-commerce, insurance tech and classifieds marketplaces.
Questions this talk answers
Why is strong user research not enough to get stakeholder buy-in for a new product?
How can you tell whether user testing results are trustworthy?
How should you position a new product inside an established company?
What should a product manager always have ready?
How can a product manager prove their value in a job interview?
Drafted with AI from the talk transcript. Editor review pending.
Frameworks and ideas mentioned
Opportunity solution tree
Design sprint
A/B testing
How might we
Minimum viable product (MVP)
Strong opinions held loosely
Resources mentioned
Teresa Torres (recommended to follow)
Cite this talk
Corina Dumanovschi. "Product Sailor Caught in a Storm." WomenTech Network, 2020. https://www.womentech.net/video/corina-dumanovschi-product-sailor-caught-in-storm