<?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 Astrid Noya on Medium]]></title>
        <description><![CDATA[Stories by Astrid Noya on Medium]]></description>
        <link>https://medium.com/@astrid.noya?source=rss-3b9fc1566c60------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*g_r4cPQJQQqOvpM74AHy1w.jpeg</url>
            <title>Stories by Astrid Noya on Medium</title>
            <link>https://medium.com/@astrid.noya?source=rss-3b9fc1566c60------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 06:00:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@astrid.noya/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[Why Systems Thinking belongs in Product Management]]></title>
            <link>https://medium.com/@astrid.noya/why-systems-thinking-belongs-in-product-management-ea7b5a555666?source=rss-3b9fc1566c60------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea7b5a555666</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[Astrid Noya]]></dc:creator>
            <pubDate>Thu, 09 Apr 2026 11:56:40 GMT</pubDate>
            <atom:updated>2026-04-09T11:56:40.355Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8KyuFwViCiyZ0HAknr17IQ.jpeg" /></figure><p>Whenever someone asks what I’m studying for my Master’s, I prepare myself for the inevitable confusion. I say “Systems Design,” and their minds immediately jump to Systems Engineering or Backend Architecture. I then find myself explaining that I’m not looking at servers or code, but at patterns, behaviors, and interconnections.</p><p>It is the skill that separates those who fix symptoms from those who solve problems. In an era where “AI skills” dominate every LinkedIn headline, Systems Thinking often feels like the quiet, less trendy skill. But as product landscapes become increasingly complex, it may be the most underrated tool a PM can have.</p><p><strong>So, what is Systems Thinking?</strong></p><p>Systems thinking is both a methodology and a practice that understands the world as a web of interconnected elements rather than a collection of isolated objects. Within this framework, elements are organized specifically to fulfill a particular purpose. Donella Meadows in Thinking in Systems (2008) understands the system as categorized by three essential pillars: elements, interconnections, and a function or purpose. While the physical elements are typically the most visible features, the interconnections, often functioning as flows of information, are what truly govern how the system operates.</p><p>That’s the basic theory. Now let’s talk about what it actually looks like when you are building a product.</p><p><strong>Case 1: Product Teams Working in Silos</strong></p><p>Often in product teams, as PMs are divided by domains, each team works in silos with not much communication between them. From a systems thinking perspective, we understand that the product is interconnected. We are solving the needs of a user as a whole, which means when working on roadmaps, we should think about the product as a system rather than isolated domains. That way the fixes are sustainable over time and don’t create new problems down the line, both from a UX and a technical perspective.</p><p><strong>Case 2: Customer Journeys and Loops</strong></p><p>A tool I find fascinating to use is the customer journey.</p><p>Besides helping to map friction points, systems thinking pushes you to go one step further: to look for the loop behind the friction. Why are users doing what they’re doing at a structural level, not just at a motivational level?</p><p>A concrete example: imagine a SaaS product where users consistently drop off during their second week. The instinct is to look at that moment in isolation. Is the onboarding too long? Is a feature confusing? But if you map the full journey and layer your analytics on top, you might notice something else. Users who engage with a core feature in week one tend to stay. Users who don’t, leave by week two without exception. The drop-off in week two isn’t the real problem. It’s the result of something that already went wrong in week one. You were looking at the symptom, not the loop.</p><p>When you see that, you stop optimizing the wrong node. You go upstream.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*BOkIDaEjo45Usvs8DDmReQ.jpeg" /></figure><p><strong>Case 3: Avoiding Rebound Effects</strong></p><p>One of the most common mistakes in product teams is what systems thinkers call a rebound effect, when a solution creates a new problem somewhere else in the system.</p><p>A team notices engagement is dropping. They add a notification system to bring users back. Engagement goes up. Three months later, opt-out rates spike and app store reviews mention feeling spammed. The metric they optimized created pressure somewhere else, and the system pushed back.</p><p>This is especially common in health or social products, where the stakes of unintended consequences are higher. But it happens everywhere. A feature that increases short-term retention can quietly erode trust. A growth lever that works in Q1 can hollow out your user base by Q3.</p><p>The antidote isn’t to move slower. It’s to ask, before a launch: what else will change if this changes? Map the connected nodes. Think about delays too. Systems often don’t give you feedback immediately, and by the time the data shows up, you have already made three more decisions on top of the broken one.</p><p><strong>The PM habit that changes everything</strong></p><p>Before diagnosing a metric, map the loop. Ask: what is sustaining this behavior?Is this behavior slowing down on its own, or is it getting bigger over time?And how long does it take for my actions to show up in the data?Sometimes PMs are trained to move fast and ship often. That’s not wrong. But without a model of the system you are operating in, speed just means you are making more mistakes per quarter.</p><p>Systems Thinking doesn’t slow you down. It tells you which lever to pull and what will actually happen when you do.</p><p>I came to Product Management from Clinical Psychology. In therapy, you learn quickly that treating symptoms without understanding the system behind them is not just ineffective and it can make things worse. Product works the same way. A metric that drops isn’t a problem to fix. It’s a signal from a system trying to tell you something that is probably happening much deeper. The question is whether you are listening to the signal or just reacting to the number.</p><p>That’s why I think Systems Thinking belongs in every PM’s toolkit. Not as a framework to follow, but as a way of seeing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea7b5a555666" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Experience as a Design Ops Intern: Research and Design]]></title>
            <link>https://medium.com/@astrid.noya/my-experience-as-a-design-ops-intern-research-and-design-95b1ae4f5957?source=rss-3b9fc1566c60------2</link>
            <guid isPermaLink="false">https://medium.com/p/95b1ae4f5957</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[heatlhcare]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[intership]]></category>
            <dc:creator><![CDATA[Astrid Noya]]></dc:creator>
            <pubDate>Sun, 30 Mar 2025 15:51:36 GMT</pubDate>
            <atom:updated>2025-03-30T15:51:36.561Z</atom:updated>
            <content:encoded><![CDATA[<p>When you’re in university, you have a vision of what your career path will look like, but it rarely goes exactly as planned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sRwTEyieGwi6Us9n3cNONg.jpeg" /><figcaption>Photo credit: <a href="https://unsplash.com/de/@zanecrtr">zane carter</a> @ unsplash</figcaption></figure><p>I did my bachelor’s in Psychology, worked in educational innovation for a couple of years, and then jumped into tech as a Product Manager. Coming from a humanities background taught me to reflect deeply, but thinking in processes and from a more technical perspective was a real challenge. I had to learn a lot about product, UX, and some basic coding, and I loved it.</p><p>This drive for innovation and my curiosity about how big tech companies create new technologies led me to Germany, and eventually, to Doctolib. It was my first time on a Design Operations team, which focuses on maximizing the impact and efficiency of design processes in the company. Working in Design Ops gave me a sense of just how large and sophisticated an organization can be.</p><p>In nearly three years as a Product and Project Manager, I learned a lot about digital products and how to launch new features. Still, I felt like I was missing pieces of a puzzle and couldn’t see the bigger picture. During my 6-months internship at Doctolib, I worked closely with the research and design teams, which are quite large and international, spanning across Italy, Amsterdam, Berlin, and Paris. After many coffee chats, meetings, and shadowing different projects, I finally put together the puzzle I had struggled with for so long</p><p><strong>Behind the Scenes of Research</strong></p><p>As part of my role, I dove deep into the research process. This involved a variety of tasks, including note-taking, screening participants, participating in debrief sessions, developing recruitment strategies, and coordinating research participants for various projects. Essentially, I supported our research projects in areas that can often lead to bottlenecks.</p><p>When a team is ready to do research, they usually know what kind of participants they need. But if the criteria are very specific or if they are short on time, they ask our team for help. I have to admit, recruitment isn’t the most thrilling part of research, but it was my first real glimpse into how to conduct proper studies. It made me realize just how crucial planning and selecting the right participants are. Without proper recruitment, research simply cannot move forward.</p><p>Beyond recruitment, I also handled logistics like contracts and payment follow-ups. Before this role, I had never tackled these kinds of administrative tasks. To my surprise, I found them quite enjoyable. Identifying issues, addressing bottlenecks, streamlining processes for our team, and brainstorming solutions turned out to be a rewarding experience. These tasks might seem underrated, but they are truly the heart of the machine — without proper administration, there can be no effective research. Through these responsibilities, I’ve gained a deeper appreciation for the behind-the-scenes work that makes research possible</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-3HWm-3F2UsPwUNb6Ocxdg.jpeg" /><figcaption>Photo Credit: Andrea<strong> </strong>Piacquadio<strong> </strong>@pexels</figcaption></figure><p><strong>Organizing an On-Site Research Event</strong></p><p>At Doctolib, our team ideally organizes office events every semester to connect designers and product managers with our users. These events facilitate in-person interviews and bring in medical experts to provide feedback on prototypes. My manager asked if I would be willing to organize the next event. Even though I had never done it before, I accepted the challenge, but I underestimated how much planning is required for this kind of event. I initially thought a week of work would be enough to set it up. In the end, I managed everything, from recruitment plans and screening surveys to onboarding product leads and designers, as well as handling logistics, presentations, contracts, and a feedback survey. It was far more complex than I expected and required many more hours than I had anticipated, but it gave me confidence in managing projects and people in both English and German, and helped me overcome any lingering insecurities when it came to managing big groups of people.</p><p><strong>Conducting Research: Navigating Language and Healthcare Terminology</strong></p><p>I was born in Peru and learned English at school. German was a language I studied at university for over four years, but when I started at Doctolib I didn’t feel confident enough to facilitate research sessions in technical German, especially with specialized healthcare vocabulary. However, I made it my goal to eventually conduct a research session in German. Through the onsite research event, I had the opportunity to step in as an interviewer. It became a key moment for me. Not only did I moderate a session, but I also helped analyze the insights. It was challenging at first, but once I understood how to do it, the process became enjoyable. Translating user comments into pain points showed me that users often bring their own solutions, but we need to stay focused to uncover the true problems behind their words. We presented the results to the team, and I felt very proud of our work.</p><p><strong>Diving into Design</strong></p><p>Before joining Doctolib, I had some design-related experience, but never in depth. It all started to come together when I participated in a design days event. It’s a catch-up to share global advancements on features in our team. At the moment I was hearing about the design projects and updates, I knew I wanted to become more involved in design processes. I began looking for opportunities to design or shadow product designers during their meetings, which was one of the best decisions I made.</p><p>I started shadowing a project with a service chatbot with AI that I found super interesting. I also started participating in mentoring sessions from designers to familiarize myself with our design system and to develop the capacity to design from scratch. I learned how to put together wireframes, explored Figma features, and started developing a strong understanding of frames, auto layout, and<a href="https://oxygen.doctolib.design/"> our Design System</a>. It was a challenge because I don’t have a formal design background, but it made me realize how much I enjoy contributing to the product from a design perspective. Designing became the highlight of my week. I am grateful to the designers as <a href="https://medium.com/u/589177f5da91">Celina</a>, <a href="https://medium.com/u/45554841f107">Colbys</a>, Laura, <a href="https://medium.com/u/5869cd3486e1">Asier</a>, Felix, and Lisa, who took time to have coffee with me, share resources, events or review how I could improve with the tools of Figma.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NGodY-3t9dOsafPcMh4tIw.jpeg" /><figcaption>Figma Event</figcaption></figure><p>Each of these experiences shaped how I view research, design, and product. From recruiting and organizing on-site events to shadowing design sessions, my last six months were packed with learning. I arrived determined to learn as much as possible, and I didn’t just acquire new frameworks, methodologies, and processes. I also gained clarity on where I want to focus — Product, Research, and Design — which make up my puzzle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TgJd4cOg66KpdIVT0BB3jg.jpeg" /><figcaption>Photo credit: Benjamin Zanatta @unsplash</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95b1ae4f5957" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>