Prompt Almanac

Create advanced Works with: Any AI

Asana Goals and Key Results Draft Linked to Projects

Structured brief Has example

Write goals with measures and connect them to work.

Open in ChatGPTOpen in Claude

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Rate this prompt

Loading ratings…

Draft goals for [TEAM_NAME] to set up in Asana. Company or department priorities: [PRIORITIES]. Current projects: [PROJECTS]. Last period's results and learnings: [LAST_RESULTS].

For each of up to three objectives, write the objective in plain words, then two or three measurable key results, each with a starting value, a target and how we will measure it, and name the projects or tasks that support it. Check that every key result is an outcome and not an activity, and rewrite any that are activities. Show the arithmetic for any target expressed as a percentage change. Use only the starting values I supplied and write [MEASURE NEEDED] where there is no baseline.

For each key result, say what would make the target unrealistic and suggest a fair stretch level. Delete any key result that someone other than its owner cannot measure, and any objective that is just a project name. Check the objectives for overlap and keep the total number of key results small enough to remember.

Finish with how the team should update progress each week in two minutes, what to do when a target proves wrong, and which risks could stop a key result and who would notice first.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

See an example result (fictional data)
Objective: Make onboarding faster and clearer for new customers.
Key result 1: Reduce median days from signup to first project from 9 to 5 (start 9, target 5, a 44 percent reduction: 4 / 9). Key result 2: Raise the share of customers finishing the setup checklist from 52 percent to 70 percent. Key result 3: Reduce onboarding-related support tickets from 120 to 90 a month (25 percent fewer).
Linked projects: Setup checklist redesign, Welcome email series, Help article refresh. Weekly check: update the three numbers every Monday in two minutes. Confidence: medium; risk is dependence on the engineering release in April.

Illustrative only, made-up data. Your results will differ and must be reviewed.

Related prompts