Every week, Emily needed to prepare a slide for a cross-functional meeting between product marketing leadership and enablement stakeholders.

The process included manually pulling updates from Asana, copy and pasting them into a slide, formatting and organizing the content, and distributing it after the meeting. This took around 2 hours every week.

But the bigger issue wasn’t just time. It was usability. The slide contained too much information, which made it difficult to scan and interpret. It wasn’t tailored to all stakeholders and it didn’t naturally support discussion.

As Emily put it, the output often felt like something that could have just been an email, not a collaborative planning tool.

To fix this, Emily built an enablement dashboard using Claude Code for logic and iteration, Google Apps Script for hosting and accessibility, and Asana as the source of truth.

Instead of generating a static slide, the system now pulls live data directly from the product marketing Asana board, displays it in a clean, navigable interface, and links directly back to underlying Asana tasks.

This means no more manual copying and pasting, no outdated links, and no ambiguity about where information lives.

The dashboard isn’t just faster. It’s better.

Key improvements include relevant, scoped information instead of overloaded slides, direct links to Asana tasks, enabling real-time updates, and live data, ensuring everything is always current and that there is clear ownership, so stakeholders know exactly what to do.

Instead of reviewing a static artifact, teams now interact with a shared workspace that reflects the current state of product launches and enablement activities.

One of the most interesting outcomes was behavioral. The new dashboard made meetings more interactive, encouraged real-time updates and discussion, and prompted broader process improvements across the workflow.

What used to be a one-way update is now a collaborative planning session.

The impact is immediate and measurable:

• 2 hours per week → seconds to generate the dashboard

• information is available instantly at the click of a button

• no post-meeting follow-up required

Emily also layered in an additional automation. Previously, she would send a follow-up email with the slide. Now, Spinach automatically sends meeting notes, including a link to the dashboard.

This creates a fully automated loop, where a meeting happens, the dashboard is referenced live, and a recap is sent automatically with the correct link. No manual follow-up needed.

A notable part of this project was how it was built. Emily used Claude Code conversationally to design the system, iterate on logic, and troubleshoot issues. Claude didn’t initially suggest Apps Script as a hosting solution. Emily had to guide it there. Once prompted, implementation became straightforward.

This highlights an important pattern: AI accelerates building, but human direction still shapes the solution space.

The dashboard is already delivering value, but there’s room to expand.

Next steps include incorporating additional enablement workflows (e.g., SE Masters sessions), expanding coverage across more teams and processes, and continuing to refine the interface based on stakeholder feedback.

When you replace static artifacts with live systems, you don’t just save time, you unlock better ways of working.