Product Leader Profiles is a twice-monthly series about product people doing exceptional work: the operators, builders, and leaders you don't always hear about, but should.
Maria Knausz is the Senior Director of Product Operations at Korn Ferry, where she owns the company's software development lifecycle, governance, release enablement, tooling stack, and executive reporting across product, engineering, and operations. She's held the product operations title for about a year and a half, but she's been doing the work, in one form or another, for more than 18 years.
I sat down with Maria to talk about the checklist habit that started in a cockpit, how to get leaders to actually ask for the data, and what AI is changing about the way product teams operate.
You wanted to be an Air Force pilot. How did you end up in product operations?
Getting to the world of product has definitely been a winding road! I started out wanting to be an Air Force pilot. While I ultimately chose a different path, getting a pilot's license taught me something that's relevant to my job today – the gift of a great checklist. A checklist shouldn't exist just for the sake of having one. It should have a purpose. Checklists and procedures are critical to pilots, and learning the importance of them stuck with me later on as I transitioned into product. Although, I started working in product before I ever even realized it.
My first role after graduate school was actually as a marketing manager at a healthcare software company. Yet, for all intents and purposes – it really was a product role. I was writing requirements, talking to customers, running user testing sessions, and even overseeing QA on top of writing marketing materials.
My first official product management role was at a startup in Cleveland focused on electronic health records and billing products. I stayed in healthcare technology for the first 12 years of my career, then moved into HR technology – first at UKG and now Korn Ferry. And this is where I started focusing on the discipline of product operations.
What was the transition from product management to product operations like?
Whether it was in an official capacity or not, I’ve been working in product management since the early 2000’s. In all of my product roles, I found myself writing down processes and making checklists for releases. For one company, I even wrote our entire Software Development Lifecycle process and published it – creating an entire operating model around it. That all happened before people really even had a name for the product operations function. So when the opportunity to transition into product operations came up here at Korn Ferry, it seemed like it would be a very natural one for me. Working on that side of the business has given me the chance to impact product in a different way.
What's a story from your career that other product people should hear?
One of the first things I did when I started at Korn Ferry was implement Pendo. But at first, adoption internally was a struggle. I set everything up, built useful dashboards, and identified all of my product champions thinking that would help with adoption. In my mind, I did everything the right way.
Then we put together a slide deck for a leadership meeting where we had a lot of big decisions on the table, and we expected the product data to be a huge part of the conversation. Everybody walked in prepared. My team followed the template I'd given them and presented it… but then the meeting just kept going. The leaders didn't ask about the data and nobody made a point to speak to it. So while the data was in the presentation, it didn't change the decisions that were made in the room that day.
That was a big aha moment for me. I realized if a leader isn’t asking about something that they know is important, it likely isn’t because they don’t care. It’s because they don’t know why it’s important. I understand now that the data and insights my team has access to is quite valuable and is often what leaders need in order to understand the importance and value of an issue or project. But it’s my job to proactively bring up the data and insights that come along with it even when nobody asks.
After that aha moment, how did you get leaders to start speaking the language of data?
The language of data is very unique to each individual leader. You have to understand each leader and help them interpret the data in a way that speaks to them. Sometimes it can be a challenge to get certain leaders to care about the data. In those cases, I try to understand what’s important to them and what’s keeping them up at night. Chances are, there’s data we have access to that can address that concern.
A recent example: We started seeing questions coming in around renewals. In almost all of the cases, the answers people were looking for were hidden inside our product usage data. Being able to find the data people needed (even before they explicitly asked for it) and proactively serving it to them really made a big difference in showing the value of the product operations function internally.
It was almost like I needed that hook to get our leaders to look at what I had been trying to show them. Once I had that hook, our leaders started to see product operations as a strategic function within the business.
How is your team structured, and what tools do you rely on?
I lead a lean team that reports to the SVP of Operations. We're organized around three capabilities:
- Product Delivery System: release planning and readiness, SDLC rigor, and AI-enabled development practices.
- Operating Infrastructure: planning, intake, reporting, and the tools behind them.
- Enablement and Adoption: making sure new processes, tools, and insights actually become how teams work.
We operate across Product, Engineering, UX, Compliance, and Operations, so rather than owning one product or deliverable, my team builds and runs the operating system that connects investment decisions to reliable delivery and measurable outcomes.
Our stack is Aha! for planning, Jira and Confluence for execution, Pendo for product usage data, and SharePoint for the Product Operations Hub. The hardest to give up out of all of them would be Pendo, as we really need that data to make better decisions.
What does a typical week look like? What always happens, no matter what?
First, I'm keeping planning and execution connected. That might mean checking whether priorities still fit the capacity we actually have, surfacing dependencies and trade-offs, and making sure commitments are represented consistently across the roadmap, delivery tools, and leadership reporting.
Second, I'm creating clarity across functions. I spend time with Product, Engineering, UX, Compliance, Finance, and Operations, making sure that all of the different perspectives can turn into a decision – with a clear owner and next steps. That could be an annual planning decision, an SDLC governance question, or even just a product data issue.
Third, I'm closing the gap between deciding and adopting. Something always needs translating into decision-ready language, and some cross-functional friction point always needs tending, whether that's a tooling conflict or a process disagreement between functions. Every week includes some mix of communications, training, documentation, reporting, and follow-through, so that great process actually becomes how people work.
What do you spend time on that people might not expect from your title?
I spend a lot of my time translating and pressure-testing different perspectives as well as building trust – both between people and between people and data.
People hear "product operations" and picture tools, processes, and dashboards. Those are part of it, but much of my time goes to turning ambiguous leadership direction into something teams can evaluate and execute. On the flip side, I spend a lot of time reviewing proposals to see whether the choices, recommendations, dependencies, measures, and asks are clear enough for people to act on.
I also spend more time than people might expect nurturing the connections between teams, and between systems and teams. That includes helping rebuild working relationships between functional leaders who have historically clashed, and making sure the tools we use and the data that comes from them – along with governance expectations and release planning – all tell the same story.
Because a lot of what I do comes down to trust – I turn to Brené Brown's work on trust and vulnerability as I’ve found it to be so useful. It connects directly to the cross-functional and trust-repair work that's most of my job.
What's the best piece of advice you've received?
This one is about caring so much that you try to take care of everyone all the time. Once I was given the advice, "When you protect your people, you could rob them of opportunity, and when you protect your boss, you stress yourself out and deny them the opportunity to make a choice." Sometimes when it feels like you’re protecting a colleague – but you’re actually taking away their opportunity to grow.
What are you most excited about right now, and what's keeping you up at night?
The answer to both is how AI is changing our operating model. It's what I'm living and breathing right now, and it's something I feel I can actually have an impact on. I've put in the hours as a product manager and I feel like I understand what’s historically hard and easy. Now I get to sit in product operations, where I feel like I have the power to remove lots of barriers with the operational structure we can provide, especially in this new age of AI. Removing those barriers for people has been really fun.
But this is also what keeps me up at night. AI is making us go faster, but it's also expanding the risk if we make the wrong decisions. How do we know we're actually delivering value? How do we create a muscle to do things differently? I recently read research from Product Focus’s 2026 Survey of the Product Management Profession, which found that 97% of product managers report personal productivity improvement from AI, but only 64% report improvement in actual product outcomes like revenue or time to market. That's the part that worries me. We don't just want to do a show and tell, "Hey, look at this cool thing I did over the weekend with AI." We have to move beyond that to how that cool thing we built actually changes the way we work, and eventually delivers value to our customers better.
But we have to be willing to fail. We have to create opportunities for our people to know they can fail safely, take risks, and try things differently, and we have to give them the net to do it. Otherwise, we're going to take a really long time to evolve.
What's the one big takeaway you hope readers get?
Product operations is so much fun. I never realized how much fun it could be until I got a chance to actually do it. As somebody with almost 20 years of experience in product management, getting to solve problems from this side of the house is the best. I'm having a blast.
Connect with Maria on LinkedIn.
Know someone who belongs in this series? Reach out to me directly at mike.belsito@mindtheproduct.com