- THE PERSPECTIVE
Field notes, frameworks, and case patterns. Written by the operators who shipped them. No SEO bait, no thought-leadership theatre - only what we'd send to a client we respect.
CATEGORY
A pattern from twelve enterprise migrations: the technology lands in year one, but the operating model that supports it never does. By year two, the cracks are visible to the board.
Why restructures fail when leaders confuse boxes and lines with how work actually flows. A short framework for distinguishing structure from operating discipline.
An anonymized walk-through of a multi-country systems consolidation we led from kickoff to cutover - including the two near-misses that nearly derailed it.
If a transformation is going to land, the answers to these five questions need to be defensible before kickoff. Most programmes can't answer two of them.
Notes from operating-partner-side and management-side seats on what separates value creation programmes that compound from those that get diluted.
Designed for engagement metrics, not organizational consequence. Here's what the small number of programmes that actually move the needle have in common.
Beyond Scrum and Kanban: a practitioner's read on the methodologies that are quietly working at scale - and the ones that are mostly conference theatre.
An honest look at what Scrum gets right, what it never solved, and where mature engineering organizations are quietly moving past it. Not a takedown - a recalibration.
Agile values collaboration, but it doesn't guarantee it. Field-tested approaches for surfacing, naming, and resolving conflict in cross-functional teams without losing pace.
Remote was a forced experiment. The firms still running distributed-first did something specific. Here's what separated structural redesign from improvisation that never ended.
Beyond ergonomic chairs and async standups: the operating mechanisms - meeting rhythm, written discipline, decision logs - that make distributed work compound rather than corrode.
Most retrospectives are theatre - same complaints, same nodding, same nothing. A short structure for running a year-end retrospective that produces decisions, not catharsis.
A specific retrospective format for when a team needs to surface uncomfortable truths without descending into blame. Six segments, three rounds, one conversation worth having.
Most brainstorms reward the loudest. A short protocol that gets quiet contributors on the page first - and produces noticeably better output as a consequence.
High-performing teams do not collapse loudly. They drift - through small accommodations, polite avoidances, and rationalisations no one names. A short field guide to spotting the drift early.
Tools sit on top. Practices below. Principles below that. Mindset at the core. A short walk through the layers - and where most adoptions get stuck.
Product, engineering, QA - in the same room, on the same item, before sprint planning. A short rhythm for reducing in-sprint surprise to almost zero.
A practitioner handbook for running retrospectives that actually compound learning - not the calendar tax most teams have made them into.
The Scrum Master is the most frequently mocked role in modern delivery. Mostly by people who have never had a good one. A short defence of what a great one actually does.
The styles that travel well across function, geography, and crisis - and the contexts each one collapses in. A short, opinionated taxonomy.
A revisit. The mistakes we kept seeing teams make after the first piece on retrospectives - and the small adjustments that fix them.
It worked when work was repetitive, supervision was visual, and the cost of errors was low. None of those conditions describe modern enterprises - which is why the style now actively destroys output.
Velocity is not a metric. Burndown is not a metric. Here is the short list of measurements that change behaviour - and the longer list of dashboard ornaments that do not.
Agile is not a framework you adopt. It is a posture you take towards uncertainty. A short reflection on the posture, written for leaders who have outgrown the ceremonies.
The most underused artefact in agile delivery. A short template for writing a working agreement your team will actually refer back to - because it answers the questions that come up under stress.
Capacity discussion. Risk identification. Dependency mapping. The unsexy thirty minutes that decides whether the sprint actually lands - and why most teams go straight to story selection instead.
The DSM is the most maligned ceremony in agile - mostly because most are run badly. A short defence of why it still earns its fifteen minutes when run with discipline.
Most brainstorms generate timid lists - because they are run with the same etiquette as a status meeting. The short adjustments that produce divergence worth converging.
A sprint review is not a demo. The short distinction between the two - and why the demo culture quietly kills the feedback loop reviews are meant to create.
A short protocol for running a standup that surfaces blockers, builds team awareness, and ends in fifteen minutes - not the status-report theatre most teams have allowed it to become.
Software costs do not escalate suddenly - they escalate quietly, through accumulating compromises that look reasonable in isolation. A short field guide to spotting the drift before the budget conversation gets ugly.
Design thinking became a punchline somewhere between 2018 and 2022. Mostly because of how it was sold, not because of what it actually does. A short defence of the discipline beneath the buzzword.
- PRIVATE LIST
We publish irregularly - only when there's a pattern worth naming. Field notes from live engagements, frameworks we trust, and the occasional case study. Never marketing.
UNSUBSCRIBE IN ONE CLICK · NEVER SHARED