Prompt Details
Model
Chat - (gpt-5.5)
Token size
271
Example input
[TOPIC]: How to run effective 1:1 meetings as an engineering manager
Example output
1/13
Most 1:1s don't fail because managers don't care. They fail because they're optimized for status updates instead of better decisions. If your team leaves every meeting with the same problems they walked in with, you're wasting everyone's time.
2/13
Status belongs in Slack, Jira, or your sprint review. A 1:1 is one of the few places where someone can say what's actually slowing them down before it becomes a missed deadline or resignation.
3/13
The biggest mistake: managers show up with an agenda, a checklist, and solutions. Great 1:1s aren't about talking more. They're about creating enough trust for the real conversation to happen.
4/13
Rule #1: Make it the employee's meeting. They own the agenda. Ask them to add topics beforehand. If they come with nothing, use prompts—not a list of updates.
5/13
Rule #2: Start with energy, not tasks. Ask: "How are you feeling about work this week?" or "What's been on your mind?" Context changes how you interpret everything that follows.
6/13
Rule #3: Spend most of the time on the future, not the past. Instead of replaying last week's problems, ask: "What's the biggest risk before our next 1:1?" Prevention beats postmortems.
7/13
Rule #4: Coach before you advise. Ask: "What options have you considered?" and "What would you do if I weren't here?" You'll build judgment instead of dependency.
8/13
Rule #5: Look for patterns, not incidents. One bad PR isn't a trend. Three weeks of frustration with the same process probably is. Great managers solve systems, not isolated moments.
9/13
Rule #6: End with clear commitments. One action for them. One action for you. If neither of you leaves with something concrete, the conversation probably wasn't specific enough.
10/13
Rule #7: Keep private notes on goals, blockers, and personal context. Remembering someone's career aspirations or family situation months later builds trust more than any motivational speech.
11/13
A manager noticed one engineer repeatedly mentioning "small interruptions." Instead of giving productivity tips, they dug deeper. The real issue was constant ad hoc requests from three different teams.
12/13
The fix wasn't "work harder." They created a request process, protected focus time, and aligned stakeholders. The engineer shipped faster, stress dropped, and the next few 1:1s shifted from firefighting to growth.
13/13
The best 1:1 leaves someone with more clarity than they had walking in. Before your next meeting, delete the status updates and ask one better question. Your team will notice the difference long before your metrics do.
By purchasing this prompt, you agree to our terms of service
GPT-5.5
Turn any topic into a complete, high-performing X/Twitter thread in seconds. This prompt enforces a battle-tested 5-phase structure: a scroll-stopping hook, a relatable problem diagnosis, a numbered framework, a real example, and one actionable closer. No vague advice, no "let me explain" filler — just threads that read like a sharp friend teaching you something worth sharing.
Designed for founders, creators, and marketers who need threads that grow their audience. Each tweet stays under 280 characters, numbered and ready to post. Single variable: just type your topic and go.
...more
Added 2 days ago
