When starting a new engineering leadership role or preparing a new leader to succeed.
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: Tech Communication & Leadership - Use case: New Engineering Leader Onboarding - Source task: - Design a 90-day onboarding plan for a new {{role_engineering_manager_vp_of_engineering_cto}} joining {{describe_organisation}}. - Step 1: Days 1-30 (Listen): stakeholder mapping, 1:1s with every direct report and key cross-functional partner, understanding current pain points and team health. - Step 2: Days 31-60 (Understand): deep dive on architecture, delivery metrics, culture, and the team's relationship with other functions. - Step 3: Days 61-90 (Act): first strategic moves, communication of priorities, and quick wins that build credibility. Include the 3 most common mistakes new engineering leaders make. # Goal 3-phase 90-day plan with specific activities, stakeholder mapping approach, quick win identification, and top-3 new leader mistakes. # 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 3-phase 90-day plan with specific activities, stakeholder mapping approach, quick win identification, and top-3 new leader mistakes.
{{double-curly}} with your real context.When starting a new engineering leadership role or preparing a new leader to succeed.
The biggest mistake new engineering leaders make is trying to change things before they understand them — earn trust through listening before earning the right to lead.
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.