Asana should show what is moving, what is blocked, and who owns the next decision. Strawberry can list workspaces, projects, sections, tasks, users, and task stories; search tasks; and create or update the project work that has been reviewed.
Use it to prepare a project review, locate overdue or ownerless work, create a well-scoped task, move it into the right section, or turn a discussion into a documented follow-up.
01
See the project beyond the status colour.
A project can appear healthy while its important tasks have no clear owner, a blocked dependency, or a comment that nobody has acted on. The work is there, but the real operating state is not obvious at a glance.
Strawberry can retrieve the project, sections, tasks, and task stories to prepare a decision-oriented review. It focuses the team on what needs an answer rather than repeating a surface-level status update.
02
Turn a useful conversation into work people can complete.
Meeting notes often contain an action buried between observations, suggestions, and decisions.
If the task is created without a clear outcome or owner, the project tool simply becomes another place to lose it.
Strawberry can prepare a task with a defined name, description, assignee, due date, and project context, then create it once the details are approved. It can also add a story to preserve the decision that caused the work.
03
Keep the board aligned with the work that actually changed.
Moving a task to a new section can be meaningful when it reflects a real handoff, but meaningless board motion hides the work still stuck behind it. A clean project needs activity records as well as column placement.
Strawberry can update a task, add it to a section, and retrieve the associated stories so a proposed movement has context. The team can review the intended state change before it appears in a shared project.
04
Make the weekly review repeatable without making it robotic.
The best project review asks a stable set of questions, but it should still account for the work that changed this week. A routine is useful when it prepares the context, not when it pretends to run the project.
Save the agreed Asana review as a skill, then use a routine to compile the same read-heavy briefing for the project owner. Any task or project write should remain clearly reviewable.
Yes. It can list workspaces, projects, sections, tasks, users, and task stories, retrieve a task, and search tasks.
Yes. Native operations can create tasks and projects, then add tasks to a section. Review the owner, due date, and destination before approving creation.
Yes. It can update an existing task and move an existing task into a selected project section.
Yes. It can create an Asana story, which adds a comment to a task. Confirm the wording and task before posting it.
Yes. A reviewed, read-only delivery check can be saved as a skill and scheduled as a routine for a defined workspace or project.
Asana Strawberry