<?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 gopika Soundar on Medium]]></title>
        <description><![CDATA[Stories by gopika Soundar on Medium]]></description>
        <link>https://medium.com/@gopikasoundar096?source=rss-163a52e805fa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*d7nN1PI-87I1PWY-</url>
            <title>Stories by gopika Soundar on Medium</title>
            <link>https://medium.com/@gopikasoundar096?source=rss-163a52e805fa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:46:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gopikasoundar096/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[I Thought Generating Ideas Was Hard. Then I Had to Prioritize Them.]]></title>
            <link>https://medium.com/@gopikasoundar096/i-thought-generating-ideas-was-hard-then-i-had-to-prioritize-them-259717196205?source=rss-163a52e805fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/259717196205</guid>
            <category><![CDATA[myfirstproject]]></category>
            <category><![CDATA[travel-app-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[prioritization]]></category>
            <dc:creator><![CDATA[gopika Soundar]]></dc:creator>
            <pubDate>Thu, 22 Oct 2026 09:13:39 GMT</pubDate>
            <atom:updated>2026-10-22T09:13:39.380Z</atom:updated>
            <content:encoded><![CDATA[<p><em>My biggest product management lesson from building CatchMyVibe — my capstone project, wasn’t about coming up with ideas. It was about deciding which ones deserved to be built.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o2GiqwTLtjNwtIQ9" /><figcaption>Photo by <a href="https://unsplash.com/@thepaintedsquarejessica?utm_source=medium&amp;utm_medium=referral">Jessica Lewis 🦋 thepaintedsquare</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When I started building CatchMyVibe, our AI-powered travel-planning application, I thought the biggest challenge would be coming up with innovative ideas.</p><p>I was wrong.</p><p>The real challenge began when we had too many ideas and had to decide which ones to turn into actual features.</p><p>Let me explain.</p><h3>The excitement of having too many ideas</h3><p>When our team first started working on CatchMyVibe, we were continuously exploring possibilities.</p><p>We wanted to create a travel application that could simplify the way people plan their trips. But what would make it genuinely useful? What problems should it solve? How could we make the experience different from traditional travel-planning platforms?</p><p>We didn’t want to jump straight into building something without exploring these questions.</p><p>So, we started brainstorming. We used frameworks such as SCAMPER and ERRC to challenge existing approaches, identify opportunities, and think about how we could improve the travel-planning experience.</p><p>Our discussions opened up several possibilities.</p><p>What if users could describe their travel plans in natural language instead of navigating multiple forms? What if AI could recommend flights and accommodation, generate a day-by-day itinerary, and optimize the trip according to the user’s budget?</p><p>We also explored ideas such as weather updates, group-trip coordination, expense splitting, local guides, and photography-related services.</p><p>Every discussion opened another door.</p><p>But there was something I didn’t anticipate: <strong>generating ideas was difficult, but choosing between good ideas was even harder.</strong></p><p>Initially, we struggled to generate ideas that felt innovative and useful. Once we started exploring different frameworks and perspectives, however, the challenge changed. We suddenly had more possibilities than we could realistically build.</p><p>And that was when the real product thinking began.</p><h3>When everyone believes their idea deserves a place</h3><p>As we moved closer to defining what we would actually build, we realised that we couldn’t include every idea in CatchMyVibe.</p><p>We had limited time and resources. More importantly, adding more features didn’t automatically mean we were creating a better product.</p><p>This led to some challenging team discussions.</p><p>Each of us had ideas we believed could make the application more valuable. We would discuss why a particular feature could improve the experience, attract users, or give CatchMyVibe an advantage.</p><p>I could understand the reasoning behind different suggestions. Many of these ideas genuinely had potential.</p><p>For example, photography-related services could enhance a traveller’s experience. Group coordination could make planning with friends easier. Weather updates could help travellers prepare for their trips.</p><p>The difficulty was that each feature had a reasonable argument in its favour.</p><p>How could we choose one over another?</p><p>Should we prioritise the features that made our application more distinctive? Should we include more capabilities to make the product feel complete? Or should we focus on a smaller set of features that solved the most important user problems?</p><p>I began to realise that we were at risk of evaluating ideas based on how attractive they sounded rather than how closely they aligned with our product’s purpose.</p><p>That was an important turning point for me.</p><p><strong>The question was no longer, “Which idea is the best?” It became, “Which idea is most important for the user and for the product we are trying to build?”</strong></p><h3>The shift: From defending ideas to understanding users</h3><p>This was the mindset shift that helped me look at the problem differently.</p><p>Instead of treating prioritization as a competition between ideas, I started thinking about the experience we wanted to create for our users.</p><p>Our central goal was to simplify travel planning through a conversation-first, AI-powered experience.</p><p>A traveller should be able to explain what they wanted, receive relevant recommendations, get a personalized itinerary, understand the estimated cost, and refine the plan without having to piece everything together manually.</p><p>Once we looked at our ideas through this lens, it became easier to distinguish between the features that supported the core experience and those that could enhance it later.</p><p>For instance, photography booking could add value to a trip, but was it necessary for a traveller to experience simpler, more personalized travel planning?</p><p>Not necessarily.</p><p>On the other hand, an AI travel planner, budget optimisation, accommodation recommendations, and itinerary generation were directly connected to the core experience we wanted to validate.</p><p>This didn’t mean photography was a bad idea. It meant we needed to be deliberate about when it belonged in the product.</p><p>That distinction changed how I thought about prioritization.</p><p>I learned that putting the user first doesn’t mean building every feature that a user might appreciate. It means understanding which problems matter most and focusing on the capabilities that address them.</p><h3>How product frameworks helped us make decisions</h3><p>Once we recognised the need to narrow our scope, we used prioritization frameworks to bring more structure to our discussions.</p><p>One framework that helped us organize our thinking was <strong>MoSCoW prioritization</strong>.</p><p>Rather than treating every idea as equally important, we categorized features into four groups: Must Have, Should Have, Could Have, and Won’t Have for the MVP.</p><p>For CatchMyVibe, our Must Have features included the AI Travel Planner, Budget Optimisation, Flight Recommendations, Accommodation Recommendations, AI-Generated Itinerary, and Unified Booking Dashboard.</p><p>These capabilities formed the foundation of the experience we wanted to deliver.</p><p>Other ideas, including real-time weather and travel alerts, group-trip coordination, expense splitting, and explainable AI recommendations, were classified as Should Have features.</p><p>Photography booking, along with local guide marketplace and rental vehicle booking, was categorised as a Could Have feature.</p><p>This gave us a way to preserve ideas with potential without allowing every idea to expand the initial scope.</p><p>Looking back, I see how the frameworks we used served different purposes.</p><ul><li><strong>Brainstorming</strong> helped us explore possibilities without immediately limiting our thinking.</li><li><strong>SCAMPER</strong> encouraged us to rethink existing travel experiences and consider alternative solutions.</li><li><strong>ERRC</strong> helped us examine what we could eliminate, reduce, raise, or create in the experience.</li><li><strong>MoSCoW</strong> helped us turn a broad set of possibilities into a more focused MVP scope.</li></ul><p>The important lesson was that frameworks weren’t substitutes for judgement. They helped us ask better questions, organize our thinking, and explain our decisions more clearly.</p><p>We still needed to evaluate ideas against the problem we were trying to solve.</p><h3>What I learned about building an MVP</h3><p>Before this experience, I might have thought that an MVP was simply a version of a product with fewer features.</p><p>Now, I see it differently.</p><p>An MVP should focus on the smallest set of capabilities that can deliver the core value and help validate an important product hypothesis.</p><p>For CatchMyVibe, our hypothesis was that travellers would prefer a conversation-first, AI-powered travel-planning experience over traditional form-based booking flows.</p><p>That meant we needed to prioritise the experience that would allow us to test this hypothesis, rather than trying to create an all-in-one travel platform immediately.</p><p>It also meant accepting trade-offs.</p><p>Some useful features would have to wait. Some exciting ideas wouldn’t make it into the initial scope. And we needed to be comfortable with those decisions, even when a deferred feature had genuine potential.</p><p>I began to understand that a focused MVP isn’t a sign of limited ambition.</p><p>It is a deliberate choice to concentrate effort, reduce unnecessary complexity, and learn from the core experience before expanding it.</p><p>Of course, prioritization doesn’t end when a feature list is finalized. Once a product is tested with users, evidence may reveal that our assumptions were wrong. Features may need to be reconsidered, reprioritised, or redesigned.</p><p>That is why I believe prioritization should be an ongoing process rather than a one-time exercise.</p><h3>The product management skills I developed along the way</h3><p>Building CatchMyVibe helped me connect several product management concepts to a real team experience.</p><p><strong>Product discovery:</strong> I learned to explore a problem from multiple perspectives before settling on a solution.</p><p><strong>User-centric thinking:</strong> I learned to evaluate features according to the problems they solve, rather than how exciting they sound.</p><p><strong>Prioritization and trade-offs:</strong> I learned to distinguish between features that support the core value proposition and those that can be considered later.</p><p><strong>MVP definition:</strong> I learned to connect feature selection to the hypothesis we wanted to validate.</p><p><strong>Collaboration and communication:</strong> I experienced why teams need a shared product objective and a structured way to discuss competing ideas.</p><p><strong>Outcome-oriented thinking:</strong> I began thinking beyond the number of features we could build and towards what we wanted users to achieve.</p><p>These are skills I want to continue developing as I work towards a career in Product Management.</p><h3>My biggest takeaway</h3><p>If someone had asked me at the beginning of this project what the hardest part of product management was, I might have said generating innovative ideas.</p><p>Today, my answer would be different.</p><p>Generating ideas requires creativity. Prioritization requires creativity too, but it also demands clarity, critical thinking, trade-offs, and the ability to look beyond personal preferences.</p><p>While building CatchMyVibe, I learned that a team can have many promising ideas and still struggle to build the right product if it cannot decide what matters most.</p><p>The turning point comes when the conversation shifts from defending individual ideas to understanding the user problem, the product objective, and the value each feature contributes.</p><p>I am still learning what it takes to become a good Product Manager, but this experience changed the way I approach product decisions.</p><p><strong>I no longer think the goal is to fit as many good ideas as possible into a product. The goal is to make thoughtful decisions about which problems to solve first, why they matter, and what we need to learn before building more.</strong></p><p>And sometimes, the most important product decision isn’t about what to build.</p><p>It’s about what to leave out — for now.</p><p><em>CatchMyVibe is my capstone project exploring AI-powered, conversation-first travel planning. This article reflects my personal learning from the team’s ideation and feature-prioritization process.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=259717196205" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Fixing Tickets to Finding Product Opportunities: A Support Engineer’s Perspective]]></title>
            <link>https://medium.com/@gopikasoundar096/from-fixing-tickets-to-finding-product-opportunities-a-support-engineers-perspective-eb40f8f34e6e?source=rss-163a52e805fa------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb40f8f34e6e</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[technical-support]]></category>
            <category><![CDATA[user-empathy]]></category>
            <dc:creator><![CDATA[gopika Soundar]]></dc:creator>
            <pubDate>Thu, 22 Oct 2026 09:04:13 GMT</pubDate>
            <atom:updated>2026-10-22T09:04:13.875Z</atom:updated>
            <content:encoded><![CDATA[<h4>How recurring customer issues changed the way I think about user problems, product improvements, and the value of solving problems at their source.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t9a4R-zKgSoNTLCv" /><figcaption>Photo by <a href="https://unsplash.com/@lukesouthern?utm_source=medium&amp;utm_medium=referral">Luke Southern</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In technical support, resolving a ticket often means helping a user get past a problem. But what if the same problem keeps coming back?</p><p>At some point, I started thinking beyond the immediate resolution. Instead of asking only, “How do we fix this issue?”, I began asking, “Could the product help users avoid this issue in the first place?”</p><p>That shift in perspective helped me see recurring support issues in a different light: not just as problems to resolve, but as potential opportunities to improve the product experience.</p><p>As someone working in technical support and aspiring to transition into product management, this is one of the most valuable lessons I am learning.</p><h3>👩‍💻What technical support taught me about users</h3><p>In my current role as a Technical Support Engineer, I support more than 100 applications in an agriculture-related project. My responsibilities include investigating user-reported issues, following standard operating procedures, guiding users through resolutions, and coordinating with specialist teams when an issue requires further investigation.</p><p>This experience has given me exposure to the challenges users face while trying to complete their day-to-day workflows.</p><p>A support ticket usually starts with a problem: something is not working as expected, a step is unclear, or a user needs help completing a task.</p><p>Resolving that issue is important. But when similar issues appear repeatedly, I believe there is another question worth asking:</p><p><strong>Are we only helping users recover from the problem, or could we improve the experience so that they are less likely to encounter it again?</strong></p><p>Not every recurring ticket indicates a product design flaw. Some issues may result from technical failures, permissions, data inconsistencies, or gaps in user training.</p><p>However, recurring patterns can provide a starting point for further investigation. They can help identify where a workflow might be confusing, where guidance might be missing, or where a user could benefit from a more intuitive experience.</p><p>That is where I began seeing a connection between technical support and product management.</p><h3>💭From a recurring issue to a product opportunity</h3><p>One example from my experience involved an invalid-item issue associated with a shipment container.</p><p>When the invalid item count for a container is greater than zero, resyncing the shipment can be a relevant resolution step.</p><p>My observation led me to consider a simple question: what if the product could make that next step more visible to the user?</p><p>Instead of requiring the user to raise a support ticket or discover the resolution through existing guidance, I proposed displaying an icon with a tooltip when the invalid-item condition occurs. The tooltip would prompt the user to resync the shipment.</p><p>The idea was straightforward: provide contextual guidance at the point where the issue becomes visible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZQcAOFT8Jl4j3cuE9Y4Qvw.png" /></figure><p>I saw this as an opportunity to explore whether a small user experience improvement could make the resolution easier to discover and potentially prevent avoidable support requests.</p><p>What interested me was not the tooltip itself. It was the possibility of addressing the user’s difficulty closer to where it occurred.</p><p>Of course, this was a proposed improvement, not an implemented feature. I do not have measured results demonstrating that it reduced support tickets or improved resolution time.</p><p>But the exercise changed the way I approached the problem. Rather than stopping at the existing resolution process, I started considering how the product experience itself might help.</p><h3>🖊️How I would approach this problem as a Product Manager</h3><p>Looking back, I would structure the investigation around four questions.</p><h3>First, is this a recurring problem worth solving?</h3><p>I would examine historical support tickets to understand how often the issue occurs, whether it affects multiple users, and whether the same resolution is repeatedly required.</p><p>I would also investigate the context in which the issue appears. Ticket frequency alone would not establish that a product change is necessary.</p><p>The objective would be to understand the scale of the problem and the effort it creates for users and support teams.</p><h3>Second, why are users encountering the problem?</h3><p>Before jumping to a solution, I would investigate potential root causes.</p><p>Is the resolution difficult to discover? Is the existing workflow unclear? Are users unaware of the resync option? Or is a technical issue causing the invalid-item condition in the first place?</p><p>These explanations would require different solutions. A tooltip might help users discover an existing resolution, but it would not fix an underlying data synchronization defect.</p><p>This is an important distinction: <strong>a visible symptom is not always the root cause.</strong></p><h3>Third, is a tooltip the right solution?</h3><p>I would explore whether the proposed tooltip is sufficient or whether a different intervention would better address the problem.</p><p>For example, contextual guidance might be appropriate if users simply struggle to discover the resync action. If the issue is caused by a technical defect, fixing that defect may be more valuable than adding another interface element.</p><p>I would also check whether resyncing is safe and appropriate in every situation where the invalid-item count is greater than zero.</p><p>The goal would be to solve the actual user problem with the simplest effective intervention.</p><h3>Fourth, how would I measure success?</h3><p>I would define success before implementation rather than assuming that the proposed change would work.</p><p>A possible primary metric would be the rate of support tickets related to this specific issue, measured against a suitable baseline and adjusted for changes in usage volume. It would be the rate of invalid-item support tickets per 1,000 eligible containers, so changes in shipment volume don’t distort the comparison.</p><p>I would also monitor supporting metrics such as successful resync completion, time to resolution, and the number of users who encounter the issue again to understand whether users are actually resolving the problem.</p><p>Guardrail metrics would matter too. For example, I would want to ensure that the prompt does not lead to unnecessary resync attempts or introduce confusion into the workflow.</p><p>The exact metrics and evaluation period would depend on the available data and the technical context. Since the feature hasn’t been implemented, these are proposed metrics and a validation plan, not measured results.</p><p>The important point is that the proposal should be evaluated through evidence, not intuition alone.</p><h3>📝 Three lessons I am taking into product management</h3><p><strong>Lesson 1: Repeated problems deserve investigation, not just repeated resolution.</strong></p><p>Support tickets can reveal patterns in user difficulties. Those patterns do not automatically justify a feature, but they can help identify where deeper product discovery is needed.</p><p><strong>Lesson 2: Small improvements can be worth exploring when they address a real user need.</strong></p><p>A product improvement does not always need to begin with a large feature. Sometimes, making an existing action easier to discover may be a useful hypothesis to test.</p><p><strong>Lesson 3: A good idea is only the beginning.</strong></p><p>Identifying a problem and proposing a solution are important steps, but they are not proof of impact. Understanding the root cause, validating the solution, and measuring outcomes are equally important.</p><p>This is the mindset I want to continue developing as I move toward product management.</p><h3>💡From resolving issues to improving experiences</h3><p>My experience in technical support has helped me understand the importance of looking beyond the immediate issue. It has also shown me that the people closest to recurring user problems can have valuable observations about opportunities for improvement.</p><p>I am now working to develop that perspective further by learning product discovery, prioritization, experimentation, and analytics.</p><p>I see product management as an opportunity to bring these questions together: what are users struggling with, why does it matter, what should we change, and how will we know whether the change worked?</p><p>I am still learning, but I believe that asking better questions is a meaningful first step toward building better products.</p><p><strong>A question for fellow product people:</strong> Have you ever encountered a recurring support issue that you believed could be prevented through a product improvement? How did you determine whether it was worth solving?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb40f8f34e6e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>