<?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 Saitej Pisupati on Medium]]></title>
        <description><![CDATA[Stories by Saitej Pisupati on Medium]]></description>
        <link>https://medium.com/@saitej-pisupati?source=rss-ee30cb1dc79------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*PiwdjCSLIj-imbs5rmCt8A.jpeg</url>
            <title>Stories by Saitej Pisupati on Medium</title>
            <link>https://medium.com/@saitej-pisupati?source=rss-ee30cb1dc79------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 18:38:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@saitej-pisupati/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[Fear of anything new]]></title>
            <link>https://medium.com/@saitej-pisupati/fear-of-anything-new-1846aa2dbcdc?source=rss-ee30cb1dc79------2</link>
            <guid isPermaLink="false">https://medium.com/p/1846aa2dbcdc</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[organizational-behavior]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Saitej Pisupati]]></dc:creator>
            <pubDate>Thu, 10 Jul 2025 13:48:30 GMT</pubDate>
            <atom:updated>2025-08-04T12:36:35.347Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EOQ4LPquEu1LuJxh0Lkj7A.jpeg" /><figcaption>Innovation thrives when individuals bring the right mindset, teams practice the right rituals, and systems support the right processes.</figcaption></figure><p>Most organisations say they want innovation, but few are truly built for it. Not the type that lives in R&amp;D labs or digital sprints, but the kind that quietly transforms how everyday work gets done. This kind of innovation doesn’t require a lab coat or a PhD. It asks something harder: <strong>the courage to see differently and act on it.</strong></p><p>It starts when someone, in any role, notices something that isn’t working and dares to imagine a better way.</p><p>Sometimes that sounds like:<br><strong> “What if we did this differently?”<br> “Is there a simpler way to do this?”<br> “What’s the real need underneath this?”<br> “Could we turn this problem into an opportunity?”<br> “What’s possible if we stopped assuming this is the only way?”</strong></p><p>But here’s the broader frame: despite the hype and investment around Innovations, many never launch. <strong>According to a 2020 Kaspersky survey, 95% of innovation projects fail before launch, often due to poor planning, governance, or security blockers.</strong> It’s not because people lack ideas or ambition it’s because the environments they operate in often punish exploration rather than promote it.</p><p>This kind of innovation isn’t always loud. It’s quietly sparked by curiosity, grounded in daily work, and powered by a desire to make things better. It’s not about radical invention, it’s about fresh perspectives, better questions, and small shifts that ripple outward.</p><p>In a post-pandemic world, where remote and hybrid work are now the norm, collaboration, risk-taking, and idea-sharing have become even harder. When you’re not in the room, signalling curiosity or dissent takes more effort and more trust.</p><p>So the question isn’t just “How do we get more ideas?”, it’s: “How do we build environments where new ideas can survive?”</p><p>That’s why innovation isn’t just about new ideas — it’s about the <strong>right conditions for them to grow</strong>. It starts with the <strong>mindset of individuals</strong>, is reinforced by the <strong>rituals teams practise together</strong>, and sustained by the <strong>processes and systems that guide how work gets done</strong>. When a culture rewards compliance over curiosity or perfection over progress, even the best ideas quietly wither.</p><p>Some organisations have found their way. Take Toyota, for instance. For over 70 years, it has run a Creative Idea Suggestion System, encouraging employees to note small problems in their daily work and propose improvements. In 2023 alone, over 810,000 suggestions were submitted — about 14 per employee — proving that small, consistent innovation is possible when the system is designed for it.</p><p>This isn’t just a corporate policy. It’s a way of thinking built into the Toyota Production System (TPS), which is rooted in two core principles: continuous improvement (Kaizen) and respect for people. It encourages employees at all levels to actively spot inefficiencies and contribute to solutions, transforming every individual into a potential innovator. TPS is not a set of tools — it’s a culture of disciplined, everyday problem-solving.</p><p>One former Toyota supervisor, Oyaji Kawai, captured the spirit of this beautifully:</p><p><em>“When you’re young, you can’t make big improvements. But changing the position of a trash can so you don’t have to walk around it is also an improvement. Supervisors need to take such suggestions seriously, too. Otherwise, that person will not make another. I’ve hardly ever said no. Instead, I encourage them — ‘That sounds great! Let’s try it and see what happens!’”</em></p><p>This mindset, that every small idea matters is what makes the system thrive.</p><p>Sam Altman said in a recent U.S. Senate hearing, “I don’t do it for the money. I do it for the love of it.” That’s not just a founder’s sentiment, it’s a culture signal. Discomfort is normalised. Risk is embraced. Learning is faster than fear.</p><p>Together, Toyota and OpenAI show two ends of the same truth: innovation thrives when the environment makes it safe and worthwhile to try. That mindset of purpose over fear, exploration over control is what legacy organisations often lack. And without it, no budget or strategy deck can save an idea from dying in silence.</p><p>I saw this firsthand as an Ideation Coach in the Innovation Management team at a major British energy company. I worked with employees to shape and elevate their ideas but often, the real work was upstream: helping people feel safe enough to think differently in the first place. Through coaching, research, and interviews, I uncovered deeper forces: Fear of being wrong. Learned compliance. Reluctance to challenge authority.</p><p>These weren’t personal flaws, they were cultural patterns, reinforced by systems and leadership signals.</p><p>To better understand these forces, I began mapping them across four interconnected levels: the individual, the team, the system, and the organisation.</p><blockquote><strong>The individual level:</strong> fear, self-doubt, or learned helplessness.</blockquote><blockquote><strong>The team level:</strong> groupthink, status dynamics, or lack of psychological safety.</blockquote><blockquote><strong>The system level: </strong>misaligned incentives, rigid workflows, or opaque evaluation processes.</blockquote><blockquote><strong>The organisational level:</strong> cultural inertia, inconsistent leadership signals, and a lack of strategic clarity.</blockquote><p>Because innovation doesn’t happen in isolation, it’s shaped by everything that surrounds it.</p><h3>1. Individual: The Inner Psychology of Risk</h3><p>People want to contribute to offer ideas, challenge norms, and help things move forward. But often, what holds them back isn’t skill or ambition, it’s psychological friction. Fear and fatigue can feel small in isolation, but together, they create a culture of hesitation.</p><ul><li><strong>Fear of failure: The need for psychological safety</strong></li></ul><p>When mistakes are treated as weakness, not growth, people learn to protect themselves.</p><p><em>“So, by not celebrating failures, people are scared to kind of put up their hand and say it, you know that we didn’t do this right? It’s because failure is a failure. It’s not a learning sharing opportunity. Do we reward that?”</em></p><p>Behind this fear is a very human need: to be safe while taking risks. If trying something new feels like stepping into judgment — or worse, humiliation — silence becomes self-preservation. Innovation can’t breathe in environments where being wrong is punished.</p><ul><li><strong>Mental bandwidth: The need for space to imagine</strong></li></ul><p>Creativity isn’t just about motivation, it’s about capacity.</p><p><em>“Everyone works so hard in the organisation. Everyone is trying to do the right thing and what they need to do. Therefore, it’s easy for things like innovation to move to back of mind and not be prioritized.”</em></p><p>Even the most committed people hit a wall. If you’re constantly reacting, there’s no room to reflect. Innovation requires a pause, a breath, before new patterns can emerge. When organisations run lean, that mental space disappears.</p><p>It’s not that people don’t care. They’re just tired.</p><ul><li><strong>Why We Resist Innovation Isn’t Just a Culture Problem, It is also a Brain Problem</strong></li></ul><p>Behavioural science shows that resistance to innovation isn’t rooted in laziness or apathy, it’s rooted in how our brains are wired. Humans naturally avoid uncertainty, fear loss more than they value gain, and stick to familiar routines.</p><p>Cognitive biases like the certainty effect, loss aversion, negativity bias, and the sunk cost fallacy all conspire to keep us anchored in the known, even when it no longer serves us. Add low psychological safety or past negative experiences, and even the best ideas stay unspoken.</p><h3><strong>2. Team: Social Norms That Shape Safety</strong></h3><p>Every team has an invisible culture, a set of unspoken expectations that shapes what feels safe to say, suggest, or challenge. Even when innovation is encouraged in theory, subtle signals often tell a different story. What holds people back isn’t always the idea itself, it’s the social risk of sharing it too soon.</p><ul><li><strong>Lack of early validation = High social risk</strong></li></ul><p>In teams where feedback comes too late or not at all, people sit on ideas they’re unsure of, not because they don’t care, but because they don’t feel safe if their ideas are good enough. Without informal feedback loops those lightweight, everyday conversations ideas stall in silence. The cost of speaking up feels high when perfection is the expectation, or when people worry they’ll be seen as naive, off-track, or disruptive.</p><p><em>“Most of the times, the ideas submitted tries to answer the same problem. We should be able to understand the need that it’s solving and what value it brings to the customer. We lack having those conversations.”</em></p><p>Innovation doesn’t need a spotlight. It needs a circle, a trusted peer group where rough ideas can be shaped, tested, and improved without fear. These quiet needs to be seen, heard, and not judged are foundational. When they’re missing, innovation becomes an emotional gamble. When they’re met, creativity becomes collaboration.</p><ul><li><strong>Misaligned goals: The need for shared clarity on success</strong></li></ul><p>Even when teams are eager to innovate, unclear or misaligned success criteria slow them down.</p><p><em>“Innovation is only as good as the team’s mindset… and aligning on what success looks like is key…”</em></p><p>Without a shared understanding of value, teams struggle to prioritise or build momentum. Innovation thrives when everyone is aiming at the same target and trusts each other to co-create the path there.</p><h3><strong>3. System: Invisible Rules That Influence Behaviour</strong></h3><p>Most organisations don’t mean to block innovation. But the systems they build their KPIs, incentives, workflows, and review cycles quietly shape how people behave. And often, they send the wrong signals.</p><ul><li><strong>When innovation becomes performance, not play</strong></li></ul><p>Innovation thrives on exploration but many systems unintentionally turn it into a box to tick or a race to win.</p><p><em>“I think it’s important that it’s done in a way that people see it as an opportunity, as opposed to a tool to beat people with, or seen as more stick than carrot to improve their scores.”</em></p><p>When creativity is reduced to a metric, people stop experimenting and start performing. They optimise for safety, not originality. Real innovation needs space to fail, iterate, and grow long before it’s judged or scored.</p><ul><li><strong>The system people see is the one they trust</strong></li></ul><p>There’s often a gap between what leadership says and what the system actually rewards. Innovation may be praised in speeches but if promotions and praise go to those who manage risk rather than take it, the message is clear.</p><p><em>“You ask any leader whether they think creativity and imagination is important and they will say yes. But actually, it’s nowhere near as important as risk management or financial probity or all these other dull things.”</em></p><p>People watch what gets resourced. What gets protected. What gets celebrated. And when the system consistently prioritises caution over curiosity, innovation becomes a side-hustle not a shared priority.</p><h3><strong>4. Organisation: Leaders Shape the Limits</strong></h3><p>An organisation’s culture is a reflection of its leadership. What leaders consistently say, do, and celebrate becomes the invisible script others follow.</p><ul><li><strong>People take their cues from what leaders model not what they mandate</strong></li></ul><p>You can’t PowerPoint your way to a creative culture. When leaders talk about innovation but act with fear or rigidity, people notice.Carol Dweck’s research shows that leaders with a fixed mindset tend to value being right over getting it right. They avoid uncertainty, discourage dissent, and create blame-based environments stifling creativity before it starts.</p><p><em>“In a fixed mindset, leaders believe their talents are traits, and so mistakes expose them. In a growth mindset, mistakes are how they grow.”</em> — Carol S. Dweck, Mindset.</p><p>When leaders embrace learning over perfection, they make it safer for others to try, stumble, and grow.</p><ul><li><strong>Consistency builds trust and trust unlocks creativity</strong></li></ul><p>Great leaders close the gap between what they say and what they do. They reward thoughtful risk-taking. They admit their own mistakes. They create visible, repeatable rituals, retrospectives, open Q&amp;As, peer showcases, that normalise reflection and iteration.</p><p><em>“Leadership is not about being the smartest person in the room, it’s about making others feel smart enough to speak.” </em>— Simon Sinek</p><p>If leaders don’t make time, give attention, or offer encouragement for new thinking, innovation will always feel like a personal risk. But when they lead with curiosity, consistency, and courage, they create a culture where better ideas can rise and stick.</p><p>Culture is what leadership makes normal.</p><h3><strong>So, what can we do?</strong></h3><p>From the boardroom to the break room, innovation doesn’t begin with ideas — it begins with people.</p><p>And for innovation to truly thrive, we need alignment across every level: the <strong>right mindset</strong> in individuals, the <strong>right rituals</strong> in teams, and the <strong>right processes</strong> in systems.</p><p>Instead of simply urging people to “be more innovative,” we must <strong>design environments that reduce fear and build trust</strong>. That means rewarding small risks, making space for unpolished ideas, normalising open feedback, and visibly backing those who speak up.</p><p>Innovation doesn’t happen just because we ask for it. It happens when people feel <strong>safe enough to challenge the status quo</strong>, and <strong>supported enough to keep going — even when they fail</strong>.</p><p>In my experience as an ideation coach in a large energy company, one truth became crystal clear: <strong>Innovation isn’t about brilliant ideas alone.</strong><br>It’s about the <em>conditions</em> we create that allow those ideas to surface, grow, and thrive.</p><p>And those conditions?<br>They start with people, especially leaders, <strong>modeling the mindset, rituals, and systems</strong> that make creativity not just possible, but inevitable.</p><p>So how do we put this into action?</p><p>Start small — but start deliberately and consistently:</p><blockquote><strong>Make space for reflection:</strong> In your next team meeting, invite people to share one thing they’ve learned or one failure that taught them something.</blockquote><blockquote><strong>Encourage curiosity:</strong> Normalize questions like “What if we tried this differently?” even when you don’t have a clear answer yet.</blockquote><blockquote><strong>Create visibility:</strong> Set up a simple channel a shared board, a chat thread where raw ideas can be shared, explored, and supported.</blockquote><blockquote><strong>Celebrate effort, not just outcomes:</strong> Publicly recognize contributions to innovation, big or small. Motivation grows when effort is seen.</blockquote><blockquote><strong>Nurture the conditions:</strong> Regularly ask your team: “What’s helping your creativity? What’s getting in the way?” Then act on what you hear.</blockquote><p>Innovation isn’t a department or a deadline, it’s a way of working. A mindset. A culture.</p><p>When people feel safe enough to speak up, curious enough to explore, and supported enough to keep going, even when things don’t work, that’s when true innovation begins to take root.</p><blockquote>Because the real engine of innovation?</blockquote><blockquote>It’s not tech.</blockquote><blockquote>It’s not process.</blockquote><blockquote><strong>It’s people — supported by the right mindsets, team rituals, and system behaviours.</strong></blockquote><p>When we make space for curiosity, reward small experiments, and build trust into the culture innovation isn’t a buzzword.</p><p>It’s just how work gets done.</p><p><strong>Get those right, and the future doesn’t just happen. You invent it.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1846aa2dbcdc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding Earthlings]]></title>
            <link>https://medium.com/@saitej-pisupati/understanding-earthlings-c2c6084c5790?source=rss-ee30cb1dc79------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2c6084c5790</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[psycology]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[business-design]]></category>
            <category><![CDATA[user-centered-design]]></category>
            <dc:creator><![CDATA[Saitej Pisupati]]></dc:creator>
            <pubDate>Mon, 19 May 2025 07:42:27 GMT</pubDate>
            <atom:updated>2025-05-19T14:17:26.798Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lgbiiHCJqIH6nPj19-I5EA.jpeg" /></figure><p>When I meet someone new, I usually slide into the conversation with a rhythm that feels second nature. A few casual questions — <em>Where are you from? What kind of music do you like? Seen any good movies lately?</em> Back home, that’s all it takes. Find one shared film or artist, and suddenly, you’re quoting lines, laughing at the same jokes, and somehow already feel like old friends. It’s easy. Effortless. Like social muscle memory.</p><p>But everything changed when I moved to the UK.</p><p>I remember meeting someone who said they weren’t into movies at all. I blinked. Wait — <em>what do you mean, not into movies?</em> My go-to move was gone. I had no idea where to go from there. That moment — small as it was — cracked open a realization: I’d been relying on a very specific kind of connection, one shaped by my upbringing, my environment, and the people I’d always been surrounded by.</p><p>And to be honest, connection has never been my strongest suit. Even as a kid, I found it hard to bond with people. Not just the meeting them part, but all the invisible calculations running in the background: Where do we start? What do we even say? What would this person like? Which version of myself should I show? I never really knew. Forming a connection felt more like guesswork than intuition.</p><p>I didn’t come from a design background either. My journey into design started later, and I always believed that I learned best by watching people closely and learning directly from them. I was never the sit-down-and-read-the-manual type — I needed to be in the room, soaking things in, asking questions, mimicking what worked, and shaping it into my own style. So, when I entered the design world, I wandered. I moved between different teams, not just to participate, but to <em>study</em>. How did they talk to each other? How did they share ideas, give feedback, resolve tension? Every team became a new classroom.</p><p>Design taught me to put people at the center — to understand their needs, emotions, behaviors. The more I practiced user-centric thinking, the more I started seeing people differently. Slowly, I began to speak their lingo. I tuned into the way they communicated. I got better at connecting — not because I became more extroverted, but because I became more observant, more curious.</p><p>Still, nothing could’ve prepared me for London. Moving to one of the most culturally diverse cities in the world is like jumping from the minor leagues to the majors. You think you know how to work with people — until suddenly you’re surrounded by dozens of cultures, perspectives, and ways of thinking. The rules you grew up with? They don’t always apply here. You have to up your game.</p><p>My Master’s program was a crash course in exactly that. We had people from over 40 nationalities, 10 different professional backgrounds, a spread of ages and experiences. On paper, our project teams were dream teams. All-star lineups. But in practice? Not always. Some teams clicked. Others didn’t. Some projects soared, others struggled. And I couldn’t stop wondering — <em>why?</em></p><p>So I did what designers do best: I observed.</p><p>I watched how people worked together — how they gave feedback, how they disagreed, how they handled tension. Some classmates found my constant observing a bit much (fair enough), but I couldn’t help it. I wanted to understand what made some teams feel like magic and others feel like work.</p><p>The more I watched, the more I realized that connection isn’t just about communication — it’s about u<em>pbringing</em>. How we grew up. The way our families talked (or didn’t). The emotions we were allowed to express. The cultural rules we learned before we even knew they were rules. All of it shapes how we relate to others.</p><p>And when we enter diverse environments — whether it’s a new country or a global team — those invisible rules suddenly bump up against someone else’s invisible rules. That’s where the friction (and the opportunity) lies.</p><p>This realization became a turning point for me — not just in my work, but in how I move through the world.</p><p>Understanding people begins with understanding their upbringing, culture, experiences, environments, habits, beliefs, and motives. These aren’t just background details — they are the <em>context</em> behind every behavior, decision, and reaction. If we want to connect with someone on a meaningful level, we have to be willing to step into their world before expecting them to step into ours.</p><p><strong>This is where perspective and perception come into play.</strong></p><p><strong>Perception</strong> is how we interpret what we see, hear, or experience. It’s the lens shaped by our personal history. <strong>Perspective</strong>, on the other hand, is the mental position we take — it’s the viewpoint we choose based on what we know or believe.</p><p>Most of the time, we navigate the world through the lens of our own perception, built quietly over years through our culture, our home life, our education, and our emotional environment. But if we want to <em>understand</em> someone else — not just interact with them, but truly understand them — we have to be willing to set aside our own lens, even temporarily.</p><p>It’s not easy. Letting go of your own perceptions can feel like stepping into fog. But when you do, something powerful happens: you begin collecting new lenses. Every time you take in someone else’s point of view, you widen your emotional vocabulary, expand your empathy, and stretch your ability to navigate complexity.</p><p>Eventually, you don’t just see the world from your own perspective — you see it from many. And that changes everything.</p><p><strong>Our Early Years Shape Our Perception and Perspective</strong></p><p>To understand where perception and perspective <em>start</em>, we have to go back to childhood. The early years of our life are incredibly formative. These phases don’t just fill us with memories. They <em>program</em> us.</p><p><strong>Ages 0–7: The Absorbing Years</strong></p><p>This is often called the “sponge” stage. Children are highly impressionable, soaking up everything around them without much critical thinking. During this time, their brains are in a theta state — almost like a hypnotic trance — meaning they absorb language, behaviors, emotional cues, and belief systems directly from their caregivers and environment.</p><p>Whether it’s how their parents handle anger, how affection is shown, or whether it’s safe to speak up — these early patterns become their <em>baseline</em>. They form subconscious beliefs about the world: <em>Is it safe? Am I lovable? Do I have a voice?</em>These answers are rarely verbalized, but they’re deeply embedded in a child’s emotional system — and they continue to echo well into adulthood.</p><p><strong>Ages 7–13: The Questioning Years</strong></p><p>This is when children begin seeking structure. They start distinguishing between right and wrong, not just because they’re told to — but because they’re trying to <em>make sense</em> of how the world works. School, social groups, and family expectations become major influences. It’s a time of forming identity, often around fitting in or standing out.</p><p>Perceptions start to crystallize here. A child who’s encouraged to ask questions may grow up confident in their curiosity. One who’s constantly corrected may learn to self-censor. These aren’t fixed outcomes, but they shape our internal narratives — stories we tell ourselves about what’s allowed, what’s possible, and who we are.</p><p><strong>Ages 13–25: The Shaping Years</strong></p><p>Adolescence is where perception and perspective begin to diverge. Teenagers and young adults start questioning the beliefs they’ve inherited. This is a time of rebellion, experimentation, and deep searching. It’s also a time when the <em>prefrontal cortex</em> — the part of the brain responsible for planning, decision-making, and understanding consequences — is still developing.</p><p>During this period, people start constructing their <em>own</em> identity. They choose role models, adopt values, question authority, and test social norms. Cultural influences, education systems, and peer groups become just as (if not more) important than family. Exposure to new ideas — whether through books, travel, the internet, or relationships — can significantly shift perspective.</p><p>Over the past few decades, psychologist Carol Dweck’s research on <em>fixed</em> and <em>growth</em> mindsets has helped us understand how people respond to challenges, learning, and change. A <em>fixed mindset</em> assumes that our qualities — like intelligence, talent, or social skills — are static and unchangeable. In contrast, a <em>growth mindset</em> believes these qualities can be developed over time through effort, feedback, and learning. This shift in belief isn’t just theoretical; it has measurable effects. Studies have shown that people can change their long-held attitudes, habits, and even core beliefs by 30–40% with conscious effort and the right conditions. This capacity for transformation becomes especially relevant in complex team environments, where our preconceptions about others — based on past experiences, surface-level traits, or professional roles — can get in the way of genuine connection and collaboration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W2NsdvbpnvpzGDVvjbMhcA.jpeg" /><figcaption>A visual exploration of how thoughts, memories, emotions, and experiences interconnect to shape our perception and behavior.</figcaption></figure><p>I saw this play out in a team project during my Master’s. One of my teammates was a quiet, detail-oriented designer. At first, I assumed they weren’t very interested in the big-picture thinking or creative brainstorming we were doing — they just seemed slow to express themselves or needed more time to find the right words. But over time, I noticed how closely they observed everyone, often catching patterns and nuances the rest of us missed. When I finally asked for their perspective directly, they offered a completely fresh way of solving a problem we’d been stuck on. That moment made me realize how my own fixed mindset — formed by assumptions about their role and communication style — had narrowed my perception. This inspired me to be more observant and open, and to look beyond my initial impressions.</p><p>As we grow older, all these early influences — our cultures, families, education systems — start showing up in subtle but powerful ways. They shape how we speak, how we listen, how we show up in groups, and how we respond when things get uncomfortable. And when we step into diverse environments, all those invisible patterns start bumping up against each other. Suddenly, a simple conversation becomes layered with unspoken meaning. Misunderstandings happen not because people aren’t listening, but because they’re hearing through different filters.</p><p>Over time, I began to notice that this friction — and the potential for deeper connection — often shows up in three ways: the way we speak, the way we behave, and the way our education shapes how we think and express ourselves.</p><p><strong>1. Language Gaps:</strong> During my first Months in the UK, One of my friends and I were talking about the plans for the evening. She was telling me about how she has a date. And I was like who the guy and how did you meet. She was like no I meant with a friend. Date with a friend. Where I come from, when I’m going to meet a friend I usually say I’m meeting a friend. For me a date is reserved for someone I’m romantically interested in. That’s when I realised because we come from different countries where the first language is not always English. Our vocabulary and our usage of the words can be a bit different.</p><p><strong>“Words can mean different things to different people”</strong></p><p>This phrase highlights a crucial challenge. With team members from 40 countries, most have a first language other than English. While they may be fluent, it’s not their native tongue. This has a significant impact. Our native language forms the foundation for learning any subsequent language. For non-native English speakers, this means translating thoughts and meanings back and forth between their native language and English. This process can lead to misunderstandings because the root of learning differs for everyone. And also the way they learn the same language also differs. Nuances in meaning can shift as we rely on our native languages. Jokes that land hilariously in one language might fall flat in another (learnt that the hard way) and also can be misunderstood.</p><p><strong>2. Behaviours: </strong>In every team I’ve worked in, especially diverse ones, I’ve noticed something about myself: I’m often the most enthusiastic person in the room. I show up with high energy, speak with excitement, and when I share ideas, I tend to go all in — body, voice, everything. But more often than not, when I finish speaking, I’m met with blank stares. At first, I took this as confusion. Did I say something wrong? Was I unclear? So I’d repeat myself, reframe the idea, try again with different words, more examples, more energy — just to make sure people understood.</p><p>But over time, I started seeing a different pattern.</p><p>People weren’t necessarily confused. They were just… processing. Or maybe gathering their own thoughts. Or maybe just tired. My rhythm wasn’t their rhythm. And that was okay.</p><p>That realization taught me to look beyond words. To stop filling every silence. To read the room more carefully, and start understanding people through their behaviours — not just their responses. That quiet moment after I speak? It’s not rejection. Sometimes it’s reflection.</p><p>In any team, especially diverse ones, what people do often tells you more than what they say. Subtle behaviours — like who leans in when someone is speaking, who consistently hesitates before sharing, who interrupts and who gets interrupted — offer important signals about how comfortable or included someone feels. These cues are easy to miss when we focus only on what’s being said. But behaviours are a mirror of group dynamics: they reveal power imbalances, unspoken tensions, or even silent disengagement.</p><p>And here’s something I’ve learned the hard way: sometimes, people don’t say what they truly think — they say what they believe you want to hear. It’s a form of protection. A way to keep the peace. And if you’re not paying close attention, it’s easy to mistake politeness for agreement, or quietness for consent. But underneath that surface, there might be hesitation, disagreement, or even discomfort that never gets voiced.</p><p>For instance, a teammate who suddenly stops contributing might not be out of ideas — they might just feel unheard. Someone who always agrees could be avoiding conflict, not genuinely aligned. I’ve learned that these patterns aren’t always obvious, but they matter.</p><p>When we start tuning into body language, energy levels, turn-taking, and emotional shifts, we get a fuller picture of how a team is functioning. And when we notice what’s left unsaid, we begin to ask better questions, create space for those holding back, and build environments where everyone feels safe to participate.</p><p>It turns out, the most important things people are trying to say aren’t always spoken. You just have to know where to look — and how to listen between the lines.</p><p><strong>3. Different professions cultivate different mindsets: </strong>Education not only equips us with specialized knowledge but also shapes how we communicate and express ourselves.</p><p>An engineer, for instance, might favor clear, concise language, employing technical jargon and logical structures to present ideas. Their education emphasizes problem-solving, so their communication style often follows a similar approach, breaking down complex concepts into step-by-step explanations or utilizing data visualizations to convey information efficiently.</p><p>Doctors, on the other hand, hone their communication skills in a different way. Empathy and building rapport are crucial aspects of patient care, so their language leans towards clarity and approachability. They might explain medical conditions using analogies or metaphors tailored to the patient’s understanding, fostering trust and open communication.</p><p>Lawyers, meanwhile, develop a keen awareness of nuance and persuasive language. Their education emphasizes legal frameworks and constructing arguments, reflected in their communication style. They excel at presenting a clear and compelling case, using evidence and logic to build a strong narrative.</p><p>Finally, designers cultivate a unique visual language. Their education focuses on conveying ideas through aesthetics, user experience, and storytelling. They might express themselves through sketches, prototypes, and presentations that showcase not just the functionality of a design but also its emotional impact.<br> <br> In diverse teams, these layered differences — language, culture, personality, profession — don’t just sit in the background. They actively shape how ideas are shared, how conflict is handled, and how aligned (or misaligned) a group can feel. Which begs the real question: How do we bring people closer together, so their full input isn’t just invited, but actually felt and heard? How do we design for connection, not just collaboration?</p><blockquote><strong>How do we nurture an environment where individuals feel seen, valued, and inspired to contribute meaningfully?</strong></blockquote><blockquote><strong>Observation: </strong>Our brains are wired for efficiency. To save time and mental energy, we often rely on past experiences and assumptions to make sense of people quickly. But this shortcut has its downsides. When we operate on a fixed idea of who someone is, we often miss how their circumstances might have shifted — mentally, physically, or emotionally. Just because we see our colleagues every day doesn’t mean we truly know what they’re going through. Change can be subtle. It takes presence, empathy, and intentional observation to notice when someone’s having a rough day. And let’s be honest — some days, we don’t even have that energy ourselves. But as social beings, it’s in those exact moments that offering or receiving support becomes even more important.</blockquote><blockquote><strong>The details often reveal the truth.</strong></blockquote><blockquote>It might be a slouch in someone’s posture, a change in their tone of voice, or a word they suddenly stop using. Maybe a colleague who usually greets everyone loudly walks in quietly and heads straight to their desk. Or someone who’s always on time starts showing up late or leaving early. These aren’t just random behaviours — they’re signals. We just need to tune in. The way someone taps their foot during a meeting, how often they glance at their phone, how they respond when interrupted — these small physical details, mannerisms, and choice of words often tell us far more than their actual responses do. Observing these clues helps us meet people where they are, not where we assume them to be.</blockquote><blockquote><strong>Active Listening: </strong>Active listening is the practice of fully focusing on what someone is saying, <em>without</em> immediately planning your response. It’s listening to understand, not to reply. That means paying attention to not just words, but tone, emotion, body language, and what’s <em>not</em> being said. When we listen actively, we stop assuming that everyone means what we would mean if we said those words. Instead, we begin to ask questions like:What might this word mean in <em>their</em> world?What emotional tone are they carrying behind their sentence? What are they trying to express — even if the words aren’t quite right?</blockquote><blockquote>In multicultural environments, this kind of listening becomes a superpower. It helps teams move beyond surface-level understanding into deeper trust and connection. It also allows for more psychological safety — people feel more comfortable expressing themselves, even if they don’t have the “perfect” words. In fact, many of the challenges I saw in diverse teams weren’t due to disagreement or misalignment. They were due to people <em>thinking</em> they were misunderstood — or worse, <em>not heard at all. </em>And the solution wasn’t always clearer communication. Sometimes, it was simply better listening.</blockquote><blockquote><strong>Curiosity: </strong>We should always have a curious mindset about how people are responding to our words and the vocabulary they use as that might explain their thinking process. It explains what when and how people respond to certain topics. Which might give us an opportunity to help them to express themselves better. Words don’t mean the same to everyone. Even if you have the slightest hint that they mean something different ask them.</blockquote><blockquote><strong>Safe space of expression: </strong>Not everyone processes in real time. Some people need to reflect before they can respond. Others may have thoughts but lack the energy or confidence to share them in the moment. It’s frustrating when teams stall because someone isn’t speaking up — but it’s even more frustrating to be the person who wants to contribute but can’t find the words. We must always be alert to these dynamics. A simple gesture like offering extra time, looping someone back in, or checking in privately can make a huge difference.</blockquote><blockquote><strong>Consistency: </strong>Even if you build a dream team where everyone feels seen and heard, bad days will happen. Energy dips. People shut down. Old patterns return. This is where consistency matters. The practices of observation, curiosity, active listening, and emotional safety aren’t one-time fixes — they’re habits to sustain. They help us weather the lows and come back together stronger.</blockquote><p>These insights didn’t just help me become a better teammate — they deeply shaped how I approach user research. At its core, research isn’t just about gathering answers. It’s about knowing what to observe, when to probe, and how to make sense of the subtle human signals that don’t always make it into words. Over time, I began to realise that the same things that helped me connect with teammates — observation, attentiveness, pattern recognition, emotional attunement, and curiosity — are also the foundations of good research. When I sit down with someone for an interview or a usability test, I don’t just listen to what they say — I watch what they do. I pay attention to the pauses, the hesitations, the sidelong glances, the small shifts in tone or posture. These moments are rich with meaning. They tell you where the discomfort is, where the story goes deeper, and where people might not have the words to explain what they’re really feeling.</p><p>That’s why the ability to stay curious — to follow a thread even when it seems minor — is a powerful skill. I’ve found myself asking follow-up questions others might skip: <em>“You mentioned that seemed a bit frustrating — what part exactly felt off?”</em> or <em>“I noticed you paused there — was something confusing?”</em> These kinds of questions don’t come from a script. They come from being present, from noticing the friction points between what someone says and what they do. They come from resisting the urge to jump to conclusions and instead sitting with ambiguity a little longer. This mindset allows research to move beyond surface-level feedback into the deeper layers of people’s needs, motivations, and anxieties. It’s not just about asking <em>more</em> questions — it’s about asking <em>better</em> ones. And often, the best questions come from that moment of pause when you’re just… watching, feeling, sensing that there’s more to uncover.</p><p>In the end, what I’ve learned through all of this is simple, but not always easy: <strong><em>Be curious, not judgmental.</em></strong> This one line — often attributed to Walt Whitman, and made popular again by Ted Lasso — has become a quiet mantra in my work. Especially in diverse teams and research spaces, it reminds me to approach difference with openness rather than assumptions, and to see every interaction as a chance to learn something new about the people I’m designing for — or with.</p><blockquote>⚠️<strong> Warning: Consciously observing and being curious about people gives you powerful insight into who they are, what they do, and why they do certain things. But that information must be handled with care. It should be used only to guide and support — not to manipulate or mislead. Curiosity, when paired with empathy and ethics, creates understanding. Without those anchors, it becomes exploitation. If we want to build better teams, better systems, and better futures, then our observations must serve one goal: to help us work together better.</strong></blockquote><blockquote><strong>What Can You Do Tomorrow?</strong></blockquote><blockquote><strong>Listen Carefully</strong>: Pay closer attention to what others say, not just the words but the tone, body language, and emotions behind them. Try to understand their perspective, even if it’s different from yours.</blockquote><blockquote><strong>Ask Questions</strong>: When someone uses a word or phrase that’s unfamiliar, ask them what they mean. This can help clear up misunderstandings and open up better conversations.</blockquote><blockquote><strong>Observe Behavior</strong>: Watch for small signs in others’ actions — changes in posture, energy, or silence. These can tell you a lot about how they’re feeling.</blockquote><blockquote><strong>Create Space to Reflect</strong>: If someone seems quiet or hesitant, give them time to gather their thoughts before responding. Not everyone processes in real-time.</blockquote><blockquote><strong>Stay Curious</strong>: Approach every interaction with curiosity. Try to learn from what others say and how they express themselves.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2c6084c5790" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rocket Science of Service Design]]></title>
            <link>https://medium.com/@saitej-pisupati/rocket-science-of-service-design-9a4a695bb5fd?source=rss-ee30cb1dc79------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a4a695bb5fd</guid>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-centered-design]]></category>
            <category><![CDATA[human-behavior]]></category>
            <dc:creator><![CDATA[Saitej Pisupati]]></dc:creator>
            <pubDate>Fri, 16 May 2025 16:37:35 GMT</pubDate>
            <atom:updated>2025-05-19T07:28:37.707Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Or as I like to call it “How’s your relationship with your customer?”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BrxJis6AFpjJSEAbFGRUJw.jpeg" /><figcaption>The design of tangible and intangible interactions between people or groups of people</figcaption></figure><p>Despite living in the most connected era in human history, people are feeling more alone than ever. Studies over the past two decades have consistently shown a sharp decline in empathy, especially among younger generations. A landmark study from the University of Michigan found that empathy levels among college students dropped by 40% between 1979 and 2009 — and the trend has only worsened since. Technology has given us faster access to each other, but not necessarily deeper connection.</p><p>In our obsession with moving faster — replying instantly, delivering quickly, achieving more — we’ve lost the time and space needed to reflect, to be fully present, and to connect with others in a meaningful way. This rush leaves little room for empathy. The result? A growing sense of disconnection, not just in our personal lives, but in our professional environments too.</p><p>In our workplaces, relationships have become more transactional, and our systems — designed for efficiency, scale, and output — often fail to acknowledge the emotional and human needs of those they serve. Loneliness has quietly crept into our organizations — not as isolation, but as emotional invisibility. And when people no longer feel seen or heard, empathy becomes a casualty.</p><p>This emotional gap fuels something deeper: burnout. Not just tiredness, but an existential fatigue — of not being valued, of not belonging. Burnout has become a global epidemic, and it’s not just a personal crisis — it’s a systemic one. According to research by Boston Consulting Group, nearly half of workers globally are grappling with burnout, with feelings of exclusion and disconnection at the heart of the issue. When people don’t feel seen, heard, or valued at work, performance drops, motivation fades, and culture erodes.</p><p>At its core, this is not a productivity problem — it’s a relationship problem. Every interaction within an organization, whether between employees, with leadership, or with customers, contributes to the quality of those relationships. And like any relationship, they require care, effort, empathy, and continuity. Yet too often, the systems that make up our organizations treat people like cogs, not humans — with rigid policies, fragmented experiences, and automated touchpoints that fail to connect on an emotional level.</p><p><strong>But what if we started designing for connection, not just execution? What if we treated each moment of interaction as a chance to build — or rebuild — connection?</strong></p><p>This is where service design steps in. It’s not just about designing processes or interfaces — it’s about designing relationships. Every service is a sum of interactions, and every interaction is a moment of relationship-building. When done right, service design has the power to nurture trust, foster inclusion, and create meaningful experiences — for employees and customers alike. Companies that invest in human-centred design see 32% more revenue and 56% more shareholder returns than their counterparts. — <em>McKinsey &amp; Company, “The Business Value of Design”</em></p><p>And when we talk about service, what we’re really referring to is this:</p><blockquote><strong><em>“The design of tangible and intangible interactions between people or groups of people”</em></strong></blockquote><blockquote><strong>Explanation of the definition: (choice of words used)</strong></blockquote><blockquote><strong>Interaction: </strong><em>Mutual or reciprocal action or influence</em></blockquote><blockquote><strong>Tangible and intangible: </strong><em>not every interaction happens in a tangible way like a hug. Sometimes just by their remembrance or presence just lights up our minds with emotions.</em></blockquote><blockquote><strong>People of groups of people: </strong><em>This whole thing would have been smoother if it was just between two people. But as a organisation we know that there other possibilities for interactions to take place. Between groups of people (an interaction between teams) between groups of group of people (an Interaction between organisations) between a person and groups of group of people (an interaction between organisation and user).</em></blockquote><p>The smallest moments — a warm greeting from a customer support representative, a seamless online experience, or a thoughtfully curated playlist that makes someone’s day — all contribute to a meaningful service experience. Helping a stranger find their way, offering emotional support to a friend, or being present for someone in need — all of these are acts of service. Not the noblest one like mother teresa or Mahatma Gandhi but they still are a service. Even if they don’t involve a formal business exchange.</p><p>Organisations that create emotional connections with the people they serve see tangible benefits — from increased public trust to greater service uptake. In the private sector, companies that build these bonds outperform competitors by 85% in sales growth. Loyal customers are five times more likely to repurchase and four times more likely to refer a friend. In the public sector, programs like the NHS’s “Always Events” initiative or New Zealand’s Human-Centred Policy Design have shown that listening deeply to citizens leads to more effective, trusted, and inclusive services. When organisations — whether public or private — invest in understanding and nurturing these relationships, they don’t just retain users or customers — they create advocates. With 81% of companies now seeing customer experience as a competitive differentiator, designing services that prioritise trust, empathy, and adaptability is no longer optional — it’s essential for long-term success. On the flip side, poor service leads to staggering losses — not only in the form of customer churn for businesses, but also in eroded public trust, reduced compliance, and higher long-term operational costs in government services. <a href="https://www.forbes.com/sites/blakemorgan/2019/09/24/50-stats-that-prove-the-value-of-customer-experience/?utm_source=chatgpt.com">Forbes</a></p><p>At its heart, service design is about tending to relationships — not just at the surface, but within the very fabric of how people connect, collaborate, and care for one another across systems. It’s about understanding that every touchpoint is an opportunity to either deepen trust or erode it. To build better relationships, we must start by being intentional about the way we design interactions. And that begins by understanding how people interact, how they feel, and what they need — not just once, but over time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OkIkqQxpa-LiBrzIW1NBUw.jpeg" /></figure><blockquote><strong>How do you build such relationships?</strong></blockquote><p>The way to build such beautiful, experiential, memorable services is through building trust, communication, openness, consistently, evolving.</p><blockquote><strong>Empathy: </strong>Just like in any human relationship, empathy is the foundation of meaningful engagement. Think of that one friend who listens without interrupting, who gets you, acknowledges your emotions, and responds accordingly is someone you trust and turn to in difficult times. Services can be that, too. When a customer says, “I’m locked out of my account,” they’re not just asking for access — they’re asking for help, maybe reassurance. A gentle tone, a fast path, a small apology — they all say: “We see you.”</blockquote><p><em>Example: Duolingo’s quirky reminders make learning feel less like a chore and more like a friend cheering you on.</em></p><blockquote><strong>Active Listening: </strong>To build a lasting connection, organisations must engage in meaningful, ongoing conversations rather than one-time interactions. True listening goes beyond collecting feedback — it requires attentiveness to user behavior, context, and pain points. Just as in a strong friendship, where unspoken cues matter as much as words, service providers must observe and anticipate needs before they are explicitly expressed. By fostering curiosity about how users interact with a service, organisations can adapt proactively rather than reactively, creating a more seamless and fulfilling experience.</blockquote><p><em>Example: Some Starbucks baristas make mental or physical notes about frequent customers’ preferences and even their moods. Instead of asking “what can I get you?”, they say, “The usual today?” or “Rough day? Want to sit for a bit?”</em></p><blockquote><strong>Trust: </strong>Trust is the glue that holds any relationship together, and services are no different. Trust is built in small moments: showing up, telling the truth, doing what you said you would. The moment users sense that a organisation is more focused on its own gains rather than their well-being, the relationship starts to deteriorate. Just like in personal relationships, once trust is lost, it is incredibly difficult to regain.</blockquote><p><em>Example: Monzo publicly shares when they mess up. No spin, no jargon — just honesty. That kind of transparency builds lasting trust.</em></p><blockquote><strong>Openness: </strong>No one likes a know-it-all — not in friendships, and not in services. Saying “we’re not sure yet, but we’re working on it” is stronger than faking certainty. Pretending to know everything or overpromising inevitably leads to disappointment. Being transparent about limitations fosters credibility. Great service goes beyond transactions; it is about genuinely wanting users to succeed, even if that means guiding them outside the organisation’s ecosystem.</blockquote><p><em>Example: A small online bookshop is asked for a rare title they don’t stock. Instead of saying “sorry, not available,” the support agent says, “We don’t carry it, but here’s a link to an independent shop that does.”</em></p><blockquote><strong>Adaptable: </strong>No two relationships are identical, and no two user needs are exactly the same. A well-designed service, like a good partner, must be flexible enough to accommodate unique situations rather than relying on rigid structures. A customer service representative who goes off-script to solve a user’s specific problem mirrors the way a thoughtful friend adapts their response based on context. Luxury services were once the benchmark for improvisation — tailoring each experience to individual needs. But today, with evolving technology and customer expectations, this level of adaptability is no longer exclusive to luxury; it is becoming the standard across industries.</blockquote><p><em>Example: A great hotel concierge doesn’t follow a script — they make the impossible happen. The small, unscripted moments are often the most memorable.</em></p><blockquote><strong>Evolve:</strong> Strong relationships grow and evolve. People change, circumstances shift, and expectations develop over time. If one partner refuses to adapt, the relationship becomes stagnant. The same principle applies to service design. A static service will inevitably become irrelevant as user needs, technologies, and cultural norms shift. The best services are those that evolve alongside their users. A truly user-centered service doesn’t just react to change; it actively evolves with the people it serves.</blockquote><p><em>Example: Netflix didn’t start with originals. It started with DVDs — then listened, learned, and evolved. Today, it offers hyper-personalized content that feels like it’s growing alongside each viewer.</em></p><blockquote><strong>Consistency:</strong> Would you trust someone who’s warm one day, cold the next? A good service keeps its actions, care, tone, and clarity steady — no matter the channel. The same applies to services. Consistency reassures users that they can depend on a service no matter when or how they interact with it. A brand that delivers an outstanding experience once but fails to do so regularly creates frustration rather than loyalty. A well-designed service ensures that users always receive the same level of quality, responsiveness, and care, reinforcing the relationship over time.</blockquote><p><em>Example: Apple’s support feels calm, clear, and dependable — whether you’re in a store, online, on the phone or anywhere in the world.</em><br> <br> These relationship-driven perspectives highlight that service design is not just about solving problems — it’s about fostering meaningful interactions, just like in human connections. A well-designed service is no different from a strong, enduring relationship — it requires continuous effort, open communication, and a commitment to meeting the evolving needs of the other party. Just like in personal relationships, organisations may believe they fully understand their customers, but true understanding is an ongoing journey, not a single moment of insight. It is not about one grand gesture or a perfectly executed interaction; rather, it is about showing up consistently, listening actively, and being present in every touchpoint. Even the best relationships have moments of failure, and so do services. The key lies in acknowledging mistakes, taking accountability, and demonstrating a sincere effort to improve. Trust is built not on perfection but on the willingness to learn, evolve, and show that the customer’s experience truly matters.</p><blockquote><strong>Each individual’s change creates a ripple in the system. But systems, by nature, resist change — especially those with structures that have been established over decades. Changing these structures, however, allows the change to persist. It enables not just individual change, but a shift in how organizations function for generations to come.</strong></blockquote><p>At its core, service design is about humanizing every interaction — ensuring that whether it is a digital interface, a support call, or an operational backend process, each aspect of the service is crafted with empathy and intention. It’s about making users feel heard, respected, and cared for, just as we would want to be treated in any relationship. Senior managers setting the tone for internal discussions, frontline employees delivering services, and the smallest of user touchpoints — all contribute to shaping this experience. In a world where services define our daily lives, the ones that stand out are not just functional but deeply human.</p><blockquote><strong>The core message here is simple: every interaction is an opportunity for us to form a better relationship with partners, colleagues, managers, leaders, and, most importantly, our customers. Those interactions require each individual to have empathy, actively listen, build trust, be open, serve impromptu needs, continuously evolve, and be consistent. When each individual embodies these attributes and actions, they become part of the system’s behavior, shaping a better organizational culture. This is the ideal system in which the world could — and should — thrive. The careful crafting of such interactions and the building of such systems with empathy and intention is what service design is all about. That’s the science behind every service designer’s thinking — or at least, that’s what it should be.</strong></blockquote><p>So, how do organisations know if they are getting it right? The answer is the same as in any relationship. If your customer were to speak to you like a partner, what would they say? Would they express appreciation for being understood and valued, or would they complain about being ignored, unheard, or taken for granted? The true measure of service excellence lies in answering one simple yet powerful question:</p><blockquote><strong>“How’s your relationship with your customer?”</strong></blockquote><blockquote><em>Because behind every metric, there’s a moment.</em></blockquote><blockquote><em>Behind every KPI, a person.</em></blockquote><blockquote><em>And behind every great service —</em></blockquote><blockquote><em>A great relationship.</em></blockquote><p><strong>What Can You Do Tomorrow?</strong></p><p>You don’t need to rebuild your org. Just start small: start seeing services as relationships</p><ol><li><strong>Map Relationships, Not Just Journeys</strong><br> Where are the moments of friction, emotion, connection? Think in terms of relationships, not steps.</li><li><strong>Listen for Feelings, Not Just Feedback</strong><br> Use interviews, open-ended questions, and front-line staff to sense how users <em>feel</em>.</li><li><strong>Define Relationship Roles</strong><br> Is your service a guide, a partner, a protector? Let that shape tone, design, and policy.</li><li><strong>Empower Teams to Act Human</strong><br> Script less. Coach more. Let people respond like people.</li><li><strong>Design Feedback Loops</strong><br> Relationships grow through reflection. Ask, listen, act, repeat.</li><li><strong>Set a Relationship Goal</strong><br> What do you want your users to <em>feel</em> after using your service? Safe? Understood? Empowered? Design towards that.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a4a695bb5fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dumbing the Problem]]></title>
            <link>https://medium.com/@saitej-pisupati/dumbing-the-problem-b56b735c930c?source=rss-ee30cb1dc79------2</link>
            <guid isPermaLink="false">https://medium.com/p/b56b735c930c</guid>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Saitej Pisupati]]></dc:creator>
            <pubDate>Fri, 02 May 2025 18:22:07 GMT</pubDate>
            <atom:updated>2025-05-02T18:22:07.943Z</atom:updated>
            <content:encoded><![CDATA[<p>Craft It Right: Your No-Fluff Checklist for Writing Powerful Problem Statements</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RQTUIde7-Ec5R2R-1aITeA.jpeg" /><figcaption>An attempt to capture the chaos we don’t question — light trails from cars, blurring the line between motion and meaning.</figcaption></figure><p><strong>What is a problem?</strong></p><p>A problem is a matter or situation regarded as unwelcome or harmful and needing to be dealt with and overcome.</p><p>From a design perspective, a problem arises when users feel annoyed, frustrated, or blocked from achieving a goal or completing a task.</p><p><strong>Different levels of user or organisation pains:</strong></p><blockquote><strong>Level 1: Unpleasant experience</strong> — “Let’s just get this over with.”; “lets try and fix it”</blockquote><p><strong>Example: Spotify</strong></p><p>Before Spotify, users relied on purchasing individual songs or albums, dealing with disorganized MP3 collections, or navigating clunky digital stores. It wasn’t impossible to listen to music, but the experience was inconvenient. Spotify eliminated this by offering a seamless streaming service, personalized recommendations, and instant access to a vast music library — transforming an annoying task into an effortless experience.</p><blockquote><strong>Level 2: It’s a pain</strong> — “It’s really hard.”; “We needed to get this done yesterday”</blockquote><p><strong>Example: Uber</strong></p><p>Before Uber, getting a taxi was often a hassle — long waits, inconsistent pricing, and difficulty finding a ride. Uber streamlined the process by allowing users to hail a ride instantly, track their driver, and pay seamlessly through an app. This addressed a major pain point, turning a frustrating task into a smooth, automated experience.</p><blockquote><strong>Level 3: Complete Blocker</strong> — “I can’t do this.” ; “Our survival depends on it”</blockquote><p><strong>Example: SpaceX</strong></p><p>The cost of space travel was prohibitively expensive, making frequent missions nearly impossible. SpaceX’s innovation in reusable rockets drastically reduced costs, transforming the economics of space exploration and making commercial space travel a reality. On the verge of going bankrupt, their successful Falcon 1 launch was a turning point — proving their technology worked and securing crucial contracts that saved the company.</p><p>The different levels of user pain serve as a critical indicator of where our organization stands in terms of understanding and addressing user challenges. If most of the issues we encounter are at Level 1 (Unpleasant Experience), it suggests that while our product or service functions, there are lingering friction points that, if ignored, could erode user trust over time. If we frequently deal with Level 2 (It’s a Pain) issues, it signals inefficiencies and frustrations that actively hinder user satisfaction and productivity, requiring us to be more proactive in refining our solutions. However, if we are facing Level 3 (Complete Blockers), it means our users are struggling to achieve their core goals, and our organization is at risk of losing credibility, engagement, or even market relevance. Understanding where the majority of our users’ pain points fall allows us to assess whether we are merely iterating on minor improvements or solving fundamental problems that drive long-term value. Prioritizing the right challenges not only enhances user experience but also determines whether we are seen as a company that truly innovates or one that merely reacts to problems as they arise.</p><p>Not every problem needs the same level of urgency, but all problems need to be solved. However, it’s crucial to distinguish between <strong>root causes</strong> and <strong>byproducts</strong> of other issues. Some problems seem pressing but are merely symptoms of a deeper issue. Addressing only surface-level pain points can lead to temporary fixes rather than sustainable solutions. By focusing on the <strong>root cause</strong>, organizations can eliminate multiple related issues at once, preventing recurring challenges and improving the overall experience at a fundamental level.</p><p>These annoyances, frustrations, or blockers cause people to not enjoy products or services. Any design process can start from an idea or an opportunity, but ultimately it should solve a problem for the end user. That is what leads to a great product or service.</p><p>A counter-argument could be about problems users don’t know they have, like before the iPhone. It was a problem users didn’t know they had until someone saw it, understood it, and executed a solution to make it better for the user.</p><p>By understanding the level of pain and distinguishing between symptoms and root causes, teams can allocate resources strategically — resolving critical issues first while ensuring secondary problems don’t resurface in different forms.</p><p><strong>What does a well-defined problem bring to the process?</strong></p><p>A well-articulated problem statement serves several crucial functions:</p><p><strong>Clarity and Focus:</strong> It clearly defines the issue at hand, helping designers, stakeholders, and team members focus their energy on understanding the problem and its impact.</p><p><strong>User-Centricity:</strong> By understanding the root cause of the problem, designers can ensure solutions are truly user-centric, addressing the user’s needs and pain points effectively.</p><p><strong>Improved Decision Making:</strong> A strong problem statement guides design decisions throughout the process, ensuring every step contributes to solving the core issue. This leads to saving time, efforts and money for the organisation.</p><p>In business or even generally in life, people spend ample time getting problem statements right but still fail to capture the essence of the problem. Capturing the right essence is what makes businesses truly understand what people say and what they need.</p><p><strong>Common mistakes when writing a problem statement:</strong></p><p><strong>Excess Jargon:</strong> Using complex words or company/department-specific vocabulary makes statements unnecessarily complex. Anyone from distant parts of the company should be able to understand the statement in one read and contribute to the problem. This openness creates great collaborative organizations.</p><p><strong>Length:</strong> If the statement is too long, it means you don’t understand the problem yourself. Keeping it simple allows people to draw from their experiences to help solve the problem.</p><p><strong>Lack of Evidence and Data:</strong> Relying on gut feelings or anecdotal evidence shapes problem statements inaccurately, leading to assumptions and solutions that miss the mark.</p><p><strong>Narrow Framing:</strong> Considering only the immediate problem without acknowledging the broader context results in solutions that address a single issue but fail to consider the long-term impact.</p><p><strong>Example:</strong></p><ul><li>❌ “The app isn’t popular among millennials.” → Too vague.</li><li>✅ “80% of millennial users abandon the app within the first minute due to complex onboarding.” → Specific and actionable.</li></ul><p><strong>How do you get to the right problem?</strong></p><p>Finding the right problem is like fixing a toy car that keeps getting stuck. Simply reading the instructions (the brief) isn’t enough — you need to see how it moves, where it stops, and why.</p><ul><li><strong>Ask “Why” Repeatedly:</strong> Don’t stop at surface answers. Dive deeper to find root causes.</li><li><strong>Observe &amp; Empathize:</strong> Understand user behavior, not just user feedback.</li></ul><blockquote><em>Good research doesn’t just highlight the problem — it explains why it exists.</em></blockquote><blockquote><strong>The 5 Pillars of a Powerful Problem Statement:</strong></blockquote><blockquote><strong>Empathy:</strong> It must show an understanding of the pains, gains, actions, and relevant activities of the people we seek to serve.</blockquote><blockquote><strong>Simplicity:</strong> It should be short, succinct, clear, and to the point (AKA, will a 10-year-old “get it”?).</blockquote><blockquote><strong>Evidence:</strong> We must be transparent about assertions backed by facts and data versus those that are opinions or hunches.</blockquote><blockquote><strong>Traceability:</strong> We seek to understand, validate, and address the root causes, not just the symptoms. We should detail what we believe drives problems.</blockquote><blockquote><strong>Alignment:</strong> Solving this problem should help us solve for people, profit, society, and the planet.</blockquote><p>Even with these principles and avoiding the mistakes mentioned, there can still be doubt or hesitation about whether you have found the right problem. Don’t worry, we have that covered too.</p><p><strong>Testing Your Statement: The Five Whys</strong></p><p>Here is a “Five Whys” technique to evaluate the strength of your problem statement. Ask “why” five times in a row, probing deeper into the root cause. If your statement allows you to answer these “whys” effectively, you’re on the right track.</p><p>Asking why throughout the process is what true designers are really good at. This helps us explore all the angles of the given context and the possibilities of what the best solution is. Exploration and validation by asking why is the true testament of a good product or service.<br> <br> <strong>Example: Ineffective vs. Effective Problem Statements</strong></p><p><strong>Ineffective Problem Statement: “We need to add more features to our product to improve user engagement.”</strong></p><p>❌ <strong>Why it’s ineffective:</strong></p><ul><li>Assumes a solution (adding features) without identifying the actual issue.</li><li>Lacks user perspective — doesn’t define what’s preventing engagement.</li><li>Doesn’t explain why engagement is low or what users truly need.</li></ul><p><strong>Effective Problem Statement: “Users are struggling to navigate the product due to unclear interface design, leading to high drop-off rates and reduced engagement. The current onboarding process does not adequately guide new users, resulting in frustration and churn.”</strong></p><p>✅ <strong>Why it’s effective:</strong></p><ul><li><strong>User-centered:</strong> Focuses on the real issue — poor navigation and onboarding, rather than assuming feature expansion is the answer.</li><li><strong>Root cause-focused:</strong> Identifies the actual pain points rather than treating symptoms.</li><li><strong>Actionable:</strong> Provides clear direction for product decisions — improving UI and onboarding rather than arbitrarily adding features.</li></ul><p><strong>Demonstrating the Strength of the Effective Statement Using the 5 Whys</strong></p><ol><li><strong>Why</strong> are users not engaging with the product?<br> → Because they struggle to navigate and understand how to use it.</li><li><strong>Why</strong> is navigation difficult?<br> → Because the interface lacks clear visual hierarchy and intuitive user flows.</li><li><strong>Why</strong> does the interface lack clarity?<br> → Because the onboarding experience does not effectively introduce core product functions.</li><li><strong>Why</strong> is onboarding ineffective?<br> → Because it assumes users will figure things out on their own rather than providing guidance.</li><li><strong>Why</strong> has guidance not been prioritized?<br> → Because the early roadmap was shaped around feature development to drive adoption, and usability improvements are now emerging as a key area of focus.</li></ol><p><strong>Key Takeaway: </strong>The <strong>ineffective problem statement</strong> (<em>“We need more features…”</em>) assumes a solution without investigating the root cause, whereas the <strong>effective problem statement</strong> reveals the true issue — poor navigation and onboarding, leading to user frustration and disengagement. This guides product teams toward meaningful, user-centered improvements.</p><blockquote><strong>Final Thoughts: </strong>A well-defined problem statement is the foundation of great design. It creates focus, fosters collaboration, and ultimately leads to products that solve real user needs. Take the time to get it right — because the quality of your solution depends on the clarity of the problem you’re solving.</blockquote><p><strong>DUMB THE PROBLEM: The Ultimate Problem Statement Checklist</strong></p><p><strong>Empathy:</strong> Have you observed real user behavior rather than relying only on assumptions Have you identified whether the issue is an unpleasant experience, a pain, or a complete blocker?</p><p><strong>Simplicity:</strong> Is the problem statement short, straightforward, and free from jargon? Can someone outside your team understand it in one read?</p><p><strong>Evidence:</strong> Does it explain how the problem impacts the user’s ability to achieve their goal? Does the statement focus on the <strong>user’s experience and challenges</strong> rather than internal business issues?</p><p><strong>Traceability:</strong> Have you <strong>asked ‘Why?’ multiple times</strong> to get to the true root cause? Does the statement <strong>address the core issue</strong>, not just its symptoms?</p><p><strong>Alignment:</strong> Does the statement provide a clear direction for solving the problem? Does it set up a problem that can be <strong>measured and validated once solved</strong>?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b56b735c930c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Two Service Designers beating the odds on an Urban Planning project]]></title>
            <link>https://medium.com/@saitej-pisupati/two-service-designers-beating-the-odds-on-an-urban-planning-project-d63d7446bf44?source=rss-ee30cb1dc79------2</link>
            <guid isPermaLink="false">https://medium.com/p/d63d7446bf44</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[citizen]]></category>
            <category><![CDATA[urban-planning]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Saitej Pisupati]]></dc:creator>
            <pubDate>Thu, 04 Feb 2021 11:01:29 GMT</pubDate>
            <atom:updated>2021-03-04T19:32:14.907Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bHzgcxxa6UayZF4kqiwEAw.jpeg" /><figcaption>A Citizen centred urban planning program which connects streets soul to people’s heart</figcaption></figure><p>This article is a reflection of two service designer students working on a project about urban planning while beating the odds of the tough year 2020.</p><p>Service design is a discipline that leans on collaboration and hands-on research. So working from two different countries while being restricted from going outside is not usual. That is why we wanted to share some of our reflections on how we came through, hoping you can learn from our mistakes, as well as get inspired by our successes.</p><p><strong>Let’s start from the beginning, what success meant for us?</strong></p><p>The process of selecting a project in our course is easy, there are several briefs drafted from different clients to choose from. You would usually walk around the class, exchange opinions with your colleges, find colleges to work with, create a WhatsApp group, sync your calendars, and start working. This ritual is repeated at the beginning of each term, followed by a mix of fear and excitement.</p><p>But this time things where different.<strong> </strong>Hours away before submitting our decision, everyone’s phone was constantly ringing. The usual wandering around the classrooms was replaced by a flood of messages with the same subject header: “what are you choosing to work on?”.</p><p>Sara and I were both interested in different projects at first and our decision was driven by different motives. One cared about finding the right people to work with the other cared about finding an exciting project to work on. But the turning point was when we had the conversations about what was a success for us? What would make us proud at the end of the project?</p><p>We both had the same vision, for us, it was about exploring the project in a holistic way, having fun, experiment with new things, and having a measurable impact. Because we had the same goal, we decided to work together and chose a brief that fuelled our curiosity and that was open for us to experiment. Since we have already worked together prior with three other colleagues, we knew we would achieve our goal, but it was scary to think that it’s just the two of us.</p><p>We could see a lot of situations where we would struggle, so we decided to partner with a colleague who was working alone on a similar project. Whenever we would get stuck, we would meet with him to receive feedback or get validation. It was good to add a third person’s perspective because it gave us the motivation to move ahead in the project and helped us reach our goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PU2MLinBCu8--AYh8H78ew.jpeg" /></figure><p><strong>Working from different countries.</strong></p><p>Throughout the project, Sara and I were in different countries and had the same challenges as any remote working team. We would often lose motivation, especially during long periods of lockdown.</p><p>Before the pandemic, we would work together in the same room around one big desk. To mimic the studio environment, we would stay on the zoom call even when we were working on individual tasks. This was the only way to keep the connection alive, and letting the other know that you were there to discuss findings or to just have a quick chat. We always felt like we were in the same place mentally and the physical distance never bothered us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5kL9YkbKH8siapL2ncb7eA.jpeg" /></figure><p><strong>Writing things down.</strong></p><p>During some of the intense conversations, there would be moments where Sara and I would say or think something fundamental for the project. When asked to repeat it, we would fail to do so. This happened often until we both realised that we needed to start documenting our thoughts before discussing them. This allowed us to have solid discussions but also kept a track of how our project evolved.</p><p>There were different ways we used to document these conversations. We started with the classic pen and paper but, because we were working remotely, we would find ourselves holding the paper in front of the camera for the other person to see.</p><p>So what started on paper moved to the screen. We used Keynote as a digital diary and sketched on the slide using the Apple Pencil. We were both very bad at drawing but this wasn’t about how well you could draw, it was about expressing ideas, bringing each other on the same page. This new approach always excited us, those drawing discussions were the fuel that kept our project driving at a pace.</p><p>We realized the importance of documenting our work when we started to experience lockdown in our own countries in different periods. Unfortunately, the lockdown periods were happening when we started to do field research. Because only one of us could go out, we documented our visits to the high streets, when we were allowed to visit them, by recording our walks. We would then watch the recording together and discuss it. This was interesting because when we showed each other the documentaries, you would hear new perspectives that would have gone unnoticed if not documented.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m8eqFgGuNndvJA7fen5SZA.jpeg" /></figure><p><strong>We are immigrants</strong></p><p>The complexity of this project was one of the biggest challenges.</p><p>Although we were designing for London, we were not able to experience the city because of the restrictions. So while doing desk research we started to bring our culture and backgrounds into the project. We would reference our own cities, explore them, and presenting them to each other. By doing so we were able to embed some positive aspects into our project. Of course, we had to readapt them to make them familiar to the country we were designing for, but that helped us to expand our creativity and solve interlinked problems.</p><p><strong>Researching the meaning of the words</strong></p><p>Since neither one of us are native English speakers we often found ourselves not understanding each other. Some words would carry a meaning that the other person would not know or understand differently. Sometimes that meaning was purely fictional or influenced by our culture. We would sometimes argue on the etymology, so we would spend some time researching the meaning on dictionaries or google. This might sound silly but it helped us understand the true meaning of certain words and avoided confusion. We would sometimes go far as visualizing the word through sketches so that we would be on the same page. Afterwards, we would be really careful about what we said and also made sure people understood our meaning of the word.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OP6Sc1I-xstY5jBd2emi7A.jpeg" /></figure><p><strong>We took a leap of faith</strong></p><p>We know that by being in school we were in a safe place to experiment. While deciding our design strategy we decided to experiment with a new process that I was developing.<strong> </strong>I knew that the process would work, but it had never been fully tested on a developing project. Experimentation was one of the key factors for our success, so we took a leap of faith and decided to test it out. After all: “ if you don’t try new things you’ll never learn”.</p><p>So, don’t fear failure, fear never trying something new.</p><p><strong>The duo</strong></p><p>Initially, we were afraid of only being two people working on such a vast topic for only two months.</p><p>But ultimately we had a lot of fun working together. Since it was just the two of us we could take breaks whenever we wanted, we stopped working sometimes early, sometimes late.</p><p>There is a downside to this as well. How do you deal with a situation where there is a conflict? How can we criticize our own work? That is when we would ask for help from colleges and tutors. We would search for criticism and accept it because we knew that’s the only way to expand our thinking, go beyond the size of the canvas and have a successful project.</p><p>From our experience, no matter what the team size is, getting external fresh perspectives every now and then is a good way to handle a design project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NBpyTM4CjT8EVsMg4PoUmA.jpeg" /></figure><p><strong>Conclusion</strong></p><p>Times are tough, and working in teams is not easy. Everyone has something going on in their lives and that goes beyond a pandemic. People may not be able to grab everything in one meeting, topics can deviate, time can be managed poorly, kids may be crying in the background, zoom might not work, etc. That is why I believe that everyone should be looking out for one another. We need to learn to empathize with our colleagues and not just with users. It should be all teammate’s responsibility to make sure everyone is doing ok and support whoever is in need. Find what makes your team tick to keep the momentum of the project. If a team member is having a bad day, just give them the day off and trust them that they would come back stronger the next day. Remember none of this is easy, but again if it was easy everybody would be doing it.</p><blockquote><em>Lastly, When it gets tough going, only the tough get going.</em></blockquote><p>You can check out our project here.</p><p><a href="https://www.rcaservicedesign.com/wip-projects-2021/native">Native</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d63d7446bf44" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>