Why your engineers belong in the room with your customers
Engineers building an API should be able to explain how it changes the customer's experience, yet in some organizations they sit behind a wall, far from customers. Rawia Ashraf, a former antitrust lawyer who now oversees seven products as Vice President of Product at Thomson Reuters, argues that split teams burn story points on work that serves no priority. So what does acting as one team really take?
Learn four habits that align product and engineering, plus ways to run braver retros
Rawia Ashraf, Vice President of Product at Thomson Reuters, argues that product and technology teams succeed when they act as one team, whatever the org chart says. She sets out four principles (be one team, share priorities and accountability, share the customer, and communicate) and answers audience questions on retros, launch decisions, customer co-design and learning from failure.
“And what I mean by that is tech should not be behind a wall and not get access to customers.”
“And when you do see yourself as one team, it's much easier within that environment to challenge rather than feeling like you're sitting on the outside criticizing another team.”
What you will learn
Align product, engineering, UX and architecture around one shared set of weekly priorities.
Share accountability for missed deadlines by showing up together in front of stakeholders, in both directions.
Bring engineers into customer meetings and feedback sessions so they can connect their work to customer pain points.
Protect developers' focus time by agreeing fixed meeting blocks instead of mid-day interruptions.
Encourage candour in retros through one-to-one conversations beforehand and by modelling honest feedback yourself.
Key takeaways from the speaker
A key driver of success is making sure the product team and technology team share the same vision and priorities.
Details
Level
Beginner
Format
Talk
Technical depth
Non-technical
For
Early career, Mid-career, People manager
Length
18:40
Published
July 2021
Questions this talk answers
How can product and tech teams work well when they report to different leaders?
Rawia Ashraf says they should treat themselves as one team regardless of the org chart. She calls acting as one team the greatest predictor of success.
How do you keep a cross-functional team focused on what matters most?
Her team meets at the start of every week with engineers, product owners, the architect and UX to state the week's top priorities, so people can redirect work that does not support them.
Why should engineers have direct access to customers?
Any engineer should be able to articulate how their work affects the customer's experience, and nothing beats hearing customers describe their challenges in the room. She invites engineers, dev leads and architects to customer and feedback meetings.
How do you encourage free expression in retros?
Hold one-to-one conversations beforehand with people who are hesitant to speak, and model honesty yourself so others see that candour leads to positive outcomes.
How can a product team co-create solutions with customers?
Run preliminary interviews, sketch back your understanding of the problem, then hold a co-design workshop where customers define an ideal outcome and prioritize what would help most, using Miro when working virtually.
About this talk
A look at how technology and product teams can truly partner to deliver amazing solutions.
Our next speaker who's here with me now, Rawia Ashraf, Vice President of Product Legal Practice and Productivity at Thomson Reuters, is going to share more about partnering with your product team. She believes that a key driver of success in making sure the product team and technology team share the same vision and priorities. Please welcome Rawia on this stage. We're super excited to have you here with us today. Rawia Ashraf: Hi, thank you, Anna. I'm really excited to be here. It's been such a wonderful conference and it's great to see so many women sharing with each other and so motivated. I'm really thrilled to be here joining you all. As mentioned, my name is Rawia Ashraf and I'm at Thomson Reuters. Just a little bit of background. I am a lawyer by training. I practiced law for 10 years in the U.S.
and New York and Washington, D.C. And then I joined Thomson Reuters and I've been in product management since then and I have to say I love it. And so today I'm going to talk about my experiences working with tech and sort of some of the lessons learned and what has to happen or what goes well when product and tech teams are working together. So I'm just going to share these key principles. And so these are the things I'm going to talk about today. Being one team, sharing priorities and accountability, sharing your customer and then really communicating. And I'm hoping that there will be plenty of time for questions at the end. I'd love to hear what others think about this as well. So let's start out with the first
principle and that is be one team. I think the title of my talk is a bit of a misnomer because it's how can product and tech teams work well together. And I think the idea is that they shouldn't think of themselves as separate teams. No matter what the org chart says, you know, if engineering rolls up into one part of the business and product is in a different part of the business or even UX is into a different leader, the people working on one product or delivering a project should consider themselves all part of the same team. I've had the opportunity to work on a bunch of different teams and different structures. And my favorites have been the one where everyone's reporting into the same leader, right?
Where the tech lead and the UX lead and the product lead, they all have the same boss. They are all moving in the same direction, very similar to the startup experience. But if you are in more of an enterprise organization working in a large company, it's tough to sort of have an org chart that reflects that way of working. And so I just encourage everyone to think of yourselves as one team and act like one team. And that's sort of the greatest, I think, predictor of your success. But then what does it really mean to be one team? And I think those are sort of the next principles I want to talk through.
So to my mind, to be one team, tech and product have to share priorities and accountability, right? So for example, everyone should sort of be rowing in the same direction and needs to know what the most important things are on the roadmap, or what are the most important customer problems, or what are the biggest sort of tech challenges the team is handling. And so if everyone's sort of pointed in the same direction, you're much more set up for success. And so along those lines, my engineering partner, sort of the tech lead for one of my teams, he and I get together with our full team at the beginning of every week, and we share what the priorities are for that week. The engineers are there, the product
owners are there, the architect is there, the UX team is there. And we just actually articulate this week, these are our top priorities. And I think hearing that at the beginning of the week helps everyone align their work towards those right priorities, they could be spending tons of time, tons of story points on something that's actually not pointed towards a key priority. And if, if you understand those priorities, you can redirect your efforts or sort of raise your hand and say, Hey, I've got something I'm totally heads down on it. And I don't see how it lines up with the priorities.
And it's a really good way for the whole team to assess that. And similarly, sort of the flip side to that is the team has to share accountability, right? So that means, um, if, if, uh, a deadline's being missed, a ship date is being missed, um, tech teams should show up with the product team. You know, if there's a meeting out to stakeholders to explain sort of wise, why are we missing this release date or what's going on with this environment? If, if tech partners show up with their product partners at those meetings, it really goes a long way to presenting, um, the group as one team. And it's not just sort of like a product team and they have an engineering team over here on the side that's
doing the work, but isn't actually part of that core accountability. So I've always found that goes really well and it has to go the other way too, right? If, if the product team hasn't given enough requirements, hasn't given enough specificity to the dev team and things aren't, um, on, on target or on schedule, I think the product team needs to show up at those meetings where the tech teams explaining why deadlines were missed to say, look, that was our miss. We, we needed to do better there and we're, we're on it going forward. So in addition to that, one thing that I've found hugely helpful, um, in successful teams is if the technology team and the product managers share a customer. And what I mean by that is tech should not be behind a wall and not get access to customers. And if that's
sort of the experience you have, or that's sort of the way your organization is structured, you should really raise your hand and ask to learn more about the customer. I fully believe that any engineer or developer who's maybe working on an API or setting up an environment or, or pulling together the architecture for, for a build should be able to articulate how that's going to impact the customer's experience. Right. And to do that, you need to be able to explain what the customer's problems are and what the customer's pain points are something in the product world that we talk about a lot is falling in love with your customer's problem, right. And making it your own problem so that you think about it, you think about how to solve it from that customer's perspective. And I think that it should
extend to technology as well. One thing that we've done at TR that I've seen pay great dividends is that I invite, um, engineers, dev leads, architects to meetings with customers so that they can hear it firsthand. It's all well and good to get a summary. You know, if you share like a market research report or customer research report with, with your developers, it's, it's helpful. They'll understand some of the context, but nothing beats being in the room with the customer and hearing them talk about their challenge and what they need solved. It really can animate and motivate all the work people are doing after, after that. In addition to that, um, it's good to hear customer feedback as well, right. That tends to go so beyond the discovery phase of figuring out what the customer's challenges
are. Once the product's live or you're doing, you know, you're revamping it or something, it's really good to hear that real time feedback that sales teams or account teams are hearing from the customer. So I always encourage technology people to join those sorts of meetings. And if you're not doing that, raise your hand, ask for that, ask. I think it'll just make everyone so much better at their job and really be able to, again, to share those priorities. If they understand that the customer's problems that the product is meant to solve. And then finally, sort of the next key, um, principle for success is to communicate. I mean, I know that one's obvious. We hear that all the time, but I just want to dig into a little bit about what that means. So, for example, one thing I learned from,
um, um, my dev team that I work with is that they need hours and hours of uninterrupted time if they're going to complete a task. Right. And so the way that product people work or managers work is that we tend to be in meetings after meetings after meetings. And so we schedule our days that way, but our dev team is very clear. Like they can't, if you go to a 30 minute meeting in the middle of the day, it sort of breaks up your breaks up your whole flow and the whole task you'd set up to challenge gets interrupted. And so if that's the way you work, communicate that our team communicated it to us. And so we've set up certain hours, uh, you know, Tuesday or Wednesday mornings where we can have meetings where we invite the
developers or, you know, maybe on Thursday evenings, there's, there's a block of time where we can invite developers, but we are now know not to interrupt the middle of their day and their flow with a meeting. Um, also, I, I think this goes without saying, but if something's not going right, communicate that early to your, your product partners, let them know, give them a heads up, um, and come with solutions, right? So if you think something's not going well, product team would totally appreciate it. If you say, Hey, this is sort of not, this is going a little bit off the rails, or we see some risk here, and here's what we think we should do to mitigate it, or here's what we need to be able to mitigate
it. So those sorts of things, if you put them on the table early, I think that only makes the team better and more equipped to deal with challenges. And then sort of another thing that's good practice is to do retros, right? After the fact, communicate about what went well, what didn't go well, what should we keep doing? What do we need to change? Where do we need more impact or sorry, um, process?
How are we delivering all of those sorts of things make the team continually get better and better. And then another piece of communicating, I think is also being comfortable challenging and pushing back, right? If something's happening, some, the product team is maybe put something together and there aren't enough requirements, or you don't understand how it leads to the vision, or maybe it's not technically feasible or is not funded properly. Raise your hand and push back on that. Challenge the team. I think that's always helpful and it leads to better outcomes. And when you do see yourself as one team, it's much easier within that environment to challenge rather than feeling like you're sitting on the outside criticizing another team. You know, I've, I have seven products now that roll up into my
team. So I've had lots of different experiences working with different types of tech teams, different types of product teams. And I will say above all to me, the most important thing is that everyone is on the same page about priority. So I'll just like hit that one again. Everyone needs to be sort of sharing the same North stars and knowing what is going to deliver the most value to your customers. Instead of thinking about, you know, feature 53 on the backlog, right? Think about how those things that you're building are going to help the customer and why those are your priorities. So I'll stop there to see if there's any questions or any comments. Okay. I see one from Nikita on how do you encourage free expression during
retros, especially when you have a diverse team of tech and product people? Oh, that's such a good question. We often run into an issue like that where we'll have a big retro and then no one will talk, right? You're like, Hey guys, let's get it all out there. Let's figure out what we need to do. And if that's what's happening, I think there's a couple of tools or solutions. One is that you can have sort of one-on-one conversations ahead of time before the retros. If you think there's some people who are sort of shy or hesitant to speak, I think that's a good way to sort of get them to share their concerns one-on-one and then either represent those concerns at the retro or encourage them to share those because
you, when you know that they have a concern that they wanted to raise. I think the other way to do that is to model it, right? To be brave and say, Hey, I don't think this went well and here's why. And if people see you do that and see that that actually yields a positive outcome and there aren't terrible repercussions for it, I think that they'll also have the confidence to do that.
Are there any other questions? What has been the most complex situation that you have lived with your team? How have you faced it? Wow. So there's probably a number of them. I always think a really complex situation is in the in the pre launch period, making that go no go decision, right? Like, because I always believe that you should launch a product. You know, there's that old saying that if you're not embarrassed of your MVP, you've launched too late, right? Like you need to get your product out there and start getting feedback and get it in customers hands. And I think that's always a complex situation of figuring out like, are we there? Do we have an MVP? Have we delivered enough value that we can get this out there and start getting customer feedback and start testing what we've built?
Um, without actually just put shipping something that's not ready, not ready to go live. And so that takes everyone's input, right? You have to have the UX team saying, look, we think these are the three minimal things that we have to have in the product before we launch. And you have to have the tech team say, these are the sort of functional and non-functional things we need before we can be ready to launch.
And then you have to have the product team saying, these are the sort of use cases or user stories that we need, um, people we need to be able to deliver before we can launch. And that is always a bit of a dance, right? Because you're nervous, but you still want to launch a product. I mean, I guess the other really complex situation is when you don't have enough funding to do what you want to do, but I think we all learn to make do and figure out what you have to shave off of your roadmap and out of your backlog to do the best, um, with what you've got. Um, okay. I think that's really on all of it for me. Um, if there aren't other questions,
yeah. Hi Ravia. Hey, let's take some questions from the chat. Okay. Are there more methodologies, techniques are there? Okay. Yeah. There's a ton more coming. Okay. What kind of methodologies? Sorry. So what kind of methodologies techniques are you using to co-create with a customer? Um, so my favorite one is to do a design session with a customer, right? Where first you do some interviews and you understand if the customer has a particular problem. So the products I build are in the legal space, right? So let's say the issue is the customer say this part of, of contracting or drafting a contract is very difficult, right? We're struggling with that. So you do some preliminary interviews to sort of understand or hear them describe that problem in their own words. And then
the next thing I like to do. So then you take that back, you sketch that out. You're like, here's our understanding of your problem. And then you have a co-design workshop with the partner with the customer where you say, let's look at your problem. Let's talk about what the main challenges are in this sort of design thinking. And then what could be an ideal outcome? You know, what would be the end state that would work for everyone? And then you sort of prioritize within that to have the customer say, if you did this thing, this would help me the most. Or if we could have a better integration here, that would make our life so much better. And so I think it's really getting out there and whiteboarding
it with customers. Since the pandemic, we've been using Miro a lot to do it virtually with customers, but it's really getting in the room with them and charting it out and talking about the biggest problems and the biggest impact from solving those problems. Like what problem could, what could, what should you prioritize in terms of solving? Have you had any failures and what was the biggest lesson?
Oh my God, tons of failures. Um, and I think for me, the biggest lesson, especially like sort of growing up, you know, in school, like always an A student, always got good feedback. And I, I thought that failure was not acceptable, right? If you failed at something that was some sort of reflection on you or like a, uh, a weakness in you. And then you learn that you actually, you just, nobody is perfect. You have to fail at things. It's just the, the laws of probability, things are going to go wrong. And so that I think was my first big learning of getting comfortable or accepting the fact that I'm going to fail. Cause that, that was, that didn't come natural to me. And I don't know that it comes natural to anybody. And then the second one is, all right,
so if I failed, what do I do with this? Right. And I think that comes down to, I have to learn something from this failure. Right. Cause if you're not learning from the failure, you're going to continually repeat that. And so that's sort of why retros are helpful with a group, but you should even do a retro with yourself. Like that meeting I had didn't go well. Why do I feel like it didn't go well? And think about it and sort of reflect on yourself. Like what was I not prepared? Was the other side sort of, did they have different expectations? You just sort of really figure out, you know, with yourself what you could have, what you could do better or differently in that situation.
Do we have any more questions coming in? Thanks to everyone who is chatting in and participating. I really appreciate that. Fantastic presentation. I love how masterful you're moderating the chat and this interaction with our audience is fantastic. And I can totally relate about the failure and I think that we should get more comfortable with the failure and also reflect on it. Yeah, absolutely. Thank you. Thank you. Great presentation. Yeah, my pleasure. Thanks for having me and enjoy the rest of the conference, everyone.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Article based on this talk
Why product and engineering teams should act as one team
Rawia Ashraf of Thomson Reuters explains how shared priorities, shared customers and honest communication turn separate functions into one delivery team.
In short
Product and technology teams deliver best when they stop thinking of themselves as separate teams. Rawia Ashraf, Vice President of Product at Thomson Reuters, sets out four principles for making that real: be one team, share priorities and accountability, share the customer, and communicate openly, including pushing back when something is off.
Key takeaways
A key driver of success is making sure the product team and technology team share the same vision and priorities.
One team, whatever the org chart says
Rawia Ashraf practiced law for ten years before joining Thomson Reuters and moving into product management, a field she says she loves. Today seven products roll up into her team, which has given her experience with many different tech and product structures. Her opening point is that the title of her own talk is slightly misleading: product and engineering should not be partners across a line, they should be one group.
"No matter what the org chart says, you know, if engineering rolls up into one part of the business and product is in a different part of the business or even UX is into a different leader, the people working on one product or delivering a project should consider themselves all part of the same team." (1:53)
Her favorite setups have been the ones where the tech lead, UX lead and product lead all report to the same boss, much like a startup. In large enterprises that is rarely possible, so she asks people to adopt the mindset regardless: "And so I just encourage everyone to think of yourselves as one team and act like one team." (2:35)
Shared priorities and shared accountability
For Ashraf, being one team starts with everyone knowing the most important items on the roadmap, the biggest customer problems and the hardest technical challenges. She and her engineering partner gather the full team (engineers, product owners, the architect and UX) at the start of every week to name that week's top priorities.
"And I think hearing that at the beginning of the week helps everyone align their work towards those right priorities, they could be spending tons of time, tons of story points on something that's actually not pointed towards a key priority." (3:52)
Accountability has to be shared in both directions. When a ship date slips, tech partners should join product partners in front of stakeholders. And when product has not given enough requirements or specificity, product should stand beside engineering and own that miss. Above everything else, she returns to alignment: "Everyone needs to be sort of sharing the same North stars and knowing what is going to deliver the most value to your customers." (10:35)
Share the customer
Ashraf believes any engineer working on an API, an environment or an architecture should be able to explain how that work affects the customer's experience. That requires direct exposure to customers, not just reports about them.
"And what I mean by that is tech should not be behind a wall and not get access to customers." (5:01)
At Thomson Reuters she invites engineers, dev leads and architects into customer meetings. Research summaries help with context, she notes, but "They'll understand some of the context, but nothing beats being in the room with the customer and hearing them talk about their challenge and what they need solved." (6:34) She also encourages technologists to join sessions where sales and account teams relay live feedback after launch, and to ask for access if they do not have it.
In the Q&A she describes her favorite co-creation method: preliminary interviews to hear the problem in the customer's own words, a sketch of that understanding, then a co-design workshop where the customer describes an ideal end state and prioritizes what would help most. Since the pandemic her teams have run these sessions virtually in Miro.
Communicate, push back and run honest retros
Communication sounds obvious, so Ashraf makes it concrete. Her developers told her they need hours of uninterrupted time, and that a 30-minute meeting in the middle of the day breaks their flow. The team now holds meetings with developers in agreed blocks rather than interrupting their day. She also asks engineers to flag risks early and to bring proposed mitigations, and she recommends regular retros on what went well and what needs to change.
Pushing back is part of communicating, whether requirements are thin, the link to the vision is unclear, or something is not technically feasible or funded. "And when you do see yourself as one team, it's much easier within that environment to challenge rather than feeling like you're sitting on the outside criticizing another team." (9:46)
Asked how to get people talking in retros, she suggests one-to-one conversations beforehand with hesitant colleagues, and leading by example: "I think the other way to do that is to model it, right?" (12:05)
Launch decisions and learning from failure
The most complex moment for her teams is the pre-launch go or no-go call. She leans toward shipping early: "You know, there's that old saying that if you're not embarrassed of your MVP, you've launched too late, right?" (12:34) Getting there takes input from UX on the minimum experience, from tech on functional and non-functional needs, and from product on the essential use cases.
She closes with a personal lesson. As a lifelong A student she once saw failure as a weakness, and had to learn that failure is inevitable and that the real work is extracting a lesson from it. "Cause if you're not learning from the failure, you're going to continually repeat that." (17:15) She recommends running a retro with yourself after a meeting that goes badly.
Watch the talk
"Partnering with your Product Team" by Rawia Ashraf (19 minutes): https://www.womentech.net/video/rawia-ashraf-partnering-your-product-team
About the speaker
Rawia Ashraf is Vice President, Product - Legal Practice and Productivity at Thomson Reuters, where she develops customer-driven legal software that helps attorneys get their jobs done. She previously led Thomson Reuters' Practical Law product strategy and, before that, practiced antitrust law at Simpson Thacher & Bartlett in New York and Washington, DC.
Questions this talk answers
How can product and tech teams work well when they report to different leaders?
How do you keep a cross-functional team focused on what matters most?
Why should engineers have direct access to customers?
How do you encourage free expression in retros?
How can a product team co-create solutions with customers?
Drafted with AI from the talk transcript. Editor review pending.
Frameworks and ideas mentioned
Minimum viable product (MVP)
Retrospectives
Design thinking
Co-design workshop
Story points
Resources mentioned
Miro
Cite this talk
Rawia Ashraf. "Partnering with your Product Team." WomenTech Network, 2021. https://www.womentech.net/video/rawia-ashraf-partnering-your-product-team