fun with balance balls

Adam Englebright•9 July 2015•1 min read
fun with balance balls
			<iframe src="https://vine.co/v/enV3IZqxQ1a/embed/simple" width="600" height="600" frameborder="0"></iframe>

Brightlocal, the company with whom we share an office, are very keen on balance balls. This has now spread to us, with Juan and Dara both abandoning their chairs for them (Mark and I both tried and decided against). Balance balls, though, are by nature quite bouncy. This leads to a lot of... the kind of thing in the vine above.

Ready to talk?

Book a free discovery call to discuss how we can help with your data and analytics challenges.

Book a discovery call

Check your setup for free

Our instant analytics audit scans your GA4 configuration and flags what's missing, broken or misconfigured.

Run a free audit

Suggested content

Siloed data, central intelligence

Someone in your organisation has already connected an AI agent to a live data source. Probably several people have. They've pointed Claude at HubSpot, asked it to pull numbers from Google Analytics, had it read a Jira board or reconcile figures across two systems. The data never moved. Nobody waited for a pipeline. Nobody asked the data team. They did this because it was easy. And people will always go where the friction is least. This is happening everywhere, across every function, in organis

Matthew Hooson•9 Apr 2026

What we learned building AI agents for clients (and ourselves)

From internal experiments to client-facing data products Eighteen months ago, we started building AI agents internally. Not as a product play - as a way to stop doing repetitive work. Documentation, QA checklists, data validation. The kind of tasks that every analytics consultancy does hundreds of times a year and nobody enjoys. That experiment became our first internal AI assistant. And what we learned building it changed how we think about data products for clients. Here's what we know now

Mark Rochefort•8 Apr 2026

What is a semantic layer and why your AI agents need one

Companion piece to Measure Pod #139 with Colin Zima and #98 with David Jayatillake Your warehouse is full of tables. Your agents can query them. The question is whether they'll get the same answer. Ask three different agents "what's our monthly revenue?" and you'll get three different numbers. Not because the data is wrong - because nobody defined what "revenue" means in a way machines can consistently resolve. Is it gross or net? Recognised or invoiced? Including refunds or not? Each agent ma

Mark Rochefort•7 Apr 2026