Photo by Markus Spiske on Unsplash

Kick-starting Product Operations

Baris Ermut
5 min readJan 9, 2023

--

Alright, first post of the year. Happy new year everyone, I believe that 2023 will be really good year, especially for the Product Operations.

In July, when I was just started working on Product Operations, I’ve written a post about it. “Operations’ Rising Star, Product Operations”. However, after months of learning, experiencing, reading and listening, now, I have some different mindset.

In my very first couple of months, I was stuck with pillars. I kept trying to understand how to implement those to our company ( at that time Storyly never had Product Operations). Apparently, that wasn’t a quite well approach, here comes my first and most important learning;

Do not stuck with pillars, every company’s structure is different and every product team has different problems to solve!

What are we talking about today?

Well, as I drop a hot take above, I now will get into the real content how to kick-start Product Operations? The answer is really simple; you have to start listening to people and learn what’s going on around you.

This time, my entire post will be about importance of listening tours when you or your company is new to Product Operations.

“The most basic of all human needs is the need to understand and be understood. The best way to understand people is to listen to them.” — Ralph G. Nichols

So, what is a listening tour? A listening tour is when a person actively listens to stakeholders/teams to gather feedback and insights. These tours can be conducted in person and are a way to understand the root problem. The purpose of a listening tour is to identify and address any issues or challenges that may be present.

Pretty understandable right? What we do as Product Operations fellows is trying to make our teams day-to-day lives easier and efficient. To be able to do that properly, first thing we need to know is the real problem and/or broken/missing pieces.

How can you conduct listening tours?

As I mentioned in the beginning, I’ve read so many stuff when I first get into Product Operations. One great post I’ve read and got me into thinking about this different kind of listening tours was from Joshua McLaughlin. His post Product Operations: From zero to one enlighten me a lot.

I was so confused about the structure, how to measure those listening tours, and how to actually know which problem come up more than others. In the post of Joshua, he actually brings out an amazing idea, having questions on a NPS-like structure. Let your team, your stakeholders score the questions on a scale of 0–5 and voila! you’ll have amazing results that you can visualize to understand what’s going on around.

So, my second concern was including everybody on this listening tour. Like, time is the most valuable thing in every single one of our lives. This was the reason why I did not conduct the listening tours via a call (as we work remotely).

I decided to ran a survey including almost the entire company with 3 to 5 NPS-like questions to understand where should we tackle first. The questions vary for different teams. Engineering team had more product management and product related questions, while, Sales, Marketing and Customer Engagement teams had more product and releases related questions.

To be honest, making those listening tours in person could grant me more detailed information and this might be one of the things I wonder, still, this was a solid way to learn.

How was our listening tour survey questions?

And, what kind of questions I put into those surveys. Almost all of the questions were NPS-like and the structure was “How well are you aware ___?”. You can fill the blank with anything you are curious about.

In our case, we’ve included stuff like;

  • Product roadmap,
  • Upcoming features,
  • Competition,
  • Recent releases etc.

I also wanted to add a couple of open-ended questions as well, especially for the Engineering team survey. The reason for that was basically to understand the missing pieces on product-development lifecycle. I was kind of concerned to pick or decide on these questions and again, Joshua’s post I linked above was truly a diamond on that one.

The questions I’ve decided to use were about;

  • Most satisfying parts of product-development lifecycle,
  • Most frustrating parts of product-development lifecycle,

So, it is all about what you want to learn and which parts of your organization you think might have missing pieces that can be fixed with a small participation of Product Operations.

What did we get at the end?

In the end, once everyone answered the surveys, we had a huge data which is also applicable on graphs to visualize it.

I’ve grouped the questions into headlines;

  • Communication
  • Customer Insights
  • Upcoming Features
  • Roadmap
  • Competition
  • Q&A (this was about understanding how Product team is communicating when there is a question, feedback, issue etc.)

and calculated the NPS score of each headline to put on a bar chart. This gave us a good vision on overall experience and knowledge. We also made a breakdown of this into the different teams we ran the survey with, so that we could understand the missing piece/information through different teams Product team interacted with.

So, at the end of the day, we had 2 different graphs showing us the results of our surveys, both visually and mathematically and once you look at the charts, it was amazing that we easily spotted the missing pieces we should start working on.

Quick and important note. The one thing you need to make sure everyone having this survey understands that; you are not trying to test anyone, or any knowledge. You are just listening to them to understand the missing piece and start working on it.

Let’s just sum things up before ending this post. Quick disclaimer, all the things I’ve mentioned are related with my own experiences and can be different for you or your company.

If you are starting building a Product Operations function from ground-zero or even maybe you’ve started working as Product Operations fellow, listening tours should always be your #1 task before getting your hands dirty.

By running listening tours, you’ll realize that you are addressing the actual missing pieces and wasting your time trying to fix something that already works properly or re-invent the wheel.

What’s next for us? We’ve already started working on improving the missing pieces and probably we’ll make those surveys on a quarterly basis to understand if our changes, processes, improvements are actually helping out.

Remember! Learning never ends. The more you listen carefully, the more you’ll learn and in the end, the more valuable actions you can take.

Would love to hear your thoughts and ideas about listening tours. Feel free to drop a comment.

Up next, I’m thinking of sharing what type of actions we took right after understanding the missing pieces.

Hope you’ve enjoyed and might learn something new or insightful! I’m totally open for all kind of comments and coffee-talk about Product Operations 🙋‍♂

🔍 If you are curious about our product itself, feel free to check Storyly’s website.

Feel free to contact me via;

Twitter https://twitter.com/barisermut

LinkedIn https://www.linkedin.com/in/barisermut/

--

--