Episode #83: Product Strategy, Prioritization, and Customer Advocacy with Siddharth Ilangovan

Product managers rarely receive a perfectly defined problem, complete data, and unanimous stakeholder support. In Episode #83, Siddharth Ilangovan explains how teams can turn that ambiguity into direction by combining customer empathy, product strategy, evidence, and informed conviction.

A product career built around customer understanding

Siddharth began in the technology industry as a business analyst in India. Clients, often product managers, supplied requirements, and he translated them into specifications and user experiences that engineering teams could build. He later continued similar work at telecom software company Plintron before completing an MBA at Arizona State University. An internship at Autodesk focused on trial users and subscription conversion, and he later joined Amazon Web Services as a senior technical product manager in the IoT data visualization space.

Across those roles, the scope changed from supporting requirements to owning products and then portfolios. The common thread was empathy. Siddharth sees the product manager as the voice of the customer, responsible for helping colleagues understand why users need a feature or struggle with an experience.

That responsibility also creates tension. Stakeholders inside and outside a company bring competing requests. A PM has to weigh customer value, business viability, strategic fit, feasibility, and the existing roadmap rather than treating every request as an instruction.

What you'll learn

• How product strategy creates a model for choosing customer problems

• Why repeated communication is necessary for strategy adoption

• How prioritizing problems differs from ranking proposed solutions

• Why quantitative trends need qualitative context

• How customer evidence helps PMs challenge powerful stakeholders

Start with strategy, then make it usable

For Siddharth, product strategy starts with customers. Teams need to understand where the product performs well, where it falls short, and why. That customer view then has to connect with the company's mission, vision, goals, and the product's stage. A team focused on acquisition may make different choices from one focused on revenue.

External context matters too. Siddharth follows industry news and uses Reddit to observe conversations about both his products and competitors. Taken together, customer feedback, company goals, market movement, and competitive signals provide the canvas for a strategy.

Writing the strategy is only half the work. A document that nobody adopts cannot guide decisions. Siddharth recommends turning the strategy into a simple, repeatable explanation and reinforcing it across conversations for months. When stakeholders begin using that reasoning themselves in meetings, the strategy has become a shared working model rather than a presentation artifact.

Prioritize problems with science and art

Prioritization combines structured analysis with product judgment. The scientific side estimates impact and effort through frameworks suited to the company's constraints. The art comes from understanding customers, their industry, likely changes over the next two or three years, and emerging competition. That accumulated context becomes informed conviction when the available data is incomplete.

One of Siddharth's clearest career lessons is to prioritize problems, not solutions. Earlier in his career, he ranked features or proposed answers. With experience, he shifted toward deciding which customer problems deserve attention. Once the team agrees on the important problem, solution exploration can follow without prematurely locking the roadmap to a single idea.

Customer requests also need interpretation. People often describe a desired solution when the underlying need is something else. The PM's task is to ask enough questions to separate the problem from the requested implementation. That protects the team from building a feature that satisfies the wording of a request but misses its cause.

Combine data with context and conviction

Dashboards can show direction, seasonality, and comparisons, but they cannot explain every reason behind a change. Siddharth argues for combining quantitative metrics with qualitative evidence. A usage decline during a holiday period, for example, means something different from the same decline during normal operations. Customer conversations and contextual notes help explain the pattern.

He imagines dashboards where qualitative observations are annotated over quantitative trends. This would let teams connect movement in a metric with the customer or market context surrounding it. AI may help with early drafts of strategy documents, root-cause analysis, and metric definition, but he still places the decisive value in human creativity and insight.

The same evidence supports stakeholder management. Siddharth had to develop the ability to disagree even without formal authority. His approach is to understand the customer thoroughly, bring product and competitive data, and push back when necessary. Conviction is not stubbornness. It is confidence earned through preparation.

Episode #83 offers a practical model for product leadership: listen for the real problem, align it with strategy, combine data with context, and keep the customer represented when decisions get difficult. Listen to the full conversation on Spotify.