<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title><![CDATA[Nexzone Pulse Shift]]></title>
  <link>https://nexzonepulseshift.com/</link>
  <description><![CDATA[Nexzone Pulse Shift helps small and mid-size teams fix operational drag and decision-making. Flat-fee consulting engagements, San Francisco.]]></description>
  <language>en</language>
  <atom:link href="https://nexzonepulseshift.com/feed.xml" rel="self" type="application/rss+xml" />
  <item>
    <title><![CDATA[How to run a meeting audit on your own team in 90 minutes]]></title>
    <link>https://nexzonepulseshift.com/notes/meeting-audit-guide-90-minutes.html</link>
    <guid>https://nexzonepulseshift.com/notes/meeting-audit-guide-90-minutes.html</guid>
    <description><![CDATA[There is a particular kind of exhaustion that has nothing to do with the volume of work. It settles in around three in the afternoon, when you look at the day behind you and realise that you have attended six meetings, contributed meaningfully to perhaps two of them, and produced almost nothing you could point to. This is not a time-management problem. It is a structural one — and it lives inside the calendar, hiding in plain sight. The meeting audit exists to make the invisible visible: to give a team a shared, honest account of how its collective attention is actually being spent. What follows is the exact process Nexzone Pulse Shift uses in the first week of every Diagnostic Sprint, stripped of the facilitation scaffolding and written for any team leader willing to give a Tuesday morning — or a long lunch hour — to the work of looking clearly.]]></description>
    <pubDate>2024-12-17</pubDate>
  </item>
  <item>
    <title><![CDATA[The seven places decisions stall in a growing team]]></title>
    <link>https://nexzonepulseshift.com/notes/where-decisions-stall-growing-team.html</link>
    <guid>https://nexzonepulseshift.com/notes/where-decisions-stall-growing-team.html</guid>
    <description><![CDATA[There is a particular kind of meeting that most teams recognise by feel long before they can name it — the one where a decision that should have taken twenty minutes has now occupied three separate sessions, generated a shared document with eleven versions, and still has no owner. The people in the room are not incompetent. The organisation is not badly led. What has happened, usually, is that the team has outgrown the invisible decision-making architecture it built when it was smaller, and nobody has yet noticed the scaffolding has been left behind. In five years of diagnostic work inside teams ranging from six-person early-stage ventures to divisions of several hundred, the same seven structural failure points appear with such consistency that they have come to feel less like accidents and more like laws. Understanding them does not require a restructure. It requires, first, the willingness to look at the map.]]></description>
    <pubDate>2025-11-04</pubDate>
  </item>
  <item>
    <title><![CDATA[What a leadership handover actually involves (and what gets forgotten)]]></title>
    <link>https://nexzonepulseshift.com/notes/leadership-handover-what-gets-forgotten.html</link>
    <guid>https://nexzonepulseshift.com/notes/leadership-handover-what-gets-forgotten.html</guid>
    <description><![CDATA[Every leadership transition carries a version of the same quiet disaster: a competent successor walks into an office that looks orderly, inherits a filing system that seems complete, and then spends the next eighteen months discovering what was never written down. The institutional memory, the trusted relationships, the unspoken rules about who actually makes decisions and who merely approves them—none of it appears in the handover binder. This is not carelessness on anyone's part. It is, rather, a structural failure in how organisations think about knowledge: we document outputs and overlook the processes, relationships, and judgment calls that produce them. What follows is an attempt to name the things that get forgotten, and to offer a practical method for surfacing them before the outgoing leader walks out the door for the last time.]]></description>
    <pubDate>2026-01-12</pubDate>
  </item>
  <item>
    <title><![CDATA[Why flat-fee consulting aligns incentives better than hourly billing]]></title>
    <link>https://nexzonepulseshift.com/notes/flat-fee-consulting-incentive-alignment.html</link>
    <guid>https://nexzonepulseshift.com/notes/flat-fee-consulting-incentive-alignment.html</guid>
    <description><![CDATA[There is a particular kind of silence that falls over a client meeting when the question of billing comes up. It is not the silence of confusion — everyone in the room understands money — but the silence of misaligned expectation, of two parties who, until that moment, believed they were working toward the same thing and have now discovered that the meter has been running in a direction no one fully acknowledged. At Nexzone Pulse Shift, we made the decision some years ago to charge per engagement rather than per hour, and it was not a decision made for marketing reasons or to seem modern. It was made because we kept watching hourly billing warp the work — subtly, insidiously, in ways that neither we nor our clients always noticed until the damage was done. What follows is an honest account of that distortion, and of what a flat-fee structure actually demands of a consultancy willing to stand behind it.]]></description>
    <pubDate>2024-12-27</pubDate>
  </item>
  <item>
    <title><![CDATA[How to tell if your team has a strategy problem or a decision-making problem]]></title>
    <link>https://nexzonepulseshift.com/notes/strategy-vs-decision-making-problem.html</link>
    <guid>https://nexzonepulseshift.com/notes/strategy-vs-decision-making-problem.html</guid>
    <description><![CDATA[There is a particular kind of organisational exhaustion that sets in around the third quarter of a difficult year. The team has been working hard — genuinely hard — and yet the results feel thin, the direction feels murky, and someone in a leadership meeting eventually says it: "I think we need to rethink our strategy." The room nods. A consultant gets called. A two-day offsite gets booked. And six weeks later, the new strategy document sits in a shared drive, largely unread, while the same problems quietly reassert themselves. The strategy was never the problem. What most teams are actually suffering from is a decision-making failure — a structural confusion about who decides what, when, and with whose input. Learning to tell the difference between these two distinct ailments is not a semantic exercise. It is, in practice, the difference between spending four months and considerable money on a strategy refresh and spending four hours redesigning a meeting cadence.]]></description>
    <pubDate>2025-09-17</pubDate>
  </item>
</channel>
</rss>
