All Posts

Right now, somewhere on your team, someone is making a confident decision from the wrong version of your spreadsheet. They don’t know it. You don’t know it. They’re reading numbers they completely trust, in a file that looks exactly like the real one and you’ll both find out it was wrong in about three weeks, when a deadline slips or a figure refuses to reconcile, long after the copy that caused it has been overwritten and the trail has gone cold. If that sounds familiar, the

The spreadsheet that saved your team last year is the one that will quietly fail it this year. Nobody will break it on purpose. It will simply be handed a job it was never built for, the moment a second person opens it, then a fifth, then a whole department and it will start to buckle under a weight it was never designed to carry. A spreadsheet is built for one author. One purpose, one owner, one mental model of what every column means and why. For that job it is close to pe

You never noticed the moment your spreadsheet started charging you. There was no invoice, no line item, no approval to sign. Just a few minutes gone every time you opened it, working out what changed since yesterday, which tab is the live one, who overwrote the column you were using. On any single morning it feels like nothing, barely worth mentioning. That is exactly why it is so expensive. Multiply those minutes by everyone on the team, by every day of the year, and you are

Your best process has a single point of failure, and it is a person. The one who remembers to chase the approval. The one who spots the request before it goes cold. The one who knows whose turn is next. Put them on a flight for six hours and watch what happens: the approvals stall, the requests pile up in five different inboxes, and nobody notices until the deadline has already passed. You did not build a process. You built a dependency on one person’s memory and you have bee

Here's the biggest mistake teams make when they move from Excel to Asana and it's not a technical one. It's migrating everything. It feels like diligence. Every row, every tab, every colour-coded column, faithfully recreated in the new tool. But a spreadsheet that has run a team for three years isn't a clean data model. It's the fossil record of every workaround you ever invented: the column someone added for one awkward client, the tab that exists because two people disagree

Here's the direct answer, because this comparison has one: it depends on what the file is doing. If the file is calculating budgets, forecasts, models, analysis Excel wins, and it isn't close. If the file is coordinating people, deadlines, handoffs, status, Asana wins, and it isn't close either. But here's the thing: if you're searching this comparison at all, something in your week already hurts. Nobody googles "Asana vs Excel" while their tracker is working. You google it t

Here's an unfashionable opinion: more features aren't always an advantage. Beyond a certain point, they're a liability you pay for every day. That idea captures the Asana vs. ClickUp decision. ClickUp's pitch is simple: one app to replace them all, covering tasks, docs, whiteboards, chat, goals, time tracking, and more. Asana takes a narrower approach, focusing on clarity about who's doing what, by when, and why, at any scale. The everything app versus the clarity app. Which

Let us start with the claim you were probably braced for, so we can get rid of it: agentic work management does not replace project management. Anyone telling you it does is selling something and overselling it. If you run operations or a PMO, you have earned your scepticism. You have survived at least one "revolutionary" tool rollout that produced a licence bill and a graveyard of half-adopted boards. So this article will not ask you to believe in a revolution. It will do s

There's a moment most growing teams in the Netherlands hit with Asana. The tool is live, the projects exist, everyone technically has an account and yet the work still runs the way it always did: in someone's head, in a spreadsheet on the side, in the Thursday meeting where everyone finds out what's actually happening. The scale of that gap is measurable. Asana's own Anatomy of Work research has consistently found that knowledge workers spend around 60% of their time on "work

For twenty years, "work management" meant a place to store work: tasks, owners, due dates, status. A human read the board and did the next thing. Agentic Work Management breaks that assumption. In this model the software doesn't just hold the plan it can also act on it, because AI agents sit inside the same projects as your team, with the same context and the same rules. Asana defines it in one sentence: "Agentic Work Management is how people and agents run critical workflows

Asana's AI platform has three headline products, and teams routinely buy the wrong one first. They share a brand, a data model, and even a billing pool but they solve different jobs. THE 15-SECOND ANSWER AI Teammates = ready-made agents that do the work. Dash = a personal orchestrator that tells you what needs attention and routes work to those agents. AI Studio = a no-code builder for your own custom AI workflows when no prebuilt agent fits. What each one actually is Not sur

Here's something I see constantly: ops managers, agency founders, and team leads who have genuinely talented people sitting right in front of them and still can't figure out why performance keeps plateauing. The team isn't the problem, the absence of a structured learning system is. When there's no training plan, people guess what "good" looks like. They either over-train or coast entirely. And the cost of that ambiguity shows up in missed handoffs, repeated mistakes, and the

Let's be honest about what performance review season actually feels like for most team leaders. It's that sinking feeling the week before reviews are due, suddenly you're digging through six months of Slack threads, emails, and half-remembered project updates trying to piece together a fair picture of what someone actually accomplished. You want to give your team the thoughtful, meaningful feedback they deserve, but the process is so exhausting that you end up rushing it. And

I know what it feels like when content production is running you instead of the other way around. Tasks being built from scratch every single time. Production requirements living in someone's head instead of in the system. Editors spending more time chasing status updates than actually editing. Stories falling through the cracks not because anyone was careless, but because the process had too many gaps for things not to fall. Here's the thing I've learned after watching teams

Let me tell you what having "an AI strategy" actually looked like for us twelve months ago. One person swearing by ChatGPT. Another using Claude. Our SEO specialist was sitting on a goldmine of prompts she'd built over months of prompts that had never made it to the content team, or anyone else. Everyone feels productive. Everyone feeling busy. And somehow the outputs were all over the place. Inconsistent brand voice. Duplicated workflows. Knowledge trapped in individual inbo

I've sat in enough rooms with enough leaders to know exactly what AI conversations look like right now. Executives are genuinely excited. And the people actually doing the work? They're nodding along in the meeting and quietly going back to their desks feeling anxious about what all of it actually means for them. This tension is backed by real data. And once you see it clearly, you know exactly why so many AI rollouts are struggling, and more importantly, what the ones that a

In our last post, we spoke on Why Your Team Isn't Using AI And Five Unconventional Ways to Actually Fix It, today we’d be sharing a practical guide on How to Get Organizational Alignment on AI. Here's something that broke my heart the first time I saw the data: more than half of employees genuinely believe AI will help their organization hit its goals. More than half. The will is there, the hope is there. And yet only 17% have ever received any training on how to actually u

I've watched the same thing happen at organisation after organisation, and it goes like this. Leadership comes back from a conference fired up about AI. Tools get purchased. A company-wide email goes out. There's a kickoff meeting with a slide deck and genuine energy in the room. And then, six months later, barely anyone is actually using them. The tools sit there. The mandate fades. The team carries on exactly as before and leadership is left quietly wondering whether the pr

The campaign went live on a Thursday. Nobody celebrated. We were just relieved it hadn't collapsed. The creative arrived two days late. Someone on the team had been working off a brief that had been updated without anyone telling them. And I found out about a deadline change three days after it had already shifted through a Slack message buried under 20 other notifications. We hit publish. We moved on. And I sat with this quiet, uncomfortable question for days afterward: why

I remember the exact moment I realised our marketing strategy was dead, not because it was a bad strategy, but because we had no system to keep it alive. It was a Wednesday, and we'd just wrapped what felt like our best quarterly planning session ever. Clear goals. Aligned priorities. Everyone in the room nods, I walked out genuinely confident we had something. By Friday, three different team leads were executing three completely different versions of the plan. Nobody was lyi