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

Reviewing Proposed Workflows

Learn how to review and provide feedback on your proposed Asana workflows in Miro—and why timely feedback is critical to your project timeline.

Once we’ve mapped out your future-state workflows in Miro, we’ll walk you through the proposed structure live—either during your Design Workshop or in a standalone review session. This is your opportunity to validate, adjust, or approve what will eventually be built inside Asana.


How Workflow Reviews Are Delivered

You’ll typically receive your proposed workflows through one or more of the following formats:

  • Live walkthroughs during Design Workshops
    We’ll guide you through your Miro board and explain the logic behind each part of the workflow.

  • Loom recordings
    We may send short videos between sessions to get your feedback asynchronously, especially when there are questions or decisions to be made between meetings.

  • Miro board access for review and comments
    You’re welcome to leave sticky notes, comments, or questions directly in the board.


How to Provide Feedback

To keep the project on schedule, feedback should be submitted within the requested timeframe provided by your Project Manager. This varies depending on scope, but delays in response will delay delivery.

You can provide feedback in a few different ways:

  • Comment directly on Loom videos (timestamped comments are especially helpful)

  • Circulate a document internally to collect team input, then return a consolidated summary

  • Save feedback for the next live session—but please flag in advance so we can allocate time for review


Why Timely Feedback Matters

Your feedback is required to move forward. Once we receive approval on the proposed workflow, that becomes our milestone marker. We use your sign-off as the signal to begin building and automating in Asana.

Delays in feedback can lead to:

  • Missed milestones

  • Extended project timelines

  • Build decisions being made without full team input

  • Rework if expectations shift after approval


Final Note on Approval

Once you approve the workflow structure, changes become significantly harder to implement. We strongly recommend making all structural decisions (steps, roles, fields, rules, and logic) during this review window.

Our team cannot begin the Asana build without your sign-off.