<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sami Topal on Medium]]></title>
        <description><![CDATA[Stories by Sami Topal on Medium]]></description>
        <link>https://medium.com/@samitopal?source=rss-6b8989857d2d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FYL7jPWKOJvWDbudmvEtEw.jpeg</url>
            <title>Stories by Sami Topal on Medium</title>
            <link>https://medium.com/@samitopal?source=rss-6b8989857d2d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 12:22:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@samitopal/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[My Decision-Making Evolution]]></title>
            <link>https://medium.com/@samitopal/my-decision-making-evolution-a586e7d50ecd?source=rss-6b8989857d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a586e7d50ecd</guid>
            <dc:creator><![CDATA[Sami Topal]]></dc:creator>
            <pubDate>Wed, 12 Feb 2025 13:41:47 GMT</pubDate>
            <atom:updated>2025-02-12T13:41:47.450Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mCllbZND40w1H5km8g2_tA.png" /></figure><p>For years, making decisions, especially in my career, felt like a real mental battle. Not complete paralysis, but a definite internal struggle. I was always searching for that “single right answer” to every problem, every choice. But the reality is, in the real world, particularly at work, “right” is often elusive. You’re juggling shifting priorities, and much feels subjective. How do you ever feel confident in your decisions?</p><p>It used to frustrate me. Let’s say we made a choice and it was successful, generated revenue, and satisfied customers. But what if we had chosen the other option, perhaps achieving much better results? Maybe we made the right choice, but overlooked something in the design or gave up because it required too much effort. What if we hadn’t given up and had been even more successful? These thoughts inevitably lead one to consider all alternative universes and scenarios. This is actually an impossible and meaningless endeavor. Worse, basing choices solely on our current perspective felt risky — what if our perspective changed tomorrow?</p><p><strong>The “Right Answer” Myth</strong></p><p>It seemed everyone else had it all figured out, speaking with certainty, as if their ideas were divine decrees, not just… thoughts. These doubts chipped away at my confidence. I’d second-guess myself, a project manager supposed to be decisive and persuasive. Self-doubt is no ally. Looking back, I see I still delivered, made bold choices, often trusting my gut. But that underlying uncertainty lingered, sometimes thinking for the more defined world of coding.</p><p>These doubts, they didn’t stop me in my tracks, but they definitely chipped away at my confidence. I’d question myself, second-guess things. And when you’re a project manager, supposed to be persuasive, decisive, leading the charge… self-doubt is not your friend. Looking back, I can see I still got things done, even made some bold calls, often going with my “gut” when the moment came. But that underlying uncertainty was always there.</p><p><strong>The Liberation of “No Single Right Answer”</strong></p><p>But then, slowly, something shifted. It wasn’t just an intellectual thing; it was deeper. I truly accepted that there isn’t just one “right” answer. And you know what? It wasn’t depressing or overwhelming at all. It was… freeing. It was like this huge weight lifted. Suddenly, I didn’t have to chase this impossible ideal of perfect decisions anymore, didn’t have to burn myself out trying. I could channel that energy elsewhere.</p><p><strong>“Another Framework?”</strong></p><p>Okay, so no single right answer. That’s liberating, but it also leaves you with a big question: how do you make good decisions then? Do you just wing it? Should there be some kind of guide, a framework? I realized there’s no magic, one-size-fits-all solution for every company or product process. But I became convinced that every individual needs a dynamic, “living” process, something that can evolve, to enhance their personal decision-making within any context. A good, adaptable framework can bring in different viewpoints, make things transparent, improve teamwork, and cut down on conflicts. It moves decision-making beyond just one person’s instincts and provides a structure you can personally refine. This framework, of course, isn’t designed to replace your company’s existing procedures. Rather, it’s a personal approach you can adapt to enhance your own decision-making capabilities within the company processes already in place. So, I started thinking about the key ingredients — the moving parts of this “living” personal framework. It’s not like this framework is set in stone once you build it. It’s meant to evolve. I think I will cover the details of this in another article.</p><p><strong>The Clarity that Fuels You</strong></p><p>The big lesson for me was this: When I stopped chasing the perfect decision and accepted that multiple paths could work, my energy surged. Instead of getting drained by searching for mythical “right” answers, I found power in understanding that our world is interconnected and ever-changing. By really understanding that change is constant and outcomes aren’t always predictable, I stopped fighting against uncertainty. Paradoxically, this acceptance of life’s dynamic nature gave me both mental clarity and renewed energy to move forward with confidence.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a586e7d50ecd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Handle Conflicts as a Product Manager]]></title>
            <link>https://medium.com/@samitopal/how-i-handle-conflicts-as-a-product-manager-c19ddcab36d0?source=rss-6b8989857d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c19ddcab36d0</guid>
            <dc:creator><![CDATA[Sami Topal]]></dc:creator>
            <pubDate>Thu, 06 Feb 2025 21:46:47 GMT</pubDate>
            <atom:updated>2025-02-06T21:46:47.006Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oiFu5Dii0IhqWNxlEdL1sA.png" /></figure><p>Conflicts are inevitable in any team, but I truly believe that prevention is often more effective than correction. Just as a simple design review can save weeks of rework, building a foundation of trust and mutual understanding can help address disagreements before they escalate.</p><p>I focus on nurturing strong relationships with my colleagues — especially engineers and designers — to create an environment where issues are discussed openly. This proactive approach not only makes it easier to find common ground but also helps everyone understand each other’s perspectives.</p><h3>Empowering Stakeholders Through Transparency</h3><p>I’m a big advocate of empowering stakeholders with the right information. By providing up-to-date roadmaps, weekly status updates, and regular office hours for feedback, everyone stays in the loop without the need for constant one-on-one check-ins. This self-service mindset fosters transparency and collaboration, reducing misunderstandings that can lead to conflicts.</p><p>I also appreciate the idea of an “open kitchen” approach in product management. While you can’t invite everyone into the nitty-gritty details of your work every day — just as a restaurant doesn’t give every guest a tour of its kitchen — occasional behind-the-scenes sessions can really help stakeholders appreciate the complexity of our process. These moments go a long way in building trust and mutual respect.</p><h3>Recognizing the Types of Conflicts</h3><p>In my experience, conflicts usually fall into three categories:</p><p><strong>Healthy Pushback: </strong>This is when cross-functional partners — like engineers challenging technical assumptions or designers advocating for a better user experience — provide feedback that ultimately strengthens the product.</p><p><strong>Misalignment: </strong>Sometimes conflicts arise due to differing priorities, resource constraints, or conflicting stakeholder demands. Open communication, clear goal-setting, and finding common ground typically help resolve these issues.</p><p><strong>Personal Differences: </strong>At the end of the day, we’re all human and won’t always see eye-to-eye. Not every disagreement needs to be “fixed” immediately, and sometimes it’s okay to agree to disagree.</p><h3>Strategies for Resolving Disagreements</h3><p>When conflicts arise, I find it essential to revisit the product’s purpose and overall goals. Understanding each stakeholder’s underlying motivations helps me identify areas of alignment and potential compromises. Techniques like stack-ranking competing objectives can also provide clarity, allowing us to prioritize what truly matters.</p><p>In the rare cases where consensus remains elusive, I escalate the matter to management. I document the situation, outline the attempted solutions, and clearly state what I’m asking for. This not only brings in a fresh perspective but also helps facilitate a constructive discussion that leads to a mutually acceptable solution. Early intervention prevents conflicts from harming product delivery, team morale, or my reputation as a product manager.</p><p>Ultimately, effective conflict resolution is an ongoing process. By nurturing relationships, refining communication channels, and staying proactive, we can navigate disagreements and drive successful product development.</p><h3>Energy Management Reflections</h3><p>As I practice these approaches, I often reflect on a few key lessons that help me manage my energy and maintain sustainable performance:</p><p><strong>On Relationship Dynamics:</strong></p><ul><li>I find that my energy is most effective when I focus deeply on key stakeholder relationships.</li><li>Authentic, professional collaboration often matters more than striving for perfect harmony.</li></ul><p><strong>About Building Self-Service Systems:</strong></p><ul><li>I’ve seen better results when I grow these systems organically, starting with immediate needs.</li><li>Each iteration reveals what stakeholders truly value, and small, successful steps build more momentum than big, exhausting pushes.</li></ul><p><strong>Reflecting on “Open Kitchen” Moments:</strong></p><ul><li>The most impactful sessions tend to naturally align with project milestones.</li><li>Group dynamics can bring unexpected synergies and shared understanding.</li><li>Genuine stakeholder curiosity often leads to a clear sense of purpose.</li></ul><p><strong>Understanding Conflict Patterns:</strong></p><ul><li>Not every tension needs active intervention — some issues resolve themselves with a bit of space.</li><li>The most draining conflicts often share common warning signs that, once recognized, can be managed more effectively.</li></ul><p><strong>Personal Sustainability Insights:</strong></p><ul><li>The quality of interactions often matters more than their frequency.</li><li>Clear boundaries benefit everyone involved, not just me.</li><li>Being aware of my fluctuating energy levels helps me adapt and stay effective.</li></ul><p>By embracing these strategies and reflections, I’ve learned that effective conflict management is as much about understanding people as it is about processes and strategies. In the end, it’s all about building an environment where every voice is heard and every challenge becomes an opportunity for growth.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c19ddcab36d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Do You Decide What to Build? A Product Manager’s Perspective]]></title>
            <link>https://medium.com/@samitopal/how-do-you-decide-what-to-build-a-product-managers-perspective-9700cd66cd7e?source=rss-6b8989857d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9700cd66cd7e</guid>
            <dc:creator><![CDATA[Sami Topal]]></dc:creator>
            <pubDate>Thu, 06 Feb 2025 21:43:28 GMT</pubDate>
            <atom:updated>2025-02-06T21:43:28.534Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QcsUfXRjgubA5l-iZFaYMA.png" /></figure><p>This question is quite challenging, and to be honest, the word “decide” makes me a little stressed!</p><p>Every company, product, and team is unique. The need for product management (PM) depends on factors such as company culture, product life cycle, strategy, and market competition. To begin, let’s start with the definition of product management.</p><p>The definition of product management can vary significantly from one company to another. If you ask different people within the same organization, you’re likely to receive different answers. My perspective has evolved over the past five years — and it may continue to change as I gain more experience.</p><p>Currently, I like to define product management as follows:</p><p><strong>A product manager is responsible for identifying the right problems to solve, defining what success looks like, and guiding their team to achieve successful outcomes.</strong></p><p>So, according to that definition, PM is primarily responsible for <strong>identifying the right problems to solve.</strong></p><p>It’s also helpful to start with a few assumptions:</p><ul><li>The company has a clear strategy, and the product team understands its approach and definition of success.</li><li>Every individual in the company shares a common goal that does not conflict with others.</li></ul><h3>Recognizing Uncertainty</h3><p>First, it’s important to acknowledge that there is no 100% reliable way to predict the future using data, customer feedback, market conditions, or other signals. When you decide to act — for example, delivering a product within a month — the market may have shifted by launch time. <strong>Your insights could be influenced by personal thoughts, biases, or desires, and you might not present your product in a way that truly resonates with customers.</strong> Additionally, customers may choose not to use a feature or product for a variety of rational or emotional reasons.</p><p>I accept that every opportunity is based on assumptions. By embracing this reality, I focus on increasing my chances of success, especially given the limitations of time, money, and resources.</p><h3>Frameworks and Processes</h3><p>Moving on, one might ask if there is a definitive framework to guide these decisions. In short, I don’t believe there is one absolute solution or a single correct framework for every situation, company, or product. However, I do believe every company should maintain a dynamic, “living” process or framework. With a well-defined process, stakeholders remain informed and engaged without relying solely on the product manager. This approach increases transparency, fosters collaboration, and reduces potential conflicts.</p><h3>Leading Through Influence and Building Trust</h3><p>Another key aspect of product management is that it’s an individual role based on influence rather than authority. You cannot simply order what to build — you need to persuade and inspire others. While market data, customer insights, and other arguments are useful, the most effective approach is building trust. When you share your thought process openly, consider all possibilities, and demonstrate genuine care for the company’s best interests, you earn that trust. It can get a bit emotional at times, but that genuine connection is crucial.</p><p>The key to effective product management isn’t just about making the right decisions — it’s about creating a sustainable process that consistently supports decision-making while keeping the team aligned and motivated. This balance requires a mix of analytical thinking, emotional intelligence, and strategic vision.</p><h3>Embracing Uncertainty and Experimentation</h3><p>Sometimes, deciding what to build goes beyond data and rigid frameworks — it’s about trusting our gut, embracing uncertainty, and learning from every stumble along the way. I remember when the fear of failure used to paralyze me. The idea of trying something new was daunting, and I worried endlessly about what could go wrong. Over time, I learned that every small experiment, no matter how imperfect, is an opportunity to grow.</p><p>For example, I once ran a low-stakes pilot for a new feature with a select group of users. Their feedback completely changed our approach, teaching us invaluable lessons about our customers and the market. Each “failure” turned out to be a stepping stone toward a better understanding of what truly matters.</p><h3>The Power of Genuine Communication</h3><p>Equally important is the value of genuine, unguarded communication. Some of the best insights come during casual chats over coffee or quick hallway conversations, where everyone feels safe sharing even their half-formed ideas. Without the pressure of formal meetings or the fear of judgment, creativity flows naturally. In those moments, it becomes clear how essential it is for everyone to feel heard and valued.</p><p>For me, product management isn’t about following a strict set of rules or sticking rigidly to a framework. It’s about embracing uncertainty, being willing to take risks, and learning from our missteps. Every honest conversation and every small, brave experiment brings us closer to building something that truly matters — not just for the business, but for the people we serve.</p><h3>In Conclusion</h3><p>At the end of the day, deciding what to build isn’t about having a foolproof plan. It’s about being open to the journey — a process of continuous learning and adaptation where every challenge and breakthrough brings us closer together as a team. Knowing that we’re all in this together, learning from each other every day, is what makes this work so incredibly rewarding.</p><p>This journey is messy and full of uncertainties, but it’s also where real growth happens. Embrace the process, communicate openly, experiment boldly, and trust that every step — whether a success or a failure — is part of building something truly meaningful.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9700cd66cd7e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Reflection on Jeffrey Pfeffer’s 7 Rules of Power]]></title>
            <link>https://medium.com/@samitopal/a-reflection-on-jeffrey-pfeffers-7-rules-of-power-fb1c6493cc34?source=rss-6b8989857d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb1c6493cc34</guid>
            <dc:creator><![CDATA[Sami Topal]]></dc:creator>
            <pubDate>Sun, 23 Jun 2024 14:19:09 GMT</pubDate>
            <atom:updated>2024-06-23T14:19:09.952Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently listened to an episode of Lenny’s podcast featuring the distinguished professor and author Jeffrey Pfeffer. Before this episode, I was unfamiliar with Jeffrey, but I quickly realized it was a significant oversight.</p><p>The discussion centered around Pfeffer’s latest book, “7 Rules of Power.” I found myself increasingly conflicted as the conversation progressed. Let me list the rules to make it more clearer:</p><ol><li><strong>Get out of your own way.</strong></li><li><strong>Break the rules.</strong></li><li><strong>Show up in a powerful fashion.</strong></li><li><strong>Create a powerful brand.</strong></li><li><strong>Network relentlessly.</strong></li><li><strong>Use your power.</strong></li><li><strong>Understand that once you have acquired power, what you did to get it will be forgiven, forgotten, or both.</strong></li></ol><p>At one point, Lenny echoed my own sentiments, saying, “I think here people might be hearing this and they’re like, I don’t want to be this person. I don’t want to be talking all the time. I don’t want to be pretending like open posture. Is the advice here just you don’t need to do all these things.” This question encapsulated the internal conflict I was experiencing.</p><p>Pfeffer’s response was both insightful and unsettling. He shared that people typically navigate through four stages when confronted with such teachings: denial, anger, sadness, and acceptance. He explained, “When they get angry at me, how can you teach us this stuff? Then they’ll go into sadness. I actually believe this and I’m depressed. And if we’re successful, they will go through acceptance.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ty2HAbKr8Z_rQGzih3yukQ.png" /></figure><p>Personally, I find myself hovering between stages 2 and 3 — anger and sadness. I know human nature, but these teachings clash with my values. While I acknowledge that adhering to these rules can make life easier, I’m troubled by the notion of promoting such principles.</p><p>This discomfort stems from a deeper conviction that life lessons should be imparted differently. Everyone seems to learn these harsh truths through personal trials and tribulations. Perhaps our families or society at large should bear the responsibility of teaching us how to navigate the complexities of life. <strong>Or,</strong> i<strong>f we collectively believe these power dynamics are flawed, shouldn’t we strive to construct systems that foster fairness and justice?</strong></p><p>In conclusion, while Jeffrey Pfeffer’s 7 Rules of Power offers a pragmatic roadmap to gaining power, it also raises critical ethical questions for me personally. I hope that as humankind continues to evolve, we will strive to be better than that. My wish is for a future where power is wielded with integrity, empathy, and a genuine commitment to fairness and justice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KQXFaa86HRtAEBlcBFuUXw.png" /></figure><p>Podcast link: <a href="https://www.lennysnewsletter.com/p/the-paths-to-power-jeffrey-pfeffer">https://www.lennysnewsletter.com/p/the-paths-to-power-jeffrey-pfeffer</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb1c6493cc34" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dergilik Journey Part 4 — Podcast Studion]]></title>
            <link>https://medium.com/@samitopal/dergilik-journey-part-4-podcast-studion-b2e27500f4d?source=rss-6b8989857d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2e27500f4d</guid>
            <category><![CDATA[fizy]]></category>
            <category><![CDATA[dergilik]]></category>
            <category><![CDATA[podcast]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Sami Topal]]></dc:creator>
            <pubDate>Mon, 27 Dec 2021 06:06:51 GMT</pubDate>
            <atom:updated>2025-02-12T13:59:33.580Z</atom:updated>
            <content:encoded><![CDATA[<h3>Dergilik Journey Part 4 — Podcast Studion</h3><p>Exploring and sharing my evolving thoughts. Check out my <a href="https://blog.samitopal.com/">blog</a> (<a href="https://blog.samitopal.com/">https://blog.samitopal.com</a>) for more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hSaI2gMs-L7Wj6W4iiFjug.jpeg" /></figure><p>The idea of a podcast platform had been brewing since my time at fizy. Strategic priorities shifted, and the project remained on the back burner. However, when I joined Dergilik, the concept resurfaced, and I was excited to finally bring it to life! 🎉 This marked the beginning of the “Podcast Studion” project.</p><p>Bringing Podcast Studion to fruition was a truly collaborative effort. It was an incredible opportunity to work alongside talented colleagues and supportive managers from across various departments — development, quality assurance, design, business strategy, operations, security, legal, marketing, and more. The success of this project is a testament to their collective expertise and dedication. 🙏</p><p>Our initial strategy evolved as the project progressed. The refined plan was ambitious: to launch a dedicated podcast platform under a new brand, “Podcast Studion,” and then seamlessly distribute these podcasts through both the Dergilik and fizy applications. Furthermore, during development, new content regulations emerged, necessitating a moderation process. We proactively adapted our architecture and workflow to incorporate this crucial step. The diagram below illustrates the core components of our final architectural design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eqpBaSamf6_Kk9pDmSxCUg.png" /></figure><p><strong>Podcast Studion — Building the Foundation</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n8YfGDgDIE931X3S4hu62A.png" /></figure><p>Our first priority was to build a robust foundation with Podcast Studion itself. This platform needed to be ready to onboard podcasters and facilitate early adoption. We meticulously considered the entire podcaster journey: from streamlined registration and podcast ownership verification to comprehensive customer support. Once a podcaster was verified, our platform intelligently parsed their RSS feed, automatically extracting essential metadata and episode audio files. To optimize performance and security, we hosted these audio files on our Content Delivery Network (CDN). Importantly, we built a flexible “switch” feature, allowing us to either host the audio files directly or deliver them from the podcaster’s original source, giving us control and adaptability. After four months of focused effort, the team proudly launched Podcast Studion! 🚀</p><p><strong>Dergilik App Integration — Enhancing User Experience</strong></p><p>With Podcast Studion live, we shifted our focus to seamless integration with the Dergilik mobile application. Leveraging the Audio Article and Auto-list improvements we had previously implemented (as discussed in earlier articles), we extended these functionalities for podcasts. This resulted in a dynamic and intuitive podcast experience within the Dergilik app. Beyond the user-facing features, we also integrated comprehensive analytics into the podcast platform. This crucial step laid the groundwork for providing podcasters with valuable performance insights directly through their podcaststudion.com dashboards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q_x0myGUMTYCEaMdvfMixQ.png" /></figure><p><strong>Review and Moderation Process — Adapting to Regulations</strong></p><p>During development, new content regulations mandated a podcast review process. Adapting to this requirement meant developing an efficient content approval workflow. We integrated an approval phase into the podcast publishing process, defining essential editor roles within Podcast Studion and building tools for editors to listen to, search for, and approve episodes. This adaptation, integrated into an existing workflow, presented a unique development challenge. Furthermore, in collaboration with our AI team, we implemented a Speech-to-Text (STT) based analysis process for all episodes. The AI platform now automatically analyzes each episode and flags content requiring editorial review, ensuring compliance and content quality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/531/1*AWTFB9I-WQNn4dKYaSpkdQ.png" /></figure><p><strong>Addressing Challenges and Optimizations — Refining the Platform</strong></p><p>As podcasters began populating the platform, we encountered real-world challenges and identified opportunities for optimization. The lack of standardization among podcast hosting providers initially caused some integration issues. Once these were resolved, we proactively focused on platform optimization, even without immediate performance bottlenecks. We meticulously refined our content crawling process, optimizing the frequency for adding, updating, and removing podcast episodes. By implementing solutions like e-tag and hash-based checks, we systematically addressed these issues, ensuring a robust and efficient platform.</p><p><strong>Podcast Analytics Dashboard — Empowering Podcasters</strong></p><p>Providing podcasters with insightful data was paramount. Therefore, we developed a comprehensive analytics dashboard within Podcast Studion. This dashboard provides key metrics such as follower counts, unique listener numbers per episode, average listening time, and more. To further empower podcasters, we also designed a monthly insights newsletter, delivering a summary of their podcast performance directly to their inbox.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/226/1*P8RovTlyP7uYcfJ5eeTfog.png" /></figure><p><strong>fizy App Integration — Expanding Reach</strong></p><p>The final stage was integrating Podcast Studion with the fizy application. Following architectural alignment, we established a data pipeline using Kafka to deliver podcast metadata and updates to fizy. fizy then leveraged the same analytics infrastructure to populate their podcast dashboards. With the fizy app launching podcast support, podcasters now have the exciting opportunity to distribute their content across two major platforms, significantly expanding their reach to millions of potential listeners! 🎉</p><p><strong>Conclusion — Success and Future Potential</strong></p><p>The Podcast Studion project exemplifies the power of collaboration, adaptability, and a user-centric approach. From initial concept to multi-platform launch, we navigated evolving requirements and technical complexities to deliver a robust and valuable podcasting platform. Podcast Studion not only provides a seamless experience for podcasters but also expands Dergilik and fizy’s content offerings, opening up new avenues for audience engagement and growth. We are incredibly proud of what the team accomplished and excited to see Podcast Studion continue to thrive and evolve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jytj_wXW3VoQ37ONLGEzUg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kAAFJOA-uICBnPJLsjNq_w.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2e27500f4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dergilik Journey Part 3 — Search]]></title>
            <link>https://medium.com/@samitopal/dergilik-journey-part-3-search-b49dccbfe28f?source=rss-6b8989857d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b49dccbfe28f</guid>
            <category><![CDATA[improvement]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[elasticsearch]]></category>
            <category><![CDATA[dergilik]]></category>
            <dc:creator><![CDATA[Sami Topal]]></dc:creator>
            <pubDate>Tue, 14 Dec 2021 17:27:00 GMT</pubDate>
            <atom:updated>2025-02-12T13:52:17.369Z</atom:updated>
            <content:encoded><![CDATA[<h3>Dergilik Journey Part 3 — Search</h3><p>Exploring and sharing my evolving thoughts. Check out my <a href="https://blog.samitopal.com/">blog</a> (<a href="https://blog.samitopal.com/">https://blog.samitopal.com</a>) for more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ml3Hf8RfFnGwLx8QnBBQOQ.png" /></figure><p>Dergilik, a content platform established in 2011, faced a growing business challenge: user search. Our aging search infrastructure was hindering user engagement and content discovery. <strong>From a product perspective, this translated to lost opportunities for content consumption and potentially lower user retention.</strong> Imagine a user, actively seeking specific news, typing keywords and encountering frustratingly irrelevant or empty result pages. This was the daily experience for many Dergilik users, directly impacting their satisfaction and our platform’s value. User experience analysis quantified this, revealing significant issues — users struggled to find desired content, often failing completely. <strong>The data clearly indicated a critical need: a strategic product initiative to dramatically overhaul the search experience and unlock the full potential of our content library.</strong></p><p>The strategic objective became clear: <strong>revolutionize content discovery and enhance user engagement through a superior search experience.</strong> The chosen solution was the development of a new search engine for Dergilik, leveraging Elasticsearch. For me, as a key team member on this initiative, this was a significant opportunity and a steep learning curve. My technical background provided a solid base, but my manager’s deep Elasticsearch expertise and strategic vision were invaluable. He articulated the potential impact of improved search — not just faster results, but a fundamental shift in how users interacted with Dergilik. <strong>His vision underscored the business value of this project and was a primary driver for my commitment.</strong> Eager to contribute to this impactful initiative, I dedicated myself to mastering Elasticsearch. The initial learning phase presented challenges, but through focused effort, I quickly developed the necessary skills. Building a cloud-based sandbox with Dergilik data and seeing it deliver relevant results was a pivotal moment, solidifying my readiness to drive this project forward.</p><p>We approached implementation strategically with a phased plan. <strong>From a risk mitigation perspective,</strong> our first step was to replicate the existing search functionality on the new infrastructure. This ‘lift and shift’ approach provided a stable foundation for testing, performance monitoring, and minimized immediate disruption to the user experience. Gaining robust production environment monitoring capabilities was also crucial for ongoing optimization. <strong>I want to specifically acknowledge Derya’s critical role in enabling this monitoring infrastructure.</strong> Her expertise and collaborative approach were instrumental throughout the project. In fact, her consistent ownership, problem-solving skills, and team-oriented approach have been invaluable across numerous Dergilik projects, making her an exceptional asset to the team.</p><p>Understanding the existing user search behavior was essential. Users could search article titles, magazine/newspaper names, and article text. However, the limitations were significant: lack of prefix and fuzzy search directly hampered usability. Even minor typos resulted in zero results, effectively locking users out from relevant content and <strong>creating a negative user experience that impacted product satisfaction.</strong></p><p>Our first phase with Elasticsearch prioritized backend stability. <strong>This was a conscious product decision to de-risk the migration.</strong> By initially mirroring the old search, we focused on validating the new architecture, rigorously testing Elasticsearch performance, and proactively identifying potential issues — all <em>before</em> introducing any user-facing changes. <strong>This phased approach was crucial for ensuring a smooth transition and minimizing user disruption.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X_-1qT0HioH6VKykai34-A.png" /></figure><p>Phase two directly addressed user needs and focused on <strong>delivering tangible user-facing improvements.</strong> We prioritized three key feature enhancements:</p><ul><li><strong>Prefix Search (Improved Search Efficiency):</strong> Users could now find content faster and more intuitively by typing just the initial letters of a word. “uy” instantly suggesting “uykusuz” significantly streamlined search. <strong>This directly addressed user efficiency and reduced search time.</strong></li><li><strong>Fuzzy Search (Error Tolerance &amp; Inclusivity):</strong> Minor typos no longer presented roadblocks. “uuykusuz” intelligently resolving to “uykusuz” <strong>made the search more forgiving and inclusive, catering to real-world user input patterns.</strong></li><li><strong>Intelligent Scoring (Relevance &amp; Content Prioritization):</strong> Implementing tailored scoring algorithms based on read counts, downloads, and publication date ensured that the most popular and relevant content was prioritized in search results. <strong>This directly enhanced content discoverability and drove engagement with high-value content.</strong></li></ul><p>The subsequent phase expanded <strong>content coverage and search depth.</strong> Full-text search across newspapers and magazines was implemented. <strong>This strategic expansion unlocked a vast amount of previously unsearchable content.</strong> Users could now effortlessly locate specific mentions within article text, dramatically increasing the utility of search for niche topics and detailed information retrieval.</p><p>Finally, and importantly for long-term user engagement, we launched “Similar Articles.” <strong>This feature went beyond basic search, proactively promoting content discovery and personalized user journeys.</strong> By providing recommendations based on reading habits, “Similar Articles” fostered deeper exploration and increased time spent within the Dergilik platform. <strong>This feature directly supported our goals of increased user engagement and content consumption.</strong></p><p>The Dergilik search engine overhaul has been a <strong>successful product initiative with demonstrable impact.</strong> By strategically leveraging Elasticsearch and adopting an iterative, user-centric approach, we have not only modernized our technology stack but fundamentally enhanced content discovery and user satisfaction. While specific performance metrics are internal, we observed a <strong>significant positive shift in user engagement metrics and overwhelmingly positive user feedback, indicating a clear ROI for this product investment.</strong> Looking ahead, we are committed to continuous improvement, leveraging user data and exploring advanced features to ensure Dergilik’s search remains a key differentiator and driver of user value in the competitive digital content landscape.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*sniiI_TgJXsJB3gypIXnZQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b49dccbfe28f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dergilik Journey Part 2 — Text to Speech]]></title>
            <link>https://medium.com/@samitopal/dergilik-journey-part-2-text-to-speech-b0f92f1861e6?source=rss-6b8989857d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0f92f1861e6</guid>
            <category><![CDATA[dergilik]]></category>
            <category><![CDATA[tts]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[text-to-speech]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Sami Topal]]></dc:creator>
            <pubDate>Thu, 09 Dec 2021 16:46:30 GMT</pubDate>
            <atom:updated>2021-12-09T16:46:30.426Z</atom:updated>
            <content:encoded><![CDATA[<h3>Dergilik Journey Part 2 — Text to Speech</h3><p>Users have the option of reading articles from Dergilik, which can cover a wide range of topics such as travel and tourism, cooking and food, car economy, and so on. As I mentioned in <a href="https://medium.com/@samitopal/dergilik-journey-part-1-e47b1a1aa517">part 1</a>, we wanted to provide another option to our users when they are doing chores around the house or driving during their commute, and their eyes and hands are occupied with something else. So we wanted to give our customers a listening experience🎧 with Text-to-Speech.</p><p>We started to review TTS Engines; Google, Microsoft, and Nuance for the Turkish language with our contents. Google did a good job, but our AI team did better. The only risk was that it was not yet ready for production.🙈 Anyway, we’ve decided to stick with our AI team solution, and we’re glad we did.🚀</p><h3>Mobile App</h3><p>I wanted to start with mobile applications because it is easier to explain with photos. We had excellent mobile developers on staff at Dergilik, and we came to gather with the fizy(music streaming app) mobile team to speed up things. Luckily, you can find many developers in every field in Turkcell who have experience and can ask questions. We got all the key points and knowledge about streaming in the iOS/Android ecosystem. And let me show you two pictures. The left one was our first version🙈, and the right one current version.🚀</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OW8M9XTUPffuqa1HW0JkDw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7MTZSmhvMuYO66pjHDBJNg.png" /><figcaption>Tablet and Phone</figcaption></figure><p>You can easily see the differences, but let me explain further below.</p><ul><li>The user could not change the playback speed in the first version.</li><li>The user could not share content in the first version.</li><li>After listening to one article, the user was stuck because he didn’t have a playlist in the first version.</li><li>The user could not seek on the player in the first version.</li><li>The second one is far superior and more functional from a design standpoint.</li></ul><blockquote>We launched our first version in three months, and we didn’t try to make it perfect; instead, we tried to iterate on adding something new in the shortest amount of time possible. Therefore, we started with the most basic features and made continuous optimizations with the A/B test and user feedback.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2UIWcj0i234sCsb5cupVew.png" /></figure><p><strong>CMS &amp; AI</strong><br>We came together with the team and told them what we wanted to do, and they told us their working methods.</p><ul><li>They prepared around 10+ new articles with different topics every day.</li><li>They prepared articles usually between 08:00–11:00.</li><li>They could probably change the content of an article.</li><li>They could prepare drafts without publishing.</li><li><strong>We asked them to listen to these TTS files before publishing</strong>. So default value of visibility audio files was false.</li></ul><p><strong>We decided to make it mandatory to listen to articles before publishing because we wanted to be sure about the quality of audio files.</strong> After launching the feature in whitelist users, we got feedback from the content management team and made these changes.</p><ul><li>We put simple player, but we missed time information and seek option in player. It was painful for our content team to listen and seek at on specific time. They had to download mp3 files to their computer to solve that problem. So we updated our player quickly.</li><li>They made more changes to the articles as we expected. So It caused an overload problem which slowed down the translation process on the TTS platform. The AI team found a clever solution; they cache each article and only process/consider changing sentences. It solved our problem without expanding our infrastructure.</li><li>TTS is not an easy job. Every language has its unique grammar, and we do not usually care about grammar. There were different problems such as abbreviations, special names, and foreign words. So our AI team put great effort into that and quickly trained the TTS platform to solve these problems.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/180/1*MLyW7iwBb-yPvMYVYPidsg.png" /></figure><ul><li>We changed our rule to listen to articles before publishing because it was inefficient. We let the content team publish articles without listening and put a Beta label on the Android player. Unfortunately, we couldn’t put it on the Apple platform because of their policy.</li><li>We launched the application in whitelist to Turkcell employees. It’s a great way to gain feedback with this beta group.</li></ul><p><strong>Platform</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/892/1*e2bNY56G2B_xDb880Vaw1g.png" /></figure><p>I want to put a schema to show the basic architecture. As I mentioned, we started with a mobile client because the TTS platform was not production-ready. While developing necessary services for TTS, we also changed our list architecture. We developed an architecture called as Auto-List. maybe we’re not good at naming :) The idea was that everybody could create an auto-list of articles, magazines, newspapers without development or deployment. For example, they’d create “most popular articles, articles from X magazine, articles for business people” without any development with basic SQL, and it’s live on production. We used that architecture in articles and podcasts, and I’ll go into detail in the podcast part.</p><p>Anyway, after Auto-List, we started to develop integration with the TTS platform. We sent article text to the TTS platform, and we were waiting for audio file location asynchrony. After we got the audio file location, we uploaded audio files to our cdn and made them playable for mobile apps. Of course, this was the happy path and, we also need to handle:</p><ul><li>We didn’t have an unlimited source; the TTS platform could be busy on the ongoing process, so we had to implement a retry mechanism.</li><li>We had to monitor ongoing tasks easily, and we had to make them visible to everyone.</li><li>If we got errors on a task/process, we needed to report the necessary people with details. Maybe in some cases, we are required to retry.</li></ul><p>The entire team (Development, QA, Content Management, Business, Operation, AI, Security, and many others) took the initiative and worked efficiently. We did not work extra hours for this job; it’s all the result of teamwork. In just three months, we were able to launch this feature. Over 2 million audio articles were listened to in the first 11 months alone.🚀✌🏻👏🏻</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*qUO97tWTKLFU_6G6OQwJ2g.gif" /></figure><p><strong>In Part 3, I’ll be talking about how we changed the Speech Experience</strong>. As a memory, I’d want to share some highlights from our team. Since we started working remotely after covid, we did not have a chance to get together. That’s why photos may not include all team members.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cFb91xY7UUoqXwNbLxQjqw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nnjacDmgJkZME0XS-etl-A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VqzQ9EBjpNQy5-tD_0faEA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NG7l8arb0M5v9dnaJqbjDg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0f92f1861e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dergilik Journey — Part 1]]></title>
            <link>https://medium.com/@samitopal/dergilik-journey-part-1-e47b1a1aa517?source=rss-6b8989857d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e47b1a1aa517</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[dergilik]]></category>
            <category><![CDATA[digital-publishing]]></category>
            <category><![CDATA[data-analytics]]></category>
            <dc:creator><![CDATA[Sami Topal]]></dc:creator>
            <pubDate>Thu, 25 Nov 2021 13:01:07 GMT</pubDate>
            <atom:updated>2021-11-25T13:01:07.638Z</atom:updated>
            <content:encoded><![CDATA[<h3>Dergilik Journey — Part 1</h3><p>I worked as a product manager for <strong>Dergilik</strong> for nearly two years, and I’d want to share my journey. Since I couldn’t cover everything in this series, I’ll focus on the ones in which I’ve been actively involved. <strong>First of all, during those two years, I had the chance to meet and work with amazing people, thanks for all.</strong> Let’s start by explaining the product.</p><p>Dergilik is a digital reading platform in Turkey with around <strong>1 million monthly active users and 20 million downloads</strong>. Users can read a wide variety of magazines and newspapers as well as listen to podcasts from any mobile device. In fact, users can play different games just like Netflix does these days. The app allows you to access a wide range of magazines, newspapers, and podcasts of your choice anytime, anywhere with just one click without having to carry them physically. (<a href="https://dergilik.com.tr/">https://dergilik.com.tr</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3KQnoDUsn-LYXSinK2ST2Q.png" /></figure><p>Even if Dergilik is the biggest and leading digital reading platform, it is clear that reading habits are decreasing, that’s a whole other discussion. Anyway, we identified that as our focus and adopted a new strategy. “<strong>Find innovative ways to deliver digital content and make user experience easy and enjoyable</strong>”. The product has changed dramatically since this new strategy was implemented, but I’ll concentrate on the changes that I’ve been actively involved with.</p><h3>Data &amp; Analytics</h3><p>We started with data &amp; analytics and our objective was obviously to send all necessary data (events, dimensions, etc). It was very important, there is no need to go into detail to explain its importance. <strong>It helps you build the right thing and solve problems quickly. “Without data, you’re just another person with an opinion” (W. Edwards Deming).</strong> So we made a gap analysis and prioritized each necessary metric. Although it may not seem like a very difficult job to do, it was not. Let me try to explain with an example; we wanted to track reading and listening durations and we had to consider all edge cases. For example:</p><blockquote>User gets a phone call in the middle of reading a magazine or listening an article User abandons the app and attends to the caller. What happens to your duration metrics?</blockquote><p>Our most important KPIs were related to duration. If we hadn’t thought and covered those edge cases we would be in a worse situation before. So there were showstopper edge cases that must be considered carefully.</p><blockquote>Of course, it was really critical to monitor those KPIs. But there are other priorities, and if we only focused on these KPIs, we wouldn’t be able to provide any benefits to our customers.</blockquote><p>As a solution, we used 20% of our velocity per sprint for these tasks. I think it’s good practice to allocate a percentage of each Sprint’s sprint capacity to handle such ongoing tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rb_WDMnEX059YTQnF2lsmg.png" /></figure><p>We were using Firebase and Google Analytics as our analytics tools. We even created a dashboard using Google Data Studio to make it easy to focus on specific metrics. Finally, we were able to track key metrics (KPIs) such as:</p><ul><li>Average reading durations for each content type (article, magazine, newspaper)</li><li>Average listening durations for each content type (article, podcast)</li><li># of read, listen, download, favorite, share for each content type</li><li>Search activities</li><li>Retention Rate, Churn Rate, MAUs, DAUs, Average Session, Installs/Uninstalls, Registrations, Subscriptions</li><li>App Performance: Load Time, Crashes, API Latency</li></ul><p><strong>In Part 2, I’ll be talking about Text-to-Speech Experience</strong>. As a memory, I’d want to share some highlights from our team. Since we started working remotely after covid, we did not have a chance to get together. That’s why photos may not include all team members.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PJQE95xrkEQgG5-6x45rpw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PB60hEm_hSjwF2OXjTQXnw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SBwKyPZK0u1b4qjCqdqfmg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JrX6uUmj4gzKuHFJ50oxPA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BJR_OlSdPp1FUvO2S-P18w.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e47b1a1aa517" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product I Love — FlowCV]]></title>
            <link>https://medium.com/@samitopal/product-i-love-flowcv-fd8371f8480d?source=rss-6b8989857d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd8371f8480d</guid>
            <category><![CDATA[resume-builder]]></category>
            <category><![CDATA[resume]]></category>
            <category><![CDATA[cv]]></category>
            <category><![CDATA[cv-builder]]></category>
            <dc:creator><![CDATA[Sami Topal]]></dc:creator>
            <pubDate>Fri, 05 Nov 2021 21:03:37 GMT</pubDate>
            <atom:updated>2021-11-05T21:03:37.190Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product I Love — FlowCV</h3><p>Writing a resume is really difficult. I have been struggling for years to find a proper tool that would create resume. I am sure you are having the same problem.</p><p>I’ve been using <a href="https://flowcv.io/">FlowCV</a> for over a year and I’m very satisfied with the results. You can prepare different versions of your cv easily and you can also use for your cover letters. If you’re looking for a tool, then <a href="https://flowcv.io/">FlowCV</a> is a tool that you should check out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6jEPsopslKPiokLu7Dzneg.png" /><figcaption><a href="https://flowcv.io/">https://flowcv.io/</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd8371f8480d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product I Loved — Waking Up]]></title>
            <link>https://medium.com/@samitopal/product-i-loved-waking-up-e2bb0c483bb0?source=rss-6b8989857d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2bb0c483bb0</guid>
            <category><![CDATA[meditation]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[sam-harris]]></category>
            <category><![CDATA[waking-up]]></category>
            <dc:creator><![CDATA[Sami Topal]]></dc:creator>
            <pubDate>Thu, 04 Nov 2021 07:45:16 GMT</pubDate>
            <atom:updated>2021-11-04T07:46:18.822Z</atom:updated>
            <content:encoded><![CDATA[<h3>Product I Loved — Waking Up</h3><h3>Waking Up</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*Bgd0qF7ORho7TYBtRcce6A.png" /></figure><p>I got to know about this app when I listen an <a href="https://designdetails.fm/episodes/9If3dnMP">episode</a> from podcast Design Details. Cemre Güngör was a guest on a part of the Design Details podcast and suggested this <a href="https://wakingup.com/">application</a>. By the way it was an enjoyable episode that about the transition process from design to product management. It might be worth listening especially if they’re thinking of transitioning.</p><p>I did not have much knowledge for meditation before. I wanted to try it for some time, but gave up after a few tries.</p><p>Now it’s been about 2 months, and I’m still using app. I’m not sure if it will continue or not but I’ve really enjoyed it.</p><p>I like that Sam Harris guides you during the meditation stage and guides you by adding little bits in each episode. I don’t think there will be any difficulty understanding the language, even though it is in English.</p><p>Interestingly, he discussed a quite different approach to pricing in the first episode. They point out that the annual price of $99 is too high for you and you can request a free account if that’s what you’re hesitant to use. This is a luxury price for Turkey and as they said when I requested a free account they defined it immediately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wZ1V7MOPeipfIunpvRP_Vg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2bb0c483bb0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>