<?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 Ceri Newton-Sargunar on Medium]]></title>
        <description><![CDATA[Stories by Ceri Newton-Sargunar on Medium]]></description>
        <link>https://medium.com/@ceri_54940?source=rss-18f1cde0f113------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*64B2-owhBrg8T0N39fppGQ.jpeg</url>
            <title>Stories by Ceri Newton-Sargunar on Medium</title>
            <link>https://medium.com/@ceri_54940?source=rss-18f1cde0f113------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 11:20:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ceri_54940/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[When to stay, when to walk away]]></title>
            <link>https://medium.com/@ceri_54940/when-to-stay-when-to-walk-away-ed0765b64384?source=rss-18f1cde0f113------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed0765b64384</guid>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[Ceri Newton-Sargunar]]></dc:creator>
            <pubDate>Tue, 28 May 2019 14:01:00 GMT</pubDate>
            <atom:updated>2019-05-28T14:01:00.924Z</atom:updated>
            <content:encoded><![CDATA[<p>I attended a tech meetup a while back, and then I came home and felt <strong>utterly dejected</strong>. And then I wrote a self-deprecating tweet, took a mini lesson in Tech Basics from my lovely, eternally patient husband, and felt much better.</p><p>The reason for the dejection is simple: a heady combo of knowing juuuust enough to know that I know <em>nothing</em>, being in a room full of people who mostly do know (or if they don’t, they know enough related material for it not to matter, or they just don’t care), and then trying to hold a conversation with some of them. Most of my comments were along the lines of “I’m in no way technical, but I really enjoyed your talk. I want to understand more… Could you please explain what you were saying?”</p><p>Which… Is fine, actually. I don’t have a massive problem, or a chip on my shoulder, about not knowing stuff at deeply technical meetups that are completely outside my own field of expertise. Not knowing stuff is ok, and learning about stuff you didn’t know before is even better. What I apparently <em>do </em>have a huge problem with, is people monopolising conversation with deeply technical (and ultimately, unsolvable) differences in opinion, essentially in-person trolling, which means someone like me — and I wasn’t the only person in line — can’t get a word in. Or, more importantly, can’t ask for answers and clarity and crucially, and surely the whole damn point of it all: expansion of ideas.</p><blockquote>See an opportunity: take that opportunity</blockquote><p>What was <strong><em>really</em></strong> frustrating, was that I left a really interesting conversation with three fascinating, bright and knowledgeable women, whom I wanted to speak more with, because we had begun to engage in a wonderful exchange of ideas — and I left so that I could ask for clarity from someone who, ultimately, wasn’t going to speak to me.</p><p>I think, then, that I was deeply frustrated with myself: I felt guilty, and was furious with myself for leaving. My personal mantra is “see an opportunity, take the opportunity”. I could’ve trusted the conversation I was in, and asked that group to explain the complexities to me instead. Lovely crowd that they were, they probably would’ve done so with grace, kindness and clarity, and having spent 15 minutes stood watching the unresolvable debate like a <em>total muppet</em>, I now wonder if I would’ve got that from the two chaps whose shoulders I watched over with such awkwardness.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed0765b64384" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ship vs Sheep (or, struggles with change)]]></title>
            <link>https://medium.com/@ceri_54940/ship-vs-sheep-or-struggles-with-change-b44823ce3ce6?source=rss-18f1cde0f113------2</link>
            <guid isPermaLink="false">https://medium.com/p/b44823ce3ce6</guid>
            <category><![CDATA[control]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[change]]></category>
            <category><![CDATA[transitions]]></category>
            <category><![CDATA[change-management]]></category>
            <dc:creator><![CDATA[Ceri Newton-Sargunar]]></dc:creator>
            <pubDate>Mon, 20 May 2019 10:21:00 GMT</pubDate>
            <atom:updated>2019-05-20T10:21:00.916Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/520/1*rNRG5Qv5PFENOervmA6TNA.jpeg" /></figure><p>I want to talk about the sorry subject that is frustration in false starts, particularly when we embark on change processes.</p><p>You see, transformation of a business operation — be that on a team, or wider organisational basis — is often sold, by so-called change experts as a fast /simple / easy process. “Pay us big bucks, and your transformation will be smooth!”</p><p>Except that transition isn’t smooth. This is a massively deceptive, overconfident ideal, and underplays — belittles, even, the role of the many <strong>individuals</strong> in a change process.</p><p>Businesses are not faceless monoliths, sailing quietly towards world domination, aided by the <a href="https://www.growly.io/spotify-engineering-model-with-squads-tribes-chapters-and-guilds/">Spotify Model</a> and a pithy handbook from a slick sales merchant. Businesses are made up of humans: messy, distracted, halfway-through-a-divorce / power-of-attorney / about-to-have-our-first-baby / living-with-PTSD-or-my-awful-childhood / still-dealing-with-being-the-fat-kid-even-though-I-exercise-2hrs-daily, wonderfully diverse, creative, intense, humans. And there is nothing here that a pithy handbook, or all the models in the world, can help a corporation to overcome.</p><p>Perhaps you’ve been sold this yourself. You’ve bought into the “We Have A Plan!” approach, and you are happily setting off, introducing new concepts and processes and tools and models, to your teams, your management hierarchies, your conglomerate.</p><p>And perhaps you’re noticing that it’s not going quite how you expected. A few people have quit. Some targets have been missed. People are performing the steps of the dance, but it’s somehow not quite coming together.</p><p><strong>What’s missing?</strong></p><p>The problem we have when introducing one-size-fits-all plans, is that as the retail industry is fully aware — one size rarely fits all. People don’t fit neatly into little boxes with a neat label. People are like snowflakes in the wild — there are so many varying elements that has shaped and grown each one, that you can’t possibly apply one plan to all, and expect them to adhere, like sheep. Heck, even sheep don’t adhere to plans, they’re constantly finding new ways to get stuck in hedges and expire — and all <em>they</em> really have to do is eat grass, occasionally procreate, and not get eaten.</p><p>So, what to do?</p><p>Well, I obviously can’t now offer you a succinct Plan to follow, because that would be daft given everything I’ve just said. What I <em>can</em> offer you is a suggestion, something I’ve seen to be successful in change processes I’ve been involved in: we have more conversations. When it worked for us, we went and spoke to the people affected by, and directly implementing the change. We spoke about why the change was useful and necessary and how we <em>hoped</em> it would be beneficial. Note that I said <strong>conversation</strong> and <strong>discussion</strong> — we never told people “This is What Will Be Happening!” (note the absence of choice here — the difference is crucial). We would start with telling them about the proposal in detail, then asking what they thought the benefits could be to them, their team, their division, the wider business. This modelled how they could go on and have the conversation with other people in their departments and teams: discussing pros like autonomous adults on an even hierarchical footing, not hiding away from cons — and then agreeing, <em>together</em>, on the common goals, making plans <em>together</em> about the next steps — and then allowing them the autonomy to put their plans into place in a way that worked for them.</p><p>This idea of being in this together is extremely powerful — giving people joint control of their lives, work, their situation in general, leads to far greater acceptance of impending changes. People who feel more in control are happier, more co-operative; they work better with their colleagues. People who <em>don’t </em>feel that sense of control on the other hand, tend to be far less co-operative, are unhappier, take more sick days and — perhaps unsurprisingly — give themselves a sense of feeling in control by sabotaging efforts to force change, or indeed, simply making up new areas that they <em>can </em>control, instead. In a 2008 <a href="http://science.sciencemag.org/content/322/5898/115">study</a> on the effects of removing control, Jennifer Whitson and Adam Galinsky noted that “The need to be and feel in control is so strong that individuals will produce a pattern from noise to return the world to a predictable state.” — which is to say, when we don’t feel like we <em>are </em>in control, we’ll spend our time and efforts not on accepting the changes being forced upon us, but in <em>making up ways</em> we can be in control, and focusing our continuing efforts on <em>those</em> activities and areas, instead of whatever we’re meant to be doing.</p><p>If you’ve ever procrastinated over writing a report you didn’t feel wholly confident about, or a difficult email where you’re unsure of the outcome, you’ll know what I mean.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/683/1*8l7Vw15SMxh5Q6EWvQZ6QQ.jpeg" /></figure><p>Every <em>other</em> thing on your to-do list, and several things that aren’t on your to-do list, suddenly become crucial tasks that require immediate attention, so you push that report or email — which you don’t <em>really </em>want to write, anyway — off until later. Much, much later. Preferably never.</p><p>And if you’re not that person, if you don’t do that — that’s brilliant, and all kudos to you for eating that frog.</p><p>Sadly, though, most of the people we work with fall quite resolutely into the former category, the Make-Things-Up one.</p><p>Of course, people can’t control everything within an organisational change — if they could, they’d probably opt for things to stay as they were. Familiar, known, safe. A key part of this conversation, then, is identifying what individuals and teams <em>can </em>and <em>can’t </em>control within the process. For the things that can’t be controlled, talk about why — why they can’t be changed, whey they’re being implemented. Talk about what it means for you, the person leading the change; what’s in it for you as an individual, and how do you understand it to be of benefit to the team, the company, the individuals involved. Hear people’s objections and work out if there are options to deal with them — and make your people feel heard when the objections can’t be overcome.</p><p>So, once you’ve shared what you can of the control of the process change you’re embarking on together, the next step is to take it further: now we need to review, or retrospect on the process together, and at regular intervals, too — I’m talking days or weeks, not months. Re-convene at regular intervals, and in a setting of mutual respect (that is, without blame, criticism or hostility), look at what has worked: which of the steps you agreed on have yielded good results and positive change in line with the mutual goals? Which ideas haven’t worked so well? Work out <em>why </em>those areas did or didn’t work, and how you can either replicate that success, or modify that failure to make it more successful — or bin it altogether, and start again with a different tactic.</p><p>Yes, this is definitely a time-consuming process. You will almost certainly disagree, several times and in several different ways, with the people you are talking with. Some ideas will fail, and the processes you agree on will take a little time to become more refined. You will learn what works with some people / teams / departments, won’t work with others. But that’s fine — as a wise person once said, a smooth sea never made a skilled sailor. By exposing yourself to these conversations instead of hiding behind a Plan, you, and the people you work with, will all become skilled sailors — you’ll achieve better, more lasting change, from people who become as <strong>passionate</strong> as you do, because there’s a huge buzz in being an active owner of a process rather than a passive participant — a skilled sailor, or a wise shepherd, rather than sheep stuck in a hedgerow, if you will.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b44823ce3ce6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tiny mantras]]></title>
            <link>https://medium.com/@ceri_54940/tiny-mantras-edfc7f91ab52?source=rss-18f1cde0f113------2</link>
            <guid isPermaLink="false">https://medium.com/p/edfc7f91ab52</guid>
            <category><![CDATA[dunning-kruger]]></category>
            <category><![CDATA[impostor-syndrome]]></category>
            <category><![CDATA[procrastination]]></category>
            <category><![CDATA[self-doubt]]></category>
            <category><![CDATA[criticism]]></category>
            <dc:creator><![CDATA[Ceri Newton-Sargunar]]></dc:creator>
            <pubDate>Sun, 19 May 2019 12:26:01 GMT</pubDate>
            <atom:updated>2019-05-19T12:26:01.207Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KEVYudnMJ3zMSyhvB908FA.jpeg" /></figure><p>This is the daily wisdom dispensed by three post-it notes, stuck at the top of my whiteboard both at home and at work. Tiny mantras I can look at, repeat, consider, and use to shift my behaviour when I notice I’m not where I want to be, or doing what I want to be doing.</p><p>Sometimes the answers to the first post-it are not pretty. What I’m choosing to focus on isn’t always what I said I wanted to — and looking at the real reasons for my procrastination is hard, and frequently painful introspection. Looking at my own sense of inadequacy, and then working out the steps I have to take to overcome those feelings is not a swift or simple process.</p><p>Sometimes <a href="https://www.youtube.com/watch?v=Uo08uS904Rg">the wall to be climbed over</a> is particularly high. I spent a lot of time dealing with overwhelm when I was younger, and my coping mechanisms were less than healthy. My supposedly “wasted” years (they weren’t, but my inner critic is a real a*hole, and that’s what it offers my rational brain) play heavily on my mind every time I meet someone younger, who has it together more than I did at that stage of life. Brick upon brick of disappointment, worry, fear, rejection, anxiety, self-doubt, procrastination…</p><p>And sometimes I am really frightened. I’m fully aware that I’m afraid of success, just as much as I am of failure. The consequences of work, of a lucrative contract — the pressure, what it means if I get it wrong, if I don’t deliver what I say I will, what it means for my family, my reputation, my sense of self worth. I have put off things that might work out because of the potential responsibility, worried that I suffer far more from the <a href="https://www.verywellmind.com/an-overview-of-the-dunning-kruger-effect-4160740">Dunning-Kruger </a>effect than I do <a href="https://www.ted.com/talks/elizabeth_cox_what_is_imposter_syndrome_and_how_can_you_combat_it">Impostor Syndrome</a>.</p><p>Since embarking on my Agile journey, though, I’ve actively *<a href="https://www.goodreads.com/book/show/606308.Feel_The_Fear_And_Do_It_Anyway">sought out</a>* the criticism and the things that scare me, more and more — because I know it’s what continues to drive me to be and do greater things.</p><p>It’s hard, and sometimes I go backwards as much as forwards, and I definitely haven’t silenced my inner critic. But I have learned some <a href="https://medium.com/@ceri_54940/how-do-we-eat-an-elephant-ed62a86b88d7">simple steps to deal with my inner critic</a>. Whatever the “failure” is, I know I can either overcome it or discard it as not relevant or actually true, and then I can move on. I can try again, and do better next time — because there will, at some point no doubt, be a “next time”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edfc7f91ab52" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I know that I know nothing… I think…]]></title>
            <link>https://medium.com/@ceri_54940/i-know-that-i-know-nothing-i-think-217d5f881eee?source=rss-18f1cde0f113------2</link>
            <guid isPermaLink="false">https://medium.com/p/217d5f881eee</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[knowledge]]></category>
            <category><![CDATA[humility]]></category>
            <category><![CDATA[servant-leadership]]></category>
            <category><![CDATA[understanding]]></category>
            <dc:creator><![CDATA[Ceri Newton-Sargunar]]></dc:creator>
            <pubDate>Sat, 18 May 2019 13:48:29 GMT</pubDate>
            <atom:updated>2019-05-18T13:49:32.139Z</atom:updated>
            <content:encoded><![CDATA[<p>A while back now, I was working with a Proper Agile Coach (one of the ones who’ve worked with Boeing, and NASA, and Xerox and so on, you know — huge transformation companies rather than small, 30–10 employees-with-one-or-two-dev-teams-of-3-or-5-if-you’re-lucky companies I’ve graced to date). And I made a mistake.</p><p>To a more experienced Agile Coach, a fairly obvious mistake — and to the less experienced, a barely perceptible one. A minor mistake about a user story, where I started out with the end product, offering the solution as part of the problem, rather than focusing on User Need.</p><p>In this case, to illustrate a different point I was trying to make about language, my story required the specific “Cottage Pie” rather than open-ended “food”. It’s obvious in retrospect (is it? I may still actually have it wrong — if it isn’t clear to you either, DM me and I’ll give you the name of the coach, he’ll explain to you kindly &amp; clearly, more coherently than I can, as he did with me because he’s a lovely man and that’s <em>just what he does</em>).</p><p>The lovely coach pointed out my mistake. My response? To immediately, completely deny that it happened by re-framing my back-story into something else. Yes, I tried to cover my tracks.</p><p>You see, I’d recently embarked on being self-employed, and so I was (and to a large extent, still am) <em>desperately</em> trying to look good in front of people, so they might go and tell their friends that I <em>do</em> know what I’m talking about. (I don’t wholly believe I do, but I’ll never get contracts with <em>that</em> attitude, so we paint over the cracks and carry on).</p><p>And he was right: it was a comically rubbish user story, and perfectly embodied his point about user stories. But nonetheless, I covered my tracks, re-shaped my purpose to fit (it was deliberate, obviously! I <em>know</em> how it should be done, I was testing…), and stuck to it, feelings of inadequacy and a big fat chip on my shoulder shining right on through.</p><blockquote>It’s fine not to know, as long as you know you don’t know, and then go do something about it.</blockquote><p>It turns out, then, that I’m still learning that humility is a large part of Agile: a seemingly impossible trick of accepting that you know that you don’t know, and that it’s completely fine to not know, and to have other people know that you don’t know. This is all fine. And as someone who’s sat in board rooms being the only woman in the room, saying something intelligent and relevant and (dare I say it?) crucial, only to be loudly ignored, and then to have the same point made, and loudly accepted, a few minutes later by one of the men in the room, as <em>that</em> person, I can categorically state that it’s <em>really</em> flipping hard to publicly accept that you might not be right about something. Even more so if you’re doing that in front of people who might maybe want to hire you as someone who definitely, undeniably knows what they’re talking about and is 100% Proper Expert.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/329/1*iFmC8-nTP4Ngg4ThWVtGJQ.png" /><figcaption>It’s really flipping hard to publicly accept that you might not be right</figcaption></figure><p>This idea of humility, and being a constant learner is fairly well-accepted within Agile circles — certainly, it’s something I’ve touted myself in enthusiastic conversations with other Agilists who all wholeheartedly agree. It’s fine not to know, as long as you know you don’t know, and then go do something about it — it’s a journey, not a destination! All that malarkey. And it <em>is</em> wonderful malarkey. But, in the wider sphere of fear for my future and threat from Above and metrics and delivery speed being key and on-time delivery of KPIs else your job is as good as gone, buddy, though, is there, realistically, a way of taking it on the chin and owning up to not knowing something publicly like that? Is this, genuinely, a mark of strength? Or do we just say that, whilst everyone in the room smirks and exchanges knowing sideways glances?</p><p>Yeah, so, no, I don’t have the answer to those questions. This isn’t one of those posts where I deliver a valuable insight and learning point, it’s one where I admit I know <em>nothing</em> in the grander scheme of things, and highlight that there will always be experts out there <em>significantly </em>more expert than me (and, no doubt, you — unless you’re <a href="https://www.jpattonassociates.com/">Jeff Patton</a> or <a href="https://www.youtube.com/watch?v=N7oz366X0-8">Dave Snowden</a> themselves. Welcome, Jeff, Dave, lovely to have you over). And I’m happy to admit it in this really public online space, in case someone can learn something from my ignorance — but please, do also leave your thoughts, I’d love to hear what you know.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=217d5f881eee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How do we eat an elephant?]]></title>
            <link>https://medium.com/@ceri_54940/how-do-we-eat-an-elephant-ed62a86b88d7?source=rss-18f1cde0f113------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed62a86b88d7</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[inner-conflict]]></category>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[criticism]]></category>
            <category><![CDATA[continuous-improvement]]></category>
            <dc:creator><![CDATA[Ceri Newton-Sargunar]]></dc:creator>
            <pubDate>Sat, 18 May 2019 10:57:31 GMT</pubDate>
            <atom:updated>2019-05-18T11:31:12.445Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/961/1*EwsGaKOY2nNar7ifjxBpSA.jpeg" /><figcaption>(p.s. If it’s all the same to you, could we perhaps not?)</figcaption></figure><p>It’s astonishing to me how in awe we all seem to be of each other: constantly seeing how we stack up, and feeling “less than”, even though everyone *else* sees us as “more than”.</p><p>In my work, I’ve had some incredible conversations with some incredible people, teams, and business leaders. Looking at these interactions from an outside perspective, if I were able to respond to the unspoken thoughts of inadequacy, the subconscious negative upward comparisons, I would say:</p><p>You are probably a lot more than you think.</p><p>When I find I am less than I hope to be — and this seems to be something a lot of high achievers believe — the way to address that is not to sink in despair, isolating myself in a mental corner of misery, shame and self-criticism. I used to do that.</p><p>Now, I use my upward comparison as a motivator: I pick out the small actions I can take to improve or fix the situation. Instead of succumbing to my “failure”, I ask my critical inner voice some questions:</p><p>- What would you need to do, to make those criticisms wrong?<br>- What do you need to do first?<br>- How will you do that?<br>- When?<br>- Where?<br>- Who do you need?</p><p>When I have answers to these questions, I can go ahead and act on them. I jump right in and go do those things. Small things, easily achievable, not insurmountable.</p><p>Meanwhile, I can consider the bigger shortcomings on my list, and think about them, in order to find achievable solutions. Nothing too big, small steps, things I can do, or get started on, here and now. And then I get cracking on those.</p><p>How do we eat an elephant? One bite at a time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed62a86b88d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>