Weeknote 2026/35

Pre-festival dog walks (Photo: me)

“If you want the rainbow, you gotta put up with the rain,” said Dolly Parton.

It absolutely pissed down at Forwards on Saturday.

Proper, committed rain. The sort where you spend the first twenty minutes trying to preserve some vestige of dignity before accepting that your hair is fucked, your shoes are wet and this is simply your life now. At which point, pleasingly, it becomes fun. I put my raincoat on and danced like an absolute twat and it was brilliant.

This week bought the sad news that Dolly died, and I spent much of the following two days listening to her music and having a bit of a cry. So the quote has been rattling around my head ever since.

It also turns out to be a reasonably good description of running a small consultancy.

The rainbow is the bit you get to announce: we won a new client. We ran a great session. We wrote something people wanted to read. The rain is contract negotiation, procurement portals, pitch decks for meetings that get postponed, timesheets, project plans, pipeline reviews and writing a scope annex whose principal purpose is to establish, at considerable length, all the things you are not going to do.

We tend to talk about work in terms of its outputs because those are the bits you can see. Projects delivered. Decisions made. Things launched. But underneath them is an enormous amount of preparation, negotiation, context and maintenance: the work behind the work.

Most weeks, you don’t notice it particularly.

This week, there was rather a lot of rain.

This week at work

We won a new client this week. Open tender, decision faster than expected, and we’re very pleased about it.

Winning it immediately produced a full day of contract negotiation, a scope annex written from scratch to define all the things we weren’t doing, and a compliance process that ran first into a legal team needing ten working days and then into our client contact going on annual leave. None of this is billable. All of it has to happen before the billable work can begin.

The same week, we spent two days preparing for a pitch. Deck built, case studies chosen, argument sharpened, review session with someone who knows the target organisation well. The session was postponed the day before it was due to happen. It’s been rescheduled, which is the good version of this outcome. The two days don’t come back either way.

Around that: proposal responses, project plans, timesheets, finances, contracts, and a full pass over every live and prospective piece of work on the board. All necessary. None billable.

A lot of people seem to be going independent at the moment, and the advice I keep giving them is unfortunately the least glamorous advice available: be brutally realistic about how much work you can actually do.

We’re pretty efficient at this stuff. We’ve put real effort into getting the machinery down — time tracking, project management, the pipeline board, templates for almost everything — and it works. But somebody still has to run the business. Somebody still has to make sure there’s work in three months’ time. Somebody has to negotiate the contract, write the proposal, chase the purchase order and discover that the procurement portal requires a document nobody has requested since 2009.

All of those somebodies are me.

Realistically, only about half my week is available to sell. Which means the useful calculation when you’re setting a day rate isn’t what you want to earn divided by 260 working days. It’s what you need to earn divided by the days doing work somebody might conceivably pay you for.

We also ran a session for IABC this week on discovery: how to work out what an organisation’s communication problem actually is before anyone buys something to fix it.

It went well. One attendee said he was taking our hypothesis-board approach straight into a meeting that afternoon, which is about the best feedback there is. Another asked whether all this was in the book. It is, and given that I literally wrote the thing I should probably have thought to mention that myself.

The following day we agreed a second session for a different audience, and there’s a keynote version coming in October. It’s a format we do a lot, enjoy doing, and — pleasingly — people keep asking us to do without us having to invent a funnel for it.

Also this week

Bristol again, this time for Forwards. There is still nothing better than a weekend in a field with loud music and good friends, and at 46 I think we can safely conclude I’m not going to grow out of it.

The weather did its level best. Once you’ve accepted that you look like a drowned rat and there is no longer anything worth protecting, dancing in the rain turns out to be enormous fun.

Little Simz, Wet Leg, Self Esteem and Viagra Boys all delivered. Tricky did not: weirdly quiet, strange atmosphere, and the peculiar experience of being able to hear his backing singers perfectly while the man whose name was on the poster remained largely theoretical. Princess Nokia was simply bad.

And a Rubicon crossed. For the first time in my life, I had genuinely never heard of one of the festival headliners.

I assume this is how it begins. Next year I’ll be bringing a folding chair.

Consuming

All Dolly, all week, after the news broke on Wednesday. Veering chaotically between bluegrass, the classics and Backwoods Barbie, all bought during a lengthy Dolly phase that followed a trip to Tennessee and a pilgrimage to Dollywood.

Live your life such that when you die the praise is that unanimous.

Me at Dolly’s Tennessee Mountain Home, a million years ago

Coverage

I wrote a piece for Reworked about the Spirit Airlines data sale, which is now the subject of a bidding war involving Google and a startup that builds AI agents to work inside simulated companies. A sentence that would have required considerably more explanation five years ago.

The argument, roughly: we spent a decade telling people to work out loud, on the understanding that persistence would work in their favour. Write things down. Share what you know. Leave a trail somebody else can follow.

What Spirit demonstrates is that the archive can outlive the conversation, the project, the team, your employment and, eventually, the company itself. And the first thing people stop writing down once they’ve noticed that isn’t the decision. It’s the messy reasoning behind it — the disagreement, uncertainty, context and half-formed thinking — which is the only part that was ever genuinely inheritable.

There’s a second half I expected to find harder to write than I did, about why that archive is worth twelve and a half million dollars.

Workplace software gets built by small young companies where twelve people talk to each other constantly, then sold to organisations with shift patterns, works councils, contractors, subsidiaries, six layers of sign-off and thirty years of documents nobody can find. The people building software for large organisations have surprisingly little evidence of what life inside one actually looks like.

Spirit’s archive isn’t a use case. It’s a world.

Which is why the sale is simultaneously creepy and entirely economically rational. Both things can be true at once, which is what makes it an argument rather than a lament.

The whole thing started as a paragraph in a weeknote a fortnight ago. I cut it because it was too much for the space it had. Turns out it was an essay.

Published

I’ve started putting essays on the site as well as these weeknotes. Weeknotes are chaotic by design – whatever happened that week, from day rates to a Dolly Parton deep dive. Some things need more room than that, and one subject at a time.

The first few are up:

Travel

This weeknote comes to you from a characterless, overpriced pub in Bristol Airport, which scores precisely nothing under the LoungeWanker rules.

Home for forty-eight hours, then back to the UK for client meetings.

The glamour of international consultancy remains largely theoretical.

This week in photos

Weeknote 2026/34

An Amsterdam canal at night, lined with lit gabled houses and a moored houseboat with flower boxes. A small open boat full of people passes under a bridge, its wake catching the reflected lamplight.
Prinsengracht after the concert (Photo: me)

My second favourite part of the Prinsengracht Concert, after several thousand people singing Aan de Amsterdamse Grachten together, is what happens immediately afterwards.

Hundreds of boats have spent the evening crammed into the canal, several deep, wedged against one another in a configuration that suggests nobody gave much thought to the concept of leaving. Then the concert ends and, simultaneously, everyone would like to go home.

It is magnificent.

For the next half hour the Prinsengracht becomes a giant aquatic game of Dodgems. Boats reverse into gaps that don’t exist. People push off neighbouring vessels with their hands. Someone three boats away is shouting instructions to a person they have never met. Entire flotillas shuffle sideways because one tiny boat has committed to a three-point turn and apparently we’re all seeing this through now.

From the bridge, it looks like complete chaos. Except it works.

There’s a system in there. It’s just not the sort anyone would put into PowerPoint. It runs on eye contact, shouted instructions, local knowledge, mild peril and hundreds of tiny negotiations between people adjusting constantly to what everyone around them is doing. There are formal rules, obviously, but they get you only so far when you’re pointing backwards in a canal with someone’s bow six inches from your wine glass.

Organisations work rather more like the Prinsengracht at 11pm than anybody designing an operating model would ideally like to admit.

We draw the hierarchy as a pyramid, put one person reassuringly at the top, arrange everyone else underneath and call it an organisation. We map systems into boxes. We assign owners. We draw solid lines and dotted lines and spend quite a lot of money arguing about where they should go.

This is all useful, up to a point. The problem comes when we mistake the diagram for the thing it describes. Reality has an irritating habit of continuing to be three-dimensional after we’ve put it on a slide.

The mess isn’t necessarily evidence that there is no system. Sometimes the mess is the system.

This week at work

Organisations are way more complicated than their org charts.

Someone can turn up wearing one organisation’s uniform, carrying another’s lanyard, logging into a third’s systems with a password reset only the first can authorise, doing a job that half of them think belongs to somebody else.

Work runs through partners, contractors, shared services and joint ventures, and plenty of people hold more than one allegiance at once. There’s a chapter on this in the book, framed mostly around the gig economy and deskless work, but the same problem turns up anywhere separate organisations share most of a back office and almost none of a culture.

That’s a comms problem before it’s a technology one. Your channels have to fit the organisation you actually have, mess included, rather than the neat little pyramid with one person at the top and everyone else arranged obediently underneath.

This week I ran a workshop with comms and digital leaders in an organisation dealing with exactly this kind of complexity. We started with what a digital workplace actually is, and why it matters more, not less, when the organisation around it is changing.

It’s how change gets communicated, obviously. But it’s also how you unlock the value you were promised when you bought all those services in the first place. A service nobody can find is, for most practical purposes, a service you don’t have.

I introduced our graphic equaliser model: the idea that a digital workplace is a mixing desk with four faders — comms, knowledge, transactions, and community and collaboration — and every organisation runs a different mix. Some crank comms all the way up. Others lean heavily into tools and self-service. We spent time looking at where their balance sits now, and where it needs to move.

I love sessions like this because I learn as much as I share about the increasingly messy reality of how work gets done. I always say there’s no right balance, only what’s right for your organisation. What this one reminded me is that there isn’t necessarily one setting for an organisation either.

Different parts of the business need the dials in different places. Increasingly, so do individuals.

Which means the digital workplace has to flex around the organisation you actually have. That took us into the perennial question of what needs local control and what benefits from central planning.

It’s harder when there are multiple reporting lines, because budgets and approvals follow accountability, while work has the irritating habit of ignoring it. Publishing pulls hard towards shared: one system, different lenses. Discussion stays stubbornly local, because that’s where culture lives and nobody particularly wants theirs decided by committee. Planning sits awkwardly in the middle, because of course it does.

No amount of elegant architecture fixes the fact that organisations contain politics.

The dials get set by whoever holds the budget line. They get lived with by everyone else.

Also this week

I tore a hamstring in a HIIT class, which is what I get for going to HIIT classes.

It turned out to be relatively minor, but kept me out of the gym and mostly confined to the flat for the week. Last weekend I was hobbling around with a walking stick, mentally rearranging the next three months of my life around my exciting new identity as Person With Hamstring Injury. By Friday I was walking again, albeit not at my usual faintly aggressive pace.

Recovery was swift enough that I’ve decided to take personal credit for it, having contributed absolutely nothing beyond sitting still.

The one casualty was the line dancing class I’d signed up for as part of my ongoing efforts to Try New Things. I was fully prepared to attend and be heroically bad at it. Then I couldn’t go, so my potential as a line dancer remains mercifully untested.

Next time.

Saturday was the Prinsengracht Concert, one of those moments every year that makes me absurdly glad to live here. The city is both backdrop and main character: a stage built over the canal, thousands of people lining the water, boats packed in until the whole thing looks faintly impossible.

It ends, as it always does, with everyone singing Aan de Amsterdamse Grachten together — a song about how beautiful this city is and how nobody could wish for anything better than to be an Amsterdammer.

Can confirm.

Consuming

Saw Sparks in Nijmegen, for their only Dutch date this year, in a lovely outdoor theatre. We’d got ourselves in the mood the night before with The Sparks Brothers, Edgar Wright’s documentary: two and a quarter hours of people you already suspected of having excellent taste confirming that they do.

The gig was delightful right up until it wasn’t. They finished This Town Ain’t Big Enough for Both of Us and the heavens opened. They made it through Whippings and Apologies with rain sheeting off the canopies before the show was finally called off for safety.

Sixty years, twenty-odd albums, and I got about two thirds of a set. The Mael brothers have outlasted glam, disco, synth-pop, Britpop and several physical media formats, only to be defeated on Thursday night by Dutch weather.

I’ve also been transfixed by the Spirit Airlines story all week. Google has bought the bankrupt airline’s entire internal archive for $10 million: a hundred million emails, five hundred million Teams messages, seventeen million files, all to train AI on. Former employees are now in court trying to get themselves removed from the dataset.

It has absolutely everything.

What happens to how people behave at work once they realise the archive might outlive the company. The legal question of whether anything you wrote at your desk was ever really yours. Bankruptcy law colliding with data protection colliding with AI. Organisational complexity. Workplace technology. The lot.

And then there’s the bit I keep turning over, because I love nothing more than to be a contrarian, which is that this might actually make the software better.

Enterprise software has always been designed for an organisation tidier than any organisation that has ever existed. When I spoke to the Facebook team during the Workplace years, they seemed genuinely baffled that companies didn’t want information to be open in the way it was at Facebook. That openness was the product. It was also one of the reasons so many corporates couldn’t use it.

Microsoft, all these years later, still can’t cleanly accommodate someone holding multiple affiliations with one institution, never mind several institutions at once — which describes an enormous number of people I encounter through work.

Nobody has ever had a really good dataset showing how a large organisation actually functions, because all the interesting stuff is behind a firewall. The formal structure is easy. The useful bit is the messages, workarounds, accidental networks, weird permissions, duplicated effort, informal power and the seventeen people you have to ask before discovering that Sandra in Finance knows how it works.

Now, suddenly, there’s one on the open market.

The messiness is exactly what makes it valuable.

Which is also the problem. The upside depends on the data being rich, specific and human enough to reveal how work really happens. The privacy disaster is that it’s far too rich, specific and human to anonymise properly.

There’s no version where you get one without the other.

Connecting

Three this week, all people passing through.

Mark Chapman, who runs an NHS intranet, was briefly in town. I failed to have a proper conversation with him at the book launch, just as I failed to have a proper conversation with almost everyone at the book launch, so we made up for it in my local by nerding out about intranets at considerable length.

Then Chris Higham, finally, in person. Chris and I are part of a group that formed on Twitter years ago around sharing our fitness ups and downs, then migrated to WhatsApp when the platform went the way it went. It’s still one of the most supportive gangs I’m in: the rare group chat that survived the collapse of its natural habitat (I wrote about that community in 2025/49)

He was over with his family on holiday, so I got to meet all of them too.

And yesterday, a walk-and-talk with Anne Ditmeyer, a Paris-based designer and facilitator I met at the Awesome Authors meet in London in May (see Weeknote 2026/21). She was in the Netherlands for a design event, so we walked and talked about unlocking creativity. Eexactly the sort of conversation that gets better once you remove the table.

She also introduced me to Bonnie Cauble and Sarah Pedlow, both creatives based here. Amsterdam continues its long-running campaign to make everyone in the world no more than two introductions away

Travel

Autumn has been sitting ominously in the calendar for a while now.

This week it begins: a quick trip to Bristol.

This week in photos

Weeknote 2026/33

A lovely spot to ponder the nature of the universe (Photo: me)

Eighty-eight per cent of the sun went behind the moon on Wednesday and it barely got dark.

That night, every star I looked at turned out to be another sun, filed down by distance to a pinprick. The moon is a rounding error next to the sun. It just happened to be closer, and in exactly the right place to block most of it.

Scale, it turns out, is extremely easy to misunderstand.

Organisations have this problem too. The bigger something gets, the more we tend to discuss it in aggregate: tens of thousands of employees, enterprise-wide adoption, transformation at scale. Eventually the people disappear altogether and you’re left moving percentages around a slide.

Over coffee this week I spent an hour talking through one person’s job. Earlier I’d been on a call about essentially the same problem across an organisation of tens of thousands. The enormous version turned out to contain exactly the same question as the tiny one: what is this person actually trying to do, and what’s getting in their way?

That’s the irritating thing about scale. To understand the big thing, you usually have to get very close to the small one.

The trouble starts when you assume it works the other way round.

This week at work

Over coffee, a friend told me her employer has been telling everyone to use AI. She’s not against it. She just doesn’t know what she’s supposed to do with it. Nobody has said what it’s for.

There is a mandate, and there is a tool, and between them a gap roughly the size of her actual job.

So I did what any normal person does to a friend on their day off and interrogated her about work for an hour.

I didn’t start by asking what she wanted AI to do. I asked what she finds difficult. What’s stopping her being as good at her job as she’d like to be?

Planning, she said.

Her industry works a long way out; she’s on Christmas 2028 at the moment, which is a boggling timescale for me, a person for whom buying food on Sunday for Wednesday constitutes advanced logistics.

The problem isn’t really making the plan. It’s holding the thing together once it exists: knowing where versions have drifted apart, where assumptions no longer match, and where six teams have all independently decided that the same fortnight would be an excellent time to do something enormous.

This is precisely the sort of work computers are annoyingly good at and human brains aren’t. So: give it the plans. Ask it to find inconsistencies, collisions and crunch points.

She said they’re so busy they tend to repeat the things they already know work. Fine. Give it the data from the last few programmes. What performed unusually well or badly? What was different? Are there patterns worth investigating?

Within about twenty minutes we’d gone from I know I’m supposed to use AI but I don’t know what for to a list of things she was genuinely excited to try.

No use-case library. No maturity assessment. No 73-slide deck entitled Unlocking the AI-Powered Future of Work.

We just talked about her job.

Her own takeaway was better than mine. She’s going to ask everyone on her team to bring one thing they’ve used AI for lately that actually made the work better or easier.

Not a strategy. Not a policy. Not a prompt library containing 400 examples nobody will ever read. Just one thing that worked, said out loud, by someone you know and trust, and not some twat from a consultancy who wears a hat indoors.

The funny part is that I’d started the week having essentially the same conversation, only with several more zeroes attached.

I’d been on a call with someone running an AI programme somewhere very large indeed, ahead of a client conversation about what adoption looks like at that scale. And scale changes the conversation surprisingly quickly. One person has a planning problem. Ten thousand people have an adoption strategy.

At organisational scale, everything acquires nouns: Adoption. Enablement. Transformation. Capability. Use cases. You can spend months discussing all of them without getting anywhere near the awkwardly specific question my friend answered over coffee:

What is hard about your job?

Same problem. More zeroes.

The technology isn’t the difficult bit. Finding the useful problem is.

You have to do that first for a person, then for a team, then somehow across tens of thousands of people. And the further you get from the actual work, the easier it becomes to replace understanding it with buying something.

Which is how you end up with an enterprise AI strategy explaining very clearly that everyone should use AI, and an employee sitting in a café saying:

Yes. For what?

Also this week

I took 24 hours off midweek and went to the coast for the eclipse.

First surprise: the Netherlands has genuinely stunning beaches. Huge sweeps of powdery sand running from the dunes straight into the North Sea. The climate makes them properly usable for approximately nine afternoons a year, which may explain why the Dutch have declined to make this a central plank of the national brand.

We got one of the nine.

Past me had also had the unusual foresight to book a cabin near the coast and buy eclipse glasses back when they weren’t €20 a pair and being traded with the intensity normally reserved for Taylor Swift tickets and Class A drugs.

We took a couple of bottles of Sol down to the beach, which I’m going to present as thematic intent rather than the consequence of the bar offering a choice between that and Heineken.

At around quarter past seven, through the cardboard glasses, the first bite of the moon appeared at the edge of the sun. Then, very slowly, it ate it.

There’s something profoundly weird about watching celestial mechanics happen in real time. You know perfectly well that the moon goes around the Earth and the Earth goes around the sun. You have presumably known this since primary school. But normally this knowledge sits in the same part of the brain as plate tectonics and the existence of Belgium: accepted as fact, rarely requiring direct confrontation.

Then you watch one enormous object physically move across another and suddenly the solar system stops being a diagram.

What I couldn’t get my head around was the arithmetic of it. The moon is enormous. The sun is so incomprehensibly much more enormous that the comparison is barely useful. And yet from one particular patch of Dutch sand, because of an absurd coincidence of distance and geometry, they looked almost the same size.

At the peak, 88 per cent of the sun was covered. It barely got dark.

That was the bit that broke my brain. You can remove nearly nine-tenths of the thing and the remaining sliver is still bright enough for the world to carry on more or less as normal. The sun, it turns out, is quite a lot of sun.

Later that night I lay in a hammock in the Kennemerland dunes waiting for the Perseids.

The advice for watching a meteor shower is blunt: no screens. Your eyes need around twenty minutes to adjust properly to the dark, and one glance at a bright phone sets you back. This isn’t mindfulness. Nobody is asking you to reconnect with your authentic self or purchase a journal. It’s optics.

So the phone went away.

I live in a well-lit city centre and almost never see stars. Properly see them, I mean. Give your eyes enough darkness and they just keep arriving. A handful becomes dozens, then hundreds, then an absolutely unreasonable number of them.

And having spent the evening staring through cardboard at our sun, I suddenly couldn’t stop thinking about what I was actually looking at.

Every one of those pinpricks is another sun.

Not a decorative light. Not a white dot conveniently provided as background scenery. An actual star: vast and violent and burning away at an incomprehensible distance, reduced by that distance to something I could cover with the tip of my finger.

Then every so often something would tear across the whole lot. A Perseid lasts perhaps a second. A streak, sometimes a flash of colour in the tail, and gone before you’ve quite finished registering it. We’d wait in the dark for another, talking quietly, then one of us would suddenly shout there at a piece of sky the other person was inevitably not looking at.

There are worse ways to spend a night.

I lay there thinking about the scale of all of it: the sun we’d watched disappear behind the moon; the other suns scattered above us; the tiny bits of comet burning up overhead; us underneath, temporarily occupying a couple of hammocks on a sand dune beside the North Sea.

The universe is offensively large.

I found this wonderful.

And then, because apparently even transcendence must eventually become professional development, I realised something mildly embarrassing about my phone.

I’ve written a book about attention and information overload. I talk about this stuff for a living. I know that phones are designed to capture attention. I know that environment beats intention. I know all the arguments.

None of that reliably stops me looking at the bloody thing.

But tell me that one glance at it will ruin my night vision and make me less able to see the meteor shower I came here specifically to see?

Phone in a drawer. For hours. No struggle whatsoever. Turns out I didn’t need better self-control. I needed an immediate and comprehensible consequence.

Design beats willpower. I really, really should know this by now.

Consuming

Two pieces by Oana Leonte, published two days apart, which have been rattling around my head ever since. The first starts with Rick Rubin, who cannot play an instrument or read music, and who told Anderson Cooper that what he’s actually paid for is confidence in his own taste. His contribution to a record is often subtraction: take that out, strip this back, do it again. He has no signature sound because a signature would compete with the judgement.

Leonte uses him to make a distinction I haven’t stopped thinking about: attention is rented; judgement is owned. Attention has to be re-earned every day and returns towards zero the moment you stop feeding it. Judgement compounds. Demonstrate good taste often enough and eventually people trust the verdict — which is why artists at the top of their careers will fly across continents to sit in a room with a man who can’t play a note. They’re not buying his output. They’re buying his judgement.

This is inconveniently at odds with how we measure most things online. We can count impressions, views, followers, clicks and frequency, so we do. Judgement is slower, fuzzier and extremely resistant to dashboards, which means it tends to sit outside the spreadsheet twiddling its thumbs while attention gets all the credit.

Then came part two, prompted by everyone asking how. And she corrects herself: invisibility isn’t the strategy, it’s a by-product. Copy the quiet without the substance underneath it and you’re not cultivating mystique, you’re just a person nobody has heard of. Queen were broke for years being too much for the rooms they were playing. Obscurity is what you pay to get good.

What actually holds is coherence — and here she draws a distinction I’m going to steal wholesale, because half my working life is spent in rooms where coherence and consistency are treated as synonyms. Consistency is surface: same logo, palette, tone, templates, everything governed until no rogue shade of blue can threaten the enterprise. It photographs as discipline and is often just rigidity with a hex code.

Coherence is the sense that the choices belong together, even when they don’t look the same. Consistency asks whether the parts match; coherence asks whether they came from the same place. You can be flawlessly consistent and mean absolutely nothing, which explains an alarming amount of corporate communication.

And then the question I’d put on a poster: would any of this still be standing if you stopped posting tomorrow?

I read all of this while planning a mailing list, a webinar and another run of book promotion, so I’m not claiming any position of moral superiority here. The most coherent thing I did all week was spend several hours in a hammock looking at objects that have existed for billions of years without once publishing a thought-leadership carousel.

Then I came home and wrote about them on the internet. The stars, presumably, remain relaxed about the competition.

Coverage

In.Comms asked five comms pros (including me) whether it’s internal comms’ job to motivate employees. Nobody said yes, which I found reassuring, because we’ve spent far too long accepting accountability for things we have almost no authority over.

Pay. Workload. Leadership. Whether the work itself is any good. Whether your manager is a prick. Motivation is downstream of all of these things, and when they’re not working, asking comms to boost engagement is applying corporate Febreze to a structural problem.

What we can do is help people understand what’s happening, why it matters and where their work fits. What we can’t do is communicate someone into being happy about a job that’s giving them perfectly good reasons not to be. My bit sits alongside Jennifer Sproul, Jo Coxhill, Adeela Warley and Rachel Miller.

Also recorded this week: Jon and I joined Nancy Goebel on DWG’s Digital Impact podcast to talk about designing channels employees actually use — the five layers, why most organisations have a coherence problem rather than a channel problem, and the intranet manager who hit an annual page-view target in 48 hours by leaving fifty browser tabs auto-refreshing.

This is both objectively funny and a near-perfect demonstration of what happens when a metric stops measuring the thing and becomes the thing. Somewhere, a dashboard was green. Everyone could go home.

Out in the autumn, at which point I’ll link it properly.

This week in photos

Weeknote 2026/32

The World Press Photo 2026 exhibition inside De Nieuwe Kerk. A red entrance panel sits beside a large black and white portrait of an older woman in traditional dress. Photographs are hung on curved slatted wooden screens down the stone nave, with red banners overhead.
World Press Photo in de Nieuwe Kerk (Photo: me)

I’ve started thinking about the things that earn their place.

Not in a minimalist, throw-away-everything-that-doesn’t-spark-joy sense. I own far too many shoes for that, and my travel plans would not survive even the most cursory audit. More in the sense that addition ought to come with a burden of proof.

We’re very good at adding things. Another name. Another message. Another platform. Another feature. Another trip. Complexity accumulates almost invisibly because every individual addition can be made to sound perfectly reasonable on its own. It’s only when you stand back that you realise you’ve built something requiring a diagram, a 45-minute induction and a SharePoint page explaining which SharePoint page to use.

This week threw a few variations of that at me, from some fairly unexpected directions.

More isn’t inherently the problem. Neither is less inherently virtuous. The interesting bit is what happens when you stop assuming that adding something automatically makes the thing better.

The question is whether it earns the space it takes up.

This week at work

Four client projects, two proposals, and all the usual scaffolding of running a business — invoices, contracts, the small administrative barnacles that attach themselves to any given week. Jon is still away. So: a lot.

Everything is moving in the right direction, at least. But four projects at four different stages means four sets of context, four vocabularies, four mental models to load and unload across a single day. The work isn’t the tiring bit. The switching is. By Thursday I had approximately six organisations’ worth of information in my head and no reliable way of knowing which one any given acronym belonged to.

The consolation of weeks like this is the pattern-spotting. Do this for long enough and you start seeing the same problem turn up in completely different organisations wearing a different coat and insisting you’ve never met before.

This week’s recurring guest was naming.

Whether to give your channels names — and, if so, what — is one of the great perennial arguments of our trade. Alongside where IC should report into and whether anyone has ever successfully governed a SharePoint site by sending the site owner an annual email, it will presumably outlive us all.

I have Views.

Names can be genuinely useful. A name gives people something to hold onto. It’s a handle in a sentence: put it on Yammer, it’s in the Hub, check Connect. It makes an abstract thing tangible and gives people a shared shorthand for talking about it. This is useful. Humans like naming things. We named the moon and that doesn’t even have single sign-on.

The trouble is that intranets and employee apps actively resist being named, because they aren’t one thing. What do you call the platform that’s the news, the payslips, the policy library, the person finder, the canteen menu and, for reasons nobody can now reconstruct, the only place you’re allowed to order a new security pass?

Nothing specific fits. So you end up at Workplace. Or Engage. Or Connect. Or Hub.

Names for tools that do everything, which is another way of saying names that describe absolutely nothing.

Worse, every single one is already a product on the market. Frequently it’s also the name of another tool already inside the same organisation, bought by a different department in a different year with a different budget and announced with exactly the same adjectives.

We have been brought in more than once to adjudicate which platform gets to be called Workplace.

This is a service we provide. I would love to tell you it’s the most intellectually demanding work we do. It’s certainly the one that requires my best diplomacy skills.

My rule is simple: a name is only worth having if it saves you an explanation. If it doesn’t, you’ve just doubled your workload, because now you have to explain the service and the name — in every induction, on every intranet page, every time somebody new asks which one you mean.

Some years ago I worked somewhere with a room-booking system called Trimble.

Not a codename, nor a project name that had escaped containment. Just Trimble, because that was the vendor, and the vendor’s name had welded itself to the product the way Hoover did to vacuum cleaners, except nobody had ever heard of Trimble and nobody was going around saying they were going to Trimble a meeting room.

At some point a rule established itself: any mention of Trimble on Slack was answered with the same photograph of David Trimble. This one:

A black and white photo of Northern Ireland politician David Trimble, in the 1970s.

Same photo. Every time. No comment.

Nobody agreed to this. There was no meeting. No governance model. No launch plan. It simply became true, the way the most successful bits of workplace culture generally emerge while somebody elsewhere is writing a 34-page launch strategy.

It fired constantly, because most mentions of Trimble were people asking what Trimble was.

And that was precisely the problem, right there: the name was prompting the question it should have answered.

The joke ended when someone* laughed out loud in an open-plan office and had to explain why a photograph of the former First Minister of Northern Ireland kept appearing in response to questions about meeting rooms.

* it might have been me.

Eventually the organisation gave up and renamed it The Room Booking System. Everyone knew what it was immediately, forever, at zero ongoing cost. The photos stopped.

The postscript is that the software has since been sold twice and now lives inside MRI Software, where it’s called Space Scheduling. The descriptive half of the name outlasted four owners. The corporate half fell off somewhere between acquisitions, unmourned.

Call things what they are.

There’s a section on this in the Launching Channels chapter of the book, which is considerably more even-handed than I have just been: when a distinct name genuinely earns its keep, why naming competitions are a trap, and explicit permission to just call the intranet the intranet.

You do not have to call it Spark. You do not have to call it Connect. You definitely do not have to invite 14,000 employees to submit suggestions and then spend three months explaining why the winner can’t be used because somebody forgot to check the trademark.

Sometimes good design is simply resisting the urge to make a perfectly comprehensible thing more interesting.

Also this week

Saturday afternoon at De Nieuwe Kerk for World Press Photo, which I go to most years and usually leave in silence, feeling slightly worse about humanity. This year felt different, and it took me a while to work out why.

Not less bleak. There were still plenty of bombed-out streets and destroyed homes, and this year’s Photo of the Year is a family being separated by immigration enforcement in an American courthouse. Nobody’s going to World Press Photo for a restorative afternoon.

What had changed was the scale. Previous years have felt dominated by destruction seen from a distance: ruined blocks, flattened cities, the landscape of catastrophe. This year leaned much harder into resilience and resistance, told through single lives followed over months and years. Girls’ education. A 46-year-old woman living with anorexia. The lives of girls born by IVF to a 60-year-old mother. Afro-Latin communities in Colombia holding onto traditions carried from lands their ancestors were taken from centuries ago.

None of it was nice. That isn’t the shift here.

But there’s a difference between an image that shows you the size of a disaster and one that puts a person inside it and makes you stay there with them. Destruction at scale numbs you slightly, if we’re honest. At some point the numbers get too large, the rubble starts looking like other rubble, and your brain puts up a screen marked TOO MUCH.

Then, halfway round, I found the panel explaining what I’d already noticed. They’ve threaded eight projects through the exhibition under the heading Visions of Hope. The stated reason is media fatigue: audiences tell them they want to stay engaged with the world, but through stories that illuminate rather than overwhelm.

Which is a curatorial decision, obviously. But it’s also a comms one, made by an organisation whose entire purpose is bearing witness to the worst things human beings do to one another.

They’ve concluded that relentlessness is counterproductive. That if you overwhelm people, eventually they stop looking. And a record of the world that nobody can bear to look at isn’t doing much bearing witness.

It’s not a million miles from the argument I spend my working life making, arriving from a considerably more consequential direction: more information does not necessarily produce more understanding. At some point volume stops informing people and starts providing them with reasons to disengage.

The photograph I keep thinking about, though, was something else entirely.

Paula Hornickel photographed Waltraud, a resident at a care home in Albershausen, sitting across the table from Emma — a toddler-sized social robot made by a Munich startup.

German care homes are dealing with two crises at once: not enough staff, and residents who are profoundly lonely. One in five over-80s in care describe themselves as severely lonely. Emma recognises faces and remembers previous conversations. Waltraud was sceptical, then came round.

“When she tells her jokes, that’s really good.”

And there, unexpectedly, in the middle of a photojournalism exhibition, was one of the more interesting future-of-work stories I’ve encountered in a while.

We spend enormous amounts of energy arguing about which bits of knowledge work AI will automate. The lawyers. The developers. The copywriters. The consultants, who remain remarkably confident that everybody else’s job consists of repeatable tasks while theirs involves ineffable reserves of judgement and human insight.

Meanwhile, automation is turning up in care homes. At the one kind of work we tend to assume is irreducibly human because the work is being there with another person.

And it’s arriving not because somebody has produced a spreadsheet showing a 14% productivity gain. It’s arriving because there aren’t enough humans there.

I don’t know how I feel about that. I can construct the argument in both directions and dislike parts of both of them.

Waltraud seems fine about it, which is probably the only opinion that counts.

Consuming

Peaches at the Melkweg. My first gig in months, which for me is close to a personal record and not one I’m remotely proud of.

Worth the wait, though. A proper show. Giant inflatable spread legs. Dancers dressed as vaginas. Costume changes, choreography, staging that commits absolutely and unapologetically to the bit. None of the standing-behind-a-laptop-looking-intense business that passes for a live electronic set surprisingly often these days.

At one point Peaches simply walked out over the crowd, held up entirely by the audience, and carried on performing.

You either have that kind of contract with a room or you don’t.

There’s something enormously satisfying about watching someone who’s been doing this for decades know exactly what the room is for, and use every inch of it. No attempt to make herself tasteful or contemporary or slightly less Peaches now she’s in her fifties. If anything, more Peaches.

Came out sweaty, delighted, and mildly annoyed with myself for leaving it so long.

Travel

None, and I’m delighted about it.

I’m midway through a long stretch at home, and it turns out that’s exactly where I want to be. No airports. No packing. No waking up and having to spend several seconds establishing which country I’m in. Just my own bed, my own kitchen, and an entirely unremarkable knowledge of where all my things are.

The Dutch weather asks a lot of you. Months of grey, damp, low-ceilinged winter, the sort that makes you question not just your decision to move here but the entire concept of northern Europe.

But summer in Amsterdam is the finest bargain in Europe. Long evenings, terraces spilling into streets, everyone outside because we’ve collectively understood that this is temporary and must therefore be treated as an emergency. I’ve spent most of this one amazed at my luck in getting to live in it.

I could get used to this.

I have, obviously, booked an enormous amount of travel for the autumn.

This week in photos

Weeknote 2026/31

A WorldPride parade boat with a "25 Years of Marriage Equality" banner, dancers performing on top, watched by crowds along the Prinsengracht and from boats on the canal.
The Canal Parade on Amsterdam’s Prinsengracht canal (Photo: me)

I spent much of this week being reminded that systems have lives of their own.

You can appoint community champions, but the actual community will organise itself around somebody else. You can design an intranet around the company you think you have. Employees will build another one around the work they’re actually trying to do. You can ask whether AI can replace a chief executive. Then you’ll quickly learn the hard part was never making the decision; it was getting several hundred people to behave as though it was their idea all along.

And if you happen to inflate a giant Donald Trump on Amsterdam’s canals, the city’s seventeenth-century bridges will provide a piece of physical comedy no creative director could have improved upon.

Systems, it turns out, are always co-authored by reality.

This week at work

Two client conversations this week. Different organisations, different problems. Exactly the same mistake.

One is designing a pilot community. As always, the interesting conversations aren’t about technology, they’re about people.

Specifically, which people.

Not the loudest voices. Not the volunteers. Not whoever has Community Champion in their email signature. (We’ve retired the word champion, which is probably healthier for everyone.) The people you want are the ones who are already connecting the organisation without being asked. The colleague everyone seems to know. The person whose Teams chats somehow span six departments. The ones who bridge gaps that don’t officially exist. You find them by watching what they already do, not by asking for volunteers.

The other client wanted to know why their intranet wasn’t working.

It turns out it’s organised around the people who publish to it, not the people who use it. Search for something and you don’t land on “I need to book parental leave” or “How do I order a laptop?” You land on “HR Services” or “Corporate Operations”, because the architecture reflects the org chart rather than the work. One team became so frustrated they quietly built their own version elsewhere. Nobody approved it. Nobody budgeted for it. They just needed something that solved the problem in front of them instead of the one the organisation thought they had. These are some of my favourite projects because, on paper, nothing is obviously wrong. The platform is fine. The content is mostly fine. Governance exists. Ownership exists. Every individual decision makes perfect sense.

It’s like one of those suburban Frankenhouses assembled over forty years from planning permission, optimism and B&Q vouchers. The conservatory solved one problem. The loft conversion solved another. The garage became a gym for six months before the running machine became an expensive laundry drying rack, and the room was turned into an office. Every owner improved the bit immediately in front of them until the whole thing acquired the navigational logic of an escape room whose clues were designed by six different consultancies.

None of those decisions was irrational. Every extension solved a genuine problem. It’s only when you try to get from the front door to the garden that you realise the shortest route involves passing through six unrelated architectural eras and apologising to whoever’s on a Zoom call in what used to be the garage.

Organisations build digital workplaces in much the same way.

Nobody sets out to build something incoherent. It just accretes that way, one perfectly reasonable local decision at a time. Every team improves its own room. Every department hangs another sign. Every budget cycle adds another extension. Nobody is designing the journey. They’re decorating individual rooms.

Fixing it requires someone who can look across the whole floorplan and say, “Yes, that’s better for Finance, but it’s worse for everyone else.”

Which means you need two things in the same place: someone who genuinely advocates for employees, and someone with enough authority to overrule everybody else.

Most organisations have one or the other. Very few have both.

So the house keeps growing. Another extension. Another corridor. Another perfectly sensible decision that makes the whole thing slightly harder to live in.

Two client rooms. One week. Same lesson.

Also this week

The popup gym closed this week. I found myself milking every possible moment, signing up to five classes on five successive days. And even going to a gym closing party. I’m now a person who goes to parties at the gym. Who even am I?

This weekend was Pride in Amsterdam. It’s one of my favourite weekends of the year, and this year’s had an extra layer: Amsterdam is hosting WorldPride, marking twenty-five years since the Netherlands became the first country to legalise same-sex marriage.

The city has been celebrating all week. Around the corner from me, at the Westermarkt, the festivities opened with the Drag Olympics, featuring events such as stiletto sprinting and the handbag toss. As with so many Dutch traditions, nobody seemed entirely sure whether this had always existed or had simply materialised because it was a good idea.

Yesterday was the Canal Parade. Eighty boats making their way down the Prinsengracht, representing every imaginable corner of the city’s LGBTQ+ communities, from the Ministry of Defence to Roze 50+ to Amsterdam’s museums turning up together in solidarity. Noticeably fewer corporate boats than in previous years, and all the better for it.

The best float, by some distance, was an enormous inflatable Donald Trump and Vladimir Putin locked in an embrace.

Amsterdam’s canal bridges are lower than many of the boats, so every single one has to deflate before passing underneath, then reinflate on the other side.

Which meant that, every few hundred metres, Trump and Putin would slowly crumple into one another, disappear beneath the bridge in a heap of orange and grey vinyl, then rise majestically back into existence for the next stretch of canal.

Nobody planned that joke, but the bridges just kept telling it.

Coverage

Allie Nawrat at Unleash asked me to weigh in on Skyfall AI’s plan to buy a small software company and install an AI as CEO.

I’ll never turn down an invitation to opine on this kind of thing, so I was delighted to pen an op ed in response. My take is that they’re testing entirely the wrong thing.

The experiment assumes the difficult part of being a chief executive is making decisions. It isn’t. Plenty of people can make decisions. The difficult bit is persuading several hundred other people — each with their own priorities, incentives and entirely reasonable objections — to act as though those decisions were sensible all along.

Revenue, churn and customer growth are the exhaust, not the interior. If your test company is small enough that everyone already knows everyone else, you’ve just removed the thing that makes leadership difficult in the first place.

Which is why I suspect they’re less likely to discover whether AI can replace a CEO than whether a small software company can survive six months with an unusually confusing org chart.

And, small housekeeping note: the book is now finally out in the US and Canada too. If you’ve spent the last few weeks apologetically explaining to North American colleagues that it existed but was being withheld from them for reasons nobody could satisfactorily explain, you can stop doing that.

Travel

None. I’m home, holding the fort while Jon’s in Canada. Quiet on this front for now. The calm, however, is temporary. The autumn diary is now filling up at a rate that suggests Future Sharon has made a series of commitments Present Sharon hasn’t properly thought through.

This week in photos

Weeknote 2026/30

Me speaking to guests at the Digital Communications at Work book launch (Photo: Paul Clarke)

Some weeks resist the usual format. This is one of them. I could tell you what I’ve been reading, what I’ve been watching, or how many emails I ignored. But none of that is important right now.

The story this week is that we had a launch party for the book, and I appear to have spent the days since discovering I have way more feelings than I’d budgeted for.

It was on the roof of Shoreditch House, which meant the whole thing happened against the skyline of the city I was born in, went to school in, and — bar a few brief spells elsewhere — lived in until I was thirty-nine. Most of the professional life this book is built on happened somewhere down there. Parliament. Banks. Charities. Agencies. Clients. Conference venues. Tube stations. Whichever Pret happened to be closest to whichever office I was working in that week.

London has never really felt like one place to me. It’s always been commutes and postcodes and jobs. But from up there, all at once, it suddenly became one continuous story. My story.

I should mention the dress.

I bought an incredible dress because it had a cape. An actual cape. Like I was either accepting an Oscar or about to arrest Lex Luthor.

I mentioned this to everyone. Not metaphorically. Literally everyone.

I’d be halfway through thanking someone for supporting my career over the last fifteen years before my brain interrupted with TELL THEM ABOUT THE CAPE.

“It’s got a cape.”

Reader, it did.

About 110 people RSVP’d. Fewer made it, as is always the way. I noticed for roughly twelve seconds.

Because then I looked around the room and realised what was actually there.

Twenty years of work.

Not “networking”, which is what LinkedIn insists on calling it. Just… people. Clients. Colleagues. Friends. The people who taught us the trade, challenged our thinking, hired us, argued with us, let us test half-formed ideas on organisations they were responsible for, and occasionally trusted us enough to implement them. Every one of them has ended up in this book somewhere, whether they know it or not.

Looking around the room, I realised there are only two occasions where everyone from across your life turns up at once: your funeral, and apparently your first book launch if you’ve spent twenty years in the same gloriously niche profession.

I can recommend the latter. Better catering. Less crying. And the guest of honour gets to wear a cape.

I gave a speech. On paper it was mostly self-deprecating jokes, because I don’t really know any other way of getting through emotional occasions. But somewhere around the thank-yous the armour stopped working.

Because underneath all the jokes about procrastination and mutually assured productivity was the thing I was actually trying to say.

I met Jon on Twitter around 2010. We started writing blog posts together. Then reports. Then client work. Somewhere along the way we accidentally built a company. Sixteen years later there’s a book with both our names on the spine.

A sequence of events that’s as brilliant as it is ridiculous.

I’d assumed I was fine. I’m good at being fine; it’s practically a professional competency by this point. But then I found myself standing in a room full of people who had each, in their own way, nudged that sequence along. The people who hired us before we really knew what we were doing. The people who challenged our thinking until it got better. The people who introduced us to other people. The people who kept believing we’d eventually finish the bloody thing.

The book felt like the excuse. Looking around the room, it was obvious what we were really celebrating was twenty years of friendships, collaborations and opportunities that somehow, improbably, added up to this.

The fineness rather comprehensively deserted me.

And then the microphone screamed with feedback, Jon looked at me, and we both completely lost it.

Which, in hindsight, was exactly the right ending to the emotional bit.

There’s a particular problem with being the centre of attention at your own party, which I last encountered at my wedding. It’s the exact opposite of ordinary party anxiety. You don’t spend the evening worrying you won’t know anyone. You spend it knowing everyone, and barely managing to speak to any of them.

Every time I got properly into a conversation, someone needed me to meet someone else, sign a book, pose for a photo, or stand somewhere with marginally better lighting. I’d spot someone across the room I’d been meaning to catch up with for an hour, start making my way over, and immediately get intercepted.

If we started a conversation and then I disappeared halfway through it, I’m sorry. I wasn’t ignoring you. I was being aggressively celebrated.

The overwhelm, naturally, waited until the following morning.

Overnight we’d been tagged in dozens of posts. People writing about the book, about the evening, about seeing old friends and making new ones. What struck me most wasn’t what people wrote about us. It was what they wrote about each other.

Lisa, who’s worked with Lithos often enough to know exactly which bits of our thinking need challenging, mapped a startling number of her own career connections back to a single retweet of mine from when Twitter was still good. One introduction became work with the British Red Cross. That became more work. That became an entire direction for her career.

I’d completely forgotten that retweet had happened.

Reading everyone’s posts, I realised how many of those moments there had been. Lisa could draw a straight line from one retweet of mine to a decade of work. I could draw equally improbable lines back to at least a dozen people in that room: someone who hired me, someone who vouched for me, someone who made an introduction, someone who took a punt on us when “us” was still mostly an idea.

None of those moments felt important when they happened. They took minutes, sometimes seconds. It’s only years later, when everyone starts comparing notes, that you realise careers aren’t built out of grand strategic plans. They’re built out of hundreds of tiny acts of generosity that the person doing them has usually forgotten by the following Tuesday.

There’s also a good story about how the book itself got written.

Donna at Kogan Page asked me if I’d write one in 2023. I demonstrated my enthusiasm by doing absolutely nothing about it for roughly a year. Eventually I said to Jon, “What if we wrote it together, so social awkwardness forces us to finish it?”

And that is, apparently, how you write a book.

We split chapters, swapped drafts, edited each other ruthlessly until neither of us could remember who’d written what, and hopefully ended up sounding like one person.

As chapter ten repeatedly points out, launching isn’t the end. It’s the point where people finally get to decide whether the thing deserved launching in the first place. So this is, technically, the beginning.

Thank you to Appspace for sponsoring the evening, so the emotional wreckage at least came with an open bar. To Paul Clarke, who photographed it, which means the bits I was too busy feeling things to remember are safely on record. To Donna and Anne-Marie at Kogan Page, whose faith in this book’s eventual existence significantly exceeded the available evidence. To the Lithos crew, who have spent years patiently correcting the pronunciation of a company name that two communications consultants somehow chose without ever saying it aloud first. To our clients, for occasionally letting us discover what doesn’t work on their time rather than ours.

And to David, who has lived with this book for considerably longer than any husband should reasonably be expected to.

Anyway.

tl;dr: we wrote a book. I wore a cape.

The launch in photos

Weeknote 2026/29

My book. On a shelf. In a shop. (Photo: me)

I have spent the last three weeks becoming the sort of person who cries in bookshops, obsessively refreshes Amazon bestseller rankings, and voluntarily disappears into a Dutch field with patchy phone signal.

In my defence, all three seemed perfectly reasonable at the time.

The book Jonathan and I have been writing for the last eighteen months finally hit real and digital shelves, which turned out to be a far more emotional experience than I’d anticipated. Work became an unexpectedly coherent series of conversations about AI, change and the uncomfortable gap between what organisations want technology to do and what people are actually ready for. Then, because I’d apparently reached my annual quota of thinking, I went to Down The Rabbit Hole festival and spent three days remembering that basslines solve more problems than LinkedIn ever will.

Only sitting down to write this did I realise these weren’t really separate stories at all. They were all, in different ways, about letting go. Of certainty. Of ownership. Of the comforting illusion that once you’ve finished something, the hard bit is over.

Anyway. Here’s the last three weeks.

This week at work

We’ve been working with a client that doesn’t want to upgrade their comms platform. Or migrate it. Or even skip a version.

They want to leapfrog the whole lot and build an AI-first communications architecture instead.

It’s an ambitious instinct, and I think probably the right one. If you’re convinced the next decade of work will look fundamentally different, designing for that rather than polishing the last generation of technology makes a lot of sense.

The awkward bit is that becoming AI-first is itself a massive change programme. And change programmes have always run on one thing: good communication. So the capability you’d normally rely on to help an organisation navigate a transformation like this is… the capability you’re busy transforming.

It’s less “fixing the plane while flying it” and more flying one plane while trying to assemble a second, better plane alongside it, using parts that are still on backorder until sometime in 2027.

The other thing that kept nagging at me was ownership. Move internal comms onto a platform designed primarily around work rather than communication, and comms stops being the product owner and becomes another customer. That’s not really a technical decision. It’s an organisational one. You’re asking a team to hand over not just a platform, but a chunk of its identity.

That tension turned out not to belong to just one client. It surfaced over and over again in conversations that had nothing to do with each other.

A recruiter described our profession as “sleepwalking into oblivion” — his words, not mine — and pointed to something I’ve been wondering about for a while. AI absolutely is making people more productive. The problem is that most of those gains stay private.

If a four-hour task now takes thirty minutes, there’s not much incentive to announce that fact to your employer. So the productivity improvement exists, but only at the individual level. The organisation never really gets to bank it.

A researcher looking at AI governance in financial services arrived at almost exactly the same conclusion from the opposite direction. Most governance fails because it lives in documents instead of products. Nobody wants another policy. They want the safest thing to also be the easiest thing.

Then I spoke to someone working on AI for maritime crews — people scattered across ships for months at a time, often speaking different first languages. Different industry. Different problems. Same conclusion.

AI isn’t reducing information overload. It’s accelerating it. Robots producing content for other robots to summarise, while the humans are somehow expected to emerge at the end of the process better informed.

What struck me was that none of these conversations had anything to do with each other. Different organisations. Different industries. Different starting points. Yet they all kept landing in exactly the same place.

The technology is arriving faster than organisations can absorb it. AI isn’t eliminating the need for communication, governance or judgement. If anything, it’s making all three more important.

It’s always reassuring when reality starts independently peer-reviewing your book.

Also this week

Ah yes. The book. It exists!

After twenty years in digital, where everything is iterative, agile, endlessly tweakable and somehow never actually finished, writing a book turned out to be the most waterfall project imaginable.

You research. You draft. You edit. You agonise over commas. Then, one day, someone prints the thing and that’s it. No hotfix. No version 1.1. No updating the chapter because you’ve thought of a better example.

Just several hundred pages of your opinions, frozen in time.

I’ve written before about being a late bloomer — the kid who couldn’t tie her shoelaces until she was ten, who didn’t finish university until 27, who never had a five-year plan and barely managed a five-day one. “Not reaching your full potential” was the phrase that got used, usually kindly, occasionally not.

People like me don’t write books. We’re not supposed to. So for eighteen months I treated it as a project rather than a fact — a series of Word documents that Jonathan and I could keep poking at forever. In the spring it became a PDF proof and a red pen. Abstract. Deniable. Still, on some level, not really happening.

Because of some logistical hiccups, my author copies were delayed. So I wandered down to the American Book Center here in Amsterdam and picked up a copy off the shelf, like any other customer.

And promptly burst into tears.

Not because it had become real, exactly. More because it had stopped belonging to me — and because the weird, shy, half-blind, shoelace-challenged kid I used to be would not have believed for a second that the object in my hands existed, let alone that I’d made it.

Suddenly it was a thing that people I’d never met were buying, reading, agreeing with, arguing with, using, learning from, spilling coffee on and — if I’m very lucky — recommending to someone else.

That’s a strangely emotional handover.

Since then it’s been quietly surreal seeing photos arrive from readers across the UK, Europe, Asia and Australia. A thing that lived almost entirely inside two people’s heads now seems to have escaped into the wild.

Unfortunately, so has my ability to behave normally about it.

Amazon doesn’t tell authors how many copies they’re selling in real time. It does, however, update the bestseller rankings with alarming regularity, which means I’ve spent rather more time than is healthy refreshing those charts and attempting to reverse-engineer my own sales figures from movements between books in the Public Relations chart.

This is obviously ridiculous behaviour. But I have absolutely no intention of stopping before the US launch later this month.

I also officially stepped into my role on the IABC EMENA board, taking on the professional development portfolio. Given the number of conversations I’ve been having lately about how our profession adapts to AI, changing careers and a rapidly shifting workplace, it feels like exactly the right thing to be working on.

Or, perhaps, like volunteering to captain the lifeboat while everyone is still arguing about whether the iceberg is really there. Time will tell.

Consuming

📺 Watching

Christopher Nolan’s Odyssey is either the most or least necessary film ever made, depending on your feelings about remaking one of the foundational texts of Western literature that people have already been adapting for roughly three thousand years.

It looks extraordinary. This is exactly the sort of film cinemas were invented for. Matt Damon makes a thoroughly convincing man who has spent the last decade annoying several gods simultaneously, and despite what the permanently aggrieved corners of the internet had to say beforehand, the casting is excellent throughout.

It is also, unfortunately, very long.

Not Oppenheimer long, where you somehow don’t notice. Properly, consciously long. Multiple wee break long. There were stretches where it felt less like Homer than a Hollywood epic fulfilling its contractual obligation to be Important Cinema.

Then again, The Odyssey is fundamentally the story of one man taking an absurdly long time to get home, so perhaps I should stop complaining about the pacing.

🎵 Listening

The real highlight of the last fortnight had nothing to do with books, AI or the future of work.

It was my annual pilgrimage to Down The Rabbit Hole, which also explains why these weeknotes disappeared for a couple of weeks.

The festival opened with Peaches dressed, entirely appropriately, as a bag of dicks, which immediately established that we were all in safe hands.

From there it just kept delivering. Little Simz. The xx. David Byrne somehow continuing to defy both age and physics. Empire of the Sun. CMAT. Johnny Marr.

My discovery of the weekend was Panic Shack: four women from Cardiff making gloriously unbothered punk music that sounds like someone weaponised the smoking area outside a Wetherspoons. I was completely sold within about thirty seconds. I also enjoyed The Mary Wallopers — essentially the Poundshop Pogues — considerably more than I’d expected.

Then Florence + The Machine closed the festival. The sun disappearing over the lake. Free ringing out across the site. Me dancing with my oldest and best friend.

After several weeks spent thinking and talking about AI, work, governance and the future of the profession, it was a useful reminder that sometimes the correct answer is to disappear into a field with no phone signal and listen to impossibly loud music for three days.

Life doesn’t get much better than that.

Life lately, in photos

Weeknote 2026/26

A man paddleboarding on a picturesque Amsterdam canal on a sunny day.
Going away is great. Coming home to this is even better. (Photo: me)

Human beings like to imagine that awareness is a kind of immunity. It isn’t.

This week I spent a lot of time thinking about systems: how organisations choose technology, how AI adoption actually happens, and how large companies engineer the incentives that keep us doing exactly what they’d hoped we’d do.

Then I lost my Kindle halfway through a chapter explaining Amazon’s lock-in strategy. And I replaced it within days.

It’s oddly comforting to discover that, however well you understand the machine, it still processes you exactly the same as everyone else.

This week at work

I spent a good chunk of the week with an internal communicator trying to answer one of those questions that sounds straightforward until you actually ask it: what’s the best intranet platform?

The answer, infuriatingly, is the same as it always is:  it depends.

There are dozens of dedicated intranet platforms before you even get into the various flavours of SharePoint and employee apps. Then come the demos. The analyst reports. The comparison matrices. The sales teams who all insist their product was designed specifically for organisations exactly like yours. Somewhere around this point IT joins the conversation with a list of things they’ll never support, procurement starts asking awkward questions, and everyone’s forgotten what problem they were trying to solve.

Which is why the first job isn’t evaluating products. It’s deciding how you’re going to evaluate them.

The obvious place to start is with the technology you’ve already got. If you’re a Microsoft organisation then SharePoint isn’t really a choice; it’s already sitting there waiting for you. The real decision is whether you use it as Microsoft intended, add an intranet-in-a-box product on top, or walk away from the ecosystem altogether.

All three can be the right answer.

Native SharePoint is wonderfully flexible in much the same way Lego is wonderfully flexible. Given enough time and determination you can build almost anything. You can also spend six months arguing about which brick goes where before you’ve produced anything recognisable.

An intranet-in-a-box gives you much stronger opinions. Less flexibility, more momentum. That’s often sold as a compromise. In practice it’s frequently the thing that stops a project disappearing into an endless debate about homepage layouts and whether every department deserves its own shade of blue.

Going outside Microsoft opens up some genuinely excellent user experiences, particularly for frontline organisations. But you also inherit a different set of problems: identity, people data, integrations, duplicated content, and all the other plumbing that nobody puts on the front page of the brochure.

The technology, though, is only half the story. The bigger question is what you actually need the thing to do.

An intranet serving lawyers, engineers and office workers looks very different from one serving retail staff who’ve never logged into a corporate laptop. That’s one of the reasons Jon and I built the “graphic equaliser” model into Digital Communications at Work. Every intranet is balancing the same handful of jobs — communications, knowledge, applications and collaboration — but every organisation pushes the sliders differently. It’s a much more useful place to start than asking which platform everyone else seems to be buying.

This particular communicator is already leaning away from SharePoint. That may turn out to be exactly the right decision.

The important thing is being able to explain why before the first vendor demo persuades you otherwise.

Jon and I also managed to spend a day together this week working through upcoming client projects and making one final pass at the book launch.

With publication less than a week away, the to-do list has entered that peculiar phase where everything feels both desperately urgent and somehow already too late.

We even remembered to take a photo together. Admittedly I then asked Gemini to remove the evidence that I’d apparently eaten lunch directly onto my shirt. Authenticity has its limits.

Sharon O'Dea and Jonathan Phillips stand smiling together in a bright, plant-filled hotel lobby, both wearing white shirts.
Not pictured: the lunch spilled down my shirt (AI edited)

The strangest part is that people have started receiving their copies of the book. Mine, meanwhile, is somewhere between a warehouse and Amsterdam.

There’s something slightly surreal about knowing people you’ve never met are already reading words you spent two years writing, while you still haven’t actually held the finished thing yourself.

I’m sure there’s a profound metaphor in there about letting creative work go. Fortunately, I’m under no obligation to find it.

Also this week

Back from Canada and straight into a record-breaking heatwave, which my body greeted as if someone had accidentally changed the difficulty setting.

After all of 22 hours at home I was back at Schiphol, Bristol-bound to catch up with Jon and — much more importantly — to see one of my oldest friends, Katy, for Super Furry Animals at Bristol Sounds.

It was their first tour together in more than a decade, and they wisely resisted the temptation to get clever. Hit after hit, just enough deep cuts to keep the loyalists happy, and a reminder that they were always far stranger, funnier and more inventive than they were ever given credit for.

The really odd thing was discovering that every lyric was still sitting somewhere in the back of my brain, untouched for twenty-odd years, waiting to be retrieved at a moment’s notice.

I can’t remember why I walked into the kitchen half the time, but apparently The Man Don’t Give a Fuck has been safely preserved since 1996.

The venue sits right on Bristol’s harbourside and, under normal circumstances, must be one of the nicest places in the country to watch a gig.

Unfortunately the weather had decided to recreate the surface of Mercury.

It was still glorious.

There’s a point at every really good gig where your brain stops keeping score of everything else. The heat, the crowds, your feet hurting, the price of the beer. It all just… drops away for a couple of hours.

The heatwave finally admitted defeat last night. For hours, lightning rolled across the sky behind the Westerkerk while thunder echoed around the city. I abandoned all pretence of doing anything useful, put the tripod in the window and just watched.

Nature remains embarrassingly overqualified for putting on a light show.

Consuming

I managed to lose my Kindle somewhere between Toronto and Montréal.

This would merely have been annoying were it not for the fact that I was halfway through Cory Doctorow’s Enshittification at the time.

Specifically, I’d just finished the chapter explaining how Amazon uses DRM to lock you into its ecosystem. Once your library exists inside Kindle, he argues, the cost of leaving becomes larger than the cost of staying. You’re not choosing the best device anymore. You’re paying an exit fee from a prison you forgot you were in.

Staring a bookless flight home in the face,  before heading to the airport, I went to Best Buy and bought another Kindle. Immediately.

No comparison shopping. No soul-searching. No stirring speech about refusing to reward monopolistic behaviour. Just the defeated efficiency of someone who has read the warning label, nodded thoughtfully, and carried on drinking the poison because, in fairness, it does come in a very convenient bottle.

It’s one of the defining experiences of modern life: becoming fully aware of the machine while continuing to feed yourself into it because all your stuff is already in there.

Doctorow would probably regard this as evidence. Amazon would probably regard it as a successful customer journey.

Coverage

Over on Reworked this week: More Tools Won’t Fix Collaboration. Communities Might. It’s about the thing I think a lot of AI rollouts are getting wrong.

Most organisations are still treating adoption as a licensing problem. Buy the seats. Deliver the training. Publish the guidance. Job done.

Except it isn’t. People don’t really learn new ways of working from documentation. They learn them from each other.

The missing infrastructure underneath most AI programmes isn’t another platform. It’s the social layer that helps people swap ideas, steal good workflows and discover what’s actually useful.

Seat counts tell you how much AI you’ve bought. Appropriation tells you how much you’re getting back.

This week in photos

Weeknote 2026/25

Sharon O'Dea standing in bright sunshine in Toronto, smiling at the camera in front of a large TORONTO sign. The city skyline is in the background.
A lot sunnier than the last time I was here

I came to Canada and was immediately, overwhelmingly, welcomed.

Some of it was people I already knew — friends from online, from conferences, from random corners of the world who happened to be in the same city at the same time. Some of it was strangers who became familiar within hours. A pub full of Canadians who adopted me on the basis of a red bucket hat. A room full of communicators who turned up with problems and left with each other’s contact details. A community that has been warm in the way that only happens when people genuinely care about the work they do and the people they do it with.

I love people. Specifically: being in rooms with them.

This fortnight provided an almost unreasonable quantity of that. New conversations. Old friends. Conference corridors. Hotel bars. Dinners that ran late, then turned into windowless speakeasies. The peculiar magic of finding yourself among people who understand your niche corner of the world without requiring a fifteen-minute explanation first.

And then, after several consecutive days of exactly the thing I claim to enjoy, I fled into the Quebec wilderness and spent a day hiking alone in relentless rain.

One of the more annoying discoveries of adulthood is that liking people and needing a break from them are not, in fact, contradictory positions. So I’m heading home today full. Full of conversations, ideas, and new connections.

Also, briefly, full of rainwater.

(regular readers — hello, Mum 👋 — will note there was no weeknote 24. I was just crazy busy and it fell off my radar. Bumper edition this week to make up for it.)

The last two weeks at work

The last fortnight was largely consumed by Toronto, where I spent the better part of a week oscillating between IABC World Conference and Comms Reboot. But it actually began a little earlier, with Jon and me delivering our Infozempic webinar — our increasingly elaborate attempt to explain information overload through the lens of weight-loss drugs — to communicators across Denmark, Sweden and Germany.

The session went well. The audience was engaged. The feedback was positive.

And yet presenting to a gallery of muted thumbnails remains one of the least natural activities modern working life has invented. Human beings spent hundreds of thousands of years evolving to communicate face-to-face and have somehow landed on “talking enthusiastically into a laptop while occasionally wondering whether everyone has quietly gone to make tea”.

Sunday was considerably better.

I opened the IABC Heads of Comms Special Interest Group, delivering essentially the same material to a room full of actual people. Lots of questions. Good discussion. The sort of session where you can feel the audience thinking with you. Every time I do both formats back-to-back I’m reminded that online may be more efficient, but in-person is still better.

Then came three days of the main conference.

There was plenty worth taking away. Fred Cook from USC Annenberg shared data showing the proportion of CEOs who think companies should speak publicly on social issues has fallen from 89% to 52% in just two years, which feels like one of those statistics that tells you rather a lot about the current moment. There was a surprisingly interesting session on what communicators can learn from DJs. Lots on AI, segmentation, employee engagement and the usual industry obsession with measuring things that may or may not actually exist.

I came home with a notebook full of ideas and an even bigger ‘to read’ pile than I had before.

The week finished with Comms Reboot, Jenni Field’s unconference. If World Conference is about learning from experts, Comms Reboot is about locking practitioners in a room together and seeing what happens. No speakers. No slides. No carefully polished case studies. Just people bringing problems, experiences and opinions. After three days of sitting in rows, it was refreshing to spend an evening sitting in circles.

More broadly, the whole week was a reminder of how much I enjoy spending time with people who think deeply about this work. Not people collecting hot takes or chasing engagement, but practitioners wrestling with genuinely difficult questions about trust, leadership, culture, technology and communication. I came away with pages of notes, half a dozen new ideas, and several things I thought I understood that now require further examination. Which is generally a sign that you’ve learned something worth learning.

It was also a welcome break from the strange economics of LinkedIn, where every problem can apparently be solved with a carousel, every case study is a triumph, and everyone is either disrupting, transforming or revolutionising something. There’s a lot to be said for spending time in rooms where people are allowed to admit that the work is complicated.

Back in the real world, both client projects moved forward nicely. We also picked up a new IA piece with a returning client, which is always gratifying. Winning new work is lovely. Being asked back is better.

A couple of other opportunities continue to move through the pipeline. One scoping conversation was rather more adversarial than I’d hoped, but occasionally consulting involves politely explaining that reality exists. If a prospective client can’t handle that, that’s probably not a project worth taking on.

Meanwhile the book is now less than two weeks from publication, which means the marketing machine is cranking into life. This is either exciting or terrifying. Possibly both.

Also this fortnight

I turned another year older the day before leaving for Canada. Did very little to mark it. Birthdays at this age are less a celebration than an administrative update.

The timing of the trip was fortunate in ways I hadn’t anticipated. The World Cup had just kicked off, and Toronto was a host city. I took the train in just before Canada’s first game began, dropped my bag at the hotel, changed into red and white, and headed for the nearest pub. Where I was immediately adopted by Canadians. There are worse ways to arrive somewhere.

A friend I met at a conference in Aarhus a decade ago happened to be in the city for birthday drinks of his own, which meant an unexpected reunion — one of those pleasing discoveries that some friendships travel well across a decade and an ocean. The following evening, a jetlagged dinner with one of my Colombia Flashpack group, Jenna.

After four days of Comms Reboot, I was finished. Not with the event — the event was excellent. Finished with people. Finished with noise. Finished with eye contact. Finished with hearing my own voice.

So I took a bus to Mont-Tremblant National Park and spent a day hiking alone in what I can only describe as rain with intent. Rain that had clearly reviewed my plans and taken them personally. The trails were deserted. The sky was the colour of a corporate e-learning module. By mid-afternoon I was essentially a mobile ecosystem. It was magnificent.

The Dutch call it uitwaaien — literally, “to blow out”. What I’d failed to appreciate until that afternoon is that sometimes the most effective way to stop thinking about work is to become completely preoccupied with whether your socks have dissolved. If your job depends on people, you’ll recognise the feeling. The peculiar exhaustion that comes not from hard work, but from constant connection. Eventually your brain becomes the spinning beach ball of death. At that point, mindfulness apps are of limited value. What you need is wilderness, hostile weather, and absolutely nobody asking if you’ve got five minutes for a quick chat.

The rain followed me to Montreal, where another Colombia Flashpack friend, Andrea, came to meet me for the weekend. Montreal, it turns out, is entirely unbothered by rain. We were tourists, unashamedly. It was exactly what was needed.

Consuming

Normally I’d tell you what I’ve been reading or watching. This fortnight I have been watching football. This will surprise anyone who knows me, as I have historically had the relationship with football of someone who is aware it exists and considers that sufficient. I do not have opinions on football. I do not follow football. I have never, to my knowledge, voluntarily sought out football.

And yet here I am, having thoughts about squad fitness. Tracking recent form. Trying to work out the progression paths for any of the myriad teams I am apparently entitled to support, on account of having what I can only describe as complicated nationality. The Dutch. The English. The Scottish. The French. And, because I happen to be here, Canada.

It’s a lot of flags. It’s a lot of feelings. A lot of football.

Connections

Too many to list — between IABC World Conference and Comms Reboot, both my heart and my notebook are full. But I’ll try.

It was wonderful to spend time with Lucy Eckley, Kathryn Kneller, Janet Hitchen, Eduvie Martin, Katie Macaulay, Lisa Riemers, Simon Cavendish, Simon Finch, Mike Klein IABC Fellow, Ann-Marie Blake, Sia Papageorgiou, Andrea Greenhous, Monique Zytnik, Arnab Roy Choudhury, Matisse Hemel-Nelis, Shannon Hofmeister — and to meet so many brilliant new faces from across the global community, including Pinaki Kathiari, Darlene Wilson, Mel Loy, Mirko Petricevic (and tens of others!)

At Comms Reboot, it was a joy to see Jenni Field and Chuck Gose and Priya Bates — and to meet a whole host of new faces from the Greater Toronto area.

A diverse group of eight people seated in two rows, all in black Comms Reboot t-shirts

The IABC EMENA AGM took place a couple of weeks ago, and the new board slate was ratified. I’m on it. I’ll be taking on the Professional Development portfolio — which means I’m now very keen to hear from members about what they want to learn, and equally keen to speak to people who have knowledge to share and might want a platform to do it. Word Conference was a fab opportunity to spend time with the IABC EMENA crew, and I’m looking forward to doing that a lot more in the year ahead. If you’re an IABC member with ideas, ambitions, or expertise, do get in touch.

Coverage

Two pieces out in the last fortnight.

In In.Comms, I wrote about what happens when your internal community turns on the company — and why every tool in the standard moderation playbook becomes an escalation tool the moment it does. The short version: you can’t moderate your way out of a legitimacy problem. The dissent isn’t noise to be managed down. It’s the signal.

And in PRMoment, Ann-Marie Blake wrote up my IABC Heads of Comms keynote on infobesity — the argument that information overload is structural, not personal, and that the comms equivalent of GLP-1 isn’t telling people to manage their inboxes better.

Travel

Currently: Montreal, with 24 hours left before the long journey home.

Then 24 hours at home — enough time to do laundry, presumably misplace something important, and remember what my flat looks like — before heading out again.

Not my finest logistical work. Wish me luck.

This week in photos

Weeknote 2026/23

Prinsengracht this week (photo by me)

One of the greatest disappointments of adulthood is learning that some people genuinely know what they’re doing.

Not in the broad sense. I mean specifically the people who have already booked next year’s holiday, understand their pension, and never once find themselves searching for accommodation the day before departure while wondering whether a 70-minute flight connection was always part of the plan.

I watch these people with fascination.

My own system is to organise the important 20% very efficiently, then leave the remaining 80% until it becomes an emergency. This is objectively a terrible process, but it has the advantage of being familiar.

And yet, inconveniently for anyone hoping to stage an intervention, some of the best things in my life have emerged from exactly this sort of organised chaos. Moving countries. Starting a business. Building friendships. Speaking opportunities. Entire adventures that began with a vague idea and an alarming lack of preparation.

I turn 46 this week, which some people might regard as a sensible moment for self-reflection and personal growth. After reviewing the evidence, however, I appear to have concluded that the system works.

Or at least that it fails in sufficiently interesting ways that I’m not planning to replace it now.

This week at work

A week with a theme running through it, which, as usual, I only spotted while writing this: most of what landed on my desk was some variation on “the platform isn’t the problem.”

Monday opened with a former colleague telling me about working in a building that’s actively falling apart — heating dead, a floor shut because of dodgy plumbing, a countdown underway to get everyone out before the place deteriorates any further.

The detail that stuck wasn’t the building itself, though. It was the contrast. Like a great many organisations, serious money is spent on customer-facing services, while the tools employees use all day are left to limp along for another year. The same staff being asked to transform services are doing it with systems held together by string, workarounds, and good intentions.

You can’t ask people to reinvent how they work while handing them a platform older than some of the employees.

Midweek brought news on the vendor side: a platform we’ve worked with a few times over the years has been acquired, pairing a newsletter business with an employee experience one. Old-world distribution meeting new-world engagement, if you want the elevator version.

What’s particularly interesting for us is that it lines up rather neatly with one of the threads running through the book. Organisations need both a trusted source for publishing and effective channels for distribution. We’ve spent years treating those as separate conversations, but increasingly they’re becoming the same one.

This week also brought a quick-turnaround proposal on a genuinely interesting piece of information architecture work, which I’ll seize almost any excuse to do. Partly because I get to play with dendrograms, but mostly because IA is one of those disciplines everybody agrees is important right up until it’s time to invest in it.

Findability is the whole game. It’s the difference between a channel people rely on and one they stop bothering with. Content that can’t be found can’t be used, and most organisations are sitting on shelves of the stuff: carefully created, properly signed off, and effectively invisible.

The latter end of the week went on preparing for a couple of upcoming events. A talk Jon and I are doing on Tuesday about information overload and how to tackle it, and a workshop helping a client’s team get their content “agentic ready”.

Which sounds like it should be a conversation about technology, but pointedly isn’t.

They already have a platform that does the job. The interesting questions are all the other ones: what’s actually a source of truth, what has simply been sitting there accreting since 2018, what needs to be maintained, and what can probably be allowed a dignified death.

An agent is only ever as good as what it’s reading. Which means the role starts to shift from publishing content to maintaining a clean, structured, trustworthy body of knowledge that people — and increasingly machines — can rely on. That’s a different skillset, and in some cases a different job. Pretending otherwise doesn’t help anyone.

We also spent some time this week reviewing questions for an internal comms survey, which is the sort of task that tends to provoke a certain amount of professional eye-rolling. Surveys are deeply unfashionable. Too long, too blunt, too often ignored. Most of that criticism is fair. None of it makes surveys useless; it just means most surveys are bad, which is a different problem.

The failure mode is usually the same. Someone wants to “just check” one thing. Then somebody else wants to check something else. Then a third person remembers a question they liked in another survey. Before long the thing has collapsed under the weight of its own curiosity.

Every question should earn its place by pointing at a decision. If the answer wouldn’t change what you’re going to do next, why are you asking it?

And the rule that gets broken most often: don’t ask if you’re not prepared to act. A survey is a promise disguised as a question. Ask people what’s wrong, do nothing about it, and you haven’t gathered insight. You’ve simply taught them that answering was a waste of time.

Better to ask three things you’ll genuinely act on than thirty you’ll quietly file away.

Which, now I write it down, turns out to be much the same lesson as everything else this week. The platform isn’t the problem. It’s everything around it.

Also this week

Two things, the first of which my body would like formally noted as a complaint.

The pop-up gym had an unlimited-classes deal on, and I — being me, congenitally unable to leave value on the table — fell on it with rather more enthusiasm than sense. Twelve classes in ten days, plus two more at my usual place, by which point even I could concede the maths had got away from me.

By Saturday, every muscle I possess was filing grievances with management. The whole enterprise was demanding a rest day, preferably submitted in writing and accompanied by supporting documentation.

I took one courtesy of birthday drinks with my local friends. At some point during the evening I looked around the table and had one of those moments that occasionally sneaks up on you.

I arrived in Amsterdam with two suitcases and a bag of optimism. Somehow, over the years, that has turned into a life filled with smart, funny, generous people who I genuinely enjoy spending time with. Not a bad return.

Consuming

I took my slightly sore head to the cinema on Sunday for a 25th-anniversary screening of Legally Blonde. The first thing to process was that 2001 — a year that feels, to me, basically last week — is now a quarter of a century in the rear-view, which is its own small horror.

The second was that it’s a more awkward watch than I’d filed it away as. Not in the obvious tabloid-feminism way — I can forgive a film for thinking liberation and a good blow-dry are the same project, that’s just 2001 being 2001. It’s the gay panic that’s curdled: a whole comic beat hinges on whether a man is gay or European, as though those are the only two options and both are punchlines. It plays now like a relic of a moment that thought it was being progressive and was mostly being loud.

And yet. Some of those lines have been lodged in my head for over twenty years, fully paid-up, and they still land. A film can be a period piece and a comfort blanket at once, apparently. Both things were true in a dark room and a comfy chair, hangover and all.

Connections

Two this week, both of the lovely-people-passing-through variety.

Tuesday brought Mike Wilkins, in town for a conference. Mike was a fixture of my London drinking life back when we both worked in the City and shared the good fortune of having offices within easy reach of the Old Doctor Butler’s Head — a pub that hosted a great deal of what we would have described as networking and HMRC might reasonably have described as Tuesday afternoon.

Since then we’ve scattered ourselves across continents: me to Amsterdam, Mike back to New Jersey. Which means opportunities to catch up over beers and schnitzel are rarer than either of us would like, and probably all the better for it when they happen.

Then Sarah Kocianski, another London friend, in town for Money20/20. We took the opportunity to put the world to rights over a very respectable Côtes du Rhône, as is traditional.

One of the unexpected side-effects of moving countries is that your friendships become event-based. You don’t have last-minute catch ups any more; you get concentrated bursts of conversation every few months or years. The intervals get longer, but somehow you pick up exactly where you left off.

Coverage

The folks at Nexer have put this year’s Camp Digital videos online, which means I get to point you towards 300 Seconds — the initiative I co-founded to help people who’ve never spoken at an event get their first go somewhere safe and supportive.

The format is simple: first-time speakers are paired with experienced ones to shape and rehearse a five-minute talk, then unleashed on an audience. Camp Digital have given us a slot on their agenda four years running now, and this year’s lightning talkers were Oana Puicar, Zhen Yang, Robin Roy, Aditya Shah and James Bilham.

You can watch the 300 Seconds session here.

The bit I’m proudest of, though, is what happens afterwards.

Almost every year, one of our speakers comes back with a full conference talk of their own. This year it was Jane Bowyer, who did a 300 Seconds slot in 2025 and came back to give a half-hour talk on the messy middle of design careers.

Which is really the whole point.

People often think the challenge is learning how to speak. Most of the time the challenge is believing you’re allowed to.

Five minutes isn’t just five minutes. It’s proof that you can stand on a stage, say something worth hearing, and survive the experience. Once you’ve done that, a lot of other things start to look possible.

Travel

I’m off to Canada for the IABC World Conference at the end of this week — a trip that has existed in two very different states.

The transatlantic flights and conference hotel were booked back in March, radiating the sort of competence that suggests a responsible adult was briefly involved. Everything else has been organised considerably more recently, in the long-standing tradition of confusing “I have a flight” with “I have a plan”.

The challenge now is balancing the two things I actually want to do: catch up with friends and see more of a country I’ve barely visited. Both entirely achievable goals, were it not for the small matter of attempting them during the World Cup.

It turns out accommodation pricing during a major international sporting event follows the same basic principles as airline baggage fees: technically legal, emotionally upsetting. Still, some combination of trains, optimism and questionable decision-making has got me this far. No reason to abandon a proven methodology now.

Elbows up!

This week in photos