<?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 Emma Moystner on Medium]]></title>
        <description><![CDATA[Stories by Emma Moystner on Medium]]></description>
        <link>https://medium.com/@em.moystner?source=rss-b5b26ca5ae9d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*8gdGfU_kLKamG0wB</url>
            <title>Stories by Emma Moystner on Medium</title>
            <link>https://medium.com/@em.moystner?source=rss-b5b26ca5ae9d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:17:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@em.moystner/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[Craft, Systems, and the Humans in Between: A Design Leadership Thesis]]></title>
            <link>https://medium.com/@em.moystner/craft-systems-and-the-humans-in-between-382023f57907?source=rss-b5b26ca5ae9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/382023f57907</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Emma Moystner]]></dc:creator>
            <pubDate>Sat, 18 Apr 2026 11:54:33 GMT</pubDate>
            <atom:updated>2026-04-18T11:55:05.379Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ggKAcYredpf8jk-fnts6sg.png" /></figure><h3><strong>Starting with People</strong></h3><p>Design leadership is a practice, not a title. It’s the practice of seeing entire systems through the lens of human experience, having the courage to advocate for the people inside them, and building up the designers behind you: empowering them, equipping them, challenging them to become better than you found them. That conviction didn’t come from years of leading design teams. It came from a semester of case studies, simulations, countless hours of reflection, and honest conversations about what leadership actually costs. My path into design isn’t traditional. But I’ve come to believe it’s exactly the right foundation for it.</p><p>I studied international business and cultures in undergrad, with a minor in religious studies and Spanish. That combination wasn’t accidental. I’ve always been drawn to the complexity of how people see the world differently, what Escobar calls pluriversal thinking: the recognition that there isn’t one universal way of knowing, and that culture, belief, and language shape the way we navigate the same situations in completely different ways. I loved the strategy side of business, but what pulled me in deeper was the human side: understanding why people do what they do, and how systems either support or fail them depending on who they are and where they’re coming from.</p><p>Today, I define myself as an interaction designer who thinks in systems and advocates for people. I’m drawn to industries where design decisions carry real weight: healthcare, aviation, wellness. In those spaces, a well-designed experience isn’t just pleasant. It’s a matter of dignity, safety, and trust. Costanza-Chock names this clearly: design is a site where power is exercised, and centering the people most impacted by a system isn’t a nice-to-have. It’s the whole point.</p><h3><strong>Craft, Data, and the Seat Nobody Gives You</strong></h3><p>Two threads in particular reshaped how I think about what it means to lead in design: studying Katie Dill’s career and analyzing Duolingo as an organization. But the deeper shifts came from the places where theory met practice: simulations that forced me to lead under pressure, and frameworks that helped me understand what I was doing and why.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*LQt_ceH5BniVf7aP" /></figure><p><strong>Katie Dill: Craft as the Foundation of Influence</strong></p><p>Katie Dill’s trajectory, from hands-on design roles at Lyft and Airbnb to VP of Design at Stripe, tells a story the industry needs to hear more clearly. Dill didn’t ascend to leadership by abandoning craft for strategy. She built her authority through craft. Her deep understanding of how design works at the detail level is what gave her the credibility to operate at the systems level: to shape how design functions across Stripe’s entire product ecosystem, to partner meaningfully with engineering and product, and to make the case for design’s business value in a language executives actually respond to.</p><p>What struck me most was the cross-functional dimension. Dill doesn’t lead by asserting design’s importance in the abstract. She leads by demonstrating it, by showing how design coherence across a complex financial infrastructure translates to measurable outcomes. That’s a fundamentally different model than the “fighting for a seat at the table” narrative that dominates so much design leadership discourse. She doesn’t fight for the seat. She earns it by making the work undeniable.</p><p>I saw this principle come alive in a simulation on board pressure, where I had to defend a design team’s budget during a revenue plateau. My instinct was to reframe design as a risk management function, not a cost center, and to connect it directly to revenue metrics: onboarding completion, feature adoption, retention. The principle I kept returning to: speak in outcomes, not outputs. Nobody under pressure wants to hear what your team made. They want to know what changed because your team made it. That’s the Dill model in practice.</p><p>The pattern I observed: the most effective design leaders aren’t choosing between craft and strategy. They’re using deep craft knowledge as the lens through which they see strategic opportunities that others miss. And they’re multiplying that craft by developing it in others, hiring for curiosity and agency, and building teams where designers grow into leaders themselves (Dill). Craft isn’t the opposite of leadership. It’s the prerequisite. And passing it on is the responsibility.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*y4x6C4kiZ6bmjqGw.png" /></figure><p><strong>Duolingo: Data-Driven Craft in Service of a System</strong></p><p>Duolingo challenged my assumptions about what “design-led” actually means. On the surface, it’s a language learning app with an iconic green owl and satisfying animations. Underneath, it’s one of the most intentional behavioral design systems. Every design decision is validated through relentless A/B testing and data analysis. The streak mechanic, the notification timing, and the social pressure features: every element is measured and iterated based on what actually changes behavior. The craft is exquisite, but it’s craft in service of a system, not craft for its own sake (Reyes). Verbeek would call these designed “scripts” — embedded prescriptions that actively shape how users behave. The streak isn’t a feature. It’s a behavioral architecture, and that makes it an ethical question as much as a design one. The owl isn’t unhinged by accident. It’s unhinged because delight was hypothesized, tested, and proven to drive learning outcomes.</p><p>The lesson I took from both Katie Dill and Duolingo is the same: craft mastery matters enormously, but its value is unlocked when it operates in service of something larger than the artifact. For Dill, that larger thing is organizational coherence. For Duolingo, it’s behavioral transformation. Systems thinking and human-centered design aren’t separate disciplines. They’re complementary lenses, and the tension isn’t between data and empathy. It’s between having intentional design leadership directing the system and not having it.</p><h3><strong>From Screen-Makers to System-Seers</strong></h3><p>Design leadership is changing because the work itself is changing. AI is accelerating production-level design — layout generation, component creation, copy iteration, even basic user flow prototyping — and that acceleration is shifting where designers create the most value (Verganti; Haney). The designers who thrive in this landscape won’t be the ones competing with AI on output speed. They’ll be the ones who can operate upstream: framing the right problems, mapping the systems those problems live inside, navigating stakeholder dynamics, and making strategic decisions about where design intervention matters most. Capra calls this ecological literacy — the recognition that the major problems of our time are systemic, interconnected, and impossible to understand in isolation. The designer who develops that literacy is the one who sees the feedback loops everyone else is ignoring.</p><p>But the shift goes deeper than production speed. Design must now fluently collaborate with agents and systems, not just humans. The question is no longer “how do we design a screen?” but “how do we shape human-agent relationships before they harden into defaults?” When autonomous agents learn and act on our behalf, interaction design expands beyond GUIs into the architecture of trust, consent, and agency itself. This is a fundamentally different design problem, and it demands a fundamentally different kind of design leader.</p><p>The next era of IxD leadership looks less like a designer managing a team of other designers, and more like a designer embedded in the complexity of an industry. Someone who understands the regulatory landscape, the operational constraints, the cross-functional politics, and the lived experience of the humans moving through the system. Manzini argues that resilient systems emerge from distributed, locally responsive networks, not centralized command. The system-seer designer doesn’t just understand the system. She advocates for making it more resilient. In healthcare, that means understanding clinical workflows, insurance constraints, and patient psychology. In aviation, it means understanding reservation systems, airport operations, regulatory bodies, and the full passenger journey from booking to baggage claim.</p><p>Design leaders must evolve from screen-makers to system-seers. Not by abandoning craft (that remains the foundation of credibility) but by expanding the aperture of what they apply their craft to. And as AI absorbs more of the production layer, the leader’s most important work shifts further toward people: developing designers who can think at the systems level, challenging them to operate beyond the screen, and creating the conditions where junior designers grow into the kind of leaders the profession will need next. The designer who can look at an airline’s disruption recovery process and see not just a notification screen but an entire system of human stress, operational chaos, and algorithmic decision-making: that designer is leading, whether or not they have “Director” in their title.</p><h3><strong>Designing the Organization, Not Just the Interface</strong></h3><p>If design leadership evolves in this direction, organizations have to evolve too. In aviation, the passenger experience spans booking platforms, airport infrastructure, cabin hardware, ground operations, and post-arrival services. No single product team owns that. Not every design leader needs to be a manager to influence across those silos. The IC design leader, someone with deep craft expertise and systems vision who influences through the quality and scope of their work, becomes critical. Whether or not you have direct reports, you can still be the person who makes everyone on your team better at their craft.</p><p>A simulation called “The Design Revolt” made this concrete for me. Design had no formal power, and the team was hemorrhaging talent because of it. My instinct wasn’t to plead for respect. It was to build structural authority: gate sprint planning on design sign-off, make cross-functional reviews binding, require documented rationale when design recommendations are overridden. Design leadership isn’t about persuading people to value design. It’s about building the systems that make design’s value inescapable. And the best version of that is orchestral: less about enforcing process, more about setting rhythm and harmony across contributors.</p><p>As AI handles more production work, collaboration becomes less about handoffs and more about co-creation: designers and engineers working together inside the same system, making decisions in real time. Katie Dill’s approach at Stripe offers a preview (Dill). She doesn’t run design as a siloed craft organization. She runs it as a function that creates coherence across Stripe’s complex product ecosystem, grounded in shared outcomes, not turf wars. The design leader’s role in this model isn’t to protect design’s territory. It’s to be the person in the room who keeps asking: what is the human experiencing right now, and is this system serving them?</p><h3><strong>When the Airport Becomes the Interface</strong></h3><p>Through my futures research on airline interaction design for 2036, I’ve mapped several emerging technology trajectories that fundamentally reshape what design leadership means in practice.</p><p>AI is moving from assistive to agentic. In aviation, we’re already seeing AI that autonomously rebooks passengers during disruptions. Delta’s Concierge and American Airlines’ AI rebooking tools handled hundreds of thousands of travelers in 2025 (Future Travel Experience). By 2036, the design challenge isn’t “how do we design a rebooking screen?” It’s “how do we design consent, agency, and transparency when an AI reroutes your entire journey before you even know there’s a problem?” That’s a fundamentally different design problem, one that requires understanding power dynamics, algorithmic ethics, and the psychology of trust.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/0*2--RbfpogA--shE_.jpg" /><figcaption>Delta’s Parallel Reality display</figcaption></figure><p>Ambient computing is dissolving the boundary between digital interface and physical environment. Delta’s Parallel Reality display at Detroit Metro, a single screen that shows personalized flight information to 100 different passengers simultaneously, is an early signal (Delta News Hub). AR glasses, spatial computing, and smart infrastructure are converging toward a future where the airport itself becomes the interface. The design leadership challenge here isn’t interaction design in the traditional sense. It’s attention ethics: who gets to put information in your field of vision, when, and with what consent? Verbeek calls this the mediation of perception — technologies don’t just shape what people do, they shape what people see and how they interpret it. When the airport becomes the interface, that mediation becomes inescapable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ktNUhSRF2iDtc7Lu.jpg" /></figure><p>Biometric systems are rewriting the relationship between identity and experience. IATA’s One ID initiative aims to replace physical documents with biometric digital identity across the entire travel journey (IATA). The design implications are enormous: not just the interface design of enrollment and verification, but the systemic design of consent, data ownership, and equity. Who gets left behind when biometrics become the default? What happens to the elderly traveler who can’t hold still for a scan, the burn survivor whose face doesn’t match an algorithm’s expectations, or the person who simply doesn’t trust a system that stores their body as data? Costanza-Chock names this precisely: design creates affordances for some while foreclosing them for others, and that distribution of agency reflects existing power hierarchies. Schultz goes further: when biometric systems are designed from a Western, able-bodied default, that’s not a design oversight. It’s an epistemic choice about whose body is “normal.” These aren’t edge cases. They’re the people design leaders are supposed to be fighting for.</p><p>These technologies don’t just change what designers make. They change how design teams work. The shift in the AI age is from collaboration to orchestration. Design systems must now govern both human and AI behavior, incorporating prompt architecture, behavioral constraints, ethical guardrails, and human override protocols alongside traditional component libraries and interaction patterns (Haney). The design leader’s workflow expands from managing a team of people to orchestrating a system of people, agents, and automated processes, all while maintaining coherence for the human on the other end. That requires a new kind of operational fluency that most design programs, including this one, are only beginning to reckon with.</p><p>In every case, the emerging technology creates design problems that can’t be solved at the screen level. They require designers who think in systems, who understand the human consequences of technical architecture, and who have the courage to raise uncomfortable questions about power, consent, and inclusion. That’s the kind of design leadership the next decade demands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/0*s5UzhLNvpeipi3VL.jpg" /></figure><h3><strong>The Operating System I Intend to Run On</strong></h3><p>Here’s what I stand for: design leadership must be kind and empowering. The leaders I admire most aren’t the ones who hoard influence or gatekeep expertise. They’re the ones who lift others up, who create space for people to grow into their own capability, and who lead with generosity even when the pressure is high. I want to be that kind of leader — one who empowers the people around her, not just the users she designs for. Not designing to save anyone, but designing to remove the barriers to their own agency (IDEO).</p><p>That conviction didn’t come from reading about leadership. It came from a simulation where I failed at it. In a performance review exercise set in a high-growth life sciences company, I optimized for the metrics: billability, client satisfaction, output velocity. And the numbers looked great. But when I stepped back and evaluated honestly, I had to write something uncomfortable: I hit the numbers and missed the job. I had optimized for results at the cost of team development and mentorship. The people on my team were producing, but they weren’t growing. Empowerment isn’t a soft value you layer on top of performance. It is performance, measured on a longer timeline. A leader who builds capability in others compounds her impact. A leader who only extracts output eventually runs out of both.</p><p>Design leadership in healthcare and aviation carries a different weight than design leadership in social media or e-commerce. When you’re designing for someone who is sick, scared, exhausted, or stranded, you don’t get to “move fast and break things.” The stakes demand craft precision, deep empathy, and genuine domain understanding. In these industries, getting it wrong isn’t a conversion dip. It’s a person harmed. Safety isn’t a constraint on good design. It’s the definition of it.</p><p>I’m evolving into a designer who holds both craft and context: a career changer with an INFJ’s drive to understand the patterns beneath the surface, building domain expertise every day in the industries that matter most to me. The kind of leader I’m becoming doesn’t wait for permission to lead. She leads by seeing what others miss: the seam where the experience breaks, the moment where the system fails the person. She leads by making the designers around her sharper, braver, and more capable than they were before she showed up. What I’m building toward isn’t just a career. It’s a practice: craft in service of systems, systems in service of humans. That’s the operating system I intend to run on.</p><p><strong>Works Cited</strong></p><p>Capra, Fritjof. “Connecting the Dots: On Systems Thinking and the State of the World.” Center for Ecoliteracy, 2015.</p><p>Costanza-Chock, Sasha. <em>Design Justice: Community-Led Practices to Build the Worlds We Need.</em> MIT Press, 2020.</p><p>Dill, Katie. “Building Beautiful Products with Stripe’s Head of Design.” Interview. <em>Lenny’s Podcast,</em> 2023, <a href="http://www.lennysnewsletter.com/p/building-beautiful-products-with">www.lennysnewsletter.com/p/building-beautiful-products-with</a>.</p><p>Dill, Katie. “How Design at Stripe Is Evolving.” Interview. <em>Dive Club,</em> 2026, <a href="http://www.dive.club/deep-dives/katie-dill">www.dive.club/deep-dives/katie-dill</a>.</p><p>Escobar, Arturo. <em>Designs for the Pluriverse: Radical Interdependence, Autonomy, and the Making of Worlds.</em> Duke UP, 2018.</p><p>“12 Technology and CX Trends That Can Enhance Airline and Airport Operations in 2026.” <em>Future Travel Experience,</em> Jan. 2026, <a href="http://www.futuretravelexperience.com/2026/01/12-technology-and-cx-trends-that-can-enhance-airline-and-airport-operations-in-2026/">www.futuretravelexperience.com/2026/01/12-technology-and-cx-trends-that-can-enhance-airline-and-airport-operations-in-2026/</a>.</p><p>Haney, Stephen. “The 2026 AI Design Field Report.” Interview. <em>Dive Club,</em> 2026, <a href="http://www.dive.club/deep-dives/stephen-haney-2">www.dive.club/deep-dives/stephen-haney-2</a>.</p><p>IDEO. <em>The Field Guide to Human-Centered Design.</em> IDEO.org, 2015.</p><p>Manzini, Ezio. “Resilient Systems and Cosmopolitan Localism.” <em>Networking Cultures,</em> 2015.</p><p>“Meaningful Metrics: How Data Sharpened the Focus of Product Teams.” <em>Duolingo Blog,</em> 2023, blog.duolingo.com/growth-model-duolingo/.</p><p>“One ID.” IATA, <a href="http://www.iata.org/en/programs/passenger/one-id/">www.iata.org/en/programs/passenger/one-id/</a>. Accessed 17 Apr. 2026.</p><p>“Parallel Reality™ Unlocks Simpler, Personalized Airport Experience for Detroit Customers.” <em>Delta News Hub,</em> 2022, news.delta.com/parallel-realitytm-unlocks-simpler-personalized-airport-experience-detroit-customers.</p><p>Reyes, Mig. “Harsh Truths That Designers Need to Hear.” Interview. <em>Dive Club,</em> 2025, <a href="http://www.dive.club/deep-dives/mig-reyes">www.dive.club/deep-dives/mig-reyes</a>.</p><p>Schultz, Tristan, et al. “What Is at Stake with Decolonizing Design? A Roundtable.” <em>Design and Culture,</em> vol. 10, no. 1, 2018, pp. 81–101.</p><p>Verbeek, Peter-Paul. “Materializing Morality: Design Ethics and Technological Mediation.” <em>Science, Technology, &amp; Human Values,</em> vol. 31, no. 3, 2006, pp. 361–380.</p><p>Verganti, Roberto, Luca Vendraminelli, and Marco Iansiti. “Design in the Age of Artificial Intelligence.” <em>Harvard Business School Working Paper,</em> no. 20–091, 2020, <a href="http://www.hbs.edu/faculty/Pages/item.aspx?num=57691">www.hbs.edu/faculty/Pages/item.aspx?num=57691</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=382023f57907" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Data Crisis: How Ignoring Women’s Health Data Fails Everyone]]></title>
            <link>https://medium.com/artcenter-graduate-interaction-design/the-data-crisis-how-ignoring-womens-health-data-fails-everyone-357e649994ed?source=rss-b5b26ca5ae9d------2</link>
            <guid isPermaLink="false">https://medium.com/p/357e649994ed</guid>
            <category><![CDATA[womens-health]]></category>
            <category><![CDATA[wearable-technology]]></category>
            <category><![CDATA[sports]]></category>
            <category><![CDATA[fitness]]></category>
            <category><![CDATA[equality]]></category>
            <dc:creator><![CDATA[Emma Moystner]]></dc:creator>
            <pubDate>Mon, 27 Oct 2025 11:58:10 GMT</pubDate>
            <atom:updated>2025-10-27T23:44:40.642Z</atom:updated>
            <content:encoded><![CDATA[<p>The roots run deep. For decades, medical and sports research has treated male as the default human, creating a cascading crisis we’re still living with today.</p><p>Until 1977, the FDA actually recommended excluding women who could potentially have children from early drug testing — the critical stages where researchers determine if a medication is safe and whether it works. This meant even women on birth control or whose husbands had vasectomies couldn’t participate. This cautious approach stemmed from tragedies like thalidomide, a medication linked to severe birth defects, but it created decades of male-default research leaving women’s health behind.</p><p>While the National Institutes of Health (NIH) established inclusion policies in 1986 and Congress mandated women’s inclusion through the NIH Revitalization Act of 1993, implementation was initially poor. The damage was already done — entire research paradigms, methodologies, and “standard” protocols had been built around male physiology.</p><h3>The Scale of the Problem</h3><p>Only 7.15% of sports and exercise medicine research focuses on women — barely improved from 6% a decade ago, while male-focused research is nearly triple that at 18.6% (Ose et al., 2025). This isn’t just a gap; it’s a chasm.</p><p>This decades-long exclusion didn’t just affect medicine — it shaped how we understand exercise physiology, recovery metrics, and ultimately, how we design the technology meant to help us understand our bodies. The result? Products and protocols that pretend women’s hormones don’t exist.</p><p>Most people think of reproductive health being relevant only to pregnancy. But the fact of the matter is that it affects women on a daily basis. Reproductive hormones fundamentally change how our bodies respond to training, recovery, and stress — yet most research ignores this entirely.</p><h3>How This Plays Out: The Wearable Technology Case Study</h3><p>In 2025, wearable technology has achieved what seemed impossible a decade ago. We continuously monitor heart rate, track sleep, and provide personalized recovery recommendations — all from a device on your wrist. Over 500 million people are optimizing their training and understanding their bodies in ways that previous generations never could.</p><p>As an avid runner myself, wearable technology has become essential to my training. I tracked my period on my Garmin for years. When I switched to COROS — which doesn’t have cycle tracking at all — I thought no worries. But I realized how much it affected me until I did more research. Then I figured out these wearable devices don’t really consider women’s bodies. They’re built off of men’s algorithms.</p><p>This is genuinely remarkable. But it’s built on incomplete data.</p><h3>The Biological Reality They’re Ignoring</h3><p>Men’s hormones remain relatively stable day-to-day, making their training responses consistent. Women cycle through dynamic hormonal changes every ~28 days, meaning the same recovery metrics have completely different implications depending on cycle phase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/0*8ALQnfbLqAW4mwg9" /><figcaption>The Menstrual Cycle</figcaption></figure><p>The four phases:</p><ul><li><strong>Menstrual</strong>: Hormones at their lowest. Lower energy initially, but strength often returns as hormones begin rising.</li><li><strong>Follicular</strong>: Low estrogen and progesterone. Peak cardiovascular recovery, efficient muscle building, better training tolerance.</li><li><strong>Ovulation</strong>: Estrogen peaks. Many women feel strongest here — peak performance window.</li><li><strong>Luteal</strong>: Elevated hormones. Progesterone increases core temperature, impairs recovery, decreases heat tolerance, and makes muscle building harder.</li></ul><p>Emily Capodilupo — Senior VP of Data Science at WHOOP — analyzed 5,000 women across 14,000 cycles, far exceeding typical exercise studies. After controlling for training load, women showed significantly higher cardiovascular recovery during follicular versus luteal phase.</p><h3>The Real-World Costs</h3><p>Your fitness watch says you’re “ready for a hard workout” using the same algorithm for everyone — ignoring that you’re in your luteal phase with elevated progesterone and compromised recovery. You push through, recover poorly, maybe get injured. You blame yourself, not the research gap.</p><p>This creates real consequences for women athletes:</p><ul><li><strong>Increased injury risk</strong> when training hard during luteal phase without adjusted recovery</li><li><strong>Chronic underperformance</strong> from following generic training plans that ignore hormonal fluctuations</li><li><strong>Burnout and frustration</strong> from not understanding why training feels harder some weeks</li></ul><p>At puberty, girls drop out of sports at twice the rate of boys — 51% quit by age 17. They hit puberty, their bodies start cycling, and training stops working like it used to. Instead of adapting training to hormonal reality, they’re told to push through or try harder. So they quit.</p><h3>The Technology Gap in Action</h3><p>The technology gap is stark. Most devices treat period tracking as a passive calendar in a separate tab. But cycle phase should inform every recovery score and training recommendation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D-oL8NdRLET1UpsOMc0OgQ.png" /></figure><p>This is like having a weather app that tracks temperature and humidity in separate tabs, but “How hot does it really feel?” only looks at temperature.</p><p>WHOOP’s advantage isn’t better designers — it’s that their VP of Research conducted the missing research herself. She had to generate the data (45,000+ cycles, published in Nature 2024) before her design team could build features that actually work. Other companies are waiting for someone else to do it.</p><h3>The Trillion-Dollar Blind Spot</h3><p>Even if the ethical argument doesn’t move you, the business case should.</p><p>McKinsey’s 2024 comprehensive analysis examined the economic impact of the women’s health gap across 180 countries. Their findings are staggering: closing this gap could boost the global economy by $1 trillion annually. This isn’t speculative — it’s based on concrete metrics including increased workforce participation, reduced healthcare costs, and improved productivity when women’s health is properly addressed.</p><p>Here’s what makes ignoring women particularly absurd from a business perspective:</p><ul><li>Women represent 51% of the population — the literal majority of potential users</li><li>We control 51% of personal wealth in the United States (an estimated $22 trillion)</li><li>We make 80% of healthcare decisions for our families</li><li>We purchase wearables, influence family purchases, drive consumer trends</li></ul><p>Yet entire industries design as if we’re an edge case.</p><p>When WHOOP invested in understanding women’s cycles, they didn’t just create better science. They captured a market that competitors literally couldn’t serve. They became the only major wearable where recovery scores actually adjust based on cycle phase. This isn’t charity; it’s capitalism. Every other company is leaving money on the table by designing for only half their potential market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*UPkJMQXZozQNxCtzG5C3zQ.png" /></figure><h3>A Plea for Change</h3><p>Emily Capodilupo argues we need a “Title IX for research” — dedicated funding to close the gender data gap in sports science. But this can’t wait for policy alone.</p><p><strong>To tech companies</strong>: Stop waiting for someone else to do the research. WHOOP has shown it’s possible and profitable. Invest in understanding how women’s bodies actually work. Your competitive advantage isn’t superior sensors or sleeker design — it’s serving the half of the population everyone else ignores.</p><p><strong>To researchers</strong>: We need you to push for inclusion, fight for funding, and stop accepting “standard” protocols that only study men. The 7.15% of research focusing on women isn’t just embarrassing — it’s scientifically indefensible.</p><p><strong>To designers</strong>: Push for integration, not isolation. Period tracking that actually changes recovery scores, not just sits in a separate tab. Stop treating women’s biology as an edge case or premium feature. When the UI fails to reflect users’ lived reality, they stop trusting the device, or worse, they stop trusting themselves.</p><h3>Conclusion</h3><p>This isn’t a niche problem affecting a small user segment. It’s a systematic research failure that impacts the majority of the global population.</p><p>When a woman’s device tells her she’s “ready to crush it” during her luteal phase — when her body needs recovery — we’re not just providing bad recommendations. We’re teaching her to distrust her own physiological signals. We’re contributing to the 51% dropout rate of girls from sport by age 17. We’re perpetuating the same system that has ignored women’s bodies in research for decades.</p><p>The solution isn’t complicated, but it requires commitment. Stop overlooking half the population. Stop designing for an imaginary user who doesn’t menstruate, doesn’t get pregnant, and responds to training exactly like a man.</p><p>Millions of women aren’t asking for pink bands or flower icons. We’re asking for products built on complete data, research that includes us, and technology that actually understands our bodies.</p><p>That should be the baseline, not the breakthrough.</p><p>— — — — — — — — — — — — — — —</p><p>*Update (October 24, 2025):** Since the initial compilation of this comparison, COROS has added menstrual cycle tracking to its platform as of October 2025. The “Menstrual Cycle Tracking” entry for COROS should now read “Yes” instead of “No”. However, the other cycle-based personalization features (Recovery Score Adjustment, Strain/Training Recommendations Adjustment, and Sleep Need Recommendations Adjustment) remain unavailable. This brings Coros in line with industry standards for basic menstrual tracking, though they still lag behind WHOOP in terms of comprehensive cycle-based training adjustments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=357e649994ed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/artcenter-graduate-interaction-design/the-data-crisis-how-ignoring-womens-health-data-fails-everyone-357e649994ed">The Data Crisis: How Ignoring Women’s Health Data Fails Everyone</a> was originally published in <a href="https://medium.com/artcenter-graduate-interaction-design">ArtCenter Graduate Interaction Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>