Challenge a growth hypothesis against the metric tree
Use a documented metric hierarchy to question a proposed growth initiative before the team prioritizes it.

A FIELD GUIDE TO AI AT WORK
Explore practical AI workflows for management: inputs, implementation steps, human checks and downloadable skills to adapt to your team.
ESSENTIALS / THREE FOUNDATIONS
Build the foundations with three practical skills.
Choose your recurring activities to build a starting set.
Use a documented metric hierarchy to question a proposed growth initiative before the team prioritizes it.
Turn an analytical document into a coherent deck by separating story design, missing-evidence research, assembly, and quality review.
Use recent business discussions to identify who needs an update and tailor a draft to each person’s responsibilities.
Maintain a working memory of projects, colleagues, and commitments. Use it to prepare a daily brief that highlights decisions waiting on the manager, dependencies, and useful follow-ups.
Review a proposal through several stakeholder perspectives using known priorities and previous discussions. Use the simulated debate to uncover unanswered questions and improve the supporting evidence.
A manager used meeting transcripts to examine their communication, challenge the assistant’s flattering responses, and practice better ways to handle similar situations.
Connect preparation, meeting analysis and reasoning checks so each discussion updates the next product decision.
Bring franchise operating and financial data into a dashboard that can be explored by partner, territory, month, and year. Use an assistant to prepare the data joins and reporting interface.
Connect feedback and exit interviews to proposed changes. Display impact and effort estimates so the team can choose a small set of improvements and turn them into assigned tasks.
Convert a small set of prioritized processes into an implementation plan. Describe the current workflow, the proposed assistant role, human checkpoints, dependencies, and the evidence needed to judge progress.
Use observed pilot runs to choose whether to improve the workflow, share it with colleagues, automate its execution, or keep it limited. Include the time spent checking and correcting outputs.
Record the context, reasoning summaries, artifacts, and unresolved factual questions from important assistant work. Use the record to investigate mistakes and preserve reviewed lessons for later tasks.
Use comparable completion history to communicate uncertainty about delivery.
Try a broader search or save a workflow from the library.
Please check your connection and try again.
Allow anonymous usage analytics to help us improve Plays?
We measure visits and actions, never your chat. Privacy notice