Skip to content
English
  • There are no suggestions because the search field is empty.

Design Workshops & Demo Sessions: Finalizing Your Asana Build

Learn what to expect during Cirface's Design Workshops and Demo Sessions—where your workflows take shape and final build decisions are made.

Once discovery is complete and we’ve aligned on your future-state workflows, we move into Design Workshops—the most collaborative stage of your Asana implementation.

This is where we begin translating your Miro board into Asana. You’ll see a live preview of your system in action, collaborate on key build decisions, and get early, hands-on training as the framework is shaped around your workflow.


What Happens in These Sessions

1. Live Demo of Your Future Workflow

  • We walk you through your proposed solution inside Asana

  • You’ll see how your work will look and function in real time

  • We highlight how your day-to-day activities translate to the new system

2. Collaborative Feedback

  • You’ll help finalize:

    • Custom fields

    • Roles and responsibilities

    • Approval flows

    • Project and portfolio structure

  • We discuss logic for rules and automations before anything is finalized

3. Workflow Education Built In

  • These sessions are also live learning opportunities

  • As we demo, we teach your team how to use each Asana feature in the context of your workflow

  • You’ll start building Asana confidence even before training sessions begin

4. Decision Alignment and Sign-Off

  • These sessions are the final opportunity to request changes before build

  • Once we confirm your feedback, we lock the structure and proceed into development

  • Having clear sign-off here helps prevent delays, rework, or misaligned expectations later


Why It Matters

Design Workshops are where you shift from strategy to execution. They ensure:

  • No assumptions go unchecked

  • Teams are confident in what’s being built

  • Final systems reflect your actual processes—not generic structures

These sessions reduce confusion, speed up build time, and promote team buy-in before your formal rollout.