<?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 Shakshi Neha on Medium]]></title>
        <description><![CDATA[Stories by Shakshi Neha on Medium]]></description>
        <link>https://medium.com/@snshakshineha452?source=rss-faa7af454455------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*gqHqozrfPrPiFC6R</url>
            <title>Stories by Shakshi Neha on Medium</title>
            <link>https://medium.com/@snshakshineha452?source=rss-faa7af454455------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 15:16:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@snshakshineha452/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[‍ Leading & Building: Technical & Behavioural Acumen for PMs (Part 6 of 8)]]></title>
            <link>https://medium.com/@snshakshineha452/leading-building-technical-behavioural-acumen-for-pms-part-6-of-8-8465cf053291?source=rss-faa7af454455------2</link>
            <guid isPermaLink="false">https://medium.com/p/8465cf053291</guid>
            <category><![CDATA[pm]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Shakshi Neha]]></dc:creator>
            <pubDate>Fri, 14 Nov 2025 05:35:22 GMT</pubDate>
            <atom:updated>2025-11-14T05:35:22.031Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Welcome back to the Product Management Interview Prep Series!</strong></p><p>In Part 5, we mastered data-driven decisions through metrics and experimentation. Now, in Part 6, we address two critical, yet often intimidating, areas: <strong>Technical Understanding (System Design)</strong> and <strong>Behavioural Skills</strong>. These topics assess your ability to collaborate with engineering teams, influence without authority, and demonstrate the soft skills essential for successful product leadership.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AESn7uDJovebifytr3bYMg.png" /></figure><h3>1. System Design: Bridging the Technical Gap</h3><p>PMs aren’t engineers, but they must speak their language. System design questions (e.g., “Design a URL shortener,” “How would you build an Uber-like service?”) test your ability to think about scalability, architecture, and technical trade-offs.</p><h3>Key Areas to Cover:</h3><ul><li><strong>Clarification:</strong> Just like product design, start by clarifying scope, scale, and requirements (e.g., “How many users?”, “What’s the latency requirement?”).</li><li><strong>High-Level Architecture:</strong> Propose the main components (e.g., Load Balancers, Web Servers, Database, Caching Layer, API Gateway). You don’t need to draw detailed diagrams, but mentally sketch them.</li><li><strong>Data Models:</strong> Think about the key entities and their relationships (e.g., for a URL shortener: short_url, long_url, user_id, clicks).</li><li><strong>Scalability &amp; Reliability:</strong> Discuss how you would handle high traffic (horizontal scaling), data consistency (replication), and potential failures (redundancy, monitoring).</li><li><strong>APIs:</strong> Consider the core APIs required for the service.</li><li><strong>Trade-offs:</strong> This is crucial. Every technical decision has a trade-off.</li><li><em>Example:</em> Relational vs. NoSQL database (consistency vs. flexibility/scalability).</li><li><em>Example:</em> Caching (faster reads) vs. consistency issues.</li></ul><h3>The PM’s Role in System Design:</h3><p>You are not expected to write code or design the exact database schema. Your role is to:</p><ol><li><strong>Understand the implications</strong> of technical decisions on product features and user experience.</li><li><strong>Communicate user needs</strong> and business goals clearly to engineers.</li><li><strong>Facilitate trade-offs</strong> between engineering effort, time-to-market, and product capabilities.</li></ol><h3>2. Technical Interview Steps: Structured Problem Solving</h3><p>Even if not a full system design, you might get smaller technical questions. Approach them with a clear process:</p><ol><li><strong>Clarify:</strong> Ask questions until you fully understand the problem and requirements.</li><li><strong>Base Case/Assumptions:</strong> Start with the simplest scenario and state any assumptions you’re making.</li><li><strong>Talk Aloud:</strong> Verbalize your thought process. This is critical for the interviewer to follow your logic.</li><li><strong>Write Solution (High-Level):</strong> Outline your approach, perhaps pseudocode or a list of steps.</li><li><strong>Review:</strong> Briefly check for edge cases, potential issues, and optimize if time permits.</li></ol><h3>3. Behavioural Questions: The STAR Method for Impactful Stories</h3><p>Behavioural questions (e.g., “Tell me about a time you failed,” “Describe a conflict with an engineer”) are designed to assess your soft skills, leadership potential, and cultural fit. The <strong>STAR Method</strong> is your best friend here.</p><ul><li><strong>S — Situation:</strong> Briefly set the scene. What was the context?</li><li><strong>T — Task:</strong> What was your responsibility or goal in that situation?</li><li><strong>A — Action:</strong> What specific steps did <em>you</em> take to address the task? Focus on your individual contribution.</li><li><strong>R — Result:</strong> What was the outcome? Quantify the impact if possible. What did you learn?</li></ul><h3>Tips for STAR Stories:</h3><ul><li><strong>Quantify Everything:</strong> Numbers make your impact tangible (e.g., “increased X by Y%”, “saved Z hours”).</li><li><strong>Focus on YOU:</strong> While collaboration is key, ensure your actions are highlighted.</li><li><strong>Embrace Failure:</strong> Show you learn from mistakes, don’t just blame.</li><li><strong>Practice, Practice, Practice:</strong> Have 5–7 strong STAR stories ready that cover common themes (leadership, conflict, failure, success, dealing with ambiguity, working with engineers/designers).</li></ul><h3>4. Communication &amp; Soft Skills: The PM’s Superpower</h3><p>Beyond frameworks, effective PMs are exceptional communicators and influencers.</p><ul><li><strong>Showing Empathy:</strong> Not just for users, but for your team members (engineers, designers, sales). Understand their constraints and motivations.</li><li><strong>Gaining Stakeholder Buy-In:</strong> How do you convince a sceptical executive or a busy engineering lead? It involves data, a clear articulation of value, and understanding their perspective.</li><li><strong>Adapting Communication Style:</strong> Adjust your message for different audiences (e.g., technical deep-dive for engineers, high-level business impact for leadership).</li><li><strong>Active Listening:</strong> Truly hearing and understanding others’ perspectives is vital for successful collaboration.</li></ul><p><strong>In the Interview,</strong> these skills are assessed throughout. Be articulate, listen carefully to questions, and demonstrate your collaborative nature.</p><p>In this section, we learnt that it requires both conceptual understanding and personal reflection to under the complete behaviour. You can check your knowledge with below questions.</p><ol><li><strong>System Design:</strong> Prepare a high-level design for a <strong>“Photo Sharing App”</strong> (like Instagram), focusing on scalability and core components.</li><li><strong>STAR Method:</strong> Develop a STAR story for: <strong>“Tell me about a time you had a significant disagreement with an engineer/designer about a feature, and how you resolved it.”</strong></li></ol><p>In <strong>Part 7</strong>, we will dive into the <strong>Product Requirements Document (PRD)</strong>, understanding its crucial role and key components.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8465cf053291" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Data-Driven Decisions: Metrics, Prioritisation & Experimentation (Part 5 of 8)]]></title>
            <link>https://medium.com/@snshakshineha452/data-driven-decisions-metrics-prioritisation-experimentation-part-5-of-8-133c18f11fb7?source=rss-faa7af454455------2</link>
            <guid isPermaLink="false">https://medium.com/p/133c18f11fb7</guid>
            <dc:creator><![CDATA[Shakshi Neha]]></dc:creator>
            <pubDate>Fri, 14 Nov 2025 05:34:33 GMT</pubDate>
            <atom:updated>2025-11-14T05:34:33.534Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Welcome back to the Product Management Interview Prep Series!</strong></p><p>In Part 4, we charted the course with Product Strategy and Vision. Now, in Part 5, we shift our focus to <strong>Metrics &amp; Execution</strong>. This is the heartbeat of a data-driven Product Manager — how you measure success, diagnose problems, prioritise features, and ultimately drive growth.</p><p>Interviewers will test your ability to think analytically, define KPIs, and make informed decisions. Let’s dive in.</p><h3>1. Metrics &amp; KPIs: The AARRR Funnel (Pirate Metrics)</h3><p>When asked about measuring product success, the <strong>AARRR Funnel</strong> (often called Pirate Metrics due to its pronunciation: “aaarrr!”) is your go-to framework. It provides a comprehensive view of the customer journey and helps identify key areas for improvement.</p><ul><li><strong>A</strong>cquisition: How users <strong>find</strong> your product.</li><li><em>Examples:</em> App downloads, website visits, sign-ups, unique visitors.</li><li><em>PM Focus:</em> Top of the funnel growth, marketing channels, initial awareness.</li><li><strong>A</strong>ctivation: How users experience their first <strong>“aha moment”</strong> or successful interaction.</li><li><em>Examples:</em> First successful photo upload, completing a profile, making a first purchase, using a core feature.</li><li><em>PM Focus:</em> Onboarding flow, time-to-value, reducing friction.</li><li><strong>R</strong>etention: How often users <strong>return</strong> to your product.</li><li><em>Examples:</em> Daily/Weekly/Monthly Active Users (DAU/WAU/MAU), churn rate, repeat purchases.</li><li><em>PM Focus:</em> Driving habit formation, long-term engagement, user delight.</li><li><strong>R</strong>eferral: How users <strong>share</strong> your product with others.</li><li><em>Examples:</em> Viral coefficient, invites sent, shares on social media.</li><li><em>PM Focus:</em> Built-in sharing features, incentivizing referrals, word-of-mouth growth.</li><li><strong>R</strong>evenue (Monetization): How your product <strong>generates income</strong>.</li><li><em>Examples:</em> Average Revenue Per User (ARPU), Customer Lifetime Value (CLTV), conversion rate from free to paid.</li><li><em>PM Focus:</em> Pricing strategy, upsells, new monetization avenues.</li></ul><p><strong>The North Star Metric:</strong> Beyond the funnel, understand the concept of a <strong>North Star Metric (NSM)</strong>. This is a single, critical metric that best captures the core value your product delivers to customers and aligns with your business goals (e.g., Airbnb’s NSM might be “number of nights booked”).</p><h3>2. Prioritisation Frameworks: Making Tough Choices</h3><p>A PM’s job is often about saying “no” and justifying “yes.” Effective prioritisation frameworks help you make data-backed decisions on what to build next.</p><ul><li><strong>ROI Estimate (Return on Investment):</strong> Covered in the CIRCLES Method (Part 3), this involves estimating the potential value (return) against the cost/effort (investment) of a feature.</li><li><strong>RICE (Reach, Impact, Confidence, Effort):</strong> A robust scoring model.</li><li><strong>R</strong>each: How many users will this feature affect?</li><li><strong>I</strong>mpact: How much will it move the needle on your key metrics?</li><li><strong>C</strong>onfidence: How certain are you about your Reach and Impact estimates?</li><li><strong>E</strong>ffort: How much work (person-months) will this feature require from the team?</li><li><em>Formula:</em> (Reach x Impact x Confidence) / Effort = RICE Score.</li><li><strong>MoSCoW (Must-have, Should-have, Could-have, Won’t-have):</strong> Ideal for defining scope, especially in early-stage products or for MVP (Minimum Viable Product).</li><li><strong>M</strong>ust-have: Non-negotiable, essential for the product to function or be legally compliant.</li><li><strong>S</strong>hould-have: Important, provides significant value but not critical for initial launch.</li><li><strong>C</strong>ould-have: Nice-to-have, adds value but with little impact if omitted.</li><li><strong>W</strong>on’t-have: Explicitly decided not to implement in this release.</li></ul><p><strong>In the Interview,</strong> when asked to prioritise, choose a framework, define your criteria, and then apply it to the given features, explaining your rationale.</p><h3>3. Experimentation: Designing &amp; Analysing A/B Tests</h3><p>Modern product development is all about continuous learning through experimentation. <strong>A/B testing</strong> is a PM’s superpower for validating hypotheses with real user data.</p><ul><li><strong>A/B Test Design (Hypothesis -&gt; Metrics -&gt; Guardrails):</strong></li><li><strong>Hypothesis:</strong> Clearly state what you believe will happen. <em>Example: “We hypothesise that changing the ‘Buy Now’ button colour to green (Variant B) will increase click-through rate by 10% compared to blue (Variant A).”</em></li><li><strong>Success Metric (Overall Evaluation Criterion — OEC):</strong> The primary metric you’re trying to move. <em>Example: Click-Through Rate (CTR) of the ‘Buy Now’ button.</em></li><li><strong>Guardrail Metrics:</strong> Other important metrics that you want to ensure <strong>don’t negatively impact</strong> (e.g., overall conversion rate, page load time, user satisfaction).</li><li><strong>Test Setup:</strong> Define control (A) and variant (B), audience segmentation, and duration.</li></ul><p><strong>Analysis &amp; Interpretation:</strong></p><ul><li>Was the result statistically significant?</li><li>Did the primary metric move in the desired direction?</li><li>Were there any negative impacts on guardrail metrics?</li><li>What are the next steps (roll out, iterate, abandon)?</li></ul><h3>4. Estimation/Guesstimation: Explaining Your Assumptions</h3><p>These “how many…” or “what’s the market size…” questions test your structured thinking under uncertainty. The actual number is less important than your <strong>process and assumptions</strong>.</p><p><strong>Top-Down vs. Bottom-Up:</strong></p><ul><li><strong>Top-Down:</strong> Start with a large, known number and break it down (e.g., total population -&gt; internet users -&gt; app users).</li><li><strong>Bottom-Up:</strong> Start with a small, specific data point and scale it up (e.g., users per city -&gt; total cities).</li><li><strong>Key Principle: Explicit Assumptions:</strong> Always state your assumptions clearly (e.g., “I’m assuming 50% of people own smartphones,” “The average order value is $20”).</li><li><strong>Structure:</strong> Break the problem into manageable parts, use round numbers, and explain each step aloud.</li></ul><h3>5. Pricing: Frameworks for Value Capture</h3><p>Pricing is a strategic decision that directly impacts revenue and customer perception.</p><ul><li><strong>Value-Based Pricing:</strong> Setting prices based on the perceived value to the customer, rather than cost. (e.g., A productivity tool priced based on how much time it saves users).</li><li><strong>Competitive Pricing:</strong> Setting prices relative to competitors. (e.g., Pricing a streaming service slightly below a market leader).</li><li><strong>Cost-Plus Pricing:</strong> Adding a markup percentage to the total cost of producing the product. (e.g., Hardware manufacturers often use this).</li><li><strong>Freemium:</strong> Offering a basic version for free and charging for premium features.</li><li><strong>Subscription:</strong> Charging a recurring fee for continuous access.</li></ul><h3>Your Action Plan for Part 5</h3><p>To truly master metrics and execution, practice breaking down problems.</p><p><strong>Homework:</strong> Prepare answers to these prompts:</p><ol><li><strong>AARRR &amp; NSM:</strong> “You are the PM for a new habit-tracking app. Define a North Star Metric and suggest 2–3 key metrics for each stage of the AARRR funnel.”</li><li><strong>Prioritization (RICE):</strong> “You have three features: ‘Dark Mode,’ ‘In-app Chat Support,’ and ‘Offline Sync.’ Using RICE, which would you prioritize for your productivity app, and why?” (Provide assumed R, I, C, E values).</li><li><strong>A/B Test Design:</strong> “How would you design an A/B test to see if a new onboarding flow increases user activation?”</li></ol><p>In <strong>Part 6</strong>, we will tackle <strong>Technical &amp; Behavioural</strong> questions, including the challenging world of System Design and the critical STAR method for behavioural responses.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=133c18f11fb7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[️ Strategic Navigator: Charting Product Vision & Market Entry (Part 4 of 8)]]></title>
            <link>https://medium.com/@snshakshineha452/%EF%B8%8F-strategic-navigator-charting-product-vision-market-entry-part-4-of-8-ef52caaed233?source=rss-faa7af454455------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef52caaed233</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[pm]]></category>
            <dc:creator><![CDATA[Shakshi Neha]]></dc:creator>
            <pubDate>Fri, 14 Nov 2025 05:34:14 GMT</pubDate>
            <atom:updated>2025-11-14T05:34:14.520Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Welcome back to the Product Management Interview Prep Series!</strong></p><p>In Part 3, we mastered Product Design and Critique. Now, we zoom out from individual features to the grander scope: <strong>Product Strategy and Vision</strong>. These questions assess your ability to envision the big picture, establish a compelling direction, and justify long-term investments. This is where you demonstrate leadership and foresight.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fUxNDf97aSq7lLM4ybvgpQ.png" /></figure><h3>1. Product Strategy &amp; Vision: The Guiding North Star</h3><p>Every great product needs a guiding star. As a PM, you are responsible for defining and communicating this direction.</p><ul><li><strong>The Vision (The “Why”):</strong> This is the inspirational, long-term aspiration for the product. It answers <em>why</em> the product exists and <em>what impact</em> it aims to have on the world. It should be stable, aspirational, and customer-centric.</li><li><em>Example: Google’s vision is “to organise the world’s information and make it universally accessible and useful.”</em></li><li><strong>The Strategy (The “How”):</strong> This outlines <em>how</em> you plan to achieve the vision. It involves key decisions about target users, competitive advantage, differentiation, and primary business goals. It’s more flexible than the vision, adapting to market changes.</li><li><em>Example (for Google’s strategy): Focus on AI-driven search, expanding into mobile platforms, and monetising through advertising.</em></li><li><strong>The Roadmap (The “What/When”):</strong> This is a high-level, living document detailing the <em>what</em> (features, initiatives) and <em>when</em> (timeline, phases) for achieving your strategy. It’s a communication tool, not a commitment.</li></ul><p><strong>In the Interview:</strong> When asked about strategy, start with a clear vision, then articulate a logical strategy that supports it, and finally, present a high-level roadmap to execute that strategy.</p><h3>2. Market Entry &amp; Competition: Analysing the Landscape</h3><p>When considering a new market or product, understanding the competitive landscape and your fit within it is paramount.</p><ul><li><strong>Market/Competition/Company Fit (e.g., SWOT Analysis):</strong></li><li><strong>Market:</strong> What is the total addressable market? Is it growing? What are the key trends?</li><li><strong>Competition:</strong> Who are the direct and indirect competitors? What are their strengths and weaknesses?</li><li><strong>Company Fit:</strong> Does the proposed product align with your company’s existing capabilities, brand, and resources? (This is often assessed using a <strong>SWOT Analysis</strong> — Strengths, Weaknesses, Opportunities, Threats).</li><li><strong>Porter’s Five Forces:</strong> A classic framework for analysing the attractiveness and competitive intensity of an industry.</li></ul><ol><li><strong>Threat of New Entrants:</strong> How easy is it for new competitors to join the market?</li><li><strong>Bargaining Power of Buyers:</strong> How much influence do customers have over prices?</li><li><strong>Bargaining Power of Suppliers:</strong> How much influence do suppliers have over the company and its costs?</li><li><strong>Threat of Substitute Products or Services:</strong> Are there alternative ways for customers to meet their needs?</li><li><strong>Rivalry Among Existing Competitors:</strong> How intense is the competition among current players?</li></ol><p><strong>In the Interview:</strong> When discussing market entry, use these frameworks to show you’ve considered the full strategic landscape, not just your product idea in isolation.</p><h3>3. Problem Deep Dive: The 5 Whys</h3><p>Strategic problems often have hidden roots. The <strong>5 Whys</strong> is a simple yet powerful technique for <strong>root cause analysis</strong>, helping you uncover underlying problems beyond the obvious symptoms.</p><ul><li><strong>How it Works:</strong> You repeatedly ask “Why?” (typically five times, but it can be more or less) to drill down into a problem until you reach its core cause.</li><li><strong>Example:</strong></li><li><strong>Problem:</strong> Our user engagement dropped last month.</li><li><strong>Why?</strong> Users aren’t returning to the app after the first week.</li><li><strong>Why?</strong> They don’t see immediate value after onboarding.</li><li><strong>Why?</strong> The onboarding tutorial is too long and confusing.</li><li><strong>Why?</strong> We tried to explain too many features at once.</li><li><strong>Why?</strong> We lack a clear definition of the “aha moment” for new users.</li><li><strong>Root Cause:</strong> The strategy for demonstrating early value to new users is poorly defined.</li></ul><p><strong>In the Interview:</strong> Use the 5 Whys when asked to diagnose a problem (e.g., “Why do you think our new feature isn’t being adopted?”) to demonstrate a methodical, analytical approach.</p><h3>4. Creative Solutions: Beyond Incrementalism</h3><p>Strategy isn’t just about analysis; it’s about innovative solutions. Interviewers look for “Big Thinking.”</p><ul><li><strong>Reversal:</strong> What if we did the <em>exact opposite</em> of what everyone expects? (e.g., “What if our library charged for returns instead of late fees? What would be the implications?”)</li><li><strong>Challenging the Status Quo:</strong> Don’t just accept how things are. Ask “Why?” and “What if?” constantly. This is about identifying unarticulated needs.</li><li><strong>Analogies/Cross-Industry Thinking:</strong> How do other industries solve similar problems? Can we adapt their solutions?</li></ul><h3>5. Go-to-Market (GTM) Strategy</h3><p>Launching a product is not just releasing code. A solid <strong>GTM strategy</strong> ensures your product reaches the right users effectively.</p><ul><li><strong>Key Components of a GTM Plan:</strong></li></ul><ol><li><strong>Target Audience:</strong> Who exactly are we launching this for?</li><li><strong>Value Proposition:</strong> What unique problem does this solve for them? What’s the core message?</li><li><strong>Distribution Channels:</strong> How will we reach our target users (e.g., in-app promotion, email, social media, PR, partnerships)?</li><li><strong>Launch Phases:</strong> Will it be a soft launch, beta, or full public release?</li><li><strong>Success Metrics:</strong> How will we measure the success of the <em>launch itself</em> (e.g., downloads, sign-ups, feature adoption rate)?</li></ol><p><strong>In the Interview:</strong> When asked “How would you launch X?”, structure your answer using these components to demonstrate a holistic understanding of product deployment.</p><p><em>Strategic thinking is a muscle that needs flexing.</em></p><p>For testing your knowledge, prepare answers to these prompts, using the frameworks discussed:</p><ol><li><strong>Strategy &amp; Porter’s:</strong> “Our company wants to enter the ‘smart home security’ market. What factors should we consider, and what would be your initial strategy?”</li><li><strong>5 Whys:</strong> “Why might a user stop using a meditation app after the first week?”</li><li><strong>GTM:</strong> “How would you launch a new ‘group video calling’ feature within an existing messaging app like WhatsApp?”</li></ol><p>In <strong>Part 5</strong>, we will tackle <strong>Metrics &amp; Execution</strong>, diving into the AARRR funnel, prioritisation frameworks, and the critical skill of A/B testing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef52caaed233" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Design Thinking: Mastering Product Design and Critique (Part 3 of 8)]]></title>
            <link>https://medium.com/@snshakshineha452/design-thinking-mastering-product-design-and-critique-part-3-of-8-e63e1115392c?source=rss-faa7af454455------2</link>
            <guid isPermaLink="false">https://medium.com/p/e63e1115392c</guid>
            <category><![CDATA[pmp]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[pm]]></category>
            <dc:creator><![CDATA[Shakshi Neha]]></dc:creator>
            <pubDate>Mon, 03 Nov 2025 06:35:48 GMT</pubDate>
            <atom:updated>2025-11-03T06:35:48.321Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Welcome back to the Product Management Interview Prep Series!</strong></p><p>In Part 2, we established the core identity of the Product Manager. Now, it’s time to build the product itself. Design questions — “Design X,” “Improve Y,” “Critique Z” — are the meat of the PM interview. They test your <strong>customer empathy, creativity, and structured execution</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GB-L7ZIGxKCsvgkNNY9v5w.png" /></figure><p>This part covers the two most powerful tools in your design arsenal: <strong>The CIRCLES Method</strong> for creation and the <strong>Critique Framework</strong> for evaluation.</p><h3>1. The CIRCLES Method: Your Blueprint for New Products</h3><p>Product design questions are rarely about the single best answer; they are about demonstrating a <strong>structured thought process</strong>. The <strong>CIRCLES Method</strong> is the gold standard because it forces you to think like a PM: starting with the user, prioritising ruthlessly, and articulating clear trade-offs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2vVPwdk9PvQpehMYn3zPpw.png" /></figure><h3>Example Application: The Power of Comprehension (Step 1)</h3><p>When asked, <em>“Design a feature to reduce food waste,”</em> a strong candidate starts with Step 1: <strong>Comprehend</strong>.</p><ul><li><em>Bad Response:</em> “I will design an app that tracks expiration dates.” (Jumps to L — List Solutions).</li><li><em>Good Response:</em> “Before I begin, I need to define the scope. Are we targeting <strong>consumer-level</strong> waste (e.g., households) or <strong>commercial-level</strong> waste (e.g., restaurants, grocery stores)? I will assume we are focusing on <strong>household waste</strong> in a North American market, intending to reduce weekly consumer food waste by 15%.”</li></ul><p>This initial step transforms an ambiguous prompt into a focused, measurable challenge.</p><h3>2. Product Critique Framework: The I.U.U.A.H. Qualities</h3><p>Often, you’ll be asked to critique a product: <em>“Critique the Uber Eats checkout flow”</em> or <em>“What do you think of this new social media app?”</em></p><p>The best critiques move beyond “I like it” or “I don’t like it.” Use the five key qualities (sometimes expanded) from your cheat sheet to structure a professional, insightful review:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_WcacX9bBCL5pleJD0aMgA.png" /></figure><p>A complete critique should cover all five points, identifying both the <strong>strengths</strong> (what the product does well) and <strong>weaknesses</strong> (areas for improvement) for each.</p><h3>3. User &amp; Customer Focus: Building Empathy</h3><p>Both design and critique rely on a deep understanding of users. <strong>User Personas</strong> and <strong>User Journey Maps</strong> are tools that foster empathy.</p><ul><li><strong>User Personas:</strong> These are <strong>fictional, yet realistic, representations</strong> of your key audience segments. They go beyond demographics, including goals, frustrations, motivations, and technical abilities. In the interview, defining a persona in Step 2 of CIRCLES ensures your solutions are targeted.</li><li><strong>User Journey Maps:</strong> This is a visualisation of the <strong>end-to-end experience</strong> a user has with a product or service. It maps out the <em>actions</em> the user takes, the <em>thoughts</em> they have, and the <em>feelings</em> (pain points/delights) they experience at each step. Critiquing a product often involves identifying the biggest pain point on the existing User Journey Map.</li></ul><p>You now have the tools for structured design and effective critique. For testing your understanding, you can try to apply these tools to a practice prompt:</p><ol><li><strong>Design (CIRCLES):</strong> Use the CIRCLES method to <strong>“Design a product that helps people maintain a good posture while working from home.”</strong> (Write down your step-by-step process).</li><li><strong>Critique (IUUAH):</strong> <strong>Critique the mobile app of your favourite news source.</strong></li></ol><p>In <strong>Part 4</strong>, we will shift gears to <strong>Product Strategy &amp; Vision</strong>, diving into competitive analysis, market entry, and the powerful <strong>5 Whys</strong> technique.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e63e1115392c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ The Core Identity: What Exactly IS a Product Manager? (Part 2 of 8)]]></title>
            <link>https://medium.com/@snshakshineha452/the-core-identity-what-exactly-is-a-product-manager-part-2-of-8-158ace9259a9?source=rss-faa7af454455------2</link>
            <guid isPermaLink="false">https://medium.com/p/158ace9259a9</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[pm]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Shakshi Neha]]></dc:creator>
            <pubDate>Mon, 03 Nov 2025 06:15:38 GMT</pubDate>
            <atom:updated>2025-11-03T06:15:38.786Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Welcome back to the Product Management Interview Prep Series!</strong></p><p>In Part 1, we shared the complete roadmap for this series. Today, we begin at the beginning: defining the role. While Product Management is often seen as ambiguous, success in an interview (and on the job) hinges on your ability to articulate the PM’s core responsibilities and value proposition clearly.</p><p>If an interviewer asks, “What does a Product Manager do?” this article provides the structured answer.</p><h3>1. The PM Role Definition: The Venn Diagram of Value</h3><p>The most effective way to define a Product Manager is through the famous <strong>Venn Diagram</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ge97meGRCkXKTbGU" /></figure><p>Where the role sits at the intersection of three critical disciplines:</p><ol><li><strong>Business:</strong> Ensuring the product is <strong>viable</strong> (it drives revenue, reduces cost, or fulfils a strategic goal).</li><li><strong>Technology:</strong> Ensuring the product is <strong>feasible</strong> (understanding the technical possibilities, limitations, and costs).</li><li><strong>User Experience (UX):</strong> Ensuring the product is <strong>desirable</strong> (it solves a real user problem and is intuitive to use).</li></ol><p>The PM’s primary job is to <strong>synthesise</strong> these three areas, maximising value for the customer while achieving business goals.</p><h3>The “CEO of the Product” Analogy</h3><p>You’ll often hear the PM described as the “<strong>CEO of the Product</strong>.” This analogy is useful but requires a caveat:</p><ul><li><strong>Accurate:</strong> Like a CEO, the PM sets the <strong>Vision</strong> and <strong>Strategy</strong>, makes final priority calls, and is accountable for the product’s success (or failure).</li><li><strong>Inaccurate:</strong> Unlike a CEO, the PM has <strong>no direct authority</strong> over the development team. They must lead through <strong>influence, clear communication, and data</strong>, not command.</li></ul><h3>2. Navigating the Product Lifecycle</h3><p>A PM is responsible for the product from its inception to its retirement. Understanding the <strong>Product Lifecycle</strong> demonstrates strategic foresight.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*78wM8HCYInPtAgzy-4It9A.png" /></figure><p>Interviewers often test your maturity by asking how you collaborate. Clearly defining the boundaries between roles is essential:</p><ul><li><strong>Product Manager (PM) vs. Project Manager (PjM):</strong></li><li><strong>PM Focuses on the WHY and WHAT</strong> (Vision, Strategy, Value, Market).</li><li><strong>PjM Focuses on the WHEN and HOW</strong> (Timeline, Budget, Resource allocation, execution risks).</li><li><strong>Product Manager (PM) vs. Product Marketing Manager (PMM):</strong></li><li><strong>PM Focuses on the Product</strong> (Internal, defining features, pricing, requirements).</li><li><strong>PMM focuses on the Market</strong> (External, defining messaging, positioning, launch campaigns).</li><li><strong>Product Manager (PM) vs. UX Designer:</strong></li><li><strong>PM Focuses on the User Problem</strong> (Is this the right problem to solve?).</li><li><strong>Designer Focuses on the User Solution</strong> (How can the user solve the problem easily and aesthetically?).</li></ul><h3>4. Understanding Agile &amp; Methodologies</h3><p>The PM acts as the voice of the customer within the development process, which is typically governed by <strong>Agile methodologies</strong> (like Scrum or Kanban).</p><ul><li><strong>Backlog Ownership:</strong> The PM is the <strong>owner of the product backlog</strong>. They decide which items are in it, the priority order, and ensure clarity for the team.</li><li><strong>User Stories:</strong> The PM often translates high-level requirements into detailed <strong>User Stories</strong> (e.g., “As a user, I want to filter search results so that I can find exactly what I need faster.”), which guide development.</li><li><strong>Prioritisation:</strong> The PM uses frameworks (like ROI or RICE) to justify <em>why</em> feature A is being built this month instead of feature B.</li></ul><p><strong>To test your knowledge on this topic, you can try to </strong>prepare a concise, 90-second answer to this question:</p><blockquote><strong><em>“Describe the Product Manager role and its top 3 most important responsibilities, providing an analogy to illustrate your point.”</em></strong></blockquote><p>In <strong>Part 3</strong>, we will move on to <strong>Product Design</strong>, providing a comprehensive, step-by-step guide on how to effectively use the <strong>CIRCLES Method</strong> to approach any product design question.</p><p><strong>See you in Part 3!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=158ace9259a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Essentials of Product Management]]></title>
            <link>https://medium.com/@snshakshineha452/the-essentials-of-product-management-be9b68138581?source=rss-faa7af454455------2</link>
            <guid isPermaLink="false">https://medium.com/p/be9b68138581</guid>
            <category><![CDATA[pm]]></category>
            <category><![CDATA[prd]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[pmp-certification]]></category>
            <dc:creator><![CDATA[Shakshi Neha]]></dc:creator>
            <pubDate>Mon, 03 Nov 2025 05:42:11 GMT</pubDate>
            <atom:updated>2025-11-03T06:04:28.174Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Welcome, future Product Leaders!</strong></p><p>Are you embarking on the thrilling, often challenging, journey to become a Product Manager? Or perhaps you’re an aspiring PM looking to solidify your understanding and ace those crucial interviews? If so, you’ve landed in the right place.</p><p>This is the first instalment of an eight-part series designed to be your definitive guide for conquering the Product Manager interview. We’ll leave no stone unturned, diving deep into every concept, framework, and strategy you’ll need to demonstrate your product leadership potential.</p><h3>Why This Index? Your Roadmap to PM Mastery</h3><p>The Product Manager role is a unique blend of strategy, execution, technology, and user empathy. Interview processes for PM roles, especially at top-tier companies, are designed to test the breadth and depth of your capabilities across these diverse areas. Without a clear roadmap, preparing can feel overwhelming.</p><p>That’s where this series, starting with this comprehensive index, comes in. This isn’t just a list; it’s a meticulously curated study plan that:</p><ul><li><strong>Integrates proven frameworks:</strong> We’ve incorporated time-tested methodologies like CIRCLES, AARRR, and the 5 Whys.</li><li><strong>Addresses modern expectations:</strong> We’ve added crucial topics like System Design, A/B Testing, and Go-to-Market strategies, which are increasingly vital for today’s PMs.</li><li><strong>Provides Structure:</strong> It breaks down the vast PM landscape into manageable, interconnected sections, allowing for focused, progressive learning.</li></ul><p>Think of this index as your interview blueprint — a complete map of the PM interview landscape. Over the next seven weeks, we will deep-dive into each major section listed below, equipping you with the mental tools and frameworks you need to succeed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7DOMXIUfMU6EdK4tzN9vVQ.png" /></figure><h3>1. 💡 Introduction to Product Management (The Core)</h3><p>This section defines the role and sets the stage for every PM decision you’ll make.</p><ul><li><strong>The PM Role Definition:</strong> PM is the intersection of <strong>Business, Technology, and User Experience (UX)</strong>. The “CEO of the Product” analogy and its limitations.</li><li><strong>Product Lifecycle:</strong> Understanding all phases from <strong>Idea/Concept -&gt; Development -&gt; Launch -&gt; Growth -&gt; Maturity -&gt; Decline/Sunset.</strong></li><li><strong>PM vs. Other Roles:</strong> Differentiating the PM from Project Managers, Product Marketing Managers (PMMs), and Product Designers.</li><li><strong>Agile &amp; Methodologies:</strong> Basic knowledge of <strong>Scrum/Kanban</strong> and the PM’s role in managing the backlog and setting sprints.</li></ul><h3>2. 🎨 Product Design &amp; UX (Execution/Critique)</h3><p>Mastering these topics demonstrates your <strong>customer empathy</strong> and ability to design practical, valuable solutions.</p><p><strong>a) New Product/Feature Design Framework: The CIRCLES Method</strong></p><ul><li><strong>C</strong>omprehend the situation</li><li><strong>I</strong>dentify the target Customer</li><li><strong>R</strong>eport user needs/goals</li><li><strong>C</strong>ut/Prioritise based on ROI/impact</li><li><strong>L</strong>ist solutions</li><li><strong>E</strong>valuate Trade-offs (technical, financial, competitive)</li><li><strong>S</strong>ummarise the recommendation</li></ul><p><strong>b) Product Critique Framework:</strong> Evaluating a product based on its <strong>Innovative, Useful, Understandable, Aesthetic, and Honest</strong> qualities.</p><p><strong>c) User &amp; Customer Focus:</strong> Creating <strong>User Personas</strong> and mapping <strong>User Journey Maps</strong>.</p><h3>3. 🗺️ Product Strategy &amp; Vision (High-Level Thinking)</h3><p>These questions assess your ability to envision the <strong>big picture</strong>, establish a direction, and justify long-term investments.</p><ul><li><strong>Product Strategy &amp; Vision:</strong> Defining the <strong>Vision</strong> (the “Why”), the <strong>Strategy</strong> (the “How”), and the <strong>Roadmap</strong> (the “What/When”).</li><li><strong>Market Entry/Competition:</strong> Using frameworks like <strong>Porter’s Five Forces</strong> and analysing <strong>Market/Competition/Company Fit</strong> (e.g., SWOT).</li><li><strong>Problem Deep Dive: The 5 Whys:</strong> A method for root cause analysis to uncover unarticulated, underlying problems.</li><li><strong>Creative Solutions:</strong> Techniques like <strong>Reversal</strong> and challenging the <strong>Status Quo</strong> to ensure “Big Thinking.”</li><li><strong>Go-to-Market (GTM) Strategy (Crucial Added Topic):</strong> Structuring a plan for launching a new feature or product, covering messaging, channels, and launch phases.</li></ul><h3>4. 📈 Metrics &amp; Execution (Data-Driven Decisions)</h3><p>This section covers the core of a data-driven PM, focusing on measurement, diagnosis, and growth.</p><p><strong>a) Metrics &amp; KPIs: The AARRR Funnel (Pirate Metrics)</strong></p><ul><li><strong>A</strong>cquisition</li><li><strong>A</strong>ctivation</li><li><strong>R</strong>etention</li><li><strong>R</strong>eferral</li><li><strong>R</strong>evenue (Monetisation)</li></ul><p><strong>b) Prioritisation Frameworks:</strong> Applying the <strong>ROI estimate</strong> (from CIRCLES) and mastering specific acronyms, such as <strong>RICE</strong> (Reach, Impact, Confidence, Effort) or <strong>MoSCoW</strong>.</p><p><strong>c) Experimentation:</strong> Designing and analysing <strong>A/B Tests</strong> (Hypothesis, Success Metrics, Guardrail Metrics).</p><p><strong>d) Estimation/Guesstimation:</strong> The importance of explaining <strong>Assumptions</strong> clearly for Top-Down vs. Bottom-Up estimates.</p><p><strong>e) Pricing:</strong> Frameworks like value-based, competitive, and cost-plus pricing.</p><h3>5. 🧑‍💻 Technical &amp; Behavioral (Skills &amp; Fit)</h3><p>Success here depends on demonstrating your ability to lead, influence, and collaborate with technical teams and stakeholders.</p><ul><li><strong>System Design (Crucial Added Topic):</strong> Designing scalable products (e.g., a News Feed, a URL Shortener). Focus on architecture, data models, and technical trade-offs.</li><li><strong>Technical Interview Steps:</strong> <strong>Clarify -&gt; Base Case -&gt; Talk Aloud-&gt; Write Solution -&gt; Review.</strong></li><li><strong>Behavioural Questions: The STAR Method (Situation, Task, Action, Result):</strong> Using structured stories to demonstrate leadership, handling conflict, managing trade-offs, and dealing with failure.</li><li><strong>Communication &amp; Soft Skills:</strong> Showing empathy, gaining stakeholder buy-in, and adapting your communication style.</li></ul><h3>6. 📝 Product Requirements Document (PRD)</h3><ul><li><strong>Core Role of the PRD:</strong> The definitive document that defines the <strong>“what”</strong> and <strong>“why”</strong> of the product or feature for the engineering team.</li><li><strong>Key Components:</strong> Business goals, Target Users, Functional Requirements, Success Metrics, and Assumptions.</li><li><strong>PM Ownership:</strong> How the PM creates, maintains, and uses the PRD to achieve cross-functional alignment.</li></ul><h3>7.📝 The Ultimate PM CheatSheet</h3><p>A quick review sheet for the ultimate PM guide.</p><p><em>I am excited. Are you? Let’s go!!!!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be9b68138581" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prompt Engineering: Part 1]]></title>
            <link>https://medium.com/@snshakshineha452/prompt-engineering-part-1-602834d2dd92?source=rss-faa7af454455------2</link>
            <guid isPermaLink="false">https://medium.com/p/602834d2dd92</guid>
            <category><![CDATA[prompt-response]]></category>
            <category><![CDATA[prompt]]></category>
            <category><![CDATA[prompt-engineering]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[chatgpt]]></category>
            <dc:creator><![CDATA[Shakshi Neha]]></dc:creator>
            <pubDate>Fri, 26 Apr 2024 10:16:50 GMT</pubDate>
            <atom:updated>2024-04-26T10:16:50.344Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Hi All, welcome to this series on the topic of Prompt Engineering.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*y0VdkkxZGR_p5pyh" /><figcaption>How LLMs work</figcaption></figure><p>In this series, we will learn all that is there to know about Prompting and Prompt Engineering.</p><p>This series will consist of eight sections:</p><ol><li>Introduction and Guidelines for Prompting</li><li>Interactive Prompt Development</li><li>Summarizing</li><li>Inferring</li><li>Transforming</li><li>Expanding</li><li>Chatbot</li><li>Summary</li></ol><h3>Important terms to understand:</h3><p>1. Large language models : A large language model is made up of a neural network with numerous parameters that have been trained using self-supervised learning or semi-supervised learning on huge amounts of unlabeled text.</p><p>2. ChatGPT: It is a Large Language Model that is trained to interact with the user conversationally. It is trained to follow an instruction in a prompt and provide a detailed response.</p><p>3. LLM API&#39;s: As developers, we can use the APIs that are provided by the Large Language Model to perform several tasks such as Summarization, Inferring, Extraction, Transforming, and Expanding.</p><h3>Guidelines for Prompting</h3><p>Prompting can be done by using the two principles</p><ol><li>To write clear and specific instructions</li></ol><ul><li>Using delimiters to indicate distinct parts of the input</li><li>Asking for a structured output</li><li>To ask the model to check whether conditions are satisfied.</li><li>If the task makes any assumptions that aren’t necessarily true, we can instruct the model to check those assumptions first, indicate that if they aren’t true, and sort of stop short of trying to complete the task entirely if necessary.</li><li>Few-shot prompting</li><li>Before asking the model to accomplish the real work you want it to, give examples of successful executions</li></ul><p>2. To give the model time to think</p><ul><li>To specify the steps required to complete a task.</li><li>Instructing the model to work out its solution before rushing to a conclusion</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*2MZrRtZ-v_tBJVT1" /></figure><p>An Example with Code</p><pre>import openai</pre><pre>openai.api_key = &quot;YOUR_API_KEY&quot;</pre><pre>def get_completion(prompt, model=&quot;gpt-3.5-turbo&quot;):<br>    messages = [{&quot;role&quot;: &quot;user&quot;, &quot;content&quot;: prompt}]<br>    response = openai.ChatCompletion.create(<br>        model=model,<br>        messages=messages,<br>        temperature=0,<br>    )<br>    return response.choices[0].message[&quot;content&quot;]</pre><ul><li>In the above code, a function will take a prompt as its input and return an output to that prompt.</li></ul><h4>NOTE:</h4><p>This code is given for your reference and it only works for you personal devices with your own credentials.</p><pre>text_to_get_topics_1 = f&quot;&quot;&quot;The computer consists of a keyboard, mouse and a display. The rest of the accessories should be purchased separately.&quot;&quot;&quot;</pre><ul><li>We define a variable that will contain the string that is passed to the model along with the prompt.</li></ul><pre>prompt = f&quot;&quot;&quot;<br>Given a text delimited by triple quotes. check If it contains texts based on computer, output the topics in the following format:<br><br>Topics - ...<br><br>If the text does not contain toics based on computer, then simply write \&quot;No Topics on Computer.\&quot;<br><br>\&quot;\&quot;\&quot;{text_to_get_topics_1}\&quot;\&quot;\&quot;<br>&quot;&quot;&quot;</pre><ul><li>The prompt is defined.</li></ul><pre>print(get_completion(prompt))</pre><p><strong>Output</strong>:</p><pre>Topics - computer, keyboard, mouse, display, accessories</pre><ul><li>From the above result, we can see that based on a condition the model can give different kinds of results.</li><li>In this case, the string has topics based on the computer so it returns those topics.</li></ul><pre>text_to_get_topics_2 = f&quot;&quot;&quot;The movie is a well made piece of art with deep meaning on the subject of mental health.&quot;&quot;&quot;</pre><pre>prompt = f&quot;&quot;&quot;<br>Given a text delimited by triple quotes. check If it contains texts based on computer, output the topics in the following format:<br><br>Topics - ...<br><br>If the text does not contain toics based on computer, then simply write \&quot;No Topics on Computer.\&quot;<br><br>\&quot;\&quot;\&quot;{text_to_get_topics_2}\&quot;\&quot;\&quot;<br>&quot;&quot;&quot;</pre><pre>print(get_completion(prompt))</pre><p><strong>Output</strong>:</p><pre>No Topics on Computer.</pre><ul><li>In this case, the string has no topics based on the computer so the model returns No Topics on Computer.</li></ul><p>Avoiding Hallucination</p><p>During the training process, the model is exposed to a vast amount of knowledge.However, because it has not perfectly retained the knowledge it has seen, it is not yet aware of the limits of its knowledge.</p><ul><li>This means that it might attempt to address complex questions with the ability to invent ideas that appear plausible but are untrue. We call this hallucination.</li><li>We should avoid model hallucinations by using the above-mentioned methods.</li></ul><p>This concluded the first part of this series. The second part of this series will talk about “Iterative Prompt Development”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=602834d2dd92" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Conquer C in 15 Days]]></title>
            <link>https://medium.com/@snshakshineha452/conquer-c-in-15-days-2719b7bdad3a?source=rss-faa7af454455------2</link>
            <guid isPermaLink="false">https://medium.com/p/2719b7bdad3a</guid>
            <category><![CDATA[getting-started]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[basics-of-programming]]></category>
            <category><![CDATA[c]]></category>
            <dc:creator><![CDATA[Shakshi Neha]]></dc:creator>
            <pubDate>Fri, 17 Nov 2023 01:32:08 GMT</pubDate>
            <atom:updated>2023-11-17T01:32:08.080Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi all, I will be sharing a comprehensive plan to get thorough with C in just 15 days.</p><p>Day 1–2: Getting Started with C</p><p>- Learn about the basic structure of a C program.</p><p>-Source- <a href="https://www.geeksforgeeks.org/c-programming-language/?ref=shm">https://www.geeksforgeeks.org/c-programming-language/?ref=shm</a></p><p>-Cover the first 5 topics:- C Basics, C Variables and Consonants, C Data Types, C Input and Output, C Operators</p><p>- Set up a C development environment (Use an IDE like Code::Blocks or Visual Studio, and get help from YouTube for the setup).</p><p>- Write your first “Hello, World!” program.</p><p>- Understand the compilation process in C. (<a href="https://www.prepbytes.com/blog/c-programming/compilation-process-in-c/#:~:text=The%20compilation%20process%20in%20C%20involves%20translating%20human%2Dreadable%20code,IDE%20(Integrated%20Development%20Environment).">https://www.prepbytes.com/blog/c-programming/compilation-process-in-c/#:~:text=The%20compilation%20process%20in%20C%20involves%20translating%20human%2Dreadable%20code,IDE%20(Integrated%20Development%20Environment).</a>)</p><p>-Coding problems to solve after this:</p><p>-https://www.hackerrank.com/challenges/hello-world-c/problem?isFullScreen=true</p><p>-https://www.hackerrank.com/challenges/playing-with-characters/problem?isFullScreen=true</p><ul><li><a href="https://www.hackerrank.com/challenges/sum-numbers-c/problem?isFullScreen=true">https://www.hackerrank.com/challenges/sum-numbers-c/problem?isFullScreen=true</a></li></ul><p>Hope you like this easy and direct approach to C. These study materials will help you get the necessary kickstart without any fancy courses</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2719b7bdad3a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ticket Classification and Clustering]]></title>
            <link>https://medium.com/@snshakshineha452/ticket-classification-and-clustering-cb797f35f1b5?source=rss-faa7af454455------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb797f35f1b5</guid>
            <category><![CDATA[classification]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[clustering]]></category>
            <dc:creator><![CDATA[Shakshi Neha]]></dc:creator>
            <pubDate>Mon, 30 Oct 2023 06:35:18 GMT</pubDate>
            <atom:updated>2023-10-30T06:35:18.643Z</atom:updated>
            <content:encoded><![CDATA[<p>Implementing an AI model for ticket classification and clustering is a common use case for streamlining customer support and issue resolution.</p><p>Here’s a possible step-by-step procedure which we can follow to implement this use case:</p><p>1. Data Collection:</p><p>- Gather historical ticket data, which includes the ticket text (description and content), category, and any other relevant information. If we can data for any team once for their tickets and clients, working on this model can turn out to be easy.</p><p>One dataset identified on Kaggle for training purposes is: <a href="https://www.kaggle.com/discussions/general/414512">https://www.kaggle.com/discussions/general/414512</a></p><p>- Categorize tickets as accurately as possible. This will serve as the labeled dataset for training.</p><p>2. Data Preprocessing:</p><p>- Clean the text data by removing special characters, formatting, and irrelevant information.</p><p>- Tokenize the text into words or phrases.</p><p>- Perform text normalization, including stemming or lemmatization.</p><p>3. Feature Engineering:</p><p>- Convert the text data into numerical representations using techniques like TF-IDF (Term Frequency-Inverse Document Frequency) or word embeddings (Word2Vec, GloVe).</p><p>- Extract additional features such as ticket source, date, or user information that might be useful for classification and clustering.</p><p>4. Ticket Classification:</p><p>- Choose a classification algorithm, commonly used ones are Naive Bayes, Support Vector Machines, or deep learning models like CNNs or LSTMs.</p><p>- Train the model on the labeled dataset to classify new tickets into predefined categories.</p><p>- Evaluate the model’s accuracy, precision, recall, and F1-score. Fine-tune as needed.</p><p>5. Ticket Clustering:</p><p>- Choose a clustering algorithm, such as K-Means, Hierarchical Clustering, or DBSCAN.</p><p>- Convert ticket features into vectors using dimensionality reduction techniques like PCA or t-SNE.</p><p>- Apply clustering algorithms to group similar tickets based on their content.</p><p>6. Model Integration:</p><p>- Deploy both the classification and clustering models within your ticketing system or customer support platform.</p><p>- Create an API or interface to interact with the models.</p><p>7. Automation and Workflow:</p><p>- Implement automated ticket routing. For classified tickets, route them to the appropriate support team or agent.</p><p>- For clustered tickets, automate responses or actions based on the group’s characteristics.</p><p>8. Continuous Learning:</p><p>- Monitor model performance over time. Reevaluate and retrain models as new ticket data becomes available.</p><p>- Continuously update categories or clusters as the support landscape evolves.</p><p>9. User Feedback Loop:</p><p>- Incorporate feedback from support agents and users to improve the classification and clustering accuracy.</p><p>- Users can provide feedback if their ticket was categorized incorrectly.</p><p>10. Monitoring and Optimization:</p><p>- Keep a close eye on the AI models to detect any drift or degradation in performance.</p><p>- Optimize the models, data preprocessing, and features to adapt to changing ticket patterns.</p><p>The implementation of AI models for ticket classification and clustering enhances customer support efficiency, reduces response times, and improves user satisfaction. It helps support teams prioritize and manage tickets more effectively.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb797f35f1b5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Python code to find the p-Value of the ARIMA Model]]></title>
            <link>https://medium.com/@snshakshineha452/python-code-to-find-the-p-value-of-the-arima-model-9123207bb157?source=rss-faa7af454455------2</link>
            <guid isPermaLink="false">https://medium.com/p/9123207bb157</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[arima]]></category>
            <category><![CDATA[predictive-a]]></category>
            <dc:creator><![CDATA[Shakshi Neha]]></dc:creator>
            <pubDate>Mon, 24 Jul 2023 02:57:16 GMT</pubDate>
            <atom:updated>2023-07-24T02:57:16.674Z</atom:updated>
            <content:encoded><![CDATA[<p>To find the p-value for an ARIMA model in Python, you can use the `statsmodels` library, which provides an easy way to fit ARIMA models and obtain various statistical information, including p-values.</p><p>Here’s a step-by-step Python code to find the p-value for an ARIMA model for temperature forecasting:</p><blockquote>import pandas as pd<br>import numpy as np<br>import statsmodels.api as sm</blockquote><blockquote># Sample temperature time series data (replace this with your own data)<br>temperature_data = [25.5, 26.2, 26.8, 28.0, 27.3, 26.5, 25.8, 24.9, 24.2, 23.5]</blockquote><blockquote># Convert the data to a pandas Series (if it’s not already)<br>temperature_series = pd.Series(temperature_data)</blockquote><blockquote># Fit the ARIMA model<br>order = (1, 0, 1) # Replace this with the appropriate values of (p, d, q) for your model<br>model = sm.tsa.ARIMA(temperature_series, order=order)<br>results = model.fit()</blockquote><blockquote># Get the p-value for the coefficient of the AR term (p)<br>p_value_ar = results.pvalues[1]</blockquote><blockquote>print(“P-value for the AR term:”, p_value_ar)</blockquote><p>In this code, we first create a sample temperature time series data as a Python list. We then convert it to a pandas Series using `pd.Series`. Next, we fit the ARIMA model to the temperature data using `statsmodels.tsa.ARIMA`. The `order` parameter should be set to the appropriate values of (p, d, q) for your ARIMA model. Finally, we extract the p-value for the coefficient of the AR term (p) using `results.pvalues[1]`.</p><p>Please note that the p-value provides information about the significance of the AR term in the ARIMA model. A low p-value (usually below 0.05) indicates that the AR term is statistically significant in the model. If the p-value is high, it suggests that the AR term may not be significant and might not improve the model’s forecasting performance.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9123207bb157" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>