Yoga Wigardo

PRD templates don't work. In all my jobs but this one I foolishly tried to push a PRD template with my team. But PMs will naturally adapt their approach to effectively communicate the opportunity and requirements. There was always an annoying rule-breaker who proceeded to deviate away from the template, and that rule-breaker was me. Instead of rigid templates, I now focus on requirements for the requirements. Is the problem statement specific? What input metric are we moving, and what are we controlling for? Have we made explicit the tradeoffs of potential solutions? Are we clear about our assumptions? What's the minimum we can build to validate our hypotheses? What risks and dependencies might we face? What are your termination criteria? #productmanagement

19

2 Komentar

The past 2 weeks, I've been testing out different ways to draft a PRD. By far, the fastest is ChatPRD: (This is not a sponsored post) OUR OPTIONS When we PMs walk into a company, we have 1 of 2 situations: 1. We're handed this PRD template the company has 2. It's a free-for-all with no PRD template     If there's a template, it takes roughly an hour and a half to get a first draft of a feature you have begun aligned on the problem for. If there's no template, I found it takes even longer. Around 2 hours of work. ENTER LLMS It's incredibly difficult to actually find those time blocks without working late nights. So, my latest practice had been to use a tool like GPT-4o with a mega-prompt. And this works pretty well. But there's so much editing you have to do. If you're really good, though, you can get a draft out in something like 45 minutes. So I was genuinely surprised when I tried ChatPRD. The reason is: its PRD's don't need that much editing!. It does a really good job of sounding like a PM. That's always the major challenges with LLMs, but ChatPRD is built around it. It makes sense, if you think about it. LLMs are made for generalized use cases. With a GPT atop the LLM, 3x CPO Claire Vo has exported her brain into the product. ENTER THE COLLAB With ChatPRD, I've found you can actually draft your PRD in ~30 minutes. But to make sure everyone can get to that level, I reached out to the team behind ChatPRD to write the ultimate guide. I tested all the different ways to use it, and also worked with the awesome Alisa Haman, Claire's partner in crime, to add my PRD template to ChatPRD. So, it's just one click and a few prompts to get to an Aakash-inspired draft. Check out the full guide here: https://lnkd.in/e6nsDWKt LET US KNOW WHAT YOU THINK I think it's worth a try for any PM or product leader facing a blank page or template and ready to jump into editing faster. 𝗔𝘁 𝘄𝗼𝗿𝘀𝘁: it gives you an idea of what an LLM would say—so you can do better. 𝗔𝘁 𝗯𝗲𝘀𝘁: it could cut your time to a working draft by 75%. Share your honest opinion in the comments.

653

109 Komentar

This PRD template is the culmination of my 8+ years in PM & brings everything together seamlessly 🧨 In these 8 years, one thing I’ve learned is that for a PM, alignment between tech and business is everything. And that’s why I created this PRD template. This template covers every crucial aspect of the PRD process, ensuring that no detail is left behind. From defining product goals to diving deep into design phases, it allows you to fully customise and build around your specific needs. It’s been a critical for me in driving alignment across teams and delivering successful products. If you’re looking to bridge the gap between tech and business, this might just be the missing piece you need! 💡 P.S. — Tired of not getting shortlists? Is your CV the right fit for breaking into a PM role? How should you go about build a portfolio? My program helps you ace all these situations and much more! Check out the link in comments to apply for the program! 🤩

83

8 Komentar

Pendo introduced Product Operations (ProductOps) as a counterpart to DevOps, MarketingOps, SalesOps, and other operational roles. The key role of ProductOps is to analyze and interpret data from product usage platforms and turn it into actionable insights for Product Management. In many cases, I believe the ProductOps stack should also integrate CRM data or contribute to it. Why? By making sure Sales, CSM, and Product Management are aligned, organizations can gain a more consistent perspective on the market and product performance. This helps drive better decision-making across departments and fosters collaboration. ProductOps isn't just about data. It's about empowering cross-functional teams to make informed decisions faster. Highly aligned companies, according to Forrester, grow 19% faster and are 15% percent more profitable - that is founded in good decision-making processes. By integrating CRM and usage data, teams can not only see the "what" but also the "why" behind customer behavior - allowing for a better understanding of the product's impact. What is your take? Are you using ProductOps in your organization, or are you seeing the benefit of this?

3

Man, I just love Reforge! Today, they launched what I believe is one of the best product management tools ever an extension that's a game-changer for PMs. Here’s what it does: 1. Understands what you’re trying to create, be it a PRD, Product Strategy, Hiring Plan, etc. 2. Provides insights based on the expertise of Reforge’s top-tier experts (think VPs and C-Level operators). 3. Assists in crafting various strategic documents like PRDs, Product Specs, Roadmaps, Launch Plans, and more. Just imagine experts like Elena Verna, Adam Fishman, and Andrew Chen being your Async product coaches. Thanks for launching this masterpiece Daniel Wolchonok & Brian Balfour! #technology #startups #ProductManagement #ProductManager #product 

109

4 Komentar

Having trouble with PRDs? Check out these tips to make them better (plus a free template!): 👇🏽 PRD is Flexible: It’s okay if it changes. Just make sure to explain why. Focus on Why and What: Nail down the problem and what needs to be done, and leave the 'how' to the engineers. Talk it Out: A PRD isn't a substitute for chatting with your team. Keep those lines of communication open. Your PRDs Will Be Unique: Use best practices but remember that each PRD will look different based on your needs. PRD for Clarity: Even for small features, writing it down helps clear up confusion. This post has seriously improved how I handle PRDs and keeps my team on the same page. The template is a game-changer—check it out! #ProductManagement #Product #PRD #ProductDevelopment #TeamWork #Clarity #Template #Document

2

1 Komentar

Great visual of the evolution of a PRD throughout the Product development lifecycle

7

Craft a Killer PRD: A Product Manager's Guide to Success Ever felt like your PRD is a confusing beast? You're not alone! A strong PRD is the cornerstone of successful product development, but crafting one can be tricky. Here's a cheat sheet to write a PRD that gets everyone on board: 1. Define the Problem (Not the Solution): Focus on the user's pain point. What problem are you solving, and why is it important? 2. Know Your Audience: Tailor your language for both technical and non-technical stakeholders. 3. Features vs. Benefits: Don't just list features - explain how they benefit the user. Example: Don't just say "add login functionality," say "enable users to save preferences and personalize their experience." 4. User Stories & Use Cases: Show, don't tell! Illustrate how users will interact with your product through real-life scenarios. 5. Functional Requirements: Outline the core functionalities the product must deliver. This includes things like login functionality, search capabilities, payment processing, etc. 6. Non-Functional Requirements: Specify the technical performance aspects. This could be response times, security measures, scalability needs, platform compatibility, etc. 7. Acceptance Criteria: Define clear criteria for each feature, outlining how you'll know when it's successfully implemented. This might involve specific user actions, visual elements, or performance benchmarks. 8. A Living Document: A good PRD doesn't become ancient history after it's written. It's a living document that evolves as the project progresses. Regularly update it to reflect changes or new information. It's like a dynamic story that keeps getting better with each chapter. Bonus Tip: Keep it concise and visually appealing. Ready to write a PRD that rocks? Share your best tips and lessons learned in the comments! #productdevelopment #communication #productstrategy #productmanagement #prd

5

1 Komentar

PRD isn't a document that you write just once. Rather, you write it over time. It's important for a PRD to provide clarity by reflecting the current state of the team's thinking. Here are the 6 stages of evolution I suggest: 1 — Team Kickoff Often called a speclet, at this stage the idea is 'just enough information' for the team to explore it further. It might even be just a title and a few lines. The idea is: you have identified business metrics to move, and you have 85%+ confidence of the user problem direction you'll solve. You don't know the exact problem or solution, but you're describing your best guess. It's an exercise in product sense. Then, with your designer and tech lead, you'll explore further. 2 — Planning Review This is when the PRD expands into a 1-page doc. You've started to explore the problem space with your design and engineering teammates. It's now ready for review with execs—your skip level, those VPs that care a lot about the roadmap, maybe even the CEO. This new document ends planning, showcasing the summary of your learning during the process. 3 — XFN Kick Off Once you're ready to start working on the solution space, it's time to bring all the stakeholders in: sales, customer support, product marketing... This is where you update the PRD for all of the input needed. What you need from legal, from privacy, from compliance, from QA, and everyone else. It has a compelling problem space, initial data, and serves as a canvas to get input before going full on in the solution exploration. 4 — Solution Review The next step for the PRD is generally the most stressful product review. This is the one, if it's a big feature, you might even present to the Senior Leadership Team (SLT). Many times, this will even evolve into a slide deck, or a Notion document that's ready for presentation, or a 6-page PRFAQ if you work at Amazon. The idea is to get feedback by putting your stake in the ground on the results of the solution space exploration. 5 — Launch Readiness Once you've received all that feedback and completed your exploration of the solution space, it's finally time to get the document ready for engineering. Your tech lead has been in on the whole process, but now you need to create a concrete document of edge cases, metrics, and flows. Then, the engineers building it can stress the final edge cases that only engineers can find. 6 — Impact Review Many people make the mistake of ending the PRD there. But it's worth going back to the PRD and adding a link to your feature results writeup. And, if you roll back the feature or take any other action, adding a note of it in the PRD. This enables people who find the PRD to be able to trace back what happened after to complete the build-test-learn loop. Check out the deep dive to understand this with more examples and specifics: https://lnkd.in/gaNBhKci

93

Do We Really Need a PRD (Product Requirements Document)? As a product manager with over two years of experience, one of my earliest challenges was creating a Product Requirements Document (PRD). Despite researching extensively, the process felt overwhelming. My first PRD lacked clarity, especially for non-technical stakeholders, which defeated its main purpose. A PRD should be your product's "Bible" – a document that any stakeholder, technical or non-technical, can read and understand clearly. It guides engineers, designers, and stakeholders, making it crucial to communicate your vision effectively. Over time, I’ve improved my approach to PRDs, focusing on these essential components: - Features: Describing how the features will work, the problem they solve, and the expected outcomes. - Deliverables & Requirements: Detailing the technical and non-technical needs for each feature. - Metrics & Success Criteria: Defining how the feature will impact engagement, revenue, or other key metrics. - Competitor Analysis:Highlighting the competition and how our product stands out. - Research & Justification:Including research that justifies the need for the product or feature, addressing customer pain points, market demand, and alignment with business goals. This helps stakeholders understand *why* the product is necessary and its potential impact. - Wireframes/Designs:Including Figma files or design samples to provide a visual understanding of the product. Having a clear PRD not only improves team alignment but also ensures that the product vision is well communicated and executed. In my recent projects, the difference between my first PRD and now is evident in the structure, clarity, and collaboration it fosters across teams. How about you? Do you find PRDs essential in your product management process? How have your PRDs evolved over time? I’d love to hear your experiences and insights! Let’s share and learn from each other.

9

2 Komentar

One of my favorite things about writing a PRD is the "follow on" use cases. What do I mean? A PM identifies a problem to solve. The PM then proceeds to write out use cases to solve that problem. I refer to these as the "original" use cases of the problem. The first releases, or MVP, are typically built to solve the original use cases. But once the MVP is built, and users start to actively use a product, suddenly a bunch of new possibilities open up. Now there are many other problems that can be solved, that were not obvious before. This leads to new use cases that could not be enabled before. I refer to these as "follow on" use cases. Example: ✅ The iPhone was the original use case. ✅ iPhone apps were the follow on use case. Back to my PRD, 🙂 one of the most exciting things to me when writing PRDs is the discovery of follow on use cases. These to me are like "aha!" moments where suddenly entirely new solution areas are discovered. Now, does a PM include the "follow on" use cases in the original PRD for the MVP? Or do they leave it for subsequent PRDs? That is a post for another day! 🙂 Follow me at ➡ #rajshenoiphd #productmanagers #productstrategy #productinnovation #productmanagement #mit #mckinsey

8

3 Komentar

More than double diamond

1

You don't write your PRD once. You write it over time. If the purpose of a PRD is clarity, then it's important for it to reflect the current state of the team's thinking. Here's the 6 stages of evolution I recommend: 1 — Team Kickoff Often called a speclet, at this stage the idea is 'just enough information' for the team to explore it further. It might even be just a title and a few lines. The idea is: you've identified business metrics to move, and you have 80%+ confidence of the user problem direction you'll solve. You don't know the exact problem or solution, but you're describing your best hunch. It's an exercise in product sense. Then, with your designer and tech lead, you'll explore further. 2 — Planning Review This is when the PRD expands into a 1-pager. You've started to explore the problem space with your design and engineering partners. It's now ready for review with execs—your skip level, those VPs that care a lot about the roadmap, maybe even the CEO. This new document ends planning reflecting the summary of your learning during the process. 3 — XFN Kick Off Once you're ready to take on the solution space, it's time to bring all the stakeholders in: sales, customer support, marketing... This is where you update the PRD for all of the input needed. What you need from legal, from privacy, from compliance, from QA, and everyone else. It has a compelling problem space, initial data, and serves as a canvas to get input before going full on in the solution exploration. 4 — Solution Review The next step for the PRD is generally the most stressful product review. This is the one, if it's a big feature, you might even present to the Senior Leadership Team (SLT). Many times, this will even evolve into a slide deck, or a Notion document that's ready for presentation, or a 6-page PRFAQ if you work at Amazon. The idea is, you put your stake in the ground on the results of the solution space exploration so you can get feedback. 5 — Launch Readiness Once you've gotten all that feedback and completed your exploration of the solution space, it's time to get the document ready for engineering. Your tech lead has been in on the whole process, but now you need to create a concrete document of edge cases, metrics, and flows. Then, the engineers building it can stress the final edge cases only an engineer can find. 6 — Impact Review Many people make the mistake of ending the PRD there. But it's worth going back to the PRD and adding a link to your feature results writeup. And, if you roll back the feature or something, adding a note of it. You want people who find the PRD to be able to trace back what happened after to complete the build-test-learn loop. — Ready to go further with examples and specifics? Check out the deep dive: https://lnkd.in/ef5Yde54

1.551

89 Komentar

To improve your PRD (Product Requirements Document), you could follow these best practices. Here's a breakdown of key areas to focus on: 1. Clarify Objectives Problem Statement: Ensure that you clearly define the problem this product will solve. Why is it important? What are the pain points for users or stakeholders? Goal & Success Metrics: Quantify how success will be measured. For example, if it's a software product, how will it improve user experience, adoption rate, or sales? Include KPIs (Key Performance Indicators). 2. User Stories & Personas Include Detailed User Personas: Adding more detail to the user personas can help ground the document in the real needs of the target users. Who are they, and what do they care about? Write User Stories: Translate product features into user stories that express the user’s need, e.g., “As a [user type], I want to [perform an action] so that [goal is met].” 3. Scope Be Specific on Features: Ensure each feature is described in terms of user value and technical specifications. Rank them by priority (Must Have, Should Have, Nice to Have). Non-functional Requirements: Include performance benchmarks, scalability requirements, security needs, and any other technical standards. These are crucial but often forgotten. 4. Technical Requirements Include System Architecture: Diagrams or explanations of how the system should function (front-end, back-end, databases, integrations) are helpful for developers and stakeholders. Dependencies & Constraints: Are there external systems, APIs, or frameworks that this product relies on? List out limitations or constraints, such as hardware, platforms, or legal requirements. 5. Timeline & Milestones Roadmap: Include high-level timelines for major milestones like development, testing, and launch. Realistic Deadlines: Be specific and realistic about timelines and highlight risks that may affect them. 6. Stakeholder Input & Reviews Incorporate Feedback Cycles: Add a process for stakeholder reviews and revisions. Include which stakeholders need to sign off at which stages. 7. Visuals & Prototypes Add Wireframes or Mockups: Visual representations can make the product requirements clearer for both technical and non-technical audiences. Include Prototypes: If possible, link to interactive prototypes or examples to give a clearer sense of the UI/UX vision. 8. Testing & Validation Define Acceptance Criteria: Clearly outline how each feature will be tested to ensure it meets the requirements. Include Beta or UAT Testing Plans: Describe how users or QA teams will validate the product before release. 9. Cost Estimation Estimate Budget & Resources: Include high-level budget estimates for development, design, testing, and post-launch support. 10. Post launch procedures Improving and support considerations.

5

"Can you tell me how to write a PRD ?" Time and again I have heard this question from everyone. Be it a seasoned product manager or someone who is just starting out. 📝Therefore I am sharing some insights on writing a Product Requirements Document (PRD).📝 Whether you're a seasoned product manager or just starting out, crafting a clear and comprehensive PRD is crucial for guiding successful product development. Here's a step-by-step guide to help you ace it: 1️⃣ Start with Clear Objectives: Define the purpose and goals of your product. What problem are you solving? What outcomes are you aiming for? 2️⃣ Know Your Audience: Understand who will be reading the PRD—engineers, designers, stakeholders—and tailor your language and level of detail accordingly. 3️⃣ Include Detailed Requirements: Outline the functional and non-functional requirements of the product. What features will it have? What are the performance, security, and usability requirements? 4️⃣ Provide Context: Give background information on the market, users, and any relevant industry trends. This helps stakeholders understand the rationale behind your decisions. 5️⃣ Break Down Features: Describe each feature in detail, including user stories, acceptance criteria, and any dependencies. 6️⃣ Consider Edge Cases: Anticipate potential edge cases and exceptions, and specify how they should be handled. 7️⃣ Add Visuals: Use wireframes, mockups, or diagrams to illustrate complex concepts and user flows. 8️⃣ Define Success Metrics: Clearly articulate how success will be measured. What KPIs will you track? How will you know if the product meets its objectives? 9️⃣ Review and Iterate: Seek feedback from stakeholders and iterate on the document as needed. Collaboration is key to refining and improving the PRD. 🔟 Keep It Updated: As the project progresses and requirements evolve, keep the PRD updated to reflect any changes. Still unclear? Grab my ultimate PRD template now !! PS:- I’ve recently launched a cohort that is focused on teaching end-to-end product management as well as providing career placement opportunities! 🧠 Fill in the form in the comments to register your interest in the cohort and I’ll reach out to you with further details. ✍️ #PRD #productmanagement #productlearning #mentormalay #productjobs

208

29 Komentar

How to write a launch plan in a PRD: Most PRD templates focus on defining the "why" and "what" behind the product. However, major misalignment can occur between product and go-to-market teams without adding a launch plan, leading to poor feature awareness and failed launches. Product, engineering, and design need to be aware of the launch plan because: → Certain launch activities mandate development tasks, e.g., updates to onboarding. → It clarifies how existing customers will be made aware of the feature. → They allow PMs and PMMs to align on the right KPIs. A few pointers that have helped me: [1] 𝗪𝗵𝗲𝗻 𝘁𝗼 𝗮𝗱𝗱 𝗮 𝗹𝗮𝘂𝗻𝗰𝗵 𝗽𝗹𝗮𝗻 → Compose the launch plan when the feature's scope is locked & ready for development. → The PRD can have a high-level overview linked to a separate GTM document. → Adding it at the product one-pager stage is too early. [2] 𝗪𝗵𝗮𝘁 𝘁𝗼 𝗜𝗻𝗰𝗹𝘂𝗱𝗲 𝗶𝗻 𝗮 𝗹𝗮𝘂𝗻𝗰𝗵 𝗽𝗹𝗮𝗻: → 𝗛𝗶𝗴𝗵-𝗹𝗲𝘃𝗲𝗹 𝗦𝘂𝗺𝗺𝗮𝗿𝘆: A concise overview of the launch goals and strategies. → 𝗧𝗮𝗿𝗴𝗲𝘁 𝗔𝘂𝗱𝗶𝗲𝗻𝗰𝗲: Clearly defined customer segments for the launch. → 𝗞𝗲𝘆 𝗠𝗲𝘀𝘀𝗮𝗴𝗶𝗻𝗴: The core message and value proposition will be used. → 𝗗𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁𝗶𝗮𝘁𝗼𝗿: Unique selling points to highlight during the launch. → 𝗜𝗺𝗽𝗮𝗰𝘁 𝗼𝗻 𝗣𝗮𝗰𝗸𝗮𝗴𝗶𝗻𝗴/𝗧𝗶𝗲𝗿𝗶𝗻𝗴: Highlight which tier/price the feature falls in. → 𝗥𝗼𝗹𝗹𝗼𝘂𝘁 𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝘆: Phased launch approach (e.g., geo-fenced, beta). → 𝗖𝗵𝗮𝗻𝗻𝗲𝗹 𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝘆: How the product will reach new and existing customers. → 𝗧𝗶𝗺𝗲𝗹𝗶𝗻𝗲 𝗼𝗳 𝗔𝗰𝘁𝗶𝘃𝗶𝘁𝗶𝗲𝘀: Key milestones and deadlines for the launch. → 𝗟𝗮𝘂𝗻𝗰𝗵 𝗕𝘂𝗱𝗴𝗲𝘁: Estimated budget allocation for the launch. → 𝗦𝘂𝗰𝗰𝗲𝘀𝘀 𝗙𝗮𝗰𝘁𝗼𝗿𝘀: Metrics to measure the launch's effectiveness. [3] 𝗔𝗱𝗱𝗶𝗻𝗴 𝗮 𝘁𝗶𝗺𝗲𝗹𝗶𝗻𝗲 𝗳𝗼𝗿 𝘁𝗵𝗲 𝗹𝗮𝘂𝗻𝗰𝗵 There are two methods to do this: (a) Milestone Dates: A schedule of milestones with dates and success criteria. This is ideal for low-risk launches or releases for table stakes features. (b) Gated Phases: In this plan, progress to the next phase is only made when the success criteria are met. Ideal for high-risk launches where scaling too fast can be costly. [4] 𝗖𝗼𝗺𝗺𝗼𝗻 𝗺𝗶𝘀𝘁𝗮𝗸𝗲𝘀 𝘄𝗶𝘁𝗵 𝗹𝗮𝘂𝗻𝗰𝗵 𝗽𝗹𝗮𝗻𝘀 → Not highlighting risks, their probability, and potential Plan Bs. → Using the same checklist of channels to promote every feature. → Overlooking operational readiness, e.g., assuming support teams will be trained. → Skipping legal and compliance requirements for certain promotional activities. [5] 𝗪𝗵𝗼 𝘀𝗵𝗼𝘂𝗹𝗱 𝘄𝗿𝗶𝘁𝗲 𝘁𝗵𝗲 𝗹𝗮𝘂𝗻𝗰𝗵 𝗽𝗹𝗮𝗻? The product marketer should lead this with close collaboration with the PM.

230

11 Komentar

I can bet all my money on this - If a PRD is poorly written, it won’t give birth to a successful product. All the sexy products you admire are built on strong problem discovery and a well-written PRD with a solid understanding of customer problems.  #productmanagement

136

9 Komentar

🤹 Balancing Act: Involving engineers in product solutioning when time is tight As product managers, we often face a dilemma: How do we involve our engineering team in critical product decisions when they're swamped with development work? Here are 3 strategies I've found effective: 1. Micro-consultation sessions: Schedule 15-minute stand-ups for quick insights or use your 1:1s to get feedback on proposed features ⌛️ 2. Rotate engineer involvement: Engage different team members to distribute the load. 🧠 3. Asynchronous feedback: Use tools like Slack, Confluence or Figma for non-disruptive input. 📝 Remember, engineers are one of the best problem solvers in the team and their insights are invaluable. A little creativity in engagement can go a long way in building better products.💪🏻🏆 What methods have you used to keep engineers involved despite time constraints? #ProductManagement #Engineering #SaaS #ProductDelivery

9

It's not often I share the cool features built by our Growth team under Terryin Tan's helm, but this one is an exception due to the amount of blood, sweat, tears - and most importantly, impact - that it generated 🚀 Here's a quick rundown of the story behind it. 𝗧𝗵𝗲 𝗕𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲 🤔 We identified a sizeable user segment who regularly visits our app but does not complete purchases for inexplicable reasons. This behaviour of visits sans transactions can even persist up til 11 months, and when 12 months elapses, we consider the user as "churned" from our active base. To understand why this was occurring, we conducted in-depth qualitative research and uncovered two main issues: 1. Our campaigns were perceived as overwhelming due to the sheer volume & complex permutations of voucher codes 2. The predictability and generic nature of our campaigns, which led to a lack of individual exclusivity 𝗢𝘂𝗿 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻 💡 We developed a Micro-Segmented Flash Sale feature to circumvent these pain points, wherein: 1. Users displaying a certain propensity to churn are identified 2. A series of personalised flash sales are triggered at unique times of the month, week, even day, on an individual level 3. The discounts apply only to users' specific items in their carts/wishlists, as well as algorithmically recommended products that pair well with these selected items to encourage outfit-building 4. The discounts elevate in intensity as users show a higher and higher risk of churning 𝗧𝗵𝗲 𝗜𝗺𝗽𝗮𝗰𝘁 📊 Through an AB test of this feature, we demonstrated a most likely 6 - 15% uplift in conversion rates amongst these risk-of-churn users. Crucially, we also were able to demonstrate that the profitability of these users were not harmed in aggregate, despite showing a slight dip in average profit per user (which is somewhat expected due to the additional discounts). Equally if not more importantly, we accumulated a ton of learnings to inform future experiment designs, such as the varying discount affinities of users from different OSes, and the importance of user-level micro campaigns in augmenting the overall success of BAU platform-wide campaigns (i.e.: it's not an either-or scenario but rather interplaying the two in a complementary way). This success is a testament to the power of understanding our users intimately and leveraging data-driven personalisation. A massive shoutout to Terryin Tan and team for their hard work and dedication in making this happen, and to Adela Ordoñez, Ziheng(Zi) Qiu, Joy Yuen, Jian An Lam who were instrumental in uncovering the qual/quant datapoints that informed the approach of this feature 👏 #innovation #zalora #userexperience #personalisation

125

12 Komentar