Structure a dedicated monthly career growth conversation

Run structured, 45-minute monthly career development sessions that stay separate from tactical work and bug fixes. Use this to maintain consistent growth trajectories for engineers.

You get45-Minute Meeting Agenda, guardrail Script and 4 Core Discussion Questions

Prompt

Prompt
Act as an engineering director coaching engineering managers on professional development.
Provide a repeatable framework for a dedicated 45-minute monthly career conversation that keeps sprint blockers and status updates out of the agenda.
- Emphasize long-term skill acquisition, influence, and promotional criteria over weekly tasks.
- Include exact boundary language to redirect direct reports if they drift into routine status reporting.
- Build a reliable structure that balances reflective listening with forward planning.

Output format:
1. 45-Minute Meeting Agenda (timed breakdown of discussion blocks)
2. Guardrail Script (word-for-word lines to steer the conversation back to long-term career growth)
3. 4 Core Discussion Questions (focusing on craft, scope, cross-functional collaboration, and blind spots)
4. Post-Meeting Action Item Template (simple structure to document quarterly milestones)

Example output

1. 45-Minute Meeting Agenda
  • 00-05 min: Context Reset. Reconnect on monthly career priorities and review previous commitments.
  • 05-20 min: Competency Reflection. Deep dive into one target growth area (e.g., technical design, system reliability, or mentorship).
  • 20-35 min: Upcoming Opportunities. Identify high-leverage assignments in next month's planning that provide practice in that skill.
  • 35-45 min: Next Actions & Support. Clarify concrete deliverables and manager advocacy commitments.
2. Guardrail Script

"Let's pause right there on the sprint status. The deployment pipeline is important, but we have our weekly 1-on-1 for tactical delivery. Today is exclusively for your career trajectory and long-term goals. Let's step back: how does your leadership on this project demonstrate the senior engineering competencies we discussed last month?"

3. 4 Core Discussion Questions
  1. Craft: "Which technical problem challenged you most this month, and what foundational knowledge do you want to build next?"
  2. Scope: "Where in our architecture or team workflows do you see risks that nobody else is actively addressing?"
  3. Influence: "How confident do you feel driving technical decisions with product managers and adjacent engineering teams?"
  4. Blind Spots: "What is one area where you felt your momentum slow down, and what support could clear that path?"
4. Post-Meeting Action Item Template
  • Target Skill: [Specific competency, e.g., Cross-team architectural design]
  • Observable Output: [e.g., Author RFC for service decomposition by Nov 15]
  • Manager Commitment: [e.g., Sponsor design review slot with Principal Architect by next Tuesday]
Written by AI from this prompt. Your results will vary.

Paste this prompt into ChatGPT, Claude, or Gemini without any edits. After generating the framework, ask the model to adapt the 4 core questions for an engineer aiming for a staff-level promotion.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Leadership & Management
Leadership & Management

Distribute invisible glue work across your team

Audit uncredited coordination, onboarding, and documentation duties to protect high performers from burnout. Use this when reliable contributors carry too much operational weight.

Leadership & Management

Build a thirty-sixty-ninety day onboarding plan

Generate a clear, phased milestone roadmap for incoming team members to eliminate ambiguity. Use this during hiring or early onboarding to set transparent expectations.

Leadership & Management

Create a post-crunch team recovery sprint plan

Design a two-week reset sprint to help teams recuperate after an intense deadline push. Use this to tackle low-stress tech debt, clear mental fatigue, and restore sustainable momentum.