We are all using some sort of AI at this point, but here are some ways to get better results.
“Who should the AI be?”
Role
This sets the persona or expertise you're expecting. It frames the AI’s tone, depth, and assumptions.
“What does the AI need to know?”
Context
Give the background info that influences the task. This ensures the AI understands the situation.
“What do you want it to do?”
Command
Be direct and specific about the task.
“How should the output look?”
Format
Tell the AI what kind of structure or layout you want.
Example
I want a Technical Specification of this workflow for the client after the build is complete.
Role:
- This information is for the Technical users and Process Owners.
Context:
- I need a summary that clearly explains what the workflow does, how it runs, and which integrations and accounts it uses.
Command:
- Provide the following sections:
- Summary: A high-level overview of what the workflow does.
- Workflow Actions:
- Starting with the Tigger.
- Process list of all the workflow actions.
- Integrations: Show any integration, if any.
- Accounts: All accounts and email addresses.
Format:
- Use clear section headings as follows:
- Summary
- Workflow Actions
- Integrations
- Accounts
- Use:
- Numbered lists for workflow steps.
- Bullet points for integrations and accounts.
- Use plain language and describe the purpose of each step.
