01 · The problem
Asana isn't broken. Nobody owns keeping it true.
A task board holds the cards you put in it, in the columns you drag them to. The gap you're feeling isn't a missing feature — it's a missing person. Cards go stale because updating them sits below everyone's real work, and "reconcile the board" was never actually assigned to anyone.
02 · What you need
Nothing moves in your project until you say so.
She asks the owner, carries the answer back, and checks it against Asana before touching anything. Then the change reaches you as a before/after diff — this section to that section, what changed, and why — and it waits there. The chasing runs on its own; your board stays yours.
03 · How it runs
What she runs on top of Asana.
Set where the asking happens and what an answer gets checked against. Every step rewrites itself to match, because the surface changes the words and never the work — and where a surface genuinely can't do something, it says so rather than skipping it quietly.
04 · What it's worth
What a migration actually buys you.
If Asana is genuinely the wrong shape for your team — wrong hierarchy, wrong pricing, a workflow it can't express — then move, and don't let us talk you out of it. But if what you're escaping is the staleness, read what ports over with you.