On campus? Ask Stu instead. Stu already knows our methodology, so you can skip the setup and just describe your situation. Available to UC Berkeley staff, faculty, and students.
When to use it
After your problem statement is solid. Weak objectives are the number one cause of projects that finish but don't matter, everyone was busy, but nothing measurably changed. This prompt forces the "how would we know it worked?" question early, while you can still shape the project around the answer.
Good objectives are specific and measurable. If you can't say how you'd measure it, it isn't an objective yet, it's a hope. Use this before you build your plan, so the milestones have something real to aim at.
Make it better
Your first result is a draft, not an answer. Two follow-ups worth asking:
"Which of these measures could we baseline today with data we already have?" Objectives without a baseline become opinions later.
"Which of these objectives would a sponsor actually care about, and which are just internal housekeeping?"
Additional guidance
If the first results aren't quite right, add more detail, break the request into smaller steps, or have the tool interview you first. Try: "Ask me questions, one at a time, to gather anything you need before you start."
AI output is a starting point, not a finished product. Always review it against your own context, campus policies, and judgment before you use or share it.
Put it to work
Your objectives and success measures go straight into your Project Charter. Get the template on the Initiate Project with Sponsor activity page.
