Best Practices
Revo works in two complementary modes that together unlock its full potential:
Prompting in a Context → defines how Revo thinks and behaves (system-level setup)
Chatting with Revo → is where you ask questions or give instructions in real time, usually in the chat interface
Understanding and using both well is key to making Revo work like a high-performing PM on your team.
1. Prompting in a Context (System Instructions)
This is what you configure in the “instruction” field when creating or editing a Context. It tells Revo how to behave inside that workspace.
Best Practices for Writing Context Instructions
Be explicit about the goal “You are a senior product manager focused on writing technical PRDs.”
Define the audience “Your deliverables are intended for product, design, and engineering teams.”
Give structural guidance “Use the following PRD format: Title, Problem, Goals, User Stories, Open Questions.”
Set expectations “Always be concise. Prioritize clarity over length.”
Point to data sources “Reference the folders ‘User Feedback’, ‘OKRs Q3’, and ‘Personas 2024’ when relevant.”
Examples of Context Prompts
Advanced PRD Writing “You write complete, detailed PRDs based on inputs like user flows, screenshots, and user feedback. Follow the advanced PRD format.”
Competitor Monitoring “You scan competitor updates and compare them to our current roadmap. Suggest risks or opportunities.”
Meeting Follow-up Assistant “You summarize meetings, extract action items, and convert them into issues. Use a friendly but professional tone.”
2. Chatting with Revo (in Context)
This is where you interact with Revo on a daily basis—asking questions, generating content, assigning tasks, or summarizing information.
The Context you're in defines how Revo behaves, but your prompt in the chat is what triggers it to act.
Best Practices for Chatting with Revo
1. Be Clear and Specific
✅ Good: “Summarize the top 3 pain points from feedback in the "onboarding 2025" folder.” 🚫 Less Effective: “What are users saying?”
2. Add Context Where Needed
“Summarize the persona profiles from the ‘Q2 Personas’ folder.” “What actions did we commit to in the April 10 stakeholder sync?”
3. Break It Into Steps
“First, extract the main ideas from this meeting. Then, generate a follow-up email.”
4. Use Natural Language—But Stay Structured
“Write a PRD based on this user story: [paste] Use the following format: Title, Problem, Goals, User Stories, Open Questions.”
5. Always Check the Context
If Revo’s answer feels off:
✅ Check the Context
🔄 Switch if needed
🧼 Start a new thread for clarity
How to Improve a Weak Response
If Revo gives a vague or incomplete answer, try the following:
Rephrase your question “What are our top product risks?” → “Based on feedback and missed goals, what are 3 current risks in the roadmap?”
Be more specific Add references to documents, folders, dates, or people.
Switch to a new context If your current Context isn’t set up for the task, try another.
Start a new chat thread Revo may interpret prior conversation history; a fresh thread resets the conversation logic.
Last updated