Asana Is Talking About Shared Context. Here’s Our Small Fix for Campaigns.

A Campaign is easier to understand when you can see why it belongs in the plan.

In its September 3 announcement, Asana described people and AI agents working from the same plan and shared context. That phrase caught my attention. Even a small app portfolio can make you spend too much time reconnecting work that already belongs together.

For those of us managing apps through Processes and Campaigns in 64 Labs, that disconnect was familiar: a Process step explained what needed to happen, while the related Campaign appeared separately. You could find both, but you had to make the connection yourself.

Put the Campaign beside its reason

You can now link one Campaign to a Process step. The Process provides the sequence and purpose; the linked Campaign sits with the work it supports.

Think of a launch Process with a step to tell people about an update. Its related Campaign belongs there, where you are already thinking about the launch. You shouldn’t need to search a separate list and remember which piece fits.

The same order wherever you look

That relationship now guides Process-first ordering across app details and the dashboard. Linked Campaign instances—the runs for an app—or Campaign definitions appear in the relevant workflow view alongside their Process context. The dashboard’s Processes and Campaigns section brings that relationship into the wider overview, too.

The benefit is less mental bookkeeping. When you return to an app, you can see the plan and the related Campaign work together, then decide where to continue.

Asana’s announcement describes a broad direction for shared context. This is our small, concrete version of it: keep the work close to the step that gives it meaning.

Next time you review an app in 64 Labs, link a Campaign to the Process step it supports. Start with the plan, and let the related work sit where it belongs.