5 Product Building Lessons That Dostoevsky Might Offer

Five timeless lessons from Dostoevsky's profound psychological insights that reveal how 19th-century wisdom about human nature can transform modern product building.

ProductLeadershipStrategy6 min read

In my free time, I enjoy reading psychological stuff, and one of my top picks is Dostoevsky. Although his writings feel quite modern, I always wonder how the experiences of a 19th-century novelist relate to our current reality. How many useful insights can one draw from his works to such a seemingly distant subject as product building? With this thought in mind, I decided to create a short list of 5 product building lessons that Dostoevsky might offer if he were with us today. Maybe he would have been a great product builder too, hehe.

Empathy is key

Dostoevsky's works provide a profound insight into human emotions, desires, and conflicts. One prominent example is Alyosha from "The Brothers Karamazov", whose deep empathy and understanding for those around him make him a central figure of the story. Just as Alyosha seeks to comprehend and help others in their struggles, product managers should strive to deeply understand their users' needs and aspirations.

But here's the thing - empathy isn't just about understanding what users say they want. It's about understanding why they sometimes want contradictory things, why they make "irrational" choices, why they need to feel in control even when they're asking for guidance. When product managers truly connect with users at this deeper level, they can craft products that genuinely resonate.

Beware of grand theories

Dostoevsky shows us the pitfalls of being too wrapped up in big ideas. Take "Crime and Punishment" for example, where Raskolnikov's bold theory drives him to act, only to face the consequences later. His perfectly logical system falls apart when confronted with the messy reality of human emotion and guilt.

Similarly, product people can get too focused on grand visions and elegant frameworks that might not serve real user needs. This is a nudge to remember to ground big ideas in user reality. A brilliant vision on paper doesn't always translate to real-world success. Sometimes the metrics look perfect but the product feels soulless.

Complexity of decision-making

In "The Grand Inquisitor" from "The Brothers Karamazov", Dostoevsky delves into the tough choices we make and their implications. The parable explores the tension between freedom and security, and how there's rarely a clear right answer.

For PMs, this serves as a reminder that decision-making isn't black and white. With various stakeholders, each with their distinct perspectives and priorities, product development becomes a delicate balancing act. Sometimes users say they want freedom but choose products that guide them. Sometimes they ask for simplicity but need complexity. A successful PM remains flexible, adapting strategies based on evolving insights and shifting landscapes.

Conflict can be constructive

Dostoevsky's narratives often highlight how conflicts, internal or external, lead to personal growth and reflection. Characters like Ivan and Alyosha in "The Brothers Karamazov" represent opposing worldviews, and their friction illuminates truths neither could reach alone.

This is a valuable lesson for product managers. In the iterative process of product development, differing viewpoints and debates are inevitable. Rather than shying away, PMs should embrace these as opportunities – moments that spark innovation, challenge prevailing norms, and ultimately lead to more refined and effective product decisions. Sometimes the struggle itself reveals what really matters.

The bigger picture

Dostoevsky consistently probes the broader questions of life, diving into purpose and the search for meaning. His characters constantly grapple with questions of what makes us human, what gives life value beyond mere survival or optimization.

Similarly, in product building, it's vital for PMs to occasionally step back from the specifics. It's not just about features or numbers. It's about asking: Why are we creating this? Who benefits? How does this fit into the broader journey of our users? What kind of experience are we creating for people's lives?

By looking at the larger context, we can ensure our products stay meaningful and actually improve people's lives in ways that matter.

Egor Shesternin - Senior product manager