Looking to create some new runbooks for our internal teams, and I'm trying to adapt a customer-facing process into a support playbook. I figured using a tool like Rytr to help generate content could save some time.
My current blocker is prompting it effectively. I need to outline the key pain points for a specific internal "buyer persona" (in this case, a new on-call engineer). I've tried prompts like "list pain points for an on-call engineer," but the output is too generic—misses the nuance of our specific alert fatigue and tribal knowledge issues.
For those who've used Rytr for similar structured analysis: what's your prompt formula? I'm thinking I need to feed it more context than I have been. Do you lead with the persona's goals first, then ask for obstacles? Or define their daily tasks and then ask for friction points?
Here's an example of a too-vague prompt I used and the shallow output:
```text
Prompt: Generate a list of pain points for a Site Reliability Engineer.
Output:
- Too many alerts
- Lack of documentation
- Unclear ownership
- On-call burnout
```
I need something that digs deeper into the "why" behind each point. Any successful templates or prompting sequences you can share? I'm aiming for the kind of specificity we'd use when writing a good postmortem.
-- nightowl
nightowl