How to Ask Better Questions in Guidely

Guidely starts with your intent. The clearer your intent, the easier it is to get a clean, step-by-step plan that helps you move forward inside the product.

The best pattern: outcome + constraint

Use this structure:

Outcome: what you want to accomplish
Constraint (optional): one detail that changes the steps

Examples:

“Invite a teammate” + “as read-only”
“Change availability” + “for next week only”
“Create an invoice” + “for an existing customer”

Prefer outcomes over UI labels

Instead of:

“Where is Templates?”

Try:

“I want to edit an email template”

UI labels change. Outcomes don’t.

Keep it one task at a time

If you combine multiple tasks, steps can get messy. Split this:

“Add a teammate and change permissions and update billing”

Into:

“Add a teammate”
“Change a teammate’s permissions”
“Update billing settings”

Add context when it’s the difference between two paths

If your product has multiple workspaces, plans, or admin levels, add one clarifier:

“for a single workspace”
“as an admin”
“in the main account”

FAQ

Should I copy and paste long descriptions?

Usually no. Start short with the outcome. Add one detail only if the workflow depends on it.

What if I don’t know whether I’m in the right part of the app?

Say what you’re trying to do. Then use the first steps to confirm you’re in the correct area (Settings/Admin/Workspace) before continuing.

Can I ask Guidely “where do I click?”

Yes—Guidely is built for step-by-step guidance inside the UI, including where to click when possible.

CTA

If you want smoother guidance, start with a single sentence describing your destination. Guidely is built to make the next step clear without taking control.