<?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 Myriam Goude on Medium]]></title>
        <description><![CDATA[Stories by Myriam Goude on Medium]]></description>
        <link>https://medium.com/@myriamgoude?source=rss-513594f2c347------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*aOT8V65ii8AMypz6wZ4bFQ.jpeg</url>
            <title>Stories by Myriam Goude on Medium</title>
            <link>https://medium.com/@myriamgoude?source=rss-513594f2c347------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:03:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@myriamgoude/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[2025: At the Intersection of Artificial Intelligence and Sustainable Development]]></title>
            <link>https://myriamgoude.medium.com/2025-at-the-intersection-of-artificial-intelligence-and-sustainable-development-463e1ea77277?source=rss-513594f2c347------2</link>
            <guid isPermaLink="false">https://medium.com/p/463e1ea77277</guid>
            <category><![CDATA[sustainability]]></category>
            <category><![CDATA[digital-product-strategy]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Myriam Goude]]></dc:creator>
            <pubDate>Mon, 30 Dec 2024 13:02:39 GMT</pubDate>
            <atom:updated>2024-12-30T17:13:40.212Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pUzYBBtuk0ZgGR4D" /><figcaption>Photo by <a href="https://unsplash.com/@edwardhowellphotography?utm_source=medium&amp;utm_medium=referral">Edward Howell</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Digital technology is often hailed as a key solution to driving the ecological transition, but its environmental impact remains underestimated. In 2025, artificial intelligence (AI) will continue its race to revolutionize everything: how we work, create, and think.</p><p>We, as Product Managers, will have to activate more and more AI agents to fulfill our jobs and specilize in our missions. <strong>But we have also a higher mission, we are guardians of impacts</strong>. We have to own sustainability within digital. How can we embrace this path in playing with probably one of the biggest bad-player in tech carbon footprint for the next years?</p><h3>Tech industry gas emission in the World</h3><p>Beyond AI, the broader digital ecosystem contributes significantly to global carbon emissions.</p><ul><li><strong>In 2019</strong>, its overall gas emission was 1.9% on the global emission (<em>World Economic Forum, 2019</em>). AI was a toddler with only 5% of the sector.</li><li><strong>In 2020</strong>, the Information and Communication Technology (ICT) sector emitted an estimated <strong>0.69 to 1.6 gigatons of CO₂ equivalents</strong>, corresponding to around 2<strong>.5% of global greenhouse gas emissions</strong>.</li><li><strong>In 2024</strong>, it reaches almost 4% (<em>Philippe Singer, Leaders for Climate Action</em>), taking the top1 ranking and replacing the worldwide aviation industry.</li></ul><p><strong><em>In our level of understanding:</em></strong><em><br>To put individual digital actions into perspective, consider that </em><strong><em>sending a short email</em></strong><em> emits approximately </em><strong><em>3 grams of CO₂ equivalent</em></strong><em>. While this may seem negligible, the cumulative effect is substantial: globally, emails could account for as much as </em><strong><em>150 million tonnes of CO₂ equivalent</em></strong><em>, or about </em><strong><em>0.3% of the world’s carbon footprint</em></strong><em>. This equation doesn&#39;t include storing emails, where data centers are included in the carbon cost.</em></p><h3>AI and Carbon Footprint: The Numbers That Matter</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FrI7OH0VY6iX9iuKEaKZsw.png" /><figcaption><em>Global GHG (gray) compared to ICT emissions (in blue) and AI within it (in purple). (source: GenerationAI, graph from 2019)</em></figcaption></figure><p>While promising, artificial intelligence is energy-intensive. In any Lifecycle management analysis, we consider three phases: <strong>creation, usage,</strong> and<strong> destruction</strong>. In AI, intensive research was done on energy consumption in the LLM phase. Insights have shown that learning and training are not massively consuming as they run at a non-scale and human-moderated. <a href="https://aiforgood.itu.int/speaker/sasha-luccioni/">Sasha Luccioni</a> mentioned that GPT3 asked about 550t eqCO2 for full-train. (around 500 way-back NY&lt;&gt;Paris by plane)</p><p>Regardless of the machine learning consumption itself, the usage—you and me, doing a chatGPT request—is making the biggest numbers.</p><p>Still, according to research done by Sasha Luccioni, the carbon impact varies significantly depending on the application:</p><ul><li><strong>1,000 texts generated</strong> by a small model consume the equivalent of <strong>1/8 of a smartphone charge</strong>. With a larger model, you are asking the same energy as <strong>4 full charges</strong>.</li><li><strong>1 image generated is almost the same as 1 full charge. At scale, 1,000 images generated</strong> can go up to <strong>950 smartphone charges</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bFy8fgRk85Uf-slpbDvH_Q.png" /><figcaption>gCO2 emissions regarding type of AI requests (source generationAI)</figcaption></figure><p>These figures underline the urgency of adopting more energy-efficient AI and digital technology practices.</p><h3>This is our role and our duty, as digital experts, to fix the present and prepare the future with a sustainable approach</h3><h3>Offline AI: A Game-Changer for Energy Efficiency</h3><p>One of the most promising solutions to reduce the carbon footprint of AI is the adoption of <strong>offline and edge AI</strong>. By processing tasks locally on devices rather than relying on cloud-based data centers, offline AI eliminates much of the energy consumption associated with data transfer and centralized processing.</p><p>According to MIT researchers (<a href="https://news.mit.edu/2023/new-tools-available-reduce-energy-that-ai-models-devour-1005"><em>MIT News</em></a><em>, 2023</em>), optimizing AI model training and implementing techniques like power-capping hardware can reduce energy consumption by up to <strong>80% in data centers</strong>. Moreover, <strong>edge computing</strong> — where computations are performed on local devices — can decrease network energy usage by <strong>up to 30%</strong>, making it a critical tool for sustainable technology practices.</p><p>For example:</p><ul><li><strong>Running models locally</strong> allows for real-time processing without the need for continuous internet connectivity, which saves energy.</li><li><strong>Deploying smaller, pre-trained models</strong> on devices like smartphones or laptops can handle common tasks such as grammar checking or data sorting without requiring intensive server usage.</li><li><strong>Swarm intelligence</strong> gives promising advancement (and I had the opportunity to experiment in the summer of 2023 with some small prototypes of IoT working in offline/swarm modes)</li></ul><p>Offline AI does not just enhance energy efficiency; it also improves <strong>data security and reduces latency</strong>, offering, not only worldwide accessibility but also, environmental and practical benefits.</p><h3>Toward Sustainable Technology: The Pillars of Green IT, Low Tech, and Offline AI</h3><p><a href="https://www.youtube.com/watch?v=itdm8cAOCr4&amp;ab_channel=SustainabilitySuccess">Green IT</a>, low-tech approaches, and offline AI collectively offer robust solutions to mitigate the environmental impact of digital technologies:</p><h3>1. Optimize AI Models</h3><ul><li><strong>Lighten algorithms</strong>: Focus on smaller, efficient models tailored to specific needs without excessive energy consumption.</li><li><strong>Leverage quantization and pruning</strong>: These techniques reduce model size without significantly compromising performance.</li><li><strong>Share resources</strong>: Use pre-trained models rather than building solutions from scratch.</li></ul><h3>2. Adopt Offline AI</h3><ul><li><strong>Run models locally</strong>: Process tasks directly on devices, reducing reliance on energy-hungry data centers. Most of the models today may be decoupled and dispatched through expertise recipes (eg. <a href="https://www.cs.princeton.edu/~mfreed/docs/virtualflow-mlsys22.pdf">VirtualFlow</a> management)</li><li><strong>Develop edge computing</strong>: Use mobility as an opportunity to deploy AI on IoT (smartphones, hardware, etc..), cutting down on energy-demand on data push/pull.</li><li><strong>Offline training and SDK usage</strong>: Optimize pre-built and downloaded AI tools for offline functionality,</li></ul><h3>3. Smart Hosting</h3><ul><li><strong>Switch to </strong><a href="https://kpmg.com/dp/en/home/insights/2024/01/going-green-data-centres.html"><strong>green data centers</strong></a>: Opt for infrastructures powered by renewable energy and embrace Sustainable Development Goals on the same time.</li><li><strong>Reduce unnecessary requests</strong>: Limit AI calls to situations where they are genuinely needed. ( By extension, this practice is broadly activated when it comes to Green IT and more specifically on API consumption. Sustainability by Design.</li></ul><h3>4. Prioritize Low-Energy Use Cases</h3><ul><li><strong>Limit energy-intensive applications</strong>: For example, choose text-based tools over generating images or videos when they don’t add significant value.</li><li><strong>Promote simplicity</strong>: In application design, avoid unnecessary features that bloat the product and increase energy consumption.</li></ul><h3>5. Last but not least, the impact on humans, 3rd pillar of sustainability</h3><p>Here comes our trade-off skill as Product Managers: What can we sacrifice in our comfort to make it happen? How can we consider losing something that is low-value for us and could help in gaining consequent improvements in our way to consumption?</p><p>If we consider human usage and sustainability, here are some questions as examples, we can ask ourselves about real demands:</p><ul><li>having a model calculation energy-capped will succeed in 82h instead of 80h. Would these 2 hours matter for our most frequent cases and reduce our comfort?</li><li>getting a data pattern for pendular/human routines updated every day instead of 1-hour frequency. Would this impact our daily decisions?</li><li>number of fresh calls versus cached ones reduced by 2: we mostly request the same type of information done in our recent past searches. Do we need to pull again from online with a super low chance of getting fresh updates?</li><li>Would offline be a better solution for human-context and make it a core value better than mitigating impacts?</li></ul><h3>Building the Future Together</h3><p>In 2025, it’s clear that artificial intelligence and sustainable development must progress hand in hand. Offline AI, alongside Green IT and low-tech solutions, can bridge the gap by reducing dependence on cloud-based systems, enabling more sustainable and accessible AI applications.</p><p>As studies and articles emphasized it, even small changes — like moving some AI processing offline or optimizing models — can unlock massive energy savings. These changes are not just beneficial for the environment but also pave the way for more secure, efficient, and resilient AI systems. It also preserves economics and human values, as core pillars in sustainability thinking.</p><p>AI continues to push the boundaries of possibility, it’s up to us, in our hands, to define what is acceptable to protect our planet and give us still the opportunity to develop humanity.</p><p><strong>What practices do you adopt for a more responsible digital future?</strong></p><p><em>Carbon footprint disclaimer: I used the energy consumption, equivalent of 0.3 phone charges as I was assisted by some AI tools in writing this article. No image was generated with AI, only text enhancement and correction</em></p><h3><em>Sources</em></h3><ul><li><a href="https://www.climateimpact.com/news-insights/insights/infographic-carbon-footprint-internet/">The carbon footprint of the Internet</a>, Climateimpact, 2021</li><li><a href="https://blog.worldfavor.com/the-growing-carbon-footprint-of-digitalization-and-how-to-control-it">The growing carbon footprint of digital</a>, WorldFavor</li><li><a href="https://www.techtarget.com/searchcio/feature/Understand-the-digital-carbon-footprint-of-enterprise-IT">hidden environmental costs of tech</a>, TechTarget 2022</li><li><a href="https://theshiftproject.org/en/article/unsustainable-use-online-video/">Climate Crisis, the unsustainable usage of online videos</a>, The Shift Project, 2019</li><li><a href="https://generationia.flint.media/p/comment-calculer-vraiment-impact-carbone-de-chatgpt-climat-ia-eau">Comment (vraiment) calculer l’impact carbone de chatGPT</a> ( french), GenerationIA, April 2024</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=463e1ea77277" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Services companies can scale in embracing Product methods]]></title>
            <link>https://myriamgoude.medium.com/how-services-companies-can-scale-in-embracing-product-methods-1c966c7f4b7d?source=rss-513594f2c347------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c966c7f4b7d</guid>
            <category><![CDATA[consulting-services]]></category>
            <category><![CDATA[digital-product-business]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Myriam Goude]]></dc:creator>
            <pubDate>Wed, 13 Dec 2023 22:08:27 GMT</pubDate>
            <atom:updated>2024-02-15T08:49:21.775Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Oub1T67sj5qHiL_MI34hwg.jpeg" /><figcaption>Onboarding Kit — @beautyoftech ©Unsplash</figcaption></figure><p>With 15 years of experience in Product Management, I had the chance to experience the two sides of the Digital world. Almost 12 years in Product-based companies and 3 years in Service-based companies. <br>In the last one, my first web agency, I discovered fundamental differences in the way of working with product/editor companies. I observed and intuitively thought that this type of organization has a high risk of declining business if they don’t reinvent the process they used to deliver the same service.</p><p>Here are some thoughts and insights about why and the advantage of importing Product way-of-working as a sake for their future.</p><h3>Service-based vs Product-based: Fundamental differences</h3><p>First, some posts are talking about the differences between both. To align the right definition of “Service”, I used this article here are the 2 versions we can find on the web. <br>Some are talking about tangible/intangible products. This definition is provided essentially from the US. The other one, more universal and widely spread is that a Service-based company delivers time and skills most of the time, to the ones that deliver products.</p><p>As someone who swam into both universes, here’s a view of the significant gaps between both:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9veBVVCx2jIcFv_DnbeRZA.png" /><figcaption>Differences between Service-based Companies (SBC) and Product-based Companies (PBC)</figcaption></figure><h4><strong>Difference 1: the most relevant difference: Business vs Market</strong></h4><p>A service company is centered on the <strong>client’s business</strong>. It delivers solutions dedicated to client’s needs and may allocate human resources to do the job. These people are specialized in their main area and can be immediately ready to contribute to the mission, side by side with the client while the contract is ongoing.</p><p><strong>1 need = 1 proposal</strong></p><p>On the other side, a product company is focused on a <strong>market</strong>. It delivers one or a limited number of products on the shelf, ready to be used, more or less customized but delivering the same value and answering the same need shared by many. All the people working on it are not facing the client. All of them are focusing on delivering an enhancement or improving their product but NOT the one initially required by the client.</p><p><strong>n needs = 1 solution</strong></p><h4>Difference 2: Time-to-market</h4><p>Even with 1 employee, SBCs are immediately ready to sell their activities. On the other side, PBC may have a long R&amp;D session before becoming visible and profitable.</p><h4>Difference 3: Scalability model</h4><p>If you think about development and the next steps, you may immediately understand that in the Service-based, you mechanically grow with your employees, and investment remains steady. Whereas in Product, initial investment is made to catch the market and scale, via milestones dedicated to the Product objectives, not recruitment.</p><h3>Service-based companies are navigating through the Red Ocean 🦈</h3><p>Skillsets defined in services have been known for more than 60 years now. The receipt is the same, so from a certain point of view, comfortable when looking for ready-to-activate expertise.</p><p>But as the digitalization market is now huge, it calls for more SBCs creation. It then adds new competitors with the same skillsets in the same market. <br>So in the client’s skin: “How can I choose between them, for the same offer, the same set of skills?” One of the most evident factors is … the price.<br>On a West-European pov, near shore has been exploding in the last 8 years. As working in a high-income country, I can confirm that almost none of the SBCs here are developing 100% of their digital needs locally. To stay in the competition and keep margins stable, they jumped into the trend to acquire or develop near-shore offices or partnerships.<br>However, the business evolution remains the same:</p><p><strong>Grow = Resource Acquisition</strong></p><p>This is a logarithmic-ladder curve, only pumped by punctual acquisitions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/705/1*vHir-nrvX4CP6unpNIoXkA.png" /><figcaption>SBC-PBC Simple graph to explain Growth Strategy</figcaption></figure><h3>Let’s imagine a wedding: 2 approaches</h3><h4>Strategy number 1: Erasing low-value-added from the table. Going to Excellence</h4><p>One of the best options for a service-based company in high-income countries is to opt for a high-value-added delivery and reduce time on low-value-added production.</p><p><strong><em>High-value-added</em></strong><em> production means adding strategy or tactics to each element we produce at our level. I won’t simplify with the “WOW effect” but we are not so far. For example, devs are talking about flexible components or stacks that are robust, adapted to the client’s environment, and well-balanced between performance, security, and interoperability. Designers are thinking about the multi-devices as opportunities to celebrate the consistency of brand guidelines, user researchers are finding the blind spots in the journey and delivering the right information, at the right time, with data-relevancy exploration, etc…<br></em><strong><em>Low-value-added</em></strong><em> production, in parallel, could be imagined as managing time spent per resource, applying the designs/detailing the experience on all the screens that are non-core features or simply very standard, 1000 times already-seen screens that deliver nothing new for users (thank you Jakob’s law).</em></p><p>As an objective, the SBCs have to create or reinforce their vision and mission statement to hire high-value-added producers: this means top-notch skills, and/or uniqueness in a specific domain or a compliant/certification constraint. <br>Low-value-added have no place in long-term profitability. They can be delegated. Near-shore or automatization? Your bet.<br>The downside effect of this is that it becomes difficult for junior profiles to get hired. Doing the difference between low and high-value-added is often correlated with solid experiences or in a rare case, brilliant people.</p><ul><li><strong>Pros</strong>: a raising Employer Brand, possibly lowering turnover</li><li><strong>Cons</strong>: Raising costs in Market analysis, sales approach, hiring, Juniors mostly impossible to onboard, Reshuffling organization</li></ul><h4>Strategy number 2 (guess what, the one I love ;) )</h4><p>Another approach that could be imagined is to integrate bootstrapping services. In PBC bootstrapping is saving us. We don’t start from scratch with something already proven as useful/efficient/cost-saving. We focus on why, what, and where we are different, where something doesn’t exist yet.<br>So on the service side: we don’t remove the service value but we re-use, we transpose artifacts that support our consulting expertise. The company through projects is acquiring knowledge for future clients with the same context. <br>This approach aims to give the same level of information to each team member, junior or senior, PM or dev. Thus, it leverages ownership during the mission. It gives an area to express initiative and problem-solving. The last positive effect is providing the client with a consulting posture spread through the whole team.</p><p><strong>This is what I call “Service Productization”.</strong></p><ul><li><strong>Pros</strong>: Trust score raises with employees and clients, Juniors are welcomed, the organization remains the same, near-shore reinforces a partnership, seniors are less bored/frustrated, and knowledge capital is added to the business&#39;s global value.</li><li><strong>Cons</strong>: Investing in knowledge time, automation, and onboarding time.</li></ul><h3>Examples of Service Productization</h3><p>Here are some examples I observed that were often redone from scratch 100% of the time and how they could profit from a Product mindset. They are not exhaustive, and I intently removed all the Product artifacts and frameworks we use when we are on continuous improvements. SBCs by nature are meant to leave one moment or another, so I focused only on a project lifecycle.</p><ul><li><strong>Kick-off, planning, and goals</strong>: Includes a simple Product DNA card about the state of the product itself, volume, the vision, and mission statement of the client + cursors on critical/concerning points on which to pay attention.</li><li><strong>Powerful onboarding for teams about the 3T (Taxonomy, Tools, Timeframe)</strong>: Helping anyone jumping in to know about the client’s terms, client IT tools context, and timeframe defined by the pace, size, or urgency of the project.</li><li><strong>Project starting context</strong>: What is the type of product (=support and device)? Is it something new technically (=research)? is it answering a problem solved elsewhere (= capitalization)? Is it challenging the way people are using it (=change)</li><li><strong>Agile Rituals</strong>: Saving time in rituals in advocating: “If there is no meeting goal and output expected, there is no meeting”. Promote asynchronous or duos/trios’ connection and challenge synchronous meetings as a game: 5&#39; stand-ups, retrospectives templates 24/7 days filled in, …</li><li><strong>Delivery templates</strong>: Get strong deliveries that <strong>ALL</strong>, from PM to devs, and designers, tell a story. If someone is jumping on your file, where does he start? what should he read? Think that anything, even code, can be showable and told to stakeholders on all levels.</li><li><strong>Projects wealth</strong>: Stop the follow-up by hand somewhere between Jira and Excel files. Instead, use a live automated dashboard that is filled in with basic stats, with metrics, moods, and number of sprints and/or story points, time tracked globally or per department, and last but not least critical opened points/questions/comments available at any time. Bonus: logs in the last version of deliveries (and yes, Figma does it). Give the ownership of this dashboard to the whole team.</li><li><strong>Skillsets and team organization</strong>: Avoid silos by mapping who is working on the project, with what velocity, and ideally when in the week + communicate about new client context so that experts (= knowing a techno/client/context) can support in showing up their experience or being asked for help.</li></ul><h3>Key points of Productization benefits</h3><h4>Benefit 1: Expertise trust for time-to-market</h4><p>Bootstrapping means you mastered the problem at least once. This means you know, what are the fundamental needs and can easily focus on the subtle signals that make your client different from the others. You know where are the most common risks and how to mitigate them.<br>If you jump in your client’s skin, this means you start to trust instantly the collaboration.</p><p>Not only with one hero but with the whole team.</p><p>These last years, uncertainty as a daily life moved from startups to bigger companies. You will then gain points in handling the classic traps that belong to projects.</p><h4>Benefit 2: Powerful onboarding materials</h4><blockquote>“Businesses With Organized Onboarding Have a <strong>60% Increase</strong> in a Year’s Revenue”</blockquote><p><em>Northpass study</em></p><p>This is the same in Product. Passing a dedicated time to onboarding increases client satisfaction and quality of delivery. Giving 1 or 2h time to onboard each person who will work 100 hours on the product, will result in higher qualitative service with a client-oriented solution. Similarly, allocating 2–4 hours to improve these materials will save 20 hours for each person who will use it.</p><h4>Benefit 3: Contribute to reduce turnover rate</h4><p>A disorganized company, that lacks leading or onboarding on client’s vision sharing will for sure upset its best elements. Performers love to overpass on each mission. If they have to redo the same every time they will be bored, impatient, or exhausted. And then willing to quit if the company is not investing time in this point of view shifts.</p><h3>Conclusion</h3><p>In the history of the digital world, SBCs are the oldest, almost dinosaurs, and PBCs have exploded within the early 00s. Their freshness helped them to be more adaptive to the existing market share. I would bet that smart SBC will get a second breath within the next decades if they adopt PBC&#39;s advantages and market approach.</p><p>Happy to discuss your point of view :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c966c7f4b7d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User satisfaction and the shift when a Product-Market Fit replaces Product-User fit]]></title>
            <link>https://myriamgoude.medium.com/user-satisfaction-and-the-shift-when-a-product-market-fit-replaces-product-user-fit-25595c3feb38?source=rss-513594f2c347------2</link>
            <guid isPermaLink="false">https://medium.com/p/25595c3feb38</guid>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Myriam Goude]]></dc:creator>
            <pubDate>Fri, 06 Oct 2023 13:19:52 GMT</pubDate>
            <atom:updated>2023-10-06T14:31:43.037Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6nnq3L8pXmsfo2el3LIgLA.png" /></figure><h3>User to Market: why Airbnb and Blablacar fail in their customer relationships</h3><h3>And it occurs after a Product-Market Fit (PMF) replaces a Product-User fit (PUF)</h3><h3>A short overview of Digital Product life</h3><p><strong><em>💡Disclaimer: This article does not go into detail about each stage developed here. It only explains the whole lifecycle and its correlation with Business organization in Product stages.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KcHf1EO5g1qreigz9S1n0g.png" /><figcaption>A classical 4-stages of a Product lifecycle</figcaption></figure><h3>Stage 1: Early MVP</h3><p>The early MVP serves as the starting point for a product that does not yet exist. Typically, it is defined by a few lines on a pitch deck and designs. The MVP concentrates on 2–3 features and outlines the expected results of these features. It has undergone testing by the initial group of users, which includes friends, colleagues, and a close professional network. 10% of what is visible defines 90% of the main concerns the product is addressing.</p><h3>Stage 2: The Product-User Fit (PUF)</h3><p>In this phase, the product team has something developed to show. Even in draft or half-designed, half-functional. It involves close collaboration with users, tailoring the product based on their feedback, and crafting a user-centric experience. Users are co-designing with you, and you craft your business model in parallel with the learnings performed in this phase.</p><p>Understanding and addressing user needs helps to adjust and/or pivot until you reach your PMF.</p><p>Top 3 KPIs you should monitor at this stage:</p><ul><li>CAC</li><li>Time to feature x</li><li>Retention rate</li></ul><p>At this stage, any contact with a potential customer is a privilege. Customer service is indeed infused within the team, each member of the team.</p><h3>Stage 3: The Product-Market Fit (PMF)</h3><p>This is a critical milestone for product teams, indicating the alignment between a product and its target market. Achieving PMF signifies that the product satisfies customer needs and generates demand in the market.</p><p>During the PMF phase, extensive user research, a strong business model, and a clear vision are essential to ensure the product’s success and scalability.</p><p>KPIs you should add at this stage:</p><ul><li>MRR</li><li>Lifetime Value</li><li>The success rate on tracked features</li></ul><p>An important thing here is that we do not target anymore specific customers, we target a market. This means that customers are grouped into a market with common concerns, which is considered significant enough to generate profit.</p><p>Deploying PMF often leads to scalability issues when reaching out to targeted clients who are willing to deploy it massively or spread the word. As a result, it is necessary to consider partnering with a more robust organization. This not only requires reorganizing your technical stack but also the way you manage customer relationships. While customer service might still be under the product or directly under the CEO, the change occurs in selecting who to respond to.</p><h3>Airbnb Org, before 2017</h3><ul><li>E-Staff. Executives</li><li>Online Marketing Group</li><li>Social Media</li><li>Local Operations</li><li>Customer Experience (host/guest/trust&amp;safety) <em>← Product teams are here</em></li><li>Engineering (Software)</li><li>Design</li><li>Marketing</li><li>Legal</li><li>Finance</li></ul><p>As you can see, Airbnb, in its early 10s, had still a Customer service merged with Product (The product was below CS, which is quite uncommon but made its success thanks to its Stakeholder team strategy).</p><p>This was an integral part of the product team, ensuring close collaboration and a feedback loop between users and the product development process.</p><h3>Stage 4: Industrialization</h3><p>After achieving PMF, the product can shift focus to scaling and profitability. It deploys within industrial processes, applying patterns, standardization, and sanitizing code for robustness.</p><h3>2023: Airbnb org</h3><ul><li>…</li><li>Global Head of Operations</li><li>CS Service Excellence</li><li>Global Head of Hosting <strong><em>← Product by Stakeholders</em></strong></li><li>Global Head of Marketing <strong><em>← Product Growth</em></strong></li></ul><h3>2023: Blablacar org</h3><ul><li>…</li><li>Customer Service</li><li>Marketing <strong><em>← Product Growth stands here</em></strong></li><li>Product and design <strong><em>← Product stands here</em></strong></li></ul><p>Product decisions are dispatched through multiple departments, one attached to Data, the other to China, etc. So Product decision is diluted within the organization. This organigram shows that CS is considered as an entity apart from the big profit pillars of the company: market, data, and, essential one, the saint-trinity (previous stakeholder structure): Guest/Host/Adventures.</p><blockquote>💡 Brian Chesky, as we know after his call about removing all <a href="https://jocatorres.medium.com/airbnb-and-the-end-of-the-product-managers-48108cc16188">Product managers position</a> is a person that not only validate any product decision done within the company, but also believes that anybody can own the Product. This is for sure totally aligned with how a Product organisation should work, but, the risk, shown with this organigram is that CS is isolated from core pillars of Airbnb decisions. This mechanically isolate them from the roadmap and then from the “Product” as infused through other teams within Airbnb.</blockquote><h3>What happened? Fame to Shame Hall</h3><p>During the transition from the PMF (Product-Market Fit) stage to the industrialization stage, there exists a turbulent zone where fame shines a spotlight on you. This implies that not only the media and politics will scrutinize your actions, but a second wave of customers may also have different values and concerns compared to your initial adopters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lg92kbG8RNcWTRdlin7Vtw.png" /><figcaption>From Stage 3 to Stage 3: reshuffling the cards with detractors, customers, … and teams.</figcaption></figure><h3>From Profit to Profitability</h3><p>Efforts are being made in communication to promote white hat practices that prioritize quality control and penalize negative behaviors. The customer is no longer a source of profit and should be treated as costless. This approach aims for an optimal balance between benefits and costs. In product development, our primary focus is on maximizing benefits through effective strategies.</p><p>Significant metrics to measure here are :</p><ul><li>the way you are considered ( classical NFS)</li><li>and the flexibility level the customer service has to help you ( easily measurable via a scale rate)</li><li>Number of times a ticket is reopened</li><li>Number of complains</li></ul><p>The nature of the complaints for these Airbnb and Blablacar services is quite interesting: whereas some marketplaces are trying to help with two parts struggle, these companies are the ones complainers are talking about.</p><p>Not the hosts or travelers, no.</p><p>The business itself.</p><h3>Airbnb Complaints</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fUz9tnpamkhE5k3nuMnH3g.png" /></figure><p><em>Source: From Asher Fergusson, 2021 ( link: </em><a href="https://www.asherfergusson.com/airbnb"><em>https://www.asherfergusson.com/airbnb</em></a><em> )</em></p><h3>Blablacar complaints</h3><p>Here are 2 examples of complaints from <a href="https://www.mouthshut.com/product-reviews/BlaBlaCar-reviews-925771095">https://www.mouthshut.com/product-reviews/BlaBlaCar-reviews-925771095</a></p><blockquote>“<strong>Customers are unprotected with Blablacar</strong></blockquote><blockquote>Driver can cancel in the last minute and nothing happens to them, ruining your plans. If your request is accepted and you cannot reach the driver after, they don’t reply, you may not receive the refund if you cancel.</blockquote><blockquote>Europe should regulate them and protect more the consumer. It is not quite reliable and you are unprotected.”</blockquote><blockquote><em>09.07.23</em></blockquote><blockquote><em>“</em><strong><em>Doesn’t actually work</em></strong></blockquote><blockquote>Good concept and also really good prices. Only problem, it doesn’t work. Drivers cancel last minute and even worse you have to pay BEFORE you even get a ride. so you pay money to request just for the lazy drivers to cancel and then you need to wait 7 days to get your money back. Insane to me how this app even allows such drivers to use the app. If they publish a ride, they should also be willing to commit to the time and day and actually fullfill it. If the drivers want to be flexible fine by me but then don’t publish your trip online trying to make money from it. Such a disappointing app, I wonder if people even work at this company because it feels like they gave up ages ago.”</blockquote><blockquote><em>16.07.23</em></blockquote><h3>Ok … but how to fix it?</h3><p><strong>Keeping Customer service under the product team</strong></p><p>Excellent CPOs always maintain a dashboard overview of customer service tickets, relying on both reports and their team to identify macro trends and low signals.</p><p><strong>Automation, yes …. But</strong></p><p>Most of us have interacted with a bot or an AI that tries to assist us in resolving our issues. This is quite convenient for low-level information. However, it can be frustrating when they are unable to provide a satisfactory answer and keep redirecting us to a standard FAQ response. In such instances, customers appreciate a higher level of assistance to address specific queries. At this stage, customers are looking for quality service rather than shortcuts.</p><h3>Conclusion</h3><p>As a customer of both companies, I felt neglected due to the misalignment between their product and service. In this article, I wanted to explore this shift and suggest a possible solution for early adopters in the service industry: a reorganization of customer service.</p><p>As a next step, I am interested in expanding this research to other business examples and examining whether a poor customer experience systematically leads to a turbulence zone. I welcome any contrary business cases and insights on how such issues have been resolved.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25595c3feb38" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Embracing Change: My Journey from the Web to a Sustainable Future]]></title>
            <link>https://medium.com/design-bootcamp/embracing-change-my-journey-from-the-web-to-a-sustainable-future-8bfa7be40c61?source=rss-513594f2c347------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bfa7be40c61</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[sustainability]]></category>
            <category><![CDATA[pivot]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Myriam Goude]]></dc:creator>
            <pubDate>Tue, 05 Sep 2023 13:18:23 GMT</pubDate>
            <atom:updated>2023-09-13T00:48:07.572Z</atom:updated>
            <content:encoded><![CDATA[<p>Today, I stand at a pivotal moment in my career, a milestone that compels me to reflect on the winding path that has led me here. As I gaze back over the years, I am struck by the profound transformations I’ve witnessed in the ever-evolving landscape of the web — a journey that began with humble beginnings and has now set its sights on the intersection of Product and Sustainability.</p><p>As in the HBR article, “<a href="https://hbr.org/2017/04/why-you-should-have-at-least-two-careers">Why you should have two careers”</a> I’m totally convinced after years in a first area we are stronger and smarter to address another area. But this also means that we should be proud about what’ve been done so far.</p><p>I draw a quick graph here, closed to the <a href="https://yourstory.com/mystory/d90c9e8f6b-the-startup-curve-journey-of-an-entrepreneur">Startup curve</a> but applied to career Life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JS5RJjhT-pCQ1gyEZgdVZQ.jpeg" /></figure><h3>The Early Days: Navigating the Uncharted Web</h3><p>I started my career as a simple integrator, at a time when the web was still in its infancy. Spcial homage to Internet Explorer 6? Those were the days! I then ventured into the wild, dirty and messy world of web design, using tools like Golive, Photoshop, and Dreamweaver. CSS (God thanks border-radius and float left) and HTML were my daily life and I had to take into consideration responsiveness even though smartphones were not yet launched on the market.</p><h4>A Brief Interlude: Exploring Internal Communication</h4><p>I also explored internal communication, where I was introduced to the art of startup pitch decks. And I did… a lot, 1 minute, 5 minutes, 15 minutes, 30, 40, for sales, ventures, events, whatever possible combination. I exercised to the Big Why. Little did I know that these experiences would shape my future endeavors.</p><h4>The Rise of SaaS and Cloud Computing</h4><p>The landscape evolved, and I found myself in the emerging realms of SaaS models. Cloud was shy but had to be a bet. It was an exhilarating time as these technologies started becoming more user-friendly and accessible.</p><h4>Shifting: From Frontend Development to UX and Product</h4><p>My journey then took a turn towards UX and Product. I transitioned from being a front-end developer (REST API with Angular on RoR) to delving into the world of user experience and product design. It was a time when web Products ran into a structured development, full of specs and user stories, a crucial shift in my career. And with this structure, the velocity of development slightly increased. We really delivered fast.</p><h4>And then: Into the Realm of Product Management</h4><p>Product Management became my calling, and I eagerly embraced it. Putting my UX expertise on the frontstage, I developed tactical roadmaps and put the JTBD measurements as a priority. Over time, I took on more significant responsibilities, honed my strategic skills, and led a team and/or managed a diverse product portfolio and domains.</p><h3>The (not so) Ever-changing Web Landscape</h3><p>As the web landscape evolved, it started to make a boring cycle:</p><ul><li>SaaS experienced both rise and fall, and the debate repeated over and over between premise and cloud.</li><li>3rd party integration oscillated between productivity and security concerns.</li><li>The world of frontend development witnessed cyclical shifts between centralized and decentralized coding methods, with technologies JS, then Ajax, then MVC or JAMS stacks continuously reinventing themselves. 🔄</li></ul><h4>The missing digital core needs</h4><p>Out of these infinite debates, two critical issues persist and have not been yet effectively tackled:</p><ol><li>Enhancing Energy Efficiency: The surging energy consumption within the digital realm poses a significant challenge to the efforts of the transport industry in reducing CO2 emissions. Surprisingly, this critical concern remains largely unaddressed, with no discernible consideration from various stakeholders, be it individuals, technology stacks, businesses, or models.</li><li>Ultra-Nomadic Lifestyles: People have adopted increasingly nomadic lifestyles, both in terms of geographical locations and the fluidity of time. Slashers, digital nomads, multi taskers, etc.. are the ones that we forgot in all of these evolution steps. Whatever you call your product mobile friendly most of the services are not fitted to offline/online switch or multi-modal usages.</li></ol><h4>A Wake-Up Call: The Need for Evolution</h4><p>But now, it’s time for a shift in web Product Management. We can’t keep reinventing the wheel and claim to meet users’ needs ( does this mean previous products didn’t answer then ?).</p><p>I’ve had my wake-up call, and it’s time to reimagine the approach.</p><h3>The next chapter: aligning Head and Heart</h3><h4>Embracing the pivot: Merging Engineering and Digital Product</h4><p>I’ve decided to inject fresh perspectives into my journey. I’m not discarding my past achievements; they’ve shaped me into who I am today. I’m proud of my accomplishments and eager to share and apply these skills in my next chapter.</p><p>I was just bored about the challenges I faced in ( and I hate this :) ).</p><p>In many ways, I see this transition as a pivot — much like one would do in Product Management. The current “product” (my career) needs to adapt to the next world and respond to the signals around us. This is My PMF plot.</p><h3>The thrill of a New Journey</h3><p>My passion lies in the realms of Education and Sustainability. I’m determined to address human consumption behaviors, with a particular focus on urban contexts. And I started to define the path thanks to the MIT. I have the roadmap in my head, every checkpoint is here, with metrics, with assumptions. The tree is done, will all the possibilities and the red line I don’t want to deviate. Some skills are self-learned ( such as fundamental Physics laws), with experimentations, MVPs, etc. And some are missions, projects or trainings, I would say: helps coming from super smart people and teams.</p><p>I am thrilled to embark on this new career path and the journey that lies ahead. All the encouragement I received means the world to me, and I’m deeply grateful for all the positive energy I’ve received.</p><h3>A Wonderful Second Life Challenge</h3><p>Transitioning from a world of “jobs to be done” makers to a profound exploration of our future is a wonderful second-life challenge — one that I eagerly embrace.</p><p>I’m excited to explore and merge the realms of Engineering and Product, striving for a more holistic human experience, and unlocking these skills to promote environmental shift. The adventure has just begun. 🌟</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bfa7be40c61" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/embracing-change-my-journey-from-the-web-to-a-sustainable-future-8bfa7be40c61">Embracing Change: My Journey from the Web to a Sustainable Future</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Manifesto for future UX professionals]]></title>
            <link>https://myriamgoude.medium.com/manifest-for-future-ux-people-a1a99a87cdba?source=rss-513594f2c347------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1a99a87cdba</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Myriam Goude]]></dc:creator>
            <pubDate>Thu, 02 Mar 2023 17:30:43 GMT</pubDate>
            <atom:updated>2023-03-03T05:50:20.063Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZeKeDF73juQNomJmVO6nGg.jpeg" /></figure><h3>The Future of User Experience</h3><p>I went through a big concern in the last three years that made me think about the posture of User Experience in systems. Tons of signals emerged and the last one that shuffled the world, artificial intelligence raised the necessity to lay down these thoughts here.</p><p>Technology is changing, solutions provided to usages are also changing and mindsets in companies and individuals are moving UX on another playground than the one we are today. The insights below are merging and connect the dots in my point of view. The goal is to shape the new ID Card of UX as an activity and people excelling in it.</p><h3>Experience versus Advocacy</h3><p>User Experience is no more a one-sole-person holder. Experience is a larger concern. It doesn’t cover only one topic, product, or journey. Experience is the business fueler and should be massively considered as a principle of digital experiences infused in a Design-driven mindset. No experience means no usage. So pushing a step forward, a UX personified as nonsense. This should be a concern for anybody. Anytime. Anywhere. A word that came multiple times to my ears and that is deeply aligned with the posture we get in big systems is “Advocacy”. A UX person tends to be more and more of a User advocate in the whole Product stack.</p><p>It then comes to evidence that UX people are here, around the table, to defend and shout up users’ voices.</p><h3>UX, please forget static wireframes!</h3><p>Figma got the point here: for 5 years, collaboration was stuck into siloed expertise where handover was owned by flat-designs tools. In parallel, the Dev world was mature enough to collaborate smoothly within parts of dev components through a robust and wonderful git process, branched, reviewed, and added smoothly to existing code.</p><p>So Figma infused by design/dev teams took the ball and created a collaborative tool based ( not fully operational on git methodology but tends to)</p><p>But here comes the gap: most design people continue to deliver static experience and static view of the journey: page screens. Wireframes are standardized and created without considering pages as tons of components that have their own life. Their own experience.</p><p>2020’s products are no more pages. They are pieces of global experience pushed into hybrid contexts. Please UX people, jump now into the composable and integrating world!</p><h3>Product posture</h3><p>I read in the past two great articles: the first one was provided by a former MIT chairman in early 2015 about scaling organizations and comparing services versus products. The second one sourced in Forbes told that UX Designers have to shift to another stage in the discussions to not be pushed down to execute only people. This article pointed out that this trend ( reinforced by our great article here: <a href="https://trends.uxdesign.cc/">https://trends.uxdesign.cc/</a>) is turning maze the UX job and will probably create a lot of abandons, silent quitting, and worse: burnouts 😞</p><p>In the near, very near future, UX/UI career paths will divide in two ways. Most UX people who have appetencies for strategies, business/user requirements, and feature value measurements will naturally go to Product Management core skills. On the other path, we need to get strong crafters who know how to play with code and with data, to ensure consistency within the wow experience and adopt design ops shared with devs, marketing, and data practitioners. These interaction designers will own the hybrid componenting finest solutions that deserve the global experience of a brand web ecosystem.</p><h3>Innovation within pragmatism</h3><p>UX deliverables are challenged by AI. We have to prove that AI, and automatic services, scale our expertise on top-notch or out-of-the-box thinker minds. Technology accelerates our delivery on low, effortful deliverables that don’t cross the edge of personalization and momentum. We have to innovate and guarantee that we deliver doable, quick wins within constrained roadmaps.</p><h3>Future mandatory Skillsets</h3><p>Here is, in my opinion, what I will search for in the future teammates I will work with or onboard in my team :</p><ul><li><strong>“Sponge mind”</strong>: collect the signals, collect everything you can because it will help you to reconnect the dots when a problem shows up. This means that you should not look vertically ( eg. Only looking for solutions to the same problem or sector) but also horizontally: if a different experience made a wow effect solution on the psychological issue people are facing, take it, ingest it and remodel it.</li><li><strong>Holistic view</strong>: a tough one. But this deserves great pragmatic solutions that are done in conscious of this magic sentence: “ we know that we WON’T answer this problem, but this is our choice”. Being comfortable with making decisions and priorities on top of a backlog in knowing the full system ahead will give a great commitment of business and people working with you that you are leading together somewhere. It’s better to assume failures in your choice than be passive in your production.</li><li><strong>Negotiating</strong>: yes yes, you read it well. We are in a world of a tight budget, ROI measurements, and speed-to-market deliveries. So, you have to face decisions and tradeoffs at least 100 times a day. This is the exhausting job that produces the best gold key ever: confidence. Negotiating with devs means you are concerned about their difficulties. Negotiating with marketing means you know their time-to-market tight window. Negotiating with the business will show you defend users’ interests that the business is deeply aware of.</li></ul><p>Finally, I would highly recommend having these three pillars of excellence in your knowledge portfolio :</p><ul><li><strong>Accessibility</strong>. Please don’t tell me you know WCAG criteria. This is not enough. Tell us that accessibility is a matter of everyone’s context and usability and readability are high values in the accessibility knowledge</li><li><strong>Sustainability</strong>: green design, even if the term is somehow bashed, is a mandatory one. We care about sense and a better usability world. This is aligned with the fact that users will need less consuming data and energy to empower their commitment to the experience your product is proposing.</li><li><strong>Data structure</strong>: the world goes faster to a data-driven mindset than a design mindset. This is impossible to compete. Because we love quite more to rely on facts and logical cold numbers and IDs than on a blue or red button. This is our human bias. So play with it. Take this, climb in this roadster to get the thrill of power in using data in a sexy and desirability mood.</li></ul><p>Happy to discuss and collect your feelings :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1a99a87cdba" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>