There are moments in life that don’t mean very much when they happen.

Words people say in passing.
Stories half told.
Places you leave behind without really understanding what they meant to you.

And then one day, decades later, those same moments return carrying an entirely different weight.

For me, one of those moments happened around thirty years ago when I was leaving the UK for Australia.

Our family friends said to me:

“Never forget where you came from.”

At the time, I smiled politely, probably nodded, and carried on packing my bags.

I don’t think I understood those words at all.

I do now.

I was born in England, but when I was seven years old my family moved to a small village in North Wales, near Snowdonia, to be closer to my maternal grandmother.

It was beautiful. Rugged hillsides, slate-grey skies, winding roads, old stone buildings and a sense of history that seemed embedded in the landscape itself.

But it was also a culture shock.

I didn’t speak a word of Welsh when we arrived and, in that region, Welsh wasn’t just a language — it was identity, history, resistance and belonging. In some shops and among older members of the community, Welsh was spoken almost exclusively. At school, some lessons were taught in Welsh and, as a child arriving from England, I became very aware very quickly that I was “other”.

At seven years old, you don’t have the language to explain exclusion or cultural tension. You just know how it feels.

You know what it’s like to walk into a room and not understand what’s being said.
You know what it’s like to stand out.
You know what it’s like to desperately want to fit in.

Over time, I learned the language. By high school, I could understand and speak Welsh reasonably well. But high school introduced an entirely different layer of complexity.

This was during a period where Welsh nationalism felt particularly heightened in parts of North Wales. There were tensions around identity, language, land ownership and the growing number of “holiday cottages” owned by people outside the local community. Some extremist factions responded aggressively and, in nearby areas, holiday homes were being targeted and burned.

As a teenager, it was frightening.

At school, the divisions often felt visible and tangible. I remember playgrounds that felt split down invisible lines — Welsh on one side, English on the other. There were fights, insults and hostility that no teenager really has the emotional tools to process properly.

“English go home” was something we heard often.

The irony was that many of us hadn’t chosen to be there in the first place. Our parents had made those decisions for us. We were just trying to survive adolescence while carrying labels we didn’t fully understand.

Oddly enough, my closest friendship during that time crossed those invisible boundaries entirely.

She was Welsh first-language.
I was English first-language.

Both of us already sat slightly outside the social structures of the school for different reasons and somehow that created common ground. While other kids seemed determined to pick sides, we mostly just tried to stay invisible.

That feeling — of existing between worlds without fully belonging to either — followed me for a very long time.

When I moved to Australia in my twenties, the feeling returned all over again.

Not because of language this time, but because of culture.

Australians, broadly speaking, didn’t seem particularly concerned with where you came from. At least not in the overt ways I’d experienced growing up. But beneath the surface, it was impossible not to notice undertones of racial tension and intolerance, particularly directed towards Aboriginal and Torres Strait Islander peoples.

Coming from a country with its own deeply complicated history around migration, identity and racism, I recognised some familiar patterns.

And it saddened me.

Earlier in my career, I had the opportunity to spend significant time living and working in the Northern Territory. It remains one of the most culturally rich and fascinating parts of Australia I’ve experienced.

What surprised me most was not the landscape or the remoteness.

It was the feeling.

For reasons I couldn’t properly explain at the time, I felt something there that I hadn’t felt in many other places in my life:

Connection.

Not ownership.
Not entitlement.
Just connection.

A sense of place.
A sense of history.
A sense that culture mattered.

I didn’t fully understand why it resonated with me so deeply.

Not then, anyway.

Years later, mostly out of curiosity and for a bit of fun, I completed an Ancestry DNA test.

The results came back overwhelmingly Welsh and Celtic.

Not vaguely.
Not partially.

Deeply and unmistakably tied to the very region around Snowdonia where I had spent much of my childhood feeling like I didn’t belong.

I remember staring at the results with a strange sense of disbelief.

All those years of feeling disconnected from the place… and my family history had roots there all along.

Nobody had ever really spoken about it in any meaningful way.

And yet, in hindsight, there had been fragments.

My mum once told me stories about my great-grandfather working in the Clogau gold mine — the same mine famous for supplying gold to the Royal Family. I remembered attending my Uncle Elwyn’s funeral in a tiny family-owned church nestled into the hillside. I remembered names, stories and places that suddenly carried more significance than they ever had before.

It felt like discovering pieces of myself long after I’d already become an adult.

And strangely, it also came with grief.

Not dramatic grief.
Not catastrophic grief.

Just the quiet sadness of wondering how life might have felt differently if I had understood those connections earlier.

If somebody had helped me see culture not as division, but as inheritance.
As belonging.
As continuity.

These days, I think differently about identity than I once did.

I think about language preservation.
About local communities trying to hold onto culture.
About the deep emotional connection people have to place and history.

Welsh is considered a vulnerable language. Communities in parts of Wales continue fighting to keep younger generations in local areas as housing affordability and outside ownership reshape entire regions.

And perhaps because of my own experiences — both in Wales and later in Australia — I find myself feeling increasingly passionate about protecting culture, language and Indigenous identity wherever it exists.

Not because I believe cultures should isolate themselves from others.

But because once culture disappears, something irreplaceable disappears with it.

A world view.
A memory.
A connection between generations.

Gone.

Australia is home now.

My roots, my life and my future are here.

But for the first time in my life, I also understand that where we come from matters — even when we don’t yet understand why.

Maybe especially then.

And perhaps that’s why those words from thirty years ago finally make sense.

“Never forget where you came from.”

I won’t.

Discover → Diagnose → Frame → Mobilise → Enable → Stabilise & Learn

Phase 1: Discover

Step 1: Rapid Landscape Scan

Actions:

• Build an immediate, imperfect view of the environment

• Avoid waiting for complete artefacts

Inputs & Prompts:

• Conversations

• Existing boards/tools (if any)

• Observations

Outputs:

• Initial mental model of work and pressure points

Success Measures:

• You can describe ‘what’s happening’ without needing validation from reports

Step 2: Structured Leadership Conversations

Actions:

• Meet 1:1 with managers and delivery leads

• Use consistent questioning

Inputs & Prompts:

• Now / Next / Later

• Why it matters

• Timeframes

• Dependencies

• Risks

• Needs from leadership

Outputs:

• Pattern recognition across teams

Success Measures:

• Repeated themes and inconsistencies become visible

Phase 2: Diagnose

Step 3: Identify Weak Signals

Actions:

Look for:

• ‘Everyone knows’ issues

• Cross-team dependencies

• Time-bound risks

• Low ownership areas

Outputs:

• Candidate risks

Success Measures:

• You can articulate the issue clearly and confidently

Step 4: Validate and Deepen Understanding

Actions:

• Test assumptions

• Confirm scope and impact

• Identify affected systems, teams, and processes

Outputs:

• Defined problem statement

Success Measures:

• The issue moves from vague → specific

Phase 3: Frame

Step 5: Translate to Business Risk

Actions:
Reframe into:

• Continuity risk

• Customer impact

• Financial exposure

• Strategic misalignment

Outputs:

• Executive-ready narrative

Success Measures:

• Non-technical stakeholders immediately understand urgency

Step 6: Secure Sponsorship

Actions:

Present:

• Risk

• Timeline

• Options

• Consequences

Outputs:

• Priority endorsement

• Decision rights

• Organisational backing

Success Measures:

• Work is officially recognised and supported

Phase 4: Mobilise

Step 7: Decompose into Workstreams

Actions:

• Break problem into outcome-based streams

Outputs:

• Clear work packages

Success Measures:

• Work can be parallelised and assigned

Step 8: Reduce Scope Where Possible

Actions:

Identify:

• Workarounds

• Alternatives

• Redundant effort

Outputs:

• Reduced or simplified scope

Success Measures:

• Less work required without compromising outcomes

Step 9: Assign Ownership

Actions:

• Allocate a clear owner per stream

Outputs:

• Named accountability

Success Measures:

• No workstream is “floating”

Step 10: Establish Visibility

Actions:

• Create shared view (e.g. Now/Next/Later, program board)

Outputs:

• Transparent priorities and progress

Success Measures:

• Anyone can understand what matters quickly

Phase 5: Enable

Step 11: Tailor Delivery Approach

Actions:

Match method to work type:

• Agile

• Operational

• Project-based

• Hybrid

Outputs:

• Fit-for-purpose delivery model

Success Measures:

• Teams are not constrained by mismatched process

Step 12: Coach Leaders

Actions:

Support delivery leads in:

• Planning

• Decision-making

• Team enablement

• Escalation

Outputs:

• Improved leadership capability

Success Measures:

• Leaders adapt their style to suit the situation

Step 13: Enable Team Ownership

Actions:

Shift from:

• Task assignment → Problem ownership

Encourage:

• Self-organisation

• Collaboration

• Initiative

Outputs:

• Increased engagement and speed

Success Measures:

• Teams step forward without prompting

Step 14: Monitor Flow

Actions:

Track:

• Wait states

• Bottlenecks

• Handoffs

• Lag time

Outputs:

• Realistic delivery insights

Success Measures:

• Risks are identified early, not after delay

Phase 6 — Stabilise & Learn

Step 15: Adapt Scope

Actions:

• Shift to MVP where required

• Reprioritise based on constraints

Outputs:

• Achievable delivery plan

Success Measures:

• Outcomes delivered despite disruption

Step 16: Embed Learning

Actions:

• Capture:

  • Leadership shifts

  • Team behaviours

  • Delivery improvements

Outputs:

• Reusable capability

Success Measures:

• Organisation performs better next time

Subscribe now

When we got to the last phase of the program, the work looked very different from where we started. What had started as:

• An undefined risk

• With no clear ownership

• And no coordinated response

Had become:

• A structured program

• With aligned leadership

• And teams actively engaged in delivery.

But this is often when delivery feels most vulnerable. As momentum grows, so does the pressure. The real test then is: can you keep making progress when constraints begin to tighten?

Project 2: Where Structure Faced Reality

The second main focus, improving the legacy product, needed a different approach.

While Project 1 improved thanks to changes in team dynamics and self-organisation, this stream needed:

• Tighter coordination

• Clearer sequencing

• And more deliberate tracking

So we set up a focused delivery team. It was a small, dedicated group supported by:

• A Scrum Master who took on a project coordination role

• Close collaboration with the architecture

• And clear insight into both delivery tools and timeline planning. That wasn’t welcome.

We also supplemented Jira with MS Project to help everyone see the timeline more clearly. They immediately embraced. Many felt that adding more tools, especially MS Project, just meant extra work without much benefit. It was initially seen as:

• Extra work

• Duplicate effort

• Something was removed from the ‘real’ delivery.

But then things started to change.

What Became Visible

As the plan came together, we noticed a gap in effort. Not in capability. But in flow.

The team had estimated the work well but what hadn’t been fully accounted for were the delays between steps:

• A developer completes work… and it waits for testing

• Testing completes… and it waits for review

• Review completes… and it waits for deployment

Individually, these delays seemed minor. Collectively, they were significant.

Just as importantly, we didn’t see these delays until we started looking for them.

Why This Mattered

Without that visibility, we would have continued to:

• Track effort

• Monitor completion

• And assume progress

All while losing time in the spaces between. MS Project didn’t just show us a timeline, it revealed a pattern we hadn’t seen before: systemic delay that could have pushed delivery beyond the deadline.

Once we could see the problem, we could manage it. People’s view of the tool changed quickly after that. From overhead… to insight.

Adapting Under Pressure

Halfway through delivery, we faced another challenge. An unexpected period of extended leave within a small, specialised team. No immediate backfill. Limited alternatives.

This is the moment when delivery plans really get tested. But in real life.

And at that point, there are only a few options:

• Push harder

• Add pressure

• Or make adjustments

We chose to adapt.

Reframing Success

Instead of sticking to the original plan, we redefined success. Not in terms of features, but in terms of outcomes.

What was essential to maintain business continuity? What could be deferred? What constituted a viable, stable solution within the timeframe? This led to a clear decision:

Deliver a true MVP

Not as a compromise, but as a careful, intentional choice.

What This Made Possible

By narrowing focus:

• The team maintained momentum.

• The critical path remained intact, and our delivery stayed focused on what mattered mosted most.

At the same time, we worked closely with the business to:

• Reset expectations

• Agree on a phased continuation.

• And ensure ongoing development beyond the deadline.

This wasn’t about lowering standards. It was about making sure we achieved the right outcome.

The Outcome

By the time the license expired, the organisation was prepared.

• Critical dependencies had been addressed.

• Business continuity was maintained.

• Three streams were fully delivered.

• One continued with an agreed extension.

And perhaps most significantly, the organisation avoided having to renew an expensive license that offered little value.

But Delivery Was Only Part of the Story

It would be easy to judge success only by what we delivered. But that would miss the real changes that happened. Because, alongside delivery, our capabilities grew in the Teams

Across the program, we saw:

• Leaders are evolving their approach to managing and enabling teams.

• Teams stepping into ownership, rather than waiting for direction.

• Individuals found chances to lead, no matter their title.

• Increased collaboration across roles and disciplines

And importantly, people became more confident in the organisation’s ability to handle complex delivery.

What Changed in the Environment

The conditions we created, both on purpose and in response to needs, made a difference:

• Flexibility in how people worked

• Space for teams to self-organise

• Support for those willing to contribute more

• Early experimentation with new practices and approaches

These changes weren’t official transformations, but they were meaningful changes. Shifts.

What Changed for Me

Taking on the Acting CIO role in these circumstances could have turned out in many ways. Without visibility, without context, without a defined starting point.

But through experience, structured thinking, and by applying Agile principles in a practical way, we were able to surface risk early, align the organisation quickly, and deliver under pressure.

But what mattered most wasn’t just the outcome. It was the trust we built along the way. From peers, from teams, from leadership.

Returning to the Basics

Looking back, this wasn’t about following a specific framework.The alignment is clear:

• Visibility over assumption

• Outcomes over activity

• Flow over effort

• Ownership over awareness

• Adaptation over rigidity

None of these ideas is new, but when things get tough, they make the difference between movement… and progress, activity… and delivery

A Final Thought

Leadership is often tested when the way forward isn’t clear. No handover, no roadmap, no certainty, just a situation that needs clarity, decisions, and action.

In those moments, it’s easy to look for answers. But the real work is something different.

It’s about creating the conditions where the right answers can come up
quickly enough to matter.

Series Close

Leading Without a Map has been a reflection on a real experience, not a perfect one, but a practical example of what happens when:

• Ambiguity meets urgency

• Risk meets accountability

• And teams are given the space to step forward.

Subscribe now

At some stage in every project, structure alone just isn’t enough. You can have:

• Clear workstreams

• Defined ownership

• Executive alignment

• Visible progress

Yet, it can still feel like something is missing. That’s because delivery isn’t only about what gets done. It’s also about how the work gets done and who takes the initiative to make it happen. It started to show as the program moved from planning into execution.

Where the Real Work Lived

At this point, two streams became the main focus:

• The replacement of intranet content and functionality

• The uplift of a legacy product constrained by outdated technology

Both were time-bound. Both were complex. Both required more than straightforward execution. They needed coordination, decision-making, and a kind of adaptability that process alone can’t provide.

When One Problem Becomes Two.

At first, the intranet work seemed like a single stream. But it wasn’t. Very quickly, it revealed two distinct challenges:

• Content that could be migrated relatively cleanly

• Functionality tightly coupled to the legacy licence

Each required a different approach. So, we decided to do this without formal processes or extra bureaucracy, but with clear intention.

• Content migration became a structured, business-supported effort.

• Functional components required deeper technical delivery and coordination.

This empowered and enabled both streams move forward quickly, without one holding back the other.

There’s a simple but important lesson here: when the nature of the work changes, the way you deliver should change too.

Constraint That Became the Opportunity

Within the technical stream, there was an established way of working. It had changed over time, shaped by what worked in practice. Work was typically assigned, decisions about who did what sat largely with the delivery lead. With the pressure of this program, that approach would be limiting.

This wasn’t a situation where one leader could or should make all the decisions.

Shifting the Dynamic

Rather than bringing in a new framework or forcing a process change, we chose a more practical approach. Changed how problems were presented.

Instead of assigning tasks to individuals, we began presenting problems to the team, and then we paused.

That pause matters.

That pause gives space for something different to happen.

What Happened Next

At first, there’s always a moment of hesitation.

People are used to being directed, used to waiting, used to being told where to focus.

But when people had space and clear goals, something shifted:

People started stepping forward.

Not all at once and not in a perfectly coordinated way, but enough.

And then more.

From Task Ownership to Shared Ownership

What happened next wasn’t just a change in how work was assigned. It was a change in how the team saw the work itself.

• Problems became shared challenges, not assigned tasks.

• Work progressed in parallel, not in sequence.

• Individuals began to take ownership of outcomes, not just activities.

And with that, something else happened: Momentum.

The Emergence of Micro-Leadership

One of the most interesting outcomes was what I’d call micro-leadership.

Individuals who weren’t in formal leadership roles began to:

• Step into coordination

• Guide small pieces of work.

• Support others

• And make decisions within their domain.

Not because they were asked, but because the environment made it possible. it.

These moments are easy to miss unless you’re paying attention. But they matter.

Because they’re often where capability grows the fastest.

Watching these moments emerge has been, and will continue to be, one of the most rewarding highlights of my leadership career.

A Different Kind of Coaching

During this phase, my role wasn’t to direct; it was to enable it.

That meant working closely with managers to support how they approached the work.

This included:

• Coaching on project structure and flow

• Supporting decision-making under pressure

• And, just as importantly, I challenged old patterns when they no longer served the outcome.

Evolving Leadership Styles

For the Software Delivery leader, this was a time to reflect.

The usual approach, which was more structured and directive, had worked before.

But in this situation, it was causing a bottleneck. We explored an alternative:

• Shifting from assigning work

• To help the team organise itself around the work wasn’t a theoretical conversation.

We put this into practice right away, and it had real effects. And the results spoke for themselves.

What Changed on the Ground

You could really feel the change.

• Work began moving faster.

• Multiple threads progressed simultaneously.

• Knowledge sharing increased naturally.

• And individuals gained exposure to areas they hadn’t worked in before. But maybe the biggest change was in the atmosphere.

There was energy. It was that feeling you get when a team isn’t just working,
but engaged.

Conversations were happening, problems were being solved collaboratively, people were leaning in. The team had something many aim for but rarely keep:

The buzz of a team performing at pace.

Supporting the Momentum

With that shift underway, the focus became:

How can we keep this going?

Two practical productivity-boosting decisions helped:

• Providing flexibility in how and where people work

• Offering paid overtime for those who wanted to and could contribute more, endorsed at an executive level, recognising the time-bound nature of the work.

But even more importantly, they sent a clear message:

We trust you to do what’s needed, and we’ll support you along the way.

Learning in Motion

While the team delivered, something else was happening too. The team was learning.

• New technologies

• Different parts of the system

• Alternative ways of working

They weren’t learning through formal training, they learned by doing.

And because the environment supported collaboration, that learning spread quickly.

More Than a Delivery Shift

It might be easy to call this phase a successful change in how we delivered. But that would miss the real point. The real change wasn’t just in how the work got done. It was:

• How people saw their role in it

• How leaders engaged with their teams

• And how ownership was distributed across the group

A Thought to Leave You With

There’s a common belief that structure creates high-performing teams. But it’s not enough.

Performance doesn’t come from control. It comes from:

• Clarity

• Trust

• And giving people the space to step forward. When teams are given problems to solve, not just tasks, they don’t just deliver. They grow.

Subscribe now

Clarity creates momentum, but only if you do something with it.

By this point, the situation had shifted. What began as a vaguely understood issue, something people noticed but did not address, was now clearly defined:

• A time-bound risk

• Executive-backed priority

• A non-negotiable outcome

We were no longer asking whether to act. We were asking:

How do we deliver this properly within the time we have?

The First Realisation: This Isn’t One Problem

There’s a tendency, when faced with something urgent, to treat it as a single piece of work: One issue, one solution, one plan. But that only works when the problem is simple. This wasn’t.

As we began to look more closely at the licence dependency, it became clear that we were not dealing with just one risk.

Instead, there was a network of dependencies spread across different systems, products, and operational processes.

Solving this took more than just effort, it required structure. This was about making the invisible visible.

The first step was to break the problem down into something we could actually work with. Not tasks, not technical components, but outcome-focused areas of work.

What emerged were five distinct streams:

• Data access and retention

• A customer-facing service relying on legacy functionality

• A legacy product constrained by outdated technology.

• A legacy intranet

• Remote access to critical files

Each of these represented something slightly different:

• Different stakeholders

• Different levels of complexity

• Different levels of risk

And importantly: Different paths to resolution.

Why This Step Matters More Than It Seems

At face value, this is a straightforward decomposition. But in practice, it does something much more important: it changes the nature of the work.

Instead of a single, overwhelming problem, we now had:

• Clearly defined areas

• Potential ownership points

• And the ability to move multiple streams forward in parallel

This is where delivery shifts from reactive… to intentional.

From Workstreams to a Program

With the work broken down, the next step wasn’t to start delivering immediately, it was to properly frame the work.

Because how you frame work determines how it gets prioritised, resourced, and supported.

So this wasn’t positioned as:

• A set of urgent fixes

• Or a collection of technical tasks

It became a program of work.

That distinction matters.

Programs:

• Create visibility at the right level.

• Enable coordinated delivery across teams.

• And signal importance to the organisation.

Most importantly, they create alignment of effort.

Gaining Momentum Through Sponsorship

Executive alignment had already been established. But alignment alone doesn’t drive delivery; momentum does. So the focus shifted quickly to:

• Confirming sponsorship

• Reinforcing urgency

• And ensuring that this work was seen for what it was:
  critical to maintaining business continuity

With that clarity, we had permission to move decisively.

Early Progress: Reducing the Problem Space

Before mobilising all five streams, we took a step back and asked:

Do all of these need to be solved in the same way?

Through collaboration between product and business teams, one of the streams was reassessed on its value to the business. Its dependency on the legacy environment wasn’t as fixed as initially assumed. There was an alternative. A workaround.

Not perfect, but viable, and … importantly, fast and endorsed by the users impacted.

That single decision reduced the program from five streams to four.

Why This Was More Than a Tactical Win

This wasn’t just about reducing workload. It demonstrated something critical:

Not every problem needs to be solved through engineering.

Sometimes, the fastest and most effective path comes through:

• Reframing the requirement

• Engaging the business differently

• And being open to solutions that sit outside the original system.

It’s easy to default to ‘build’ or ‘fix’. It’s harder, but often more valuable, to ask: Is there another way to achieve the outcome?

Establishing Ownership

With the program now defined and slightly reduced in scope, the next step was clear:

Ownership needed to be explicit.

Each stream required:

• A delivery lead

• A clear outcome

• And a shared understanding of urgency

This wasn’t about assigning accountability in a top-down way, it was about ensuring that every part of the program had someone:

• Thinking about it

• Driving it forward

• And surfacing risks early.

Because without that, even well-structured programs drift.

Creating Visibility (Again, But Differently)

As delivery began to take shape, visibility needed to evolve. The earlier “Now, Next, Later” view had helped establish understanding. Now, we needed something that supported execution.

So we introduced:

• Regular check-ins with delivery leads

• Structured reporting on progress, plans, and blockers

• Clear visibility of how each stream was tracking against time

And importantly:

We made the work highly visible across the organisation, not hidden in delivery tools, not confined to status reports. Visible.

Because visibility does two things:

• It drives accountability

• And it invites support where it’s needed.

Resisting the Urge to Over-Engineer

At this point, it would have been easy to introduce heavier governance.

• More reporting

• More structure

• More control

But that wasn’t what the situation needed. The timeline was tight, the work was complex, and the teams needed space to move.

So the approach stayed deliberately balanced:

• Enough structure to provide clarity

• Enough flexibility to allow delivery to adapt

If you are familiar with Agile practices, you know that effective delivery happens in the space between governance and autonomy.

Where Leadership Starts to Shift Again

With the program in motion, something subtle began to change. The problem was no longer abstract, the work was no longer theoretical, it had become:

• Real

• Visible

• And shared

And that’s the point where leadership shifts again: from defining the problem… to enabling the people who will solve it.

A Thought to Leave You With

Breaking a complex problem into parts is a familiar concept, but doing it well, especially under time pressure and with real consequences, takes more than just technique. It requires judgment.

How you define the work shapes everything that follows:

• Who owns it

• How it’s delivered

• And whether it succeeds

Structure doesn’t slow delivery, the right structure makes it possible

Subscribe now

There’s a moment in most complex environments where something shifts: not visibly. not dramatically, but just enough that, if you’re paying attention, you feel it.

It’s the point where patterns stop being abstract… and start pointing to something real. That moment came not through a single conversation, but through several:

• Different managers

• Different contexts

• Different pieces of work.

And yet, the same thing kept coming up quietly, almost as an aside.

‘Yes, we’re aware of that…’

It wasn’t raised as a risk. It wasn’t escalated as a concern. It surfaced more as background noise: ‘Yes, we know about that…’, ‘That’s coming up…’, ‘We’ll need to deal with it…’

Individually, these comments didn’t stand out. Collectively, they told a very different story: There was a licence due for renewal/expiry in three months.

At one point, it had been essential because it supported a core product used throughout the business. But that product had since been transformed. Rebuilt. Replaced. On the surface, it looked like the organisation had moved on.

In reality, it hadn’t.

What Gets Left Behind

Transformation often focuses on what’s new:

• New platforms

• New capabilities

• New ways of working

So, when you consider transformation, remember: what’s left behind - these unaddressed dependencies - can create operational risks as significant as any new system or process. Because rarely does everything move at the same pace.

In this case, several systems - and some important operational capabilities - still depended on that licence. Because over time, dependencies had become:

• Embedded

• Assumed

• And eventually, invisible

Until something forced them back into view.

The Gap Between Knowing and Acting

By this point, it was clear that multiple people knew about the licence but no one had fully stepped up to resolve it.

This is where organisations can get caught in a very specific gap: not a gap in knowledge…

A gap in ownership.

Because when something spans teams and touches multiple systems, products, and priorities, it can quietly become everyone’s problem.

And in doing so, it becomes no one’s responsibility.

Why This Happens (More Often Than We Admit)

There are a few patterns that tend to show up in situations like this:

• The original context is no longer current

• The ownership model hasn’t evolved with the architecture

• The work required cuts across multiple teams

• And the effort to resolve it feels… inconvenient

Not impossible, just complex enough to delay.

It’s acknowledged. It’s remembered. But unless someone mobilises action, this important issue remains unresolved - and the risk of inaction grows closer.

And time continues to move.

Reframing the Conversation

At this point, there were two possible ways to approach the situation:

Treat it as a technical clean-up or recognise it for what it actually was:

A time-bound business continuity risk

The distinction matters because technical problems can be deprioritised but business risks can’t. So the conversation shifted.

Not:

• ‘We have a licence expiring’

But:

• ‘In three months, parts of the business will lose access to capabilities they still rely on’

And:

• ‘We have a limited window to either remove that dependency - or accept a significant cost increase for questionable value’.

That reframing ensured the issue was treated as a business-critical risk, leading to clear prioritisation and action.

The Decision Landscape

Once surfaced clearly, the options became more explicit:

Renew the licence

• At a significantly increased cost

• With a cost-to-value ratio that no longer made sense

Detangle the dependencies

• Across multiple systems

• Within a fixed timeframe

• With no pre-existing coordinated plan

Neither option was trivial.

Only one option matched the organisation’s strategic direction, highlighting the importance of aligning technical choices with business goals.

From Awareness to Accountability

At this point, the role of leadership isn’t to solve the problem immediately, it’s to create clarity and secure alignment. So the next step was to bring this into the right forum:

• Executive leadership

• Not with technical detail

• Not with a fully formed solution

But with a clear articulation of:

• The risk

• The timeframe

• The decision required

• And the consequences of inaction

What followed was exactly what was needed:

• Sponsorship

• Priority

• Urgency

And just as importantly:

Permission to act decisively.

The Moment Ownership Becomes Real

There’s a subtle but important shift that happens when something moves from:

‘Something we know about’ to ‘Something we are now responsible for delivering’.

You can feel it. The conversations change, the focus sharpens, the edges of the problem become clearer. Because now, it’s not theoretical, It’s real work with a real deadline.

But Clarity Isn’t the Same as Simplicity. At this stage, we had:

• Visibility of the issue

• Executive alignment

• A clear direction of intent

What we didn’t yet have was:

• A defined path forward

• A structured plan

• Or a clear understanding of how deeply embedded the problem actually was

Because the next step wasn’t just to act, it was to understand what we were truly dealing with.

This deliberate assessment of the problem laid the foundation for a solution optimised for business continuity, not just technical completion.

A Thought to Leave You With

In many organisations, the biggest risks aren’t hidden. They’re known, discussed, even accepted. But without clear ownership, they sit in a kind of operational limbo: visible, but unmoved. Until time runs out.

Awareness creates comfort.
Ownership creates action.

In summary: leaders identify risks, assign clear ownership, and transform organisational awareness into decisive action. That is when knowledge becomes results.

Subscribe now

There’s a particular kind of leadership moment that doesn’t come with a briefing pack.

• No handover

• No documentation

• No tidy list of priorities waiting to be picked up and progressed

All I had was a role, some expectations, and a real sense of urgency to get up to speed quickly.

That was the situation I stepped into when I took on one of my leadership roles.

Moments like this reveal more about an organisation’s strengths and weaknesses than any formal strategy document. So, if you don’t start with information at your fingertips, what do you do next?

The Illusion of ‘No Information’

On the surface, there was no visibility.

• No single view of work in progress

• No shared roadmap

• No clear articulation of priorities across teams

But over time, I’ve learned something important: organisations rarely lack information - what they really lack is connected information. With that in mind, I considered where to begin building that connection.

The knowledge was there. It just wasn’t in one place.
It lived in conversations, in individual team backlogs, in half-formed plans, and in people’s heads.

When information is scattered like this, leading becomes a guessing game. So it’s critical to choose your starting point carefully.

Where You Start Matters

There’s a natural instinct in these situations to go hunting for artefacts: plans and reports, dashboards, anything that gives a sense of control.

But artefacts without context can mislead just as easily as they can inform.

So I started with something far more reliable: people; and this shifted the entire approach.

I met with each manager individually. These weren’t formal interviews or status checks, but conversations meant to build a clear picture.

I asked three simple questions:

• What is your team working on now?

• What’s coming next?

• What’s on the horizon for later?

And then I asked the question that tends to unlock everything else:

Why do these things matter?

From there, the conversation naturally expanded:

• What are your timeframes?

• What’s getting in your way?

• What are you worried about?

• What do you need from me?

What came out of these talks wasn’t just a list of tasks. It was context. It was intent. It was pressure points.

And importantly, it was the beginning of alignment.

This alignment would prove crucial to navigating uncertainty and driving organisational progress. But what made these conversations more valuable was their impact beyond discovery.

More Than Discovery

At face value, this might look like a simple discovery, but it’s more than that.

This is where real leadership begins to take shape.

Because in asking those questions, a few things happen simultaneously:

• Teams begin to clarify their own thinking.

• Priorities become visible beyond Leaders, and Leaders also notice where work overlaps, where conflicts arise, or where gaps exist or are left.

It’s not a workshop, it’s not a framework rollout.

It’s actually much more practical:

A shared understanding forming in real time.

If you compare this to formal practices, it’s similar to Agile portfolio thinking:

• Surfacing work

• Understanding value

• Spotting dependencies

But in reality, it doesn’t start with tools, it starts with a conversation.

The First Signals of Risk

As these conversations progressed, patterns began to emerge.

Some were expected:

• Teams focused on their own domains.

• Limited visibility of cross-team dependencies

• Competing priorities without a clear mechanism for alignment

But there was something, the kind that never appears in a report but sits just below the surface. just beneath the surface.

There was an issue that multiple people were aware of.

Not urgently discussing, not actively progressing. Just… aware.

And in complex environments, that’s often where the real risk lives. Moving from shared awareness to real ownership became essential.

Shared Awareness Isn’t Ownership

One of the more subtle challenges in leadership is recognising the difference between:

• Something that is known, and

• Something that is owned

Because those are not the same thing. In fact, they can sit dangerously far apart.

What I was beginning to see was a pattern of distributed awareness without coordinated action.

No one was ignoring the issue, nut no one had fully stepped up to resolve it either.

And without making that shift from awareness to ownership, time quietly slips away. This made me realise the need for visibility before seeking solutions.

Creating Visibility (Before Creating Solutions)

Before jumping into solutions, I needed a way to make the emerging picture visible. Not just for me, but for everyone. So I created a simple, physical representation of what I was hearing:

A Now / Next / Later view of work across the function.

Nothing complicated, no tooling, no formatting perfection. Just clarity. Making this visible invited feedback and sparked collaboration.

I put it on the wall in my office and invited people in:

“Come and have a look. This is what I’m seeing - tell me what’s missing” and something interesting happened:

• People engaged

• They challenged it

• They added to it

• They connected dots

What started as a personal sense-making tool became a shared artefact of alignment.

It didn’t stay physical for long. As it became clear that more people needed access, especially hybrid team members, we moved to a digital version using our existing tools, but the principle stayed the same:

Make the work visible, and conversations improve.

Before the Problem Fully Reveals Itself

At this point, I had something I didn’t have before:

• A cross-functional view of work

• A growing sense of priorities

• Early signals of risk

But the full shape of the problem hadn’t revealed itself yet. That came next, and it came quickly.

A Thought to Leave You With

Stepping into a leadership role without context can feel like starting from zero. But it rarely is.

• The information is there

• The signals are there

• The risks are already in motion

The essential question is: how quickly can you turn scattered knowledge into shared understanding?

Because that shift, from scattered to shared understanding, is when leadership moves from being reactive to intentional.

Subscribe now

The moment everything tilts

There were days I wanted to throw my hands up in the air but, as a resilient and proud person, I felt that I couldn’t and shouldn’t do that as it might influence others.

Ultimately, I started to notice the toll this behaviour was having on my health and on how I was turning up for others and myself. I realised the trick was to listen to what that feeling was trying to tell me, then turn it into an operational change.

What’s at stake (for me)

The journal I kept has been a mirror. Looking back over it has revealed patterns worth keeping, and a few I’m done with.

The moment of decision

I decided to keep the structures that made me steadier, kill the habits that drained me, and start a couple of practices I wish I’d adopted sooner.

What I did (the playbook)

Keep

Journals, one board, evaluation days, humane rhythms.

These are all practices that helped me maintain a routine and to put one foot in front of the other and keep moving forwards. They also helped me focus on the things that I could control in the face of the looming threat that I had no control over.

Kill

Applying for jobs when I’m tired - if I wanted to put my best foot forwards, then applying for positions when my attention span and quality levels are drifting is not the way to do it.

Trying to be everyone else’s pillar of strength without being that for myself. Ultimately, this started to take its toll and I had to take some personal leave to create space. Definitely put your own oxygen mask on before helping others with theirs

Start

Know your boundaries and don’t be afraid to set them kindly and professionally early on in the piece. I don’t regret the conversations that I had with the people who sought me out for them but I do regret not taking a beat to consider my own needs and how I could fulfil them.

I wish I’d realised that a redundancy payout doesn’t necessarily equate to just your notice period and whatever leave you have owing. Often, contracts and enterprise agreements have a schedule for termination payments. Understanding this and asking for a figure from HR materially influenced my decisions - forewarned is forearmed as they say.

What surprised me

• How much consideration I was giving to others, at the cost of considering my own needs

• Listening to anger and fatigue as signals changed my calendar for the better

• Just how crappy I can let quality of applications get when I’m tired

Leader’s Lens: If you manage people through change

• Help teams build ‘keep/kill/start’ lists post‑announcement to regain momentum.

• Protect recovery the same way you protect delivery.

Diary excerpt (lightly edited, anonymised)

“I have been spending so much time having conversations all around that today my tongue and my throat are so sore that I can’t speak without pain. I can’t even begin to think about trying to support other people when I clearly need to take better care of myself.”

Stage of Grief

Resurrection, Reconstruction

Try this (this week)

• Write your own keep/kill/start for the next 4 weeks.

• Share it with one person who can hold you kindly accountable.

Checklist

□ Keep: journals • one board • evaluation days.

□ Kill: late‑night apps • heroics.

□ Start: set boundaries • early money chats.

If your organisation is navigating change and you want calm, people‑first delivery without the drama, I can help.

This is based on my personal experience, anonymised to protect privacy. Nothing here is financial, legal, or medical advice - please seek professional guidance for your own situation.

Subscribe now

The moment everything tilts

When the feeds got noisy and stale, I stopped grazing and built a ritual. The signal returned as soon as I did.

In those early days of job searching across various platforms, I felt busier in redundancy than I ever had while employed.

I also felt overwhelmed.

There’s so much to navigate and it’s easy to underestimate the amount of time, mental, and emotional effort that goes into the search and application process.

I knew that if I wanted to have some healing and rest and relaxation time in my days, I would need to find a repeatable process that would dull the roar.

Context — what’s at stake (for me)

Recommendation engines aren’t optimised for your sanity. I wanted a rhythm that created progress on demand.

I’m an advocate for reminders for job search filters but LinkedIn in particular didn’t seem to be very intuitive. In fact, after a week or so tweaking and saving searches in LinkedIn and battling with its AI suggestions, I strongly believe that LinkedIn’s Product and Development teams have left the building. Who signed off on that monstrosity of an experience? And what’s with all the ghost posts?

Of course, being in the position of no longer casually looking for a new gig puts a different spin on things and I continued my LinkedIn dance battle because… well… what were the other options?

The moment of decision

I chose one board, clear columns, and a short daily loop to track applications and avoid confusion and duplicity. I added regular evaluation days to prevent backlog bloat1.

What I did

Now, I can see that some people might think that I went overboard with this and maybe, in some ways, I did. I was still in work mode, flexing the brain muscle in delivery mode, yearning for a repeatable process.

One memory that stuck with me from a previous (recent) job search endeavour was how difficult it became to track where applications were up to, whether I’d reviewed a posting before and discarded it (and why). I wanted to be able to hop back to a job post to review the job description again if needed or pick up where I’d left off.

That’s how I decided on a kanban board to track my applications and jobs I was interested in2. I wanted a process where I could skim through job posts quickly over coffee and then triage them later. In my triage, I would triage them again - discarding the posts that didn’t resonate and progressing the ones that I would apply for.

I also used it as an opportunity to capture data based on my own evidence as I knew I would be writing a blog series and it might come in useful.

Board & columns

Kanban board with columns for each stage of an application’s journey, from search to a natural conclusion (employment offer or rejection)

Saved • For Evaluation • Applying • Interviewing • Offer • Unsuccessful - Confirmed • Unsuccessful - Unconfirmed.

Daily triage (45 - 60 mins)

My daily process became quite simple: check my emails based on my saved filters, click through on job postings that were interesting, hit ‘Save’, move on.

I’d then go into my saved jobs section in either Seek or LinkedIn and create a card for each saved item and a link to the post.

I’d also triage any movement in my existing applications such as rejections or request for a screening call.

That was it. If I wanted to do more on any given day, then I could. If I didn’t, I could pick up where I’d left off quite easily with minimum effort.

Seek email → LinkedIn email → create/update one card per role3.

Evaluation day

On one day (perhaps one where I’d taken a break to breathe fresh air and not job hunt) I checked in on my backlog of potentials to find there were 45 of them in there!

That was the day I realised I should have more than one evaluation day!

I reviewed the 45 (quite ruthlessly due to the overwhelm) and reduced it down to a viable 10 posts. Decide deliberately or unsave ruthlessly. Evaluation day is also application day for me so strike while the iron’s hot and send off the applications at the same time (not forgoing my stop rules and quality over quantity).

Stop rules

No late‑night applications; remove duplicates; document cut‑offs on the card.

Don’t apply for jobs when you’re tired. If midnight is your time, go for gold. It isn’t my time though and I recognised when tiredness was creeping in (or monotony) and stepped away.

I also found through my process that the same jobs are often posted more than once or… worse, I had unsaved a job only to be attracted to it at a later time. My process helped me notice these more and save myself some time. If there was something particularly noticeable about the post that caused me to demote it in the list, I would capture that on the card before archiving it.

What surprised me

• Manual search beat algorithmic ‘recommendations’ by a mile.

• A single evaluation day reduced stress all week but caused its own stress with an overwhelming backlog and stealing time that I could be using to apply for jobs or do something much more interesting and meaningful.

• Ghost postings. I realised it before I started seeing the LinkedIn community complaining about them. What an absolute time-waster for people looking for a job and, in my opinion, quite insensitive to the current climate.

Leader’s Lens: If you manage people through change

• Share a basic search rhythm with impacted staff; structure returns agency.

• Reward process quality, not volume of applications.

Diary excerpt

“Today I opened Trello to evaluate and apply for viable jobs in the list. I don’t know how it got to 45 but bloody hell! Managed to whittle it down to 10 but there’s a couple of hours of my life that I won’t get back. NTS: make more time for evaluation days ‘cos that sucked!”.

Stage of Grief
Resurrection, Reconstruction

Try this (this week)

• Block 45 minutes for a triage session tomorrow.

• Book next week’s evaluation days (90 minutes).

Checklist

□ Kanban Board set with six columns.

□ Labels for Source/Priority/Status added.

□ Triage loop written down.

□ Evaluation checklist saved.

If your organisation is navigating change and you want calm, people‑first delivery without the drama, I can help.

This is based on my personal experience, anonymised to protect privacy. Nothing here is financial, legal, or medical advice - please seek professional guidance for your own situation.

Subscribe now

The moment everything tilts

I started building the series before I had a perfect view of the horizon. It felt premature and also completely right - momentum reveals the map.

I had considered consulting and contracting one of my ‘back-up plans’, not my main goal. It wasn’t until a very personal revelation changed my perspective on this and made me believe that consulting could possibly be my main plan.

What’s at stake (for me)

My strengths show up in stabilising, structuring, and pacing. The offer needed to reflect that without promising transformation theatre. I love what I do, no matter where that is and I knew that I wanted to keep doing it, I started thinking about my options for the future and their viability.

The moment of decision

Part of the redundancy arrangement was a number of hours with a career transition coach who validated the consulting thought.

The ultimate moment of decision came when I revisited an old decommissioned website and saw the previous coaching series I’d created in there but had retired. My service offerings started to cement themselves.

What I did

Service Offerings

I set to work straight away, building out my service offerings - what am I great at, where have my tangible successes landed, what do I want to do (and, importantly, what don’t I want to do).

LinkedIn

I radically adjusted my LinkedIn profile to present as a consultant. This included trimming some of the extra content that didn’t add the value it once did and a pragmatic review of top skills to align with my service offerings (which they did already but weren’t presenting that way to the public)

Network Building

I reached out to people in my network, not to ask for jobs but to shout them a coffee and get to know them and for them to get to know me. A resume or LinkedIn profile will never do me the same justice as I can do myself by just showing up.

Started a Campaign Calendar

11 years in a Marketing-as-a-Service agency and social media management for my own ventures taught me the values of planning your campaigns months ahead, leveraging the low-hanging fruit of public holidays, familiar celebration dates and so on. I gathered my themes and thought about what my strategy would be. Then I started to implement it.

What surprised me

• Starting my processes early created options I couldn’t see from the sidelines.

• Refactoring in public built trust faster than polished decks.

• How much fun it can be (and time-consuming) learning new skills for marketing your services and your ‘voice’

Leader’s Lens: If you manage people through change

• If you need interim calm, try a single stabilised period of time before asking for big commitments.

• Ask for artefacts, not adjectives.

Diary excerpt (lightly edited, anonymised)

“The hustle to get things ready ahead of time to clear the way for the meaningful days of redundancy is starting to ease off. There is a decreasing amount of work to do and my thoughts are turning away from a future here towards my own future, one that’s bright and exciting.”

Try this (this week)

• List three strengths and think about what service offering you might be able to turn them into.

• Connect with your network, shout them a coffee

Checklist

□ Service offerings drafted

□ Coffee dates organised

□ Networking event tickets acquired

If your organisation is navigating change and you want calm, people‑first delivery without the drama, I can help.

This is based on my personal experience, anonymised to protect privacy. Nothing here is financial, legal, or medical advice - please seek professional guidance for your own situation.

Subscribe now

The moment everything tilts

A rejection landed on a day I’d already labelled ‘backlog day.’ It stung, and it also gave me data. Later, a tired‑day cover‑letter glitch reinforced a simple rule: exhausted me shouldn’t apply.

What’s at stake (for me)

My nervous system doesn’t care about my calendar. Healing meant designing around capacity, not pretending I had more than I did.

The moment of decision

I created humane rhythms: nightly cut‑offs, rest days, and small, consistent prep. I treated interviews like delivery ceremonies - steady, not heroic.

What I did

Nightly cut‑offs

Pick a time. After it, no applications, no drafts, no edits.

Rest as prep

If the day is heavy, switch to low‑effort tasks and protect tomorrow.

Day‑before script

30‑minute research refresh, 10‑minute logistics check, then stop.

Post‑interview notes

Three bullets: what worked, what to tweak, one question for next time.

What surprised me

• My interview presence improved more from rest than from extra bullet points.

• Treating rejections as data kept me moving without spirals.

Leader’s Lens: If you manage people through change

• Share an interview plan early and stick to humane timings.

• Offer async options for materials where possible.

Try this (this week)

• Set a hard application cut‑off tonight.

• Write a 3‑line day‑before checklist you’ll actually use.

Checklist

□ Cut‑off time added to calendar.

□ Day‑before checklist saved.

□ Template for post‑interview notes ready.

□ One planned rest block in the next 7 days.

If your organisation is navigating change and you want calm, people‑first delivery without the drama, I can help.

This is based on my personal experience, anonymised to protect privacy. Nothing here is financial, legal, or medical advice - please seek professional guidance for your own situation.

Subscribe now

The moment everything tilts

I used to keep multiple versions of my resume to ‘cover bases.’ It actually diluted my story and was difficult to maintain. The fix for me initially was radical simplicity: one master version, one truth, tailored as needed.

What’s at stake (for me)

When everything is changing, version sprawl adds confusion. I wanted a workflow that reduced decision fatigue and preserved tone.

The moment of decision

I kept one resume, updated the headline, and, for the most part, tailored through cover letters and selection criteria only. AI helped surface strengths and I rewrote in my own voice.1

What I did

One master resume, tailored and copy saved

Maintain a single source of truth.

I would start each application from that resume and make changes to it, saving it as a new version but only for reference in the future. I’d save the tailored version with the cover letter in a specific folder and/or attached to the job card I’d created in Trello. Not being that organised previously had diluted my resume content away from my core experience, achievements etc.

Tailored cover letters

Highlight role‑specific proof points in human language.

There is a lot of chatter in LinkedIn circles over using AI for job applications - most of it negative as far as I’ve seen. I use AI as an assistant, especially when I’m struggling to leave the runway on an application or cover letter.

What I don’t do with AI, is expect it to be me. I take the highlight reel I’ve asked AI to present and I weave the pieces I want to talk to into my own narrative in the resume or cover letter.

Application tracker

Board columns: Saved • For Evaluation • Apply • Interviewing • Offer • Unsuccessful.

Quality guardrails

No applications when tired; Grammarly or a buddy check on content.

What surprised me

• The one‑resume rule sped everything up and reduced errors.

• Tailored cover letters carried more signal than tweaking bullet points.

Leader’s Lens: If you manage people through change

• Provide a minimal tracker template for impacted staff.

• Remind teams: voice and impact first, tools second.

Diary excerpt (lightly edited, anonymised)

“I updated my LinkedIn headline today with some refreshed text. Although it wasn't so long ago that I reviewed my resume, I reviewed it again to ensure it was ready for the jobs I intend to apply for.”

Thought of the Day
“Now that my Trello board is up and running for job applications, I switch my focus to following the steps of my new process”.

Stage of Grief
Reconstruction & Working Through

Try this (this week)

• Archive duplicate resumes. Keep one. Use it as your master copy

• Write a fresh LinkedIn headline that reflects your current value.

• Stand up the simple tracker board.

Checklist

□ Single resume updated.

□ Cover letter template ready.

□ Board set with six columns.

□ Cut‑off time set for applications.

If your organisation is navigating change and you want calm, people‑first delivery without the drama, I can help.

This is based on my personal experience, anonymised to protect privacy. Nothing here is financial, legal, or medical advice - please seek professional guidance for your own situation.

Subscribe now

The moment everything tilts

There was a moment in the lead up to confirmation of my redundancy where I felt like a spare part, in some ways it felt as though I was already gone I just didn’t know it (although I think I did). No one meant harm I’m sure, but the experience landed sharply and it was difficult to process. Ultimately, I realised I could either internalise it or respond professionally and keep my own story intact.

What’s at stake (for me)

I’ve never believed a title defines a person, and yet the mind does funny things under stress. Everyone felt weird - those who had received the news that they may be out of a job in the coming weeks, and those who operated beside them. It was really challenging to separate my sense of self from the position title that was being made redundant. The key for me was to remember value through outcomes, not labels.

The moment of decision

I decided to keep a ‘value file,’ to log evidence instead of adjectives, and to write a new narrative that didn’t require anyone else’s permission.

What I did

Part of my process in revisiting my resume and job search profiles had been to leverage AI agents to help me draw out areas to focus on. Unexpectedly, not only did the exercise produce starting points for resume and cover letter revisions, but it also proved a great exercise in validating my experience, knowledge, and reminding me of my successes in the face of what currently felt like failure.

Value mapping

List five business outcomes you deliver (not duties). Read them when the title voice gets loud or, as a dear family friend once told me as I left the country to move to Australia… ‘don’t forget where you come from’.

Evidence over adjectives

Collect artefacts: before/after snapshots, one‑page summaries, stakeholder notes - when I say collect, I don’t mean ‘steal’, I mean write your own notes, create your own summaries, think about the impact you made, and sure, ask people if you can use their part in your story.

Like a muscle memory, the more you do this, the easier it will get. Think of the impacts you’ve made, journal them, keep them handy so you can refer to them easily in the future. So many times we forget the twists and turns in our journey and focus on the destination, when the journey itself is often the interesting part.

Professional responses

When something stings, draft the response you’ll be proud of in six months. Then send that one.

I learned to do this over the duration of my career, through making mistakes or exercising poor judgement but if we know ourselves and how we react under stressful circumstances, we already have a head start.

Think about the scenarios that could occur and how you might be feeling. Do you want to burn bridges? If not, think about how you would like to act in those scenarios and prepare your response ahead of time. This isn’t about what people are going to say to you - that’s outside of your control - it’s about how you choose to respond and it can only be a choice if you’ve thought about it at least a little bit.

Identity language

Swap “I was [Title]” for “I help [audience] achieve [outcome].”

This was a piece of advice that I picked up from some recruiter associates. Think about the value you provide, and if you can quantify that value then even better.

Again, the more you think about this stuff, the more it becomes validating and self-perpetuating. The opposite of negative self-talk.

What surprised me

• The title voice is persistent but not powerful when confronted with proof.

• A small repository of wins did more for my confidence than any pep talk.

Leader’s Lens: If you manage people through change

• Reinforce value stories in check‑ins. Speak to outcomes, not roles.

• Depersonalise structural change without trivialising the impact.

• Don’t underestimate the power of your words and your actions

Try this (this week)

• Write a three‑line value bio that never mentions a job title (don’t be afraid or ashamed of letting AI help draw out your strengths when you’re not seeing them for yourself).

• Start a value file with two artefacts today.

Checklist

□ Five outcomes listed (value map).

□ Two artefacts saved (evidence file).

□ One professional response drafted (if needed).

□ Identity language updated in your notes.

If your organisation is navigating change and you want calm, people‑first delivery without the drama, I can help.

This is based on my personal experience, anonymised to protect privacy. Nothing here is financial, legal, or medical advice - please seek professional guidance for your own situation.

Subscribe now

The moment everything tilts

There was a day my tongue felt sore from all the talking - everyone needed something. I gave what I could, but the bill arrived the next morning: a headache, a fog, a simmering frustration with myself.

What’s at stake (for me)

I’m proud of being available. Redundancy tested that pride. The question shifted from “Can I help?” to “How can I help without emptying the tank?”

The moment of decision

I chose to treat boundaries as professional tools. I capped ‘heavy conversations,’ wrote pause scripts, and asked my GP for support when capacity was depleted. It was not an admission of defeat; it was an act of leadership.

What I did (the playbook)

Conversation caps

Decide the number you can carry today (e.g., three). After that, everything moves to tomorrow.

Kind pause scripts

“Thanks for checking in - taking a small pause today and will reply when I’m able.” Save it as a text expander.

Authorised rest

If your body is sounding alarms, see your GP. The external permission (via a medical certificate) from my GP turned guilt into space to recover.

Evening cut‑offs

No applications after a certain hour. Tired me makes errors future‑me has to clean up.

Recovery rituals

Walks, simple food, heat pack, early shower - quiet choices that pay back tomorrow.

What surprised me

• People responded well to honesty. Most were relieved to be told what to expect.

• Rest helped conversations the next day land better - for both of us.

• A single cut‑off time improved quality more than any productivity trick.

Leader’s Lens: If you manage people through change

• Model pause scripts. If leaders can rest, others feel safe to do it too.

• Offer alternatives: “I can’t do today, but here’s when I can.”

• Call out over‑functioning in kind, specific ways and offer cover so people can step back.

Diary excerpt (lightly edited, anonymised)

”Today I’m sad. My team is usually such a driven and purposeful, ever-moving force.”

Thought of the Day
When everything feels like an uphill struggle, just think of the view from the top.

Stage of Grief
Reconstruction & Working Through

Try this (this week)

• Write one boundary line you can copy/paste today.

• Set a realistic nightly cut‑off time for applications.

• Book a GP consultation if your body has been sounding alarms.

Checklist

□ Conversation caps (number for today).

□ Pause script saved and ready.

□ Evening cut‑off in calendar.

□ Recovery ritual chosen (15–20 mins).

□ GP support if capacity is depleted.

If your organisation is navigating change and you want calm, people‑first delivery without the drama, I can help.

This is based on my personal experience, anonymised to protect privacy. Nothing here is financial, legal, or medical advice - please seek professional guidance for your own situation.

Subscribe now

The moment everything tilts

I opened a blank sheet past midnight and wrote real numbers. Not the version I hoped for: the version I could live with for a quarter1. Three months is close enough to feel real and long enough to stop me from making fear‑based purchases.

What’s at stake (for me)

Between sole‑trader instincts and job‑seeker realities, the goal was runway (how long I can comfortably operate before the money runs out) and optionality. I wanted decisions I could stand by a month later, not 24‑hour lurches or costly mistakes made with from a finite bucket. That meant treating money like a project: small scopes, clear checkpoints, no drama.

The moment of decision

I chose to ask for facts early - severance estimates, leave balances - and to time any investment (like certifications) to when it served the plan, not the panic. EOFY and actual demand mattered more than my inner shopper.

What I did

Calculate a three‑month baseline

List fixed bills, essential variables, and a modest buffer.

Request a payout estimate

Ask payroll/HR for a best‑effort figure. Replace rumination with ranges you can plan from. Gap analysis between buffer needed and actual buffer.

Freeze and funnel

Pause non‑essentials; funnel savings into runway. If something returns energy or saves time, keep it deliberately (if its affordable).

Weekly money check‑in

15 minutes, same time each week. Update the snapshot and note any changing assumptions.

What surprised me

• Seeing the real number hurt less than avoiding it. The sheet made me generous to future‑me.

• Talking to the bank early will feel relieving. Clarity can feel respectful on both sides.

• A small, planned spend (that saved hours) beat a big comfort purchase every time.

Leaders Lens: If you manage people through change

• Offer a neutral explainer for severance/leave mechanics early; it lowers speculation.

• If possible, allow staff to request estimates privately without pressure.

• Point to independent financial counselling/EAP resources and normalise using them.

Diary excerpt

“I'm at that point in the process where I'm loathed to start on anything new, given the uncertainty ahead.”

Thought of the Day
In times of uncertainty, the best thing we can do is to remain curious, seek clarity, and prepare for what comes next.

Stage of Grief
Testing, Uncertainty

Try this (this week)

• Book 45 minutes to create a one‑page runway plan.

• Email HR/payroll with a kind, clear request for estimates.

• Make one keep/kill decision on subscriptions today.

Checklist

□ Snapshot: fixed, variable, buffer for 12–13 weeks.

□ Ask for payout estimate (incl. leave).

□ Pause non‑essentials; mark one deliberate keep.

□ Cert/tool grid: Time • Demand • Value • Fit.

□ Weekly 15‑minute money check‑in.

If your organisation is navigating change and you want calm, people‑first delivery without the drama, I can help.

This is based on my personal experience, anonymised to protect privacy. Nothing here is financial, legal, or medical advice - please seek professional guidance for your own situation.

---

Subscribe now

The moment everything tilts

The announcement came with that particular hush a room gets when everyone is pretending to breathe normally. Words like “consultation” and “restructure” were said out loud, but the feeling arrived first: a drop in the stomach and a rush of heat to the cheeks. I was surprised by the mix - sadness, embarrassment, protectiveness for others, and the instinct to be useful.

Later that day, came the email confirming that my position was one of several that was at risk of redundancy.

What’s at stake (for me)

I’m a delivery‑minded, people‑first operator. I like clear backlogs, honest conversations, and structures that reduce chaos.

Redundancy tugged at identity and responsibility. The first 72 hours were about answering those questions without making irreversible moves or writing a narrative I’d later regret.

The moment of decision

I decided to lead myself the way I’d lead a team through incident response: stabilise first, then plan. No public posting, no diagnosing anyone else’s motives, and no big financial or career decisions while my body was still shaking off adrenaline.

While there was to be a consultation period, I knew that this outcome was one that I had little influence over and posturing it that way in my mind was the kindest thing I could do for myself because while I wasn’t focusing on this thing I couldn’t control, I had all this time to focus on the things I could control and that felt empowering.

What I did

Ground the body before touching the inbox

Walk. Hydrate. Write one honest journal entry - no editing, just “what I feel / what I know / what can wait.” Name the feelings so they stop trying to drive.

Being no stranger to a journal, I decided to keep a journal of the journey for no other purpose than to emotion-dump and gain clarity.1

My mind would revolve like a referdex resurfacing all the things I had to think about but the journal helped to get them out of my mind so my subconscious didn’t keep trying to remember them for me.

Set kind, clear boundaries

Support people who need a human, but cap heavy conversations2. Use a pause line that keeps the door open without sacrificing my own recovery.

Create space for yourself (within reason and boundaries of your employment) through out of office replies that are written when you’re thinking clearly without an overflow of emotion or through scripts that you can just copy and paste without burning any bridges.

Capture the journey while it’s fresh

I started journalling - not to publish, just to keep a true record when memory gets fuzzy. Note dates and small facts and intentions so you can drop them from memory but return to them later.

Stand up a single “72‑hour board”

I created a Trello board, with four lists: Admin • Money • People • Options. Each list gets 3 items max. If a task feels big, halve it; if it still feels big, halve it again. I used Atlassian’s free products but there are plenty of options that might work better for you. Sticky notes or index cards work just as well.

Defer irreversible decisions

No late‑night applications. No rewriting the whole CV that evening. If something feels urgent, I asked myself what would happen if I didn’t do it right there and then.

Protect next week’s energy

Book two job‑search blocks, one portfolio block, and one wellbeing block (don’t drop the wellbeing block)

What surprised me

• Embarrassment showed up even though I know better. Naming it reduced its power.

• Journaling calmed my body. Not because the situation changed, but because I wasn’t carrying it all in my head.

• Tiny systems beat heroic effort. A four‑list board outperformed frantic productivity.

• Kindness can be loud. Accepting help can make the next step lighter.

Leader’s Lens: If you manage people through change

• Say the quiet part out loud: “This is hard. Here’s what we know and what we don’t.”

• Offer practical anchors (EAP/GP info, timelines, what the next two weeks look like).

• Open brief office hours for questions; don’t force one‑on‑ones if people need air.

• Share a simple checklist for the first 72 hours. Structure returns agency.

Diary excerpt

“Today, I admitted to my team that I had known my fate yesterday but hadn't wanted to add more to their plate. Everyone is having conversations, myself included.”

Thought of the Day
'If I can't do that, then what can I do?'
'Do what you can, not what you can't.'

Stage of Grief
Shock, Denial, Anger, Reconstruction

Try this (this week)

• Write three lines: one feeling • one fact • one next step.

• Make the four lists (Admin/Money/People/Options) and add one small item to each.

• Send one gratitude message to someone who made the day softer.

Checklist

□ Body first: walk, water, one honest page.

□ Boundaries: cap heavy conversations; use a kind pause line.

□ Journal: date, 5 factual bullets max.

□ Board: Admin/Money/People/Options (≤3 cards per list).

□ Money: 12–13‑week baseline (or whatever buffer suits you), list questions for payroll/HR.

□ People: 3 thank‑yous; 1 mentor check‑in; no public venting.

□ Next week: 2 job‑search blocks, 1 portfolio block, 1 wellbeing block.

□ Deferrals: no irreversible decisions for 48 hours.

□ Review: 10‑minute close‑down each evening.

If your organisation is navigating change and you want calm, people‑first delivery without the drama, I can help.

This is based on my personal experience, anonymised to protect privacy. Nothing here is financial, legal, or medical advice - please seek professional guidance for your own situation.

Subscribe now

Who this is for

• Professionals navigating redundancy or restructuring.

• Leaders supporting people through change.

• Anyone who prefers calm operating rhythms over drama.

What you’ll get (in every chapter)

• A short, story‑led scene in my voice.

• A practical playbook you can copy right now.

• A checklist / ‘Try this’ so you take one small step today.

• A leader’s lens for managers who want to help well.

• A clear personal narrative.

How to use this series

1) Read the TL;DR first.

2) Borrow the playbook (don’t wait for perfect clarity).

3) Use the checklist to make one small, finishable move today.

4) If you lead people, skim the ‘Leader’s Lens’ in each chapter.

5) Share this hub with someone who needs steady ground.

Ground rules & safety

• This series is based on my story and my own perspective, with details anonymised to protect privacy.

• I’ve tried to not diagnose others’ motives or assign blame - just what I did and learned.

• I am not a financial, legal, or medical professional. I may share information on what has worked for me but please be sure to seek professional advice for your own situation.

Table of contents (9 parts)

1. The First 72 Hours: a calm operating procedure: Protect your nervous system, set boundaries, start a simple system, and defer big calls until the adrenaline fades.

Read the Article [07-10-25]

2. Financial triage: Know your 12–13 week budget needs, ask for payout estimates, freeze non‑essentials, and make ROI‑driven moves.

Read the Article [14-10-25]

3. Boundaries & energy: saying no without nuking bridges: Cap heavy conversations, use pause scripts, ask your medical professional for support when capacity is depleted.

Read the Article [21-10-25]

4. Rebuilding identity: from title to value: Shift from labels to outcomes; keep a value file; respond professionally when something stings.

Read the Article [28-10-25]

5. Portfolio refresh: evidence over adjectives: One resume, tailored cover letters, a simple tracker, and quality guardrails (no late‑night apps).

Read the Article [04-11-25]

6. Applying while healing: Design humane rhythms: nightly cut‑offs, rest days, small consistent prep; treat rejections as data.

Read the Article [11-11-25]

7. From redundancy to fractional leadership: Package what you already do: stabilise, structure, coach - into short, outcomes‑based sprints.

Read the Article [18-11-25]

8. Operating rhythms that reduce chaos: Daily timeboxed triage + a weekly evaluation day beat algorithm noise and backlog bloat.

Read the Article [25-11-25]

9. What I’d do differently (and what I’d repeat): Keep journals, one board, and evaluation day; kill late‑night apps; start proof tiles and ethical asks.

Read the Article [02-12-25]

If your organisation is navigating change and you want calm, people‑first delivery without the drama, I can help.

This series, the content and any observations or suggestions made are based on my personal experience, anonymised to protect privacy. Nothing here is financial, legal, or medical advice - please seek professional guidance for your own situation and, most importantly…

Subscribe now

When you pictured a life in music, you didn’t imagine your calendar filling with emails, invoices, socials, merch orders, uploads, and travel planning. Yet the admin side is part of the gig, and if you let it, it will crowd out writing, practice, and shows.

Admin and artistry are a yin–yang: separate, but complementary. The goal isn’t to love admin; it’s to contain it, with small systems that keep the business moving while your best hours go to making music.

In this module, you’ll learn a simple, four-step way to corral the back-office work, automate what you can, and design a week that consistently protects creative time - so your career grows without burning you out.

What we’ll nail

• Map the mess → three buckets: Money (invoicing, taxes), Marketing (socials/EPK/newsletter), Logistics (gigs, travel, stock).

• Batch & block: one weekly Admin Power Hour + a 15-minute daily “inbox sweep.”

• Automate & template: invoices, pitch emails, content calendars, checklists.

• Protect peak hours: schedule two non-negotiable studio blocks; move admin to low-energy times.

Module Content

1. Learn to Level Up - Don’t wait to “be ready.” Pick one skill, make a tiny daily rep, and let new instruments/genres stretch your writing and your range. [Read the Article..]

2. Schedule the Muse - Creativity can’t be commanded, but it can be calendared. Block an hour daily, park ideas fast, and timebox experiments when you show up. [Read the Article..]

3. Delegate to Create - If admin expands, art contracts. Score the tasks, share the load, and batch the business so your best hours go to music. [Read the Article..]

Admin to Artistry: book one Admin Power Hour this week and set two 90-minute studio blocks - treat them like gigs.

Want a one-page Admin Batching Planner + invoice/pitch email templates? Say the word and I’ll share them.

This series, the content and any observations or suggestions made are based on my personal experience, anonymised to protect privacy. Nothing here is financial, legal, or medical advice - please seek professional guidance for your own situation.

Subscribe now

When one person carries all the non-music work, burnout and “bus-factor” risk go way up (what happens if that one person leaves?). Bands should distribute tasks with backups; solo artists can delegate/outsource the same way - friends, peers, paid help, or tools.

The goal isn’t to do everything; it’s to ensure the right things get done by the right people, while you protect your highest-value creative time.

How to balance the load

• List everything (social, bookings, merch, finances, web/EPK, transport/PA, content, fan mail, etc.).

• Score each task for joy, career impact, and “am I the best person?” If the total < 15, delegate.

• Assign an owner & a backup (avoid single points of failure).

• Batch admin on one day; leave the rest for creation.

• Document the basics (simple checklists/SOPs) so handoffs are painless.

Activities & exercises (aligned to your piece)

• What to Keep, What to Ditch - Scoring
  Use the sheet to rank tasks (1–10 x three). Anything under 15 moves off your plate.

• Delegation Roster & Bus-Factor Map
  “Who does what,” plus a backup and cadence. Add quick mitigations for fragile areas.

• Weekly Creative/Admin Split
  Protect creative blocks; batch admin; assign owners if you’re a band.

• Support Network Map & Ask Script
  List people you can lean on and use a kind, clear, time-bound ask.

Delegate to Create: score your tasks and move three sub-15 items off your plate this week.

Want a starter ‘Delegate to Create’ pack? Say the word and I’ll share the templates.

This series, the content and any observations or suggestions made are based on my personal experience, anonymised to protect privacy. Nothing here is financial, legal, or medical advice - please seek professional guidance for your own situation.

Subscribe now

Accomplished writers don’t wait for lightning; they build a storm window. You won’t always write a full song in your slot - and that’s fine. The win is showing up, collecting seeds, and giving them oxygen in regular sessions. The more you practice “making space,” the easier flow becomes.

What this looks like

• Two-week sprint: 60 minutes/day, same time if possible.

• Idea capture everywhere: notes/voice memos → tag and centralise.

• Session recipe: 5–10 min warm-up → 3 × 10–15 min experiments → export something → set a tiny next step.

'I'm always trying to find myself little holes where I can do some songwriting' - Darius Rucker

Activities & exercises (ready to use)

• Plan Some Creative Time
  For the next two weeks, block an hour a day. Show up. Even a messy chorus draft counts.

• Idea Parking
  Consolidate scattered scribbles/voice memos into one place with tags (mood, tempo, key, use-case).

• Session Template
  Set an intention, pull 1–2 seeds, timebox experiments, and end with a tiny next action scheduled.

Schedule the Muse: block your hour for the next 14 days and log one seed per day - lyrics, riff, or groove.

If you’d like the Schedule the Muse pack, say the word and I’ll send them through.

This series, the content and any observations or suggestions made are based on my personal experience, anonymised to protect privacy. Nothing here is financial, legal, or medical advice - please seek professional guidance for your own situation.

Subscribe now