Episode #14: Combining Customer Insight and Product Metrics with Ritika Mathur

Good product decisions require different kinds of evidence at different moments. Ritika Mathur joins us to explain how her technical, data, and customer-facing experience shapes discovery, measurement, stakeholder alignment, and risk management.

What you'll learn

• How Ritika's work in SAP consulting and data science prepared her for technical product management

• Why observing users can reveal problems before a team builds a product

• How prototypes and early feedback can clarify an MVP

• Which post-launch metrics help identify friction and connect a product to organizational goals

• How empathy supports influence, collaboration, and stakeholder relationships

Bring technical and customer perspectives together

At the time of the conversation, Ritika was a technical product manager at Arrive Logistics working on software products, APIs, and data products. Her path to product management included a master's degree focused on data analytics, work as a data scientist, and earlier SAP roles in India.

She began that earlier career as an SAP ABAP developer, then realized she wanted to work more closely with customers and help design solutions to their problems. As a functional consultant, she was already performing many responsibilities associated with product management: understanding customers, designing solutions, working with a technical team, and conducting user testing. Starting in a technical role also helped her understand what engineers needed and translate business requirements into technical ones.

Later, after a few years in data science, a manager recognized that this combination could transfer well to product management. Ritika now brings technology, data, and business context together rather than treating them as separate disciplines.

Learn differently before and after launch

Ritika divides experimentation into two phases. Before building, she prioritizes direct observation. Watching users in their normal environment, interacting with current tools and processes, can expose difficulties that may not appear in a feature request or a meeting. This phase is qualitative because the team is still trying to understand what the user does and where the real problem lies.

She also favors continuous feedback and putting design artifacts in front of users early. High-fidelity wireframes and mockups can be tested on the device where the eventual product will be used. That helps the team refine MVP scope and build a clearer view of the expected experience before committing substantial time, money, and effort.

After launch, Ritika shifts toward quantitative measurement. Instrumenting important parts of a workflow can show where users struggle and abandon a task, as well as where they move through easily. In the interview, she describes a clear separation: qualitative evidence before the product and quantitative evidence after release. The purpose in both phases is the same, but the question changes from what should we build to how is the released experience performing.

Connect workflow metrics to business outcomes

Ritika pays attention to conversion rates and whether a launched feature or product affects the organization's broader goals. A local change in user behavior becomes more meaningful when the team can connect it to an outcome the business is pursuing, such as acquiring more customers in a particular segment.

For product teams, this creates a useful measurement chain. First, identify the important steps in the user's workflow. Next, track progress and friction at those steps. Then connect any movement in those measures to a relevant organizational goal. That prevents the team from treating clicks as success when the desired customer or business result has not changed.

The approach also encourages clarity before launch. If we cannot describe how an intended behavior contributes to the larger outcome, we may need to revisit the product hypothesis or choose a better measure.

Use empathy to influence without authority

Ritika names two recurring challenges: influencing without authority and keeping everyone aligned as priorities change. Product managers still need to evangelize, negotiate, resolve conflicts, maintain roadmaps, write documents, and communicate reprioritization across business, engineering, and customers. Formal authority is not what makes that work possible.

Her guiding principle is empathy. Understanding the pressure, needs, and constraints facing stakeholders and technical teammates helps build relationships. When the product manager later needs support during a difficult push, teammates have evidence that their own concerns will also be heard. Ritika describes empathy as reciprocal: understanding other people's problems helps them understand the product manager's pressure when support is needed.

Ritika also turns her tendency to think far ahead and imagine worst-case scenarios into a professional advantage. In product work, that habit helps her identify potential gaps and consider mitigations early. Paired with customer observation and post-launch data, risk awareness can help teams prepare without losing sight of current evidence.

The full conversation offers a practical balance: observe before building, measure after launch, connect product behavior to business outcomes, and use empathy to keep people aligned. Listen to Episode 14 on Spotify for Ritika's discussion with the Samelogic team.