Teams | Collaboration | Customer Service | Project Management

When Aubrey Rogers, Head of Creative Operations & Production at Asana, kicks off a new creative campaign, she doesn’t start with execution. First, she needs to understand what’s happening and why. This often means a team kickoff, go-to-market decks, and streams of back-and-forth conversations happening on multiple platforms. In theory, Rogers should have everything she needs after kickoff. She’s defined the strategy and aligned stakeholders.

Security is what makes it possible to build and ship software with confidence. But in fast-moving engineering teams, it can drift into an afterthought—a final hurdle before launch rather than a voice at the table from day one. Varun Prusty, staff security engineer on Asana's security architecture team, believed it didn't have to work that way, so he built something to prove it.

The hardest part of a planning offsite isn't always the planning. It's translating that clarity, energy, and momentum into actual projects after everyone has left the room. For Sheila Head, Head of Marketing Operations at Asana, that translation work used to cost an entire work day. "The real work happens as soon as you wrap up the notes and assign action items and get people actually working on the initiatives you all aligned on," said Sheila.

Starting today, teams can check on their Asana portfolios, generate and preview new projects, and create tasks directly in Claude, Anthropic’s AI offering. This connection is especially meaningful for teams already using Claude to think through work.

In the evolving landscape of project management tools, teams often find themselves at a crossroads: choosing between the simplicity of Trello's digital sticky notes and the orchestrated work management offered by Asana. This guide aims to provide a comprehensive comparison, helping SMBs, growing teams, and technical leaders make an informed decision.

In this blog article, hear from Adam Higa, Growth PM at Asana. I’m a Growth PM at Asana, and yes — I use Asana to build features for Asana. Very meta, I know. But being both a user and builder gives me a unique perspective on what works. I’ve developed a system with Asana that keeps me focused on outcomes, not just shipping features. Given it’s January, I wanted to share three tips for how I approach roadmapping and OKR planning in Asana.

Great ideas start in AI tools. With 87% of employees now using AI at work,* teams brainstorm ideas, shape plans, get quick context, and move fast with the help of AI every day. And they're not waiting for official company AI rollouts either—only 31% of organizations have an AI usage policy in place.* As a result, work is no longer happening in one place. Employees jump between AI tools and their existing tech stacks, scattering tasks, content, and thinking across them.

AI promises a radical leap in productivity. There is evidence that, on an individual level, this promise is being delivered. Employees are completing tasks in minutes that took hours just three years ago. This has fueled massive economic optimism, projecting labor cost savings of up to 25% and potentially affecting almost 10% of current GDP over time. However, this stunning individual acceleration has yet to show up in the bottom line.

Common workflow bottlenecks—like complicated data audits and repetitive report drafting—don’t just grind productivity to a halt. They prevent teams from getting the clean, reliable insights they need to make smart decisions. While automation can help with simple tasks, it often falls short when it comes to solving complex problems that require context and strategic thought. This is why top organizations are adopting AI Teammates in Asana.

Government teams carry out work the public relies on every day: work that builds safer communities, strengthens infrastructure, and delivers critical services. This work demands coordination across agencies and partners, often under intense scrutiny and with limited resources. Outdated systems make that harder. Spreadsheets and email threads bury important updates, and legacy tools slow teams down when urgency is highest.