<?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 Rashi Jaiswal on Medium]]></title>
        <description><![CDATA[Stories by Rashi Jaiswal on Medium]]></description>
        <link>https://medium.com/@by.rashijaiswal?source=rss-fbebdf3ddbfa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xCIuUuSMkyeBWd4YLvBifQ.jpeg</url>
            <title>Stories by Rashi Jaiswal on Medium</title>
            <link>https://medium.com/@by.rashijaiswal?source=rss-fbebdf3ddbfa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 05:50:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@by.rashijaiswal/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[Activating the Progress Loop to Overcome Stagnancy in a Flat Team Structure]]></title>
            <link>https://medium.com/@by.rashijaiswal/activating-the-progress-loop-to-overcome-stagnancy-in-a-flat-team-structure-e424359ec6b0?source=rss-fbebdf3ddbfa------2</link>
            <guid isPermaLink="false">https://medium.com/p/e424359ec6b0</guid>
            <category><![CDATA[safe-team]]></category>
            <category><![CDATA[system]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[services]]></category>
            <dc:creator><![CDATA[Rashi Jaiswal]]></dc:creator>
            <pubDate>Sun, 02 Aug 2026 17:15:46 GMT</pubDate>
            <atom:updated>2026-08-02T17:15:46.748Z</atom:updated>
            <content:encoded><![CDATA[<p>Creative teams often choose flat structures because they promise freedom. That is, the space to make choices, express ideas openly, and work without hierarchy. However I soon realised that this freedom comes with its own contradictions. As suggested from Amy Edmondson (1999) notes, a team can be “psychologically safe” yet creatively held back. In these scenarios, team members usually fear challenging the current situation, which holds back innovation and leads to a comfortable standstill. Our team shows this clearly. We began as a self-managing group that successfully built a culture of respect, order, and safety. We have no miscommunications and are a team where people can disagree without ego and adapt to new ideas. But even within this supportive space, we found ourselves stuck in a comfortable pattern, tending to take safer options rather than taking the creative risks our work demanded. This is a typical problem that requires us to adapt: the problem was not technical that could be solved with a simple fix, but a deeply embedded cultural one that required us to change our own mindsets and behaviors.</p><p>This essay argues that for a flat team to avoid the inevitable pull of stagnancy, it must treat growth as a continuous design challenge. A team must be willing to diagnose its own weaknesses, design its own systems for accountability, and relentlessly iterate on them. Through a critical reflection on our process, from recognising the absence of a shared purpose to implementing tools that enabled progress (Figure 1), I put forward a new model for design leadership, one that moves beyond directing tasks and instead focuses on building the team’s capacity to constantly challenge itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0sSRGOy-JpM_J2tyTdwFlA.png" /><figcaption><strong>Figure 1. Progress Loop: </strong>A cycle from sensing to acting and learning, enabled <br>by honesty, limits, and rhythm to sustain progress.</figcaption></figure><h3>The Limits of a Safe Team</h3><p>Our team’s journey began with the realisation that our biggest strength, our culture of psychological safety (Edmondson, 1999) was also the source of our creative stagnancy. An early success in the in-class Marshmallow Challenge was the first sign of this contradiction within our team dynamic. We won the challenge easily, building a 56cm tower by having fun and collaborating seamlessly. But as Wujec’s (2010) talk suggests, this outcome said more about our ability to execute a clear task under pressure than our readiness to face real-world uncertainty. It reflected the success of capable students completing a well-defined challenge, rather than designers prepared to navigate the ambiguity of real projects.</p><p>This dynamic became undeniable when we settled with a “safe” digital solution for our main project. The idea was practical and achievable but it lacked ambition. It was only when our faculty challenged our proposal, pushing us to pursue a more difficult and impactful non-digital direction, that we were forced to confront our comfortable state. This external critique was needed. It was this exact challenge that ultimately led to our successful research experiment: a live, non-digital workshop designed to connect new students with their peers or seniors. The event was a clear success, confirmed by a participant who noted that ‘this didn’t feel like research.’ This feedback was the ultimate validation of our approach, proving that we had designed an experience that was not only valuable but also genuinely engaging. To understand why we were playing it safe, we turned to the “Culture Map” as a diagnostic tool.</p><p>The maps we drew showed a team culture defined by strong “Caring” and “Order,” but a significant disconnect with our desire for better “Results.” We had created an environment where our ‘System 1’ (Kahneman, 2011, pp. 19–25) instinct was to prioritise harmony, causing us to avoid the more effortful ‘System 2’ thinking required for true creative breakthroughs. We identified that our team was missing a unifying “Purpose” (Dan Pink, 2009). Without a compelling “why” to align our efforts, we were a team of talented individuals working harmoniously but without a shared direction. This was our first real breakthrough. It helped us see that while psychological safety is vital, it isn’t enough to spark innovation. Without a clear purpose to move us forward, safety can slip into comfort, and comfort into a closed system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4xFoKfxMxHXDWTC0WzJhvA.png" /><figcaption>Team Culture Map</figcaption></figure><h3>Designing Systems to Combat Stagnancy</h3><p>To combat this self-diagnosed stagnancy, we had to become the leaders we were missing. Our first experiment was the Meeting Board which acted as a progress loop. Recognising the risks of a leaderless structure, we built a system of rotating facilitators which distributed the responsibility for driving progress and gave every team member the direct, hands-on experience of guiding the group. The board’s “After this I will…” section created an additional layer holding each of us accountable, making it clear to the team who was responsible for which tasks and ensuring that momentum was maintained from week to week. This board was not just a tool for organisation, it was a system we designed to ensure that shared leadership was a daily practice, not just another concept.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bPFeASiiWlEmqb1G25utaA.png" /><figcaption>Meeting Board: Tool that acted as a Progress Loop</figcaption></figure><p>The impact of this new system is clearly visible in the iterations of our Retrospective Maps. Our first retrospective (R1) was primarily focused on establishing basic trust and functional meeting rules. By our second retrospective (R2), the conversation had matured dramatically. We were now actively challenging our own desire for harmony, a classic symptom of “groupthink,” a concept introduced by Irving Janis and discussed by Kretchmar (2018) as a major barrier to effective decision-making. Instead of avoiding difficult topics, we began to intentionally practice the principles of productive disagreement (Dhar, 2018). The focus of our discussions shifted from logistics to ambitious creative goals, such as how to create an “emotional impact” and improve our “storytelling.” This shift shows how a flat team like ours can break out of stagnation, but only if it is willing to build the tools to force itself to do so.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QpzvF6NJRokFsuRvJH898w.png" /><figcaption>Foundations to Creative Push: Findings from Retrospectives 1 and 2​</figcaption></figure><h3>How Collective Systems Unlock Individual Potential</h3><p>What truly showed our system’s success was how it helped each person grow, not just the team as a whole. Our team’s journey of iterating on our self-awareness tools perfectly illustrates this process of learning through trial and error. We began with the standard “Manual of Me,” a useful tool for establishing a baseline of understanding each other. However, we soon found it to be quite limited, as it relied only on self-perception and did not create a mechanism for growth. As our first experiment to solve this, I designed the Catalyst Card, hoping it would spark deeper reflection. However, when we tested it, the team’s feedback revealed its fundamental flaw. The questions were too ambiguous (“How do you define change?”), and as my teammates noted, it “didn’t give us a way to grow.” This failure was a crucial learning moment. It taught us that a tool for growth must do more than just prompt introspection, it needs to create a system for external feedback.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9-dDTs1f0hdKBynIjtcbBg.png" /><figcaption>The Catalyst Card</figcaption></figure><p>This insight led to our second experiment, the “Johari Window with a Twist,” adapted from Luft and Ingham’s classic model (Chapman, 2009), to create the dynamic feedback loop our team had been missing. It moved my personal challenges with focus from a “blind spot” to the “open area” aligning with Tasha Eurich’s (2020) work on the power of self awareness. But this created a new, more difficult problem, how do you ensure that awareness translates into action? It was the shared responsibility of the team members to push each other to act on the feedback that we had received. This experience proves that individual growth requires not just personal reflection, but a commitment to collective accountability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hP4zquKm1hCPDq5Xnt_Ozw.jpeg" /><figcaption>Visualisation of a Team Growth and Development Plan <br>through an adaptation of the Johari Window</figcaption></figure><p>This two-part process, awareness followed by accountability is what created the upward spiral of growth that kept our team in a state of “flow” (Csikszentmihalyi, 1990). Our shared values and respect for each other’s time created the foundation, but it was this continuous loop of diagnosing problems, building small tools, getting feedback, and holding each other accountable that kept the project moving forward and prevented us from falling back into stagnation. It proves that growth is not a straight line, but a dynamic and iterative process that must be actively designed and maintained (Figure 2).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UpsavIjDzKl3fVnPzhRLlg.png" /><figcaption><strong>Figure 2.</strong> Nonlinear Creative Trajectory with Targeted Interventions.</figcaption></figure><h3>Redefining Leadership: The Guide for Growth</h3><p>Our collective journey of designing our own growth fundamentally reshaped my definition of leadership. In a modern creative team, a leader is not a director, but a system designer. The development of our “BoldStorm” tool is perhaps the most sophisticated example of this principle in action. Recognising our tendency to play it safe, we designed a system of anonymous ideation specifically to lower the fear of judgment and encourage creative risk-taking. We proactively built a system to reinforce psychological safety (Edmondson, 1999) precisely at the moment it was most needed. The idea for our successful non-digital workshop, a dynamic session of open mic, speed-dating and guided conversations that connected new and senior students was born directly out of this tool. We didn’t wait for a leader to tell us to do better, we built the tool that would guide us there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TP0mmJWSbqdRdjuMw4PvRw.png" /><figcaption>Boldstorm (1/2): Using the Template to Build Ideas</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VhgRgGdP3N6f2ec1e9Od8w.jpeg" /><figcaption>Boldstorm (2/2): Evaluating Ideas by Impact and Feasibility</figcaption></figure><p>This experience leads me to my new model of leadership. In a flat structure, the leader’s primary role is not to direct tasks, but to constantly design and refine the systems that allow the team to guide itself. This is the essence of a constant growth leader, one who understands that tools and processes must evolve with the team. They empower growth by empowering the team to diagnose its own challenges and build its own tools to overcome them. This leader recognises that a healthy team culture isn’t defined by the absence of problems, but by the team’s capacity and trust to address them together. They combat stagnancy by creating a process for continuous improvement, ensuring the team itself becomes the engine of its own success.</p><h3>Conclusion</h3><p>In conclusion, our team’s experience demonstrates that growth is not a natural outcome of a flat structure, but a fragile state that must be continuously and deliberately designed. We started by diagnosing our comfortable patterns with the Culture Map, and through trial and error, from the flawed Catalyst Card to the successful Johari Window we learned that a team must constantly create and challenge its own systems to avoid falling back into stagnation.</p><p>This changes how we think about leadership in a flat structure. Leadership is not just a personal quality, but a design challenge. Self-management is therefore not a passive, leaderless state, but the active and ongoing work of building and iterating on the very systems that guide a team’s performance. Every tool we created is modular, they can be adapted, combined, and extended to suit the needs of any team, allowing growth to be continuous and context-specific.</p><p>The future of design leadership does not lie in directing from the front, but in designing from within, creating the conditions that allow a team to constantly challenge itself. As Peter Drucker once said, “The best way to predict the future is to create it.” In a flat team, leaders do not simply direct, they design the environment that enables the team itself to create, adapt, and thrive.</p><h3>Bibliography</h3><p>Csikszentmihalyi, M. (1990) <em>Flow: The Psychology of Optimal Experience</em>. New York: Harper &amp; Row.</p><p>Dhar, J. (2018) <em>How to disagree productively and find common ground</em>. [TED Talk]. Available at: <a href="https://www.ted.com/talks/julia_dhar_how_to_disagree_productively_and_find_common_ground">https://www.ted.com/talks/julia_dhar_how_to_disagree_productively_and_find_common_ground</a> (Accessed: 4 November 2025).</p><p>Edmondson, A. (1999) ‘Psychological safety and learning behavior in work teams’, <em>Administrative Science Quarterly</em>, 44(2), pp. 350–383. Available at:</p><p><a href="http://www.jstor.org/stable/2666999">http://www.jstor.org/stable/2666999</a> (Accessed: 8 November 2025).</p><p>Eurich, T. (2020) ‘You Aren’t Actually Self-Aware’, <em>The Science of Success</em>, 20 May. [Podcast]. Available at: <a href="https://www.successpodcast.com/show-notes/2020/5/20/you-arent-actually-self-aware-with-tasha-eurich">https://www.successpodcast.com/show-notes/2020/5/20/you-arent-actually-self-aware-with-tasha-eurich</a> (Accessed: 4 November 2025).​</p><p>Kretchmar, J. (2018) <em>Groupthink</em>. [Online]. Available at: <a href="https://www.ebsco.com/research-starters/social-sciences-and-humanities/groupthink">https://www.ebsco.com/research-starters/social-sciences-and-humanities/groupthink</a> (Accessed: 5 November 2025).</p><p>Chapman, A. (2009) <em>Johari Window Model</em> [Moodle]. Available at: UAL Moodle site (Accessed: 8 November 2025).</p><p>Pink, D. (2009)<em> The puzzle of motivation</em> [TED Talk] July. Available at: <a href="https://www.ted.com/talks/dan_pink_the_puzzle_of_motivation">https://www.ted.com/talks/dan_pink_the_puzzle_of_motivation</a> (Accessed: 8 November 2025).</p><p>Wujec, T. (2010) <em>Build a tower, build a team</em> [Online Video]. Available at:</p><p><a href="https://www.youtube.com/watch?v=H0_yKBitO8M">https://www.youtube.com/watch?v=H0_yKBitO8M</a> (Accessed: 8 November 2025).</p><p>Kahneman, D. (2011) <em>Thinking, Fast and Slow</em>. New York: Farrar, Straus and Giroux.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e424359ec6b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[05: What If You Lost Your Job Over a Link?]]></title>
            <link>https://medium.com/@by.rashijaiswal/05-what-if-you-lost-your-job-over-a-link-b43ed4a9f819?source=rss-fbebdf3ddbfa------2</link>
            <guid isPermaLink="false">https://medium.com/p/b43ed4a9f819</guid>
            <dc:creator><![CDATA[Rashi Jaiswal]]></dc:creator>
            <pubDate>Mon, 01 Jun 2026 09:39:28 GMT</pubDate>
            <atom:updated>2026-06-01T09:39:28.685Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Most people have no idea what the real consequences of a security mistake look like. What happens when you show them?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yOaZiKIkWDC2iYuw6nE8Gw.jpeg" /></figure><p>I spoke to someone who works on the security side at a large organisation recently. She described how security incidents are rated internally on a scale of one to five. Small things, a suspicious link flagged quickly, a spam email reported, sit at the low end. Above three, the conversation changes. Above three, dismissal becomes a likely outcome. Repeat offenders at any level face financial penalties on top of formal warnings.</p><p>I asked how many people in the organisation know this scale exists.</p><p>She paused. Not many, she said.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c3H1_bXC3TnNMQA67_a2sg.png" /></figure><p>That gap between what the organisation knows and what employees know is, to me, a design problem. Not a communication failure in the sense of sending the wrong email. A deeper failure in how the system was built. The stakes are real. The people inside the system do not know what the stakes are. And nobody designed a way to bridge that.</p><h3>What interviews cannot tell you</h3><p>Here is the problem with asking people how they would respond to a security incident. They have never been in one. So they answer the way they think they should answer, or the way they imagine they would feel, which is usually quite different from how they would actually feel in the moment. The question is too abstract. The answer is too clean.</p><p>My faculty suggested a different approach. Instead of asking people to imagine a scenario, put them inside it. Print the dismissal letter. Hand it to them. Tell them: you clicked a link, the company lost a significant amount, this is what happened next. Now, what do you wish had gone differently?</p><p>That shift, from imagining to experiencing, changes what comes out. People stop performing an answer. They start feeling their way through something real. And the things they say in that moment, what support they wished they had, what communication would have helped, what they did not understand that they should have, are the things that actually matter for design.</p><blockquote>“If you put them into that mindset, what they will say is very different from what they say when you just ask.”</blockquote><h3>Why this is a research method, not a design method</h3><p>I want to be clear about what this is. It is not a prototype. It is not a design intervention. It is a way of doing research by using designed artefacts, a letter, a storyboard, a scenario, to access something that a survey or interview cannot reach. Sanders and Stappers (2008) describe this kind of approach as design-led research, using the tools of design not to produce an output but to unlock insight. The artefact is a probe, not a solution.</p><p>The question it is trying to answer is not what went wrong. It is what good would have looked like. What would that person have needed, at each moment before and after the incident, to have felt informed, supported, and not simply punished? That is the design question. And I cannot get to it by asking people in the abstract. I need to put them in the room.</p><p>This is the next phase of the research. Storyboards, scenarios, possibly a physical letter. Not to scare anyone, but to make something that has always felt distant feel real enough to respond to honestly.</p><p>Because the scale of one to five exists. Most people just have no idea.</p><h4>Annotated Bibliography</h4><ol><li><strong>Sanders, E.B.N. and Stappers, P.J. (2008) ‘Co-creation and the new landscapes of design’, <em>CoDesign</em>, 4(1), pp. 5–18. </strong><a href="https://doi.org/10.1080/15710880701875068"><strong>https://doi.org/10.1080/15710880701875068</strong></a></li></ol><p><strong><em>Context:</em></strong> A foundational paper in participatory and co-design research. Sanders and Stappers argue that design is shifting from designers solving problems for people to designers working with people to understand and shape their own experiences. They introduce the idea of design-led research, where design tools like prototypes, scenarios and artefacts are used not to produce a final output but to generate insight during the research phase.</p><p><strong><em>Relevance to my project: </em></strong>Gives academic grounding to the speculative co-design method being used in this project. Printing a dismissal letter and placing it in front of a participant is not a design solution. It is a research probe, using a designed artefact to access emotional and experiential responses that a standard interview cannot reach. Sanders and Stappers provide the theoretical basis for why this approach is legitimate and what it can reveal.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b43ed4a9f819" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[04: If It’s Everyone’s Problem, It’s No One’s Problem]]></title>
            <link>https://medium.com/@by.rashijaiswal/04-if-its-everyone-s-problem-it-s-no-one-s-problem-59163649eea0?source=rss-fbebdf3ddbfa------2</link>
            <guid isPermaLink="false">https://medium.com/p/59163649eea0</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <category><![CDATA[human-centered-security]]></category>
            <dc:creator><![CDATA[Rashi Jaiswal]]></dc:creator>
            <pubDate>Sat, 30 May 2026 14:16:51 GMT</pubDate>
            <atom:updated>2026-05-30T14:23:51.958Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Everyone agrees security is important. So why does it keep slipping to the bottom of everyone’s list?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vICgU3NYNBCnXRSiKKT93g.jpeg" /></figure><p>One thing I keep hearing from people I speak to is that awareness is not entirely the problem, but it is also not the solution. Most people know the basics. They have sat through the trainings, they have watched the videos, they understand at some level that cybersecurity matters. The issue is that this knowledge does not stay active. It does not come up in team meetings unless something has gone wrong. It is not part of the casual conversations people have at work. Security lives in a corner of your brain marked &quot;important&quot; and then mostly stays there, undisturbed, until the next training cycle brings it briefly back to the surface.</p><p>A senior people operations leader at Ericsson said it clearly.</p><blockquote>“People are aware. They have done the trainings. But is that retention constant? Are people still talking about it on a regular Tuesday?”</blockquote><p>The honest answer, for alot of people in most organisations, is no.</p><h3><strong>The interesting part</strong></h3><p>This is not a criticism of the people I spoke to. The people operations leader at Ericsson is one of the most security-aware people I have talked to in this research. She described the risk ratings, the consequences, the scale of data Ericsson holds globally. She takes it seriously. The point she was making is more subtle than “people do not care.” People do care. Security is just not a conversation that happens organically outside of the teams responsible for it.</p><p>My faculty put it in a way that has stayed with me. She said:</p><blockquote>“if the problem is everyone’s problem, it becomes no one’s problem. It turns into a pointing fingers game.”</blockquote><p>She was speaking from her own experience in the industry. She talked about her own priority list as a head of design, one to twenty. Her junior designers’ progression was on it. Creating job opportunities was on it. Climate, sustainability, security? Important, yes. But not in the top twenty. And she said: should I feel guilty about that? She genuinely was not sure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LPEopUSEUJLTfWJh_I2-EQ.png" /><figcaption>Security Awareness throughout everyday work</figcaption></figure><p>That honesty is more useful to this research than any amount of corporate messaging about shared responsibility. It names the real dynamic. When something belongs to everyone equally, it is very easy for it to quietly slip down everyone’s list at the same time.</p><h3><strong>So what kind of design problem is this exactly</strong></h3><p>When I say this might be a design problem, I mean something quite specific. Security mostly shows up in two moments. First, during scheduled training, once or twice a year, in a context that feels removed from actual work. Second, when something goes wrong, in the form of a warning or an incident. Neither of those moments seems designed to keep security present in the rhythm of normal working life.</p><p>There is very little ambient reinforcement. No equivalent of a team meeting where someone mentions a quarterly target and it stays in your head for the week. Security knowledge gets deposited, and then, at least from what I have observed so far, there is not much designed to keep it circulating.</p><p>Whitten and Tygar (1999) made an observation that still feels relevant: if security gets in the way of what people are trying to do, they will work around it. The implication, perhaps, is that security needs to be designed into the moments that already exist rather than added as a separate task on top of everything else.</p><p>I am still exploring this idea, but I keep coming back to the possibility that the challenge is not simply one of knowledge or willingness. It might be about what happens after awareness is created. If security is only visible during training sessions and incidents, perhaps the real gap is the absence of mechanisms that keep it present in everyday work. Whether that is the problem, or only part of it, is something I am still trying to understand.</p><h4>Annotated Bibliography</h4><ol><li><strong>Whitten, A. and Tygar, J.D. (1999) ‘Why Johnny can’t encrypt: a usability evaluation of PGP 5.0&#39;, in <em>Proceedings of the 8th USENIX Security Symposium. </em>Washington, D.C.: USENIX, pp. 169–184.</strong></li></ol><p><strong><em>Context: </em></strong>One of the most cited papers in security research. Whitten and Tygar tested whether ordinary people could actually use PGP, an email encryption tool, and found that most couldn’t. Not because they weren’t trying, but because the software was designed for experts. The title became shorthand for a bigger idea: that making something technically secure is not the same as making it usable. <em><br></em><strong><em>Relevance to my project: </em></strong>This paper established early on that security fails when it ignores the people using it. That argument still holds twenty-five years later, and this project builds directly on it. The gap between what security teams design and what everyday staff can actually act on is the same problem, just at a larger organisational scale.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59163649eea0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[03: The Cake in the Car]]></title>
            <link>https://medium.com/@by.rashijaiswal/03-the-cake-in-the-car-89dfe82d2a35?source=rss-fbebdf3ddbfa------2</link>
            <guid isPermaLink="false">https://medium.com/p/89dfe82d2a35</guid>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[awareness]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[engagenemt]]></category>
            <dc:creator><![CDATA[Rashi Jaiswal]]></dc:creator>
            <pubDate>Thu, 28 May 2026 21:07:46 GMT</pubDate>
            <atom:updated>2026-05-30T14:20:13.163Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Ericsson made a Netflix-style heist film about cybersecurity. 60,000 employees watched it in 48 hours. And then, slowly, people forgot.</em></p><p>I had a conversation this week with a senior HR leader at Ericsson who has been at the company for nearly twelve years. She knows the security systems, the policies, the culture. She is exactly the kind of person the training is supposed to reach.</p><p>She told me she almost fell for a phishing email recently. Not a badly designed one. A LinkedIn message with one extra “n” in the URL. That was it. One letter. She caught it, but only just. She said: “I could not tell. It looked identical.”</p><p>Someone with twelve years of experience and genuine security awareness, nearly fooled by a single character. That tells you something about where the threat level actually is right now. It also tells you something about why designing for awareness alone is not enough.</p><h3><strong>The film</strong></h3><p>She told me about something Ericsson does that she genuinely admired. A few years ago, they commissioned a creative agency called Harleys to produce a cybersecurity training film. Not a slideshow. Not a compliance video. A proper short film, a 20-minute heist thriller, shot cinematically, with real characters, a real story, and genuine tension. They called it The Hack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JGjggAOFr7ww10vkfVufGg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7nO-O5TlGMyPepsNn25pRw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/1*2Iz5f0JuF595EtLaUjiDgQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6wBZkPOIFa5R2q3EWV3v-Q.png" /><figcaption>Ericsson’s cybersecurity training film: The Hack</figcaption></figure><p>60,000 Ericsson employees watched it within the first 48 hours of release. Some watched it more than once, which, as the security team noted, is essentially unheard of for compliance training. Feedback from employees included things like “gave me full hack-series-on-Netflix vibes” and “best Ericsson training content I have seen yet.” A sequel was commissioned off the back of it.</p><p>By every measurable standard, it worked. People watched it. They talked about it. They paid attention.</p><p>And then, she said, they slowly forgot.</p><h3><strong>The cake in the car</strong></h3><p>She explained it with an analogy I have not been able to stop thinking about. When you put a cake on the passenger seat of your car, you drive more carefully. You are suddenly aware of something fragile and valuable right next to you, and your behaviour changes. The cake makes an abstract risk feel immediate and real.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ys0wYL7CK-YWMeykqqq8RQ.png" /></figure><p>That is what The Hack does. It puts the cake in the car. For a while, people think differently. They talk about it at lunch. They notice the next suspicious email. The awareness spike is real.</p><p>But then you arrive, you take the cake inside, and you go back to driving the way you always did.</p><p>The film creates a conversation for the moment. People recognise the scenarios, feel the relevance, laugh about it together. And then the moment passes and the system goes back to being what it always was: something that exists in the background, managed by someone else, until something goes wrong.</p><h3><strong>What this means for my project</strong></h3><p>There is something important here that goes beyond “make training more engaging.” Ericsson did make training more engaging. It worked brilliantly on its own terms. The problem is not the quality of the intervention. The problem is that a single well-designed moment cannot hold up a system that was not built around sustained engagement.</p><p>Behavioural science has a name for this. The Ebbinghaus Forgetting Curve shows that people forget roughly 70% of new information within 24 hours and up to 90% within a month without reinforcement (Sigurðsson, 2026). A film, however good, watched once a year, is working against how memory and habit actually form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2djpYFiXfHCnu9hh6YU25w.png" /><figcaption>The Ebbinghaus Forgetting Curve</figcaption></figure><p>She mentioned wanting to run something similar with her team every quarter. That instinct is right, but it is also revealing. The desire to repeat it is coming from one person who cares, not from a system designed to sustain it.</p><p>She also described how Ericsson has gamified smaller moments. Reporting a spam email gives you a star, a little confetti animation, a brief sense of having done something. She described a colleague who became genuinely enthusiastic about it, treating each report like a small achievement. That is a simple, well-designed feedback loop. It works because it gives people a moment of positive reinforcement inside a system that usually only shows up to issue warnings.</p><p>Both of these things, the film and the star, are doing something most security design does not bother with. They are designing for the feeling of being part of something, not just the obligation to comply. That is the right instinct. The question my project keeps returning to is: how do you build that into the whole system, not just the moments someone thought to make special?</p><blockquote>“Many employees commented that they took the training multiple times, which is unheard of within the compliance training space.”</blockquote><blockquote>- Erin Swoverland, Security Competence Manager, Ericsson (Harleys, 2023)</blockquote><p>The cake gets you to drive carefully. But what you actually need is a road designed so that careful driving is the natural, default thing to do. Not a response to something exceptional sitting on the seat next to you.</p><p>That is the design problem.</p><h4>Annotated Bibliography</h4><ol><li><strong>Sigurðsson, R. (2026) ‘Cybersecurity culture in 2026: building resilience beyond compliance’, <em>AwareGO Blog</em>, 27 March. Available at: </strong><a href="https://awarego.com/cybersecurity-culture-in-2026-building-resilience-beyond-compliance/"><strong>https://awarego.com/cybersecurity-culture-in-2026-building-resilience-beyond-compliance/</strong></a><strong> (Accessed: May 2026).</strong></li></ol><p><strong><em>Context:</em></strong> A recent industry article arguing that annual security training does not work. It uses the Ebbinghaus Forgetting Curve to show that people forget most of what they learn within 24 hours without reinforcement. Written by a security awareness company, so best read alongside academic sources.<br><strong><em>Relevance to my project: </em></strong>Backs up the core argument in this project that awareness is not the problem, retention is. Used to explain why even a well-made training film like Ericsson’s The Hack fades over time. Supports the idea that security needs to show up regularly in people’s working lives, not just once a year.</p><p><strong>2. Harleys (2023) <em>The Hack: Ericsson</em>. Available at: </strong><a href="https://harleys.agency/work/the-hack/"><strong>https://harleys.agency/work/the-hack/</strong></a><strong> (Accessed: May 2026).</strong></p><p></p><p></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89dfe82d2a35" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[02: Security Has a Trust Problem]]></title>
            <link>https://medium.com/@by.rashijaiswal/02-security-has-a-trust-problem-8064090f1d35?source=rss-fbebdf3ddbfa------2</link>
            <guid isPermaLink="false">https://medium.com/p/8064090f1d35</guid>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[blame-culture]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Rashi Jaiswal]]></dc:creator>
            <pubDate>Tue, 26 May 2026 17:35:37 GMT</pubDate>
            <atom:updated>2026-05-30T14:23:10.651Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Something I kept reading that reframed the whole problem for me and why “just communicate better” isn’t the answer.</em></p><p>The more I read about cybersecurity culture, the more one thing kept coming up: blame. Specifically, the way organisations respond when something goes wrong, a phishing link gets clicked, a patch doesn’t get applied, a vulnerability slips through. The question that gets asked first is almost always who did this, not why did our system make this so easy to get wrong.</p><p>What I hadn’t fully thought about until recently is that the blame runs in both directions.</p><p>Security teams blame staff for being careless, for ignoring emails, for using unapproved tools. Staff blame security teams for sending incomprehensible messages, for making every system feel like a test they’re about to fail, for showing up only when something goes wrong. Both groups have built up a quiet resentment of the other. And sitting in between them is a communication breakdown that neither side feels responsible for fixing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oWTApS8O730fYQzIv8X-Tg.jpeg" /><figcaption>Stakeholder Tension Map</figcaption></figure><p>A 2022 Gigamon survey found that 94% of IT and security leaders believe blame culture actively deters people from reporting incidents quickly (IT Security Guru, 2023). Think about that for a second. The very culture that’s supposed to protect organisations is making them slower to respond when something actually happens because people are scared of what comes next if they speak up.</p><p>That’s not a technical failure. That’s a design failure. A system that punishes honest mistakes doesn’t produce careful people. It produces silent ones. And silence in security is its own kind of vulnerability.</p><blockquote>“A no-blame culture is your fastest detection tool. If an employee is afraid of being fired for clicking a link, they’ll hide it. That silence gives attackers days or weeks of undetected access.”</blockquote><p>What struck me reading this is how much it maps onto service design thinking. When a user consistently does the wrong thing in a system, the instinct is to blame the user. But in service design, that’s actually a signal, it means the system wasn’t designed clearly enough to make the right thing obvious. The error is a symptom. The design is the cause.</p><p>Cybersecurity has spent decades treating human error as the problem to be managed rather than the feedback to be listened to. Every ignored email, every clicked phishing link, every unapproved AI tool someone quietly adopted because the approved ones were too clunky — these are people trying to do their jobs in a system that wasn’t built for them.</p><p>They’re not the problem. They’re the data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mgeZZBVgAwZEb9K_-Ri2Fw.jpeg" /><figcaption>Traditional Security Thinking vs Service Design Thinking</figcaption></figure><p>This changes what good looks like for my project. It’s not just about making security emails clearer, though that matters. It’s about redesigning the relationship between security teams and the people they’re trying to protect. Right now that relationship is built on suspicion and compliance. It needs to be built on something closer to trust.</p><p>That’s a much harder design problem. But it’s the right one.</p><p>Uchendu et al. (2021) found that developing genuine security culture requires addressing the relationship between security professionals and the rest of the organisation as a starting point not a byproduct. I keep coming back to that framing. Culture isn’t a campaign. It’s what the system produces when nobody is looking.</p><h4><strong>Annotated Bibliography</strong></h4><ol><li><strong>IT Security Guru (2023) ‘Blame culture: an organisation’s ticking time bomb’, <em>IT Security Guru</em>, 6 September. Available at: </strong><a href="https://www.itsecurityguru.org/2023/09/06/blame-culture-an-organisations-ticking-time-bomb/"><strong>https://www.itsecurityguru.org/2023/09/06/blame-culture-an-organisations-ticking-time-bomb/</strong></a></li></ol><p><strong><em>Context:</em></strong> An industry article looking at how blame culture affects security in organisations. It draws on a 2022 Gigamon survey finding that 94% of IT and security leaders believe blame culture stops people from reporting incidents quickly. When employees are scared of consequences, they hide mistakes instead of flagging them.<br><strong><em>Relevance to my project: </em></strong>To support the argument that silence is its own security risk. When people are afraid to speak up, attackers get more time undetected. Supports the project’s position that culture and trust are design problems, not just management problems.</p><p><strong>2. Uchendu, B., Nurse, J.R.C., Bada, M. and Furnell, S. (2021) ‘Developing a cyber security culture: current practices and future needs’,<em> Computers &amp; Security</em>, 109, 102387. </strong><a href="https://doi.org/10.1016/j.cose.2021.102387"><strong>https://doi.org/10.1016/j.cose.2021.102387</strong></a></p><p><strong><em>Context:</em></strong> A peer reviewed academic paper reviewing how organisations currently build security culture and where they fall short. Most approaches focus on tools and compliance rather than the relationship between security teams and everyone else, which is often built on distrust.<br><strong><em>Relevance to my project: </em></strong>Gives academic grounding to the observation that security teams and non-technical staff frequently distrust each other, and that no training programme alone can fix that. Security communication is a relational problem, not just a content problem.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8064090f1d35" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[01: The Security Email Nobody Reads]]></title>
            <link>https://medium.com/@by.rashijaiswal/01-the-security-email-nobody-reads-61bbd96be9b4?source=rss-fbebdf3ddbfa------2</link>
            <guid isPermaLink="false">https://medium.com/p/61bbd96be9b4</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[technical-design]]></category>
            <category><![CDATA[inclusive-design]]></category>
            <dc:creator><![CDATA[Rashi Jaiswal]]></dc:creator>
            <pubDate>Wed, 20 May 2026 14:27:43 GMT</pubDate>
            <atom:updated>2026-05-30T14:27:10.890Z</atom:updated>
            <content:encoded><![CDATA[<p><em>On finding a design problem hiding inside a technical system and the moment I knew I had a thesis.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6aork516YF9JSc81xiQUQw.webp" /></figure><p>I’m Rashi, a service designer with a background in communication design, currently doing my masters at UAL. I’ve always been interested in the space where technology meets people, especially the moments where a system works perfectly on paper but completely fails for the person using it.</p><p>Cybersecurity was never really on my radar until a conversation with my dad. He mentioned how serious it was becoming. Not in a technical way, but more like this is everywhere now, attacks are increasing, and organisations still seem unprepared. We ended up talking about breaches, ransomware, and how fast threats move compared to how slowly organisations respond.</p><p>Somewhere in that conversation, something clicked for me.</p><p>This isn’t only a technology problem. It’s also a communication problem. A design problem. And nobody seemed to be talking about it that way.</p><p>So I started researching it properly. Pretty quickly, I asked someone if they could show me a security email from their workplace. Just a screenshot. I wanted to see what these messages actually looked like. They paused and said they had deleted it.</p><p>“Nobody keeps that stuff.” I’ve been thinking about that response ever since.</p><p>This person isn’t careless. They’re busy. Like most people at work, they receive hundreds of messages every day and have learned to filter out what feels unimportant. The security email didn’t survive that filter. Not because they don’t care about security, but because nothing about the message felt relevant to them.</p><p>That was the moment this project really started for me. Not with a statistic or a policy gap, but with that one sentence.</p><p>I’ve always been interested in how information moves between people. The same message can completely change depending on how it’s written, timed, or framed. Once I started looking at cybersecurity through that lens, I couldn’t stop seeing the design problems inside it.</p><p>Organisations spend huge amounts of money building systems to detect security risks. The technology itself is impressive. But once a vulnerability is found, it enters a human system. Someone has to communicate it, explain it, prioritise it, and act on it. Usually across teams with very different levels of technical understanding. And that human system was never really designed. It just grew over time.</p><p>The result is predictable.</p><p>Security analysts deal with thousands of alerts every day, many of which turn out to be false positives. Non-technical staff receive security messages they don’t understand and slowly learn to ignore them. Organisations continue running annual awareness training that checks a compliance box but changes very little about people’s behaviour.</p><p>As Verizon’s 2024 Data Breach Investigations Report put it: “Most training treats security awareness as a knowledge problem when it’s actually a behavioural challenge.”</p><p>My project is called Human-Centred Vulnerability Management, and it’s my MA thesis at UAL. I’m working with Ericsson as a primary research partner, alongside people in other larger organisations.</p><blockquote>The question I’m exploring is simple: How do you design security communication so it actually works for the people inside an organisation, regardless of their technical background, age, or ability?</blockquote><p>I’ll be writing here throughout the project. Not polished summaries of research papers, but the conversations, observations, and moments that are shaping the work as it develops.</p><h4>Annotated Bibliography</h4><ol><li><strong>Verizon (2024) <em>Data Breach Investigations Report 2024.</em> Available at: </strong><a href="https://www.verizon.com/business/resources/reports/dbir/(Accessed:"><strong>https://www.verizon.com/business/resources/reports/dbir/(Accessed:</strong></a><strong> 20 May 2026).</strong></li></ol><p><strong><em>Context: </em></strong>An annual industry report analysing thousands of confirmed data breaches globally. The 2024 edition covers the most common attack types, how breaches happen, and the role of human error. One of the most widely cited sources in cybersecurity, produced from a large dataset across multiple sectors and regions.<br><strong><em>Relevance to my project: </em></strong>Provides hard evidence that human factors drive the majority of breaches. Supports the argument that organisations keep treating security as a technical problem when the data consistently points elsewhere.</p><p><strong>2. Vassilev, A. et al. (2025) ‘Alert fatigue in security operations centres: research challenges and opportunities’, <em>ACM Computing Surveys.</em> </strong><a href="https://doi.org/10.1145/3723158"><strong>https://doi.org/10.1145/3723158</strong></a></p><p><strong><em>Context:</em></strong> A peer reviewed academic survey of alert fatigue in Security Operations Centres. It looks at why analysts get overwhelmed by the volume of security alerts, most of which turn out to be false positives, and what that does to their ability to catch real threats. Published in a leading ACM journal.<br><strong><em>Relevance to my project: </em></strong>Gives academic grounding to the analyst side of the problem. When security professionals are drowning in noise, the human cost is burnout and missed threats. Shows that the design problem exists at both ends, for the people sending security communications and the people supposed to be catching the threats in the first place.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61bbd96be9b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Starts a Conversation. The Question is Which One.]]></title>
            <link>https://medium.com/@by.rashijaiswal/design-starts-a-conversation-the-question-is-which-one-7a624ec3da5a?source=rss-fbebdf3ddbfa------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a624ec3da5a</guid>
            <category><![CDATA[feminist-design]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[speculative-design]]></category>
            <category><![CDATA[design-research]]></category>
            <category><![CDATA[future-of-work]]></category>
            <dc:creator><![CDATA[Rashi Jaiswal]]></dc:creator>
            <pubDate>Wed, 13 May 2026 14:22:59 GMT</pubDate>
            <atom:updated>2026-05-13T14:22:59.089Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Someone picks up a piece of paper during a testing session. It is a CV, but not quite like any CV they have seen before. Underneath the job titles and dates, there is a section called Life Period. It lists Primary Carer, March 2034 to ongoing. Attached to the back is a Voice Verified Reference Letter from a neighbour, based on what they have seen of this person over time.</em></p><p><em>The person holding it goes quiet for a moment. Then they say: “This felt real. Like something that is so human, because it’s not a random reference from an industry or an institution, but from someone who’s a part of your life.”</em></p><p><em>This is what this blog is about.</em></p><p><em>Not the policy framework we built around it. Not the legislation we imagined that made it possible. Not even the feminist theory that gave us the language to understand why it mattered. Just a person, holding a piece of paper from a speculative future, feeling something real. And me, watching, thinking that this is what design is for.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gesscozA32cC5m2MRVu9xw.jpeg" /><figcaption>The Life CV and Voice Verified Reference Letter</figcaption></figure><h3>01: Where I’m Coming From</h3><p>This blog is a reflection on a project my team and I made as part of the Design Futures unit on the MA Service Design course at the University of the Arts London. The unit asks students to use speculative design and a methodology called Critical Service Design to build fictional future worlds that start real conversations. We worked in teams to imagine a world set in 2036, then made artefacts from that world, objects, screens and documents that people could hold, read, and react to, and tested them with real people to see what conversations they opened up.</p><p>I came into service design through communication and branding. Before this MA, my work was about how things are presented, how messages land, how a brand makes you feel before you even read a word. I loved it. But looking back, what I actually loved was the storytelling underneath it. The way a well designed piece of communication could make someone feel seen, or make them laugh, or make them stop and think about something they had not thought about before.</p><p>I consider myself a social person. Conversations are how I think. I am the one who will talk to strangers on public transport, who will stay an extra hour at a dinner because the discussion got interesting, who notices when a room goes quiet after something unexpected is said. I am fascinated by the moment a conversation suddenly feels important.</p><p>What I did not fully understand, until this project, was that design can do exactly that. That a speculative object, placed in front of someone, can open up a conversation that would never otherwise have happened. Not because it gives them an answer, but because it makes them feel something they did not know they were carrying.</p><p>There is a phrase that has stayed with me: “Art should comfort the disturbed and disturb the comfortable.” Martins (2014, p.2) argues that speculative and critical design should use artefacts to provoke “insightful analyses of the profound impact that designed objects have on our lives.” That is a precise description of what happened in our testing sessions. The artefacts we made were not solutions. They were provocations.</p><p>But here is where this project pushed me further than branding ever did. Branding tells people what to feel. Speculative design does something harder and more interesting. It creates a situation in which people discover what they already feel, but have never been given space to voice. Ahmed (2017, p.1) describes feminism as “loud acts of refusal and rebellion as well as the quiet ways we might have of not holding on to things that diminish us.” I think that is also a description of what good design can do. It can help people stop feeling small.</p><h3>02: The Question We Couldn’t Ignore</h3><p>From the start, one question shaped the direction of our project: what if human qualities were valued more in an AI-driven world in 2036? It sounds straightforward. It is not.</p><p>Our horizon scanning, the process of looking at current trends and signals to understand what futures might be plausible, told us that 83 million existing roles will be displaced by AI by 2027, while 69 million new ones will be created (World Economic Forum, 2025). The care economy is one of the fastest growing sectors. Skills rooted in human interaction, including empathy, active listening and reasoning, currently show no substitute potential. The National Institute of Standards and Technology has identified that qualifications and credentials no longer show employers what someone is actually capable of. This suggests that the things that make us human are becoming economically valuable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VUQv3XgU7cDoJe-jREPaaQ.jpeg" /><figcaption>Horizon Scanning and Evidence Safari</figcaption></figure><p>The feminist question underneath all of this is, who is this valuable to, on whose terms, and at whose expense?</p><p>Care work has always been feminised. It has always been invisible. It has always been unpaid or underpaid. The women who spent years raising children, caring for elderly parents, supporting disabled family members, built skills in the process such as crisis management, patience, adaptability, the ability to take care of someone else’s needs while managing your own. And for decades, those skills did not exist on a CV. They were seen as a gap and something people felt they had to apologise for.</p><p>What happens when the system finally recognises that? What happens when empathy becomes a credential?</p><p>Our project, The Human Dividend, imagines a future where qualities like empathy, care, judgement, and presence are formally valued in an AI-supported world. But it also explores what happens when those qualities become measurable and commodified. By 2036, you can buy a HUMN drink at Boots for £80 before a VR assessment. The currency has changed, but who can afford it has not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/1*nv39sGbIPY-aPM7QLReX9A.jpeg" /><figcaption>HUMN drinks on the shelf at Boots, 2036</figcaption></figure><p>Costanza-Chock (2020) defines design justice as a way of understanding how design affects different groups of people, including who benefits, who is excluded, and whether design reinforces or challenges existing systems of power. Our project was an attempt to make that visible through fiction. To show that a system built with good intentions and genuine feminist intent, can still reproduce inequality if it does not question the existing structures it is built on.</p><p>Fry (2009) argues that most design limits the futures of people who are already disadvantaged by supporting systems that mainly benefit those in power. A feminist futures project instead tries to reopen those possibilities. We were trying to do that, but we eventually realised how difficult it really is. Without a feminist lens, this project would have asked how to value human skills in the future. With it, we had to ask whose skills, whose definition of value, and who the system still excludes even when it claims to include everyone. The lens did not just change the content of what we built. It changed the questions we were allowed to start from.</p><p>This project started more narrowly. We began focused specifically on women returning to work. Through research and conversation, we widened the lens to include anyone with a non-linear career path, whether because of illness, migration, care work, or personal circumstances. That felt more inclusive. But it also raised a question I kept returning to. In broadening the focus, did we risk softening the feminist edge? Care work is not gender-neutral. The people who carry it are disproportionately women, and disproportionately women of colour. Widening the frame can genuinely create inclusion. It can also be a way of avoiding the specific. I do not have a clean answer to that. I think it is more valuable to recognise that tension than to pretend it has been solved.</p><h3>03: Building the World</h3><p>Research through Design is a methodology where the act of making something, a prototype, an object, a scenario, is itself the research. You do not fully understand what you think until you have built it. Koskinen et al. (2013) describe this as “making as enquiry.” You learn through doing rather than before it. This unit asked us to work that way, and it changed how I understand what design is actually for.</p><p>Before building any artefacts, we built the world’s history. Working backwards from 2036, we mapped a legislative timeline from 2026 onwards: AI hiring scandals in 2028 that triggered the Algorithmic Hiring Transparency Act, the Care Experience Recognition Act in 2030, the Human Qualities Employment Act in 2034. Each reform was a genuine response to a real injustice. Each one also created new inequality. This process of backcasting, imagining what sequence of events would make a future world plausible, shaped everything we made. It meant our artefacts were not floating in an abstract future. They were rooted in a specific history that had its own logic.</p><p>Kirby (2010) defines diegetic prototypes as objects from fictional worlds that make new ideas feel believable because they are shown being used in everyday life. We borrowed this idea and applied it to building an entire fictional world. The point is not to build something that works in the real world. It is to build something that feels like it could.</p><p>Everything we made was designed to sit inside a familiar container. The Guardian still runs on a broadsheet. Boots still sells wellness products. Cambridge still issues GCE certificates. What has changed is what is inside those containers. Humanics Ed sits alongside Machine Learning as an A-level subject. The Life CV has a Life Period section. These shifts feel close rather than distant because the setting around them is recognisable.</p><p>Candy and Kornet (2019) call this making futures tangible and experiential. You cannot just describe a future. You have to put something in someone’s hands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k0gol9fTixZUGwODGLONYA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uJkzonCBec_LSnjlPxnSRA.jpeg" /><figcaption>Newspapers from 2036, The Guardian and The Sun</figcaption></figure><p>The newspapers came first because they set the world. The Guardian asked: “Hiring Has Changed. But Has It Changed for Everyone?” The Sun asked: “Are Human Qualities Even Real Anymore?” giving two different viewpoints on the same system. One focused on policy and legal debates while the other on public anxiety.</p><p>The Life CV and witness letter became the heart of the project. Emily Smith. Primary Carer since March 2034. The Reference Letter was voice-verified, QR coded, and signed by hand. Not from an institution, but from a neighbour. That was the design decision we were most proud of. We made the verification community based rather than professional, so the human side of the reference could not be reduced to data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UZQZlaxFMfKDxr0_0woTaw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AohK-6YOLVEdBLJHsgUvzg.jpeg" /><figcaption>A Life CV and a Voice-Verified Reference Letter from a Neighbour, 2036</figcaption></figure><p>Then came the HUMN drink. £80 and sold at Boots. Designed to help people feel more emotionally ready before assessment. Not far-fetched and completely predictable. Once human qualities can be measured, they can be turned into products. The only question is who can afford them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dcSjcZfGA6KwUlx7ITnpDQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1phX9uw5SbJ8RXiTWXeKFQ.jpeg" /><figcaption>HUMN drink and training programme poster</figcaption></figure><p>Salinas, Yarrow and Lagedamont (2024) describe Critical Service Design as an approach that uses fictional services and artefacts to explore how policies and systems might work in alternative futures. The four stages are reframing, horizon scanning, materialising alternatives, and show and tell. The materialising stage is where the project became real. Building the artefacts before the arguments were fully resolved forced decisions that theoretical framing avoided. That is the clearest description of Research through Design I found in practice. The argument arrives through the object, not before it.</p><p>One honest note about what did not work. Our initial world was too smooth. Our partners at PILAA, an EDI organisation focused on return to work challenges, pushed us harder on this. They told us that confidence bias in re-entry processes means women with care gaps consistently undersell the skills those years built, and that systems designed to recognise care experience can still penalise the people least likely to perform well in a biometric assessment. Neurodiverse candidates, trauma survivors, people whose natural emotional responses fall outside what the system reads as “appropriate” would still be excluded. We added those tensions into the newspapers, but there is more to do. A baseline that reduces physiological bias does not remove it. The system we built is still shaped around a norm. We asked whose norm it is, but did not fully answer it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SmeFx-G5x3jwpYyxsNr0SA.jpeg" /><figcaption>Machine Learning and Humanics Ed, A 2036 A-Level Certificate</figcaption></figure><h3>04: Watching It Land</h3><p>I spent a lot of time in the user-facing part of this work, talking directly with people as they encountered the world we had built. You are not defending the concept. You are listening to it land. You notice the gap between what was intended and what people actually take from it, and that gap becomes part of the design itself.</p><p>The Life CV moment I described at the start is the one I keep returning to. But there were others. When people went through the hiring process screens and received the constructive rejection email, the response was not what I expected. They did not respond to the goodness of the system. They responded to the feeling of being addressed as a person. “Knowing where I could improve at the end of the process leaves me with a forward direction and nothing is lost,” one person said. What they wanted, more than a fair system, was to be seen within it. Even in failure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dTvZleSmrF8o5kN0pOfnGA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rlE_HoFoqhJGsNgmdzqZlQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C36nYtw1T8VsqYq6r8LdWw.png" /><figcaption>The DreamWave VR briefing sheet, the full hiring journey, and a testing session</figcaption></figure><p>Freire (1968) writes that problem posing education does not support systems of oppression, because those systems cannot allow people to start asking “why?” Our prototypes did this in practice. They did not give people answers instead they placed people in situations where their own questions became unavoidable. The Life CV did not tell the person interacting that their care experience had value. It showed them a world where someone had already thought to write it down. For some people, that was enough to surface years of feeling like they had been apologising for something that was never a failure.</p><p>The HUMN drink produced a different kind of response. Someone said: “HUMN drink bottles sitting next to vitamins in Boots was the moment it felt real and wrong at the same time. Are human skill boosts only for the rich?”. That sentence is better than anything we wrote in our theoretical framing. It names the exact problem. The system has replaced credential inflation with emotional inflation.</p><p>The gaming response was also revealing: “Hidden CV text, VR preparation coaching, faking care experience, using connections to get answers. So all systems can be gamed?” What stood out was not the cynicism, but how quickly it came. People moved straight from seeing the system to thinking about how to work around it. That is not a failure of the design. It reflects how people actually respond to institutional power.</p><p>Gerber (2021) argues that prefiguration begins with recognising that the values of the current system are not working. The people in our testing sessions understood that immediately. They did not need us to explain it to them.</p><p>But there was also a clear gap in our process. Most of the people we tested with were students, faculty, and working professionals within a similar setting. Costanza-Chock (2020, p.25) insists that meaningful participation in design requires “the full inclusion of, accountability to, and control by people with direct lived experience of the conditions designers claim they are trying to change.” The people most affected by broken hiring systems, invisible care work, and the inaccessibility of emotional optimisation were largely not included in our testing. That is not a small gap. It shapes whether a project is genuinely feminist in practice or only feminist in theory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QA5XBMD35_UwaqXcShM3ZA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M_kG-G4_YMrePWgIbSaX1w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yzVgsa-tI-0mGiS7Q77q_g.jpeg" /><figcaption>Prototype Testing in Practice</figcaption></figure><h3>05: What This Changed for Me</h3><p>My comfort zone in this project was obvious to me: storytelling, idea generation, being present with people’s responses, noticing the moment something lands. What was not comfortable was sitting with a world that does not resolve.</p><p>The training I came from, branding and communication design, is fundamentally about clarity. You work until the message is clean, until the feeling is right, until the thing communicates what you want it to communicate. This project asked me to do something different. To leave the friction visible. To build a world that raises questions it does not answer. To resist the instinct to fix.</p><p>Gerber (2021, p.60) identifies the tendencies that professional designers carry, “Designers prioritise the production of tangible artifacts in defined project timeframes, while other activists are more likely to focus on building skills and relationships over long periods of time.” I recognised myself in that. I wanted to make things well and feel like we had done something. The slower work, the work of staying in the question, was harder for me.</p><p>Ahmed (2017) describes living a feminist life as working out what we are against and what we are for. This also describes our design process. You need to know what you are against before you can build something meaningful. We were against the invisibility of care work, systems that reward existing advantage, and how recognition can quickly become something that can be bought. We were for creating space for conversations that usually do not happen. We were for moments where someone holds a document and realises their experience has always had value.</p><p>The difficult question raised by Gerber (2021) is whether professional design, which comes from institutions and industrial systems, can really imagine and build something different. Or whether it just repeats what it says it is challenging, only with better presentation. I do not think we fully resolved that. I think the HUMN drink exists in our world partly because we were trained to make things feel real and desirable, and we applied those skills to something that is both desirable and troubling. We made it feel too real, and that might be the most honest thing we did.</p><h3>06: What It Made Impossible to Ignore</h3><p>If every system can be worked around, and every measure creates new ways to cheat, and even emotional qualities can be turned into something to compete over, then what is design actually for?</p><p>I keep coming back to the moment someone held the Voice Verified Reference Letter. It was not the result of a policy framework or a legislative timeline or a theory about future systems. It came from someone in the community writing a personal reference, based on what they had seen over time. How someone shows up, how they treat others, how they care. And then someone else reading it and feeling, maybe for the first time, that the years they spent doing that kind of work had been seen and valued.</p><p>The Life CV is not a solution to gender inequality in hiring. The Human Dividend does not fix the care economy. What it did was make a certain conversation unavoidable. It put something in the room that made people feel personally implicated rather than academically interested.</p><p>I came into this unit thinking design was about making things clearer. I am leaving it thinking design is about making certain things impossible to ignore. Which is a different ambition. It is harder and less satisfying in the short term. It does not give you the clean feeling of having solved something. But it gives you the room where the real conversation can start.</p><h3>References</h3><p>Ahmed, S. (2017)<em> Living a feminist life.</em> Durham: Duke University Press.</p><p>Candy, S. and Kornet, K. (2019) ‘Turning Foresight Inside Out: An Introduction to Ethnographic Experiential Futures’, <em>Journal of Futures Studies,</em> pp. 3–22. Available at: <a href="https://doi.org/10.6531/JFS.201903_23(3).0002">https://doi.org/10.6531/JFS.201903_23(3).0002</a></p><p>Costanza-Chock, S. (2020) <em>Design Justice: Community-Led Practices to Build the Worlds We Need.</em> Cambridge, MA: The MIT Press.</p><p>Freire, P. (2000) <em>Pedagogy of the Oppressed.</em> Translated by M.B. Ramos. 30th Anniversary Edition. New York: Continuum. (Originally published 1968)</p><p>Fry, T. (2009) <em>Design Futuring: Sustainability, Ethics and New Practice.</em> Oxford: Berg.</p><p>Gerber, A. (2021) ‘Prefigurative Politics and Design’, in Pivot 2021 <em>Conference Proceedings.</em> OCAD University, 22–23 July, pp. 57–63. Available at: <a href="https://doi.org/10.21606/pluriversal.2021.0005">https://doi.org/10.21606/pluriversal.2021.0005</a></p><p>Kirby, D. (2010) ‘The Future is Now: Diegetic Prototypes and the Role of Popular Films in Generating Real-world Technological Development’, <em>Social Studies of Science, </em>pp. 41–70. Available at: <a href="https://doi.org/10.1177/0306312709338325">https://doi.org/10.1177/0306312709338325</a></p><p>Koskinen, I., Zimmerman, J., Binder, T., Redstrom, J. and Wensveen, S. (2013) <em>Design Research Through Practice: From the Lab, Field, and Showroom.</em> Waltham, MA: Morgan Kaufmann.</p><p>Martins, L.P. de O. (2014) ‘Privilege and oppression: towards a feminist speculative design’, in Lim, Y., Niedderer, K., Redström, J., Stolterman, E. and Valtonen, A. (eds.) <em>Design’s Big Debates — DRS International Conference 2014</em>, 16–19 June, Umeå, Sweden. Available at: <a href="https://dl.designresearchsociety.org/drs-conference-papers/drs2014/researchpapers/75">https://dl.designresearchsociety.org/drs-conference-papers/drs2014/researchpapers/75</a></p><p>Salinas, L., Yarrow, L. and Lagedamont, M. (2024) ‘Critical Service Design for Government Innovation’, in Gray, C., Ciliotta Chehade, E., Hekkert, P., Forlano, L., Ciuccarelli, P. and Lloyd, P. (eds.) <em>DRS2024: Boston</em>, 23–28 June, Boston, USA. Available at: <a href="https://doi.org/10.21606/drs.2024.532">https://doi.org/10.21606/drs.2024.532</a></p><p>World Economic Forum (2025) <em>The Future of Jobs Report 2025</em>. Geneva: World Economic Forum. Available at: <a href="https://www.weforum.org/reports/the-future-of-jobs-report-2025">https://www.weforum.org/reports/the-future-of-jobs-report-2025</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a624ec3da5a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>