The slow drift nobody talks about

If someone new joined today and needed to pick up a live project, could they get up to speed from Asana alone - or would they need to be walked through it? If the answer is the latter, that's not a people problem. That's a system design problem.

Diagnose before you redesign

The most common mistake teams make when they notice their Asana isn't working is jumping straight to solutions. New templates. A restructure. A fresh start. All of which cost time and energy - and most of which will drift again within six months if the underlying patterns haven't been examined.

In human-centred design, the Double Diamond separates problem-finding from solution-building. The first diamond is diagnosis: understanding what's actually happening, not what you assume is happening. The second is design: building something that responds to what you found.

A mid-year reset starts firmly in the first diamond. Before you change anything, get curious.

Ask: Where do tasks fall through the cracks? Where is the real work being tracked - in Asana, or in a spreadsheet someone started "just temporarily"?

These are "how might we" questions, not "how do we fix it" questions. One opens up the problem space. The other closes it down before you've understood it.

When we sit down with clients for a workspace health check, we start here - not with "what should we rebuild" but with "what's making work harder than it needs to be right now?"

What systems drift actually looks like

The same patterns come up again and again.

• Custom fields inconsistently filled in - or duplicated because nobody could find the original.
• Templates that were great on day one but never updated to reflect what the team actually learned.
• Projects that finished months ago still sitting in active lists.
• Real people assigned to template tasks, so when someone leaves, their name lingers across every new project.
• Decisions and context living in Teams chats and emails - so anyone picking up mid-stream has no idea what happened or why.

This isn't about discipline or effort. It's about design. If the system doesn't make the right behaviour easy, people find their own path - and over time, those paths diverge.

The mid-year reset as a practice, not a project

The goal isn't a one-time clean-up. It's building the habit of reflection into how your team operates.

In change management terms, this is reinforcement - the most commonly skipped step in any adoption effort. Teams invest in training, launch, and go-live support, then move on. Without deliberate reinforcement, adoption quietly erodes.

A mid-year reset might look like:

• Active project review: what's genuinely active, what should be archived, what hasn't been touched in 90 days?
• Template audit: are people tweaking templates on live projects? If so, what needs to change in the template itself?
• Custom field health check: are fields filled in consistently, or is the same thing tracked five different ways?
• Ways of working conversation: is Asana the source of truth, or one of several places where partial information lives?

Start with questions, not answers

Slow down enough to ask good questions before reaching for solutions.

What's working? What's creating friction? What did you learn in the first half of the year that your templates don't yet reflect?

From there, you redesign with confidence - not just rebuilding what you had, but building something that reflects how your team works now.

If you want to make this a regular practice rather than a reactive one, our piece on establishing an Asana Centre of Excellence is a good starting point.