<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>The Nerve · Weekly newsletter on change at work · Amélie Beerens</title>
  <link>https://ameliebeerens.com/the-nerve</link>
  <description>The weekly newsletter by Amélie Beerens. One story a week from building, leading and transforming, and the nerve inside it: the part nobody says out loud.</description>
  <language>en</language>
  <atom:link href="https://ameliebeerens.com/the-nerve/feed.xml" rel="self" type="application/rss+xml"/>
  <item>
    <title>I converted zero clients for six months. Here's the autopsy.</title>
    <link>https://ameliebeerens.com/the-nerve/zero-clients-for-six-months</link>
    <guid isPermaLink="true">https://ameliebeerens.com/the-nerve/zero-clients-for-six-months</guid>
    <pubDate>Mon, 12 Oct 2026 12:00:00 +0000</pubDate>
    <description>For fifteen years, nine of my client conversations out of ten ended in a yes. These past months: zero. So I made myself the case study.</description>
    <content:encoded><![CDATA[<p>First issue, so let me set the tone with the most uncomfortable story I have: mine.</p>
<p>For fifteen years, nine of my client conversations out of ten ended in a yes. These past months: zero. Real interviews, real budget discussions, and then "we went with someone else." By email. No call. No reason. Every time.</p>
<p>The nerve in this story, the part nobody says out loud, is this: the reason you lost will never be written down. Not because people got rude. Because a written reason is a legal risk, and silence is the only answer that can never be held against anyone. The feedback channel didn't die of neglect. It was killed, and everyone in the room knows it.</p>
<p>So I made myself the case study. I posted the zero on LinkedIn and asked the market to talk. Sixty comments, a full DM inbox and one video message later, I had something better than feedback: a diagnosis. Why checkable proof stopped closing deals. What my 90% was actually measuring all those years. Why some interviews were never mine to win. And where the value in this profession is migrating before 2027.</p>
<p>I turned all of it into two things today:</p>
<p>The podcast episode, if you want the story told straight: <a href="https://ameliebeerens.com/blog/90-to-0">listen here</a> (or any platform you like...)</p>
<p>The full written version, what I found and what I rebuilt, with every source linked, if you want to check my work: <a href="https://ameliebeerens.com/blog/90-to-0">read it here</a></p>
<p>Next week: the best service I ever paid for, and why I left anyway. Fifteen years preaching customer experience, then I became the customer who walked.</p>
<p>Amélie<br>
<em>Transformation under real conditions, tested on real humans.</em></p>
<p>P.S. If there's a nerve you want me to touch, reply with one line. I collect them.</p>]]></content:encoded>
  </item>
  <item>
    <title>CX and EX in silos? Use this 5-step playbook to fix one bottleneck fast</title>
    <link>https://ameliebeerens.com/the-nerve/cx-and-ex-in-silos</link>
    <guid isPermaLink="true">https://ameliebeerens.com/the-nerve/cx-and-ex-in-silos</guid>
    <pubDate>Thu, 10 Sep 2026 12:00:00 +0000</pubDate>
    <description>Five steps to reset one moment that matters for customers and for the team at the same time. One moment, one fix, one signal, one month.</description>
    <content:encoded><![CDATA[<p>You know I'm obsessed with leadership. But here's the other thing: I'm a <strong>systems geek</strong>. I love fixing what looks impossibly complex, because transformation is rarely about a massive two-year program. It's about one proof of concept at a time.</p>
<p>And proof matters. According to McKinsey, <strong>around 70% of transformation projects fail,</strong> mostly because they try to do too much, too fast, with no visible proof along the way.</p>
<p>So today, I'm trying a new format with you: a saveable <strong>CX•EX Reset Playbook.</strong> These are five steps I've tested, proven, and kept in my “best practice” book. They're simple, practical, and designed to work in the mess of real life.</p>
<p>I'd love to know if you find this format useful, so hit reply after reading and tell me.</p>

<h2>The CX•EX Reset Playbook:</h2>
<ul>
  <li><strong>Step 1. Focus:</strong> Pick one moment that matters.</li>
  <li><strong>Step 2. Map:</strong> Put customer + employee journeys on one page.</li>
  <li><strong>Step 3. Fix:</strong> Choose the smallest system change.</li>
  <li><strong>Step 4. Measure:</strong> Track one signal for each side.</li>
  <li><strong>Step 5. Sprint:</strong> Run a 30-day experiment.</li>
</ul>
<p>Remember: One moment. One fix. One signal. One month.</p>

<h3>Step 1. Focus: Pick one moment that matters</h3>
<p>A service company I worked with had the same problem over and over: after signing a contract, the kickoff date kept slipping. Sales promised one thing. Delivery discovered another. Clients chased updates. The team spent hours rebuilding context.</p>
<p>That's the perfect “moment that matters.”</p>
<ul>
  <li>Customers were confused.</li>
  <li>Employees were frustrated.</li>
  <li>Nobody owned the handover.</li>
</ul>
<p><strong>Success looks like:</strong> one clearly defined moment, one owner, and a simple problem statement.<br>
<strong>Watch out for:</strong> leaders insisting on fixing three things at once.<br>
<strong>Counter:</strong> write this rule at the top: <strong>One moment. One fix. One signal.</strong></p>

<h3>Step 2. Map: Put both journeys on one page</h3>
<p>Once you've named the moment, mapping it out is where the magic starts.</p>
<p>Draw two columns: <strong>Customer side</strong> (what they see, expect, feel) and <strong>Team side</strong> (what they do, need, decide). Add timestamps and owners. Circle where people step in as duct tape.</p>
<p><strong>Our example:</strong></p>
<ul>
  <li>Client expects kickoff date within 48h of contract signature. Instead, they get a vague “welcome” email.</li>
  <li>Delivery digs for scope, access, and contacts across five different tools.</li>
</ul>
<p><strong>Success looks like:</strong> a one-page map both sides can read in three minutes.<br>
<strong>Watch out for:</strong> arguments about what <em>should</em> happen.<br>
<strong>Counter:</strong> write down what actually happens today, not what the SOP says.</p>

<h3>Step 3. Fix: Choose <em>one</em> system change</h3>
<p>Here's where leaders usually overcomplicate it. Don't redesign the entire onboarding. Choose <strong>one shared fix</strong> you can ship in 1 to 2 weeks.</p>
<p><strong>Our example fix:</strong></p>
<ul>
  <li>Create an <strong>auto-generated Kickoff Packet</strong> at contract signature: scope, roles, access checklist, and a booking link.</li>
  <li>Add <strong>a 2-minute internal checklist</strong> so Delivery starts with full context.</li>
</ul>
<p><strong>Success looks like:</strong> one friction loop removed for both sides.<br>
<strong>Watch out for:</strong> scope creep (“let's redo the whole process”).<br>
<strong>Counter:</strong> park bigger ideas in a backlog, ship one fix now.</p>

<h3>Step 4. Measure: Track one signal per side</h3>
<p>You don't need five KPIs. (Trust me, I've seen that mistake a hundred times.) You need one customer signal and one team signal. That's it.</p>
<p><strong>Our example metrics:</strong></p>
<ul>
  <li>Customer signal: time to confirmed kickoff drops from 5.2 days to under 48h.</li>
  <li>Team signal: fewer escalations on missing info.</li>
</ul>
<p><strong>Success looks like:</strong> both metrics move within three weeks.<br>
<strong>Watch out for:</strong> leaders adding five more metrics.<br>
<strong>Counter:</strong> write this rule on your scoreboard: <em>One customer metric. One team metric.</em></p>

<h3>Step 5. Sprint: Run a 30-day reset</h3>
<p>Day 1: align on one problem, one fix, one signal, one owner.</p>
<p>Weekly: 20-minute check-ins to check usage, signal movement, and blockers.</p>
<p>Day 30: lock what worked, note what didn't, and pick the next fix.</p>
<p><strong>Our example cadence:</strong></p>
<ul>
  <li>Week 1: build the Kickoff Packet + checklist.</li>
  <li>Week 2: pilot on three deals.</li>
  <li>Week 3: roll out to all new clients.</li>
  <li>Week 4: stabilize and choose the next fix.</li>
</ul>
<p><strong>Success looks like:</strong> calmer mornings, fewer “where's my kickoff” emails, no more duct tape work.<br>
<strong>Watch out for:</strong> excuses (“we skipped it on two deals because X”).<br>
<strong>Counter:</strong> treat misses as data. Ask: what in the system made the new behavior harder than the old one?</p>

<h3>What to expect in 30 days</h3>
<ul>
  <li>Less ping-pong between Sales and Delivery.</li>
  <li>Shorter time to clarity for clients.</li>
  <li>Fewer escalations for missing context.</li>
  <li>A visible lift in calm and confidence across the team.</li>
</ul>
<p>Optional extra in Week 3: add a client-facing status page both sides can see. It reduces chase emails and builds trust fast.</p>

<h3>Frictions you'll meet (and how to handle them)</h3>
<ul>
  <li><strong>Budget silos:</strong> bring in Operations as co-owner.</li>
  <li><strong>Expert mode:</strong> people overcomplicate. Bring it back to the two signals.</li>
  <li><strong>Scope creep:</strong> park extra ideas in a backlog.</li>
  <li><strong>“We're different”:</strong> same 5 steps apply. Context doesn't break the playbook.</li>
</ul>

<h3>Over to you</h3>
<p>Try this 5-step reset on one messy moment this month. Then hit reply and tell me:</p>
<ul>
  <li>Did it work?</li>
  <li>Did the friction show up differently?</li>
  <li>Do you want more of these playbooks in future newsletters?</li>
</ul>
<p>With you for results that actually feel good,</p>
<p>Amélie</p>]]></content:encoded>
  </item>
  <item>
    <title>My biggest 2025 project didn't fit on LinkedIn… so I kept it for myself.</title>
    <link>https://ameliebeerens.com/the-nerve/my-biggest-2025-project</link>
    <guid isPermaLink="true">https://ameliebeerens.com/the-nerve/my-biggest-2025-project</guid>
    <pubDate>Sat, 10 Jan 2026 12:00:00 +0000</pubDate>
    <description>Why I vanished for five months, and what integration does to a career that never stopped moving.</description>
    <content:encoded><![CDATA[<p>I hope you are fine.<br>
I know it's been a while but I have a good story for you....</p>
<p>It all started when I told him:<br>
“This is the most vulnerable thing I'll ever do.”</p>
<p>And I wasn't talking about a business challenge.<br>
I was talking about becoming a mother.</p>
<p>Yes, surprise.<br>
My biggest project of 2025 was a tiny human.<br>
And I kept it off the radar for five whole months.</p>
<p>If you've been wondering why I vanished… now you know.</p>
<p>For the last 15 years, one thing never moved: my work.<br>
My life could be messy... burnout, breakups, money stress, addictions, homelessness...<br>
but my career stayed steady.<br>
It grew, it held me up, it paid the bills, it kept me anchored.</p>
<p>I could be falling apart privately and still be a machine professionally.</p>
<p>But this time… it didn't work like that.</p>
<p>2025 changed the rules.</p>

<hr>

<p>At the start of the year, I stepped into what I instantly knew was <em>the</em> project of my life:<br>
I was pregnant.<br>
Not just “pregnant” but stepping into motherhood with full presence, intention and honesty.</p>
<p>And for the first time ever, my personal life didn't politely sit on the side.<br>
It walked into my work with muddy boots and rearranged all the furniture.</p>
<p>My time shifted.<br>
My energy shifted.<br>
My pace shifted.<br>
My identity shifted.</p>
<p>I couldn't outwork this.<br>
I couldn't “stay professional” to hide it.<br>
I had to integrate it, fully.</p>
<p>And I'll be honest: I kept it private because I was scared.</p>
<p>Scared of stereotypes about ambitious women and motherhood.<br>
Scared people would perceive fragility where there was none.<br>
Scared of being a total beginner again.<br>
Scared of being judged differently while navigating something so intimate and new.</p>
<p>I needed space.<br>
So I took it.</p>

<hr>

<p>Now that I'm officially on the other side, here's the real insight:</p>
<p>This wasn't fragility.<br>
This was expansion.<br>
Integration.<br>
A deeper version of ambition, not a smaller one.</p>
<p>Motherhood didn't replace anything.<br>
It added meaning, clarity, and a sharper filter for what truly matters.</p>
<p>There is no “professional me” and “private me”.<br>
There is just… me.<br>
In different contexts, with different stakes.</p>
<p>And instead of diluting my leadership, this experience strengthened it.</p>
<p>I feel more anchored.<br>
More intentional.<br>
More selective.<br>
More powerful.</p>
<p>This is what integration does:<br>
It forces you to let go of the artificial split and lead as a whole human.</p>

<h3>What you can take from this (no baby required)</h3>
<p>This isn't a story <em>about</em> motherhood.</p>
<p>It's a story about what happens when:</p>
<ul>
  <li>you stop pretending two parts of your life are unrelated</li>
  <li>you allow yourself to be a beginner again</li>
  <li>you let expansion reshape your systems</li>
  <li>you stop performing strength and actually embody it</li>
  <li>you build a life, a career or a business that support who you're becoming, not who you used to be</li>
</ul>
<p>Whether your “project” is a baby, a reinvention, a transition, a leap, or a quiet shift,<br>
integration beats compartmentalisation every single time.</p>
<p>It expands you.<br>
It pulls the real leader forward.<br>
It rearranges your priorities with brutal clarity.<br>
And it makes every next step feel cleaner, sharper, more aligned.</p>
<p>This is the version of me walking into 2026.<br>
And I'm incredibly proud of our debut.</p>
<p>More soon... this new chapter is just getting started.</p>
<p>Amélie</p>
<p><strong>PS:</strong> If you're entering your own era of expansion, new role, new identity, new ambition, new rules, you don't have to navigate it alone.<br>
I help women build leadership that actually fits the life they're creating.<br>
Reply if you want the details. No fuss.</p>]]></content:encoded>
  </item>
</channel>
</rss>
