When transitioning from an individual contributor to an engineering manager role.
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task. # Context - Pack: Developers & Tech Professionals - Category: Developer Productivity & Career - Use case: Engineering Manager Transition Plan - Source task: - I am a senior developer transitioning to an engineering manager role. Help me prepare. - Step 1: the mindset shift from IC to manager (what to stop doing, what to start doing). - Step 2: the first 90 days plan : 1:1s, team assessment, quick wins, relationship building. - Step 3: the core EM skills to develop: performance management, project delivery, hiring, cross-functional communication. - Step 4: how to maintain enough technical credibility without becoming a technical bottleneck. - Step 5: common first-year EM mistakes and how to avoid them. # Goal Mindset shift guide, 90-day plan, EM skill development roadmap, technical credibility strategy, and first-year mistake warnings. # Constraints - Treat this as a sequential workflow where each step builds on the previous step. - Keep every step clearly labeled and easy to run separately if needed. - Avoid generic filler, vague advice, and unsupported claims. - Make the output specific, practical, and ready to use. # Output Mindset shift guide, 90-day plan, EM skill development roadmap, technical credibility strategy, and first-year mistake warnings.
{{double-curly}} with your real context.When transitioning from an individual contributor to an engineering manager role.
The hardest part of becoming a manager is learning that your team's success is your success — optimising for your own output is the wrong instinct in this role.
Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.
Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.
Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.
Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.