What's New is most useful when it helps you make one real decision.
Set up only what you need today. You can add more context when the next question calls for it.
Try saying
“Help me choose the smallest useful next step for this product.”
Choose a job
Start from the outcome you want.
Give context
Share only what helps with this job.
Keep moving
Leave with a concrete next action.
What's New
What this is for
Learn what changed without reading release notes that do not explain when the change matters to you.
When this helps
- Users miss useful improvements.
- Release notes describe implementation instead of user benefit.
- Teams adopt features without understanding the new workflow.
How it works
What’s New groups recent product changes by user-facing outcome and links each change to the relevant workspace surface or guide. Use it as a short discovery loop, not a mandatory tutorial.
Before you start
- Your current workspace version and product context.
- A feature you want to understand or try.
What you should see
- A plain-language explanation of the change.
- A direct path to the feature or tutorial.
- A reason to adopt it now, when relevant.
Try it now
- Open What’s New from the sidebar.
- Scan the newest changes and open the one connected to your current workflow.
- Read the linked guide before turning it on for a real project.
- Try it with a small artifact and keep the change if it improves the result.
A real example
You see that new outcome tracking can link shipped work to a metric. Instead of exploring every option, open the outcome guide and attach it to one completed experiment.
Your next move
Use the Cookbook when a release note points to a repeatable workflow.
Ready to apply this?
Start with your own product and keep the first read grounded. You can create an account after you see the result.