Why interviewers ask this question
This question is most common in senior, management, or leadership interviews. It tests: whether you understand that the first priority is learning, not acting; whether you know how to build trust and relationships in a new environment; and whether you have a realistic picture of how long it takes to become effective in a new role. Candidates who come in planning to "fix things immediately" signal a lack of awareness about how organisations actually work. Candidates who plan nothing signal a lack of direction.
The question also indirectly tests your preparation: a specific answer that references the company's actual situation is dramatically more impressive than a generic 30-day plan template. Candidates who have done research and can say "given that the team is in the middle of X, my first priority would be Y" show they have engaged with the actual role, not just the job specification.
The framework that works: Listen, Learn, Then Act
The strongest 30-day plan structures are: Week 1-2: Listen and learn. Meet every stakeholder and team member individually. Ask questions rather than offering opinions. Understand what is working, what is not, and what people are most worried about. Week 3-4: Identify priorities and validate hypotheses. Form early views on the most important problems to solve and test them with the people around you. Share your initial thinking and invite pushback. End of 30 days: State your priorities and approach. Share a clear view of what you are going to focus on in the next 60-90 days and why. Get alignment with your manager.
The point of the 30-day plan is not to have fully solved anything. It is to have earned enough trust and learned enough about the environment to make informed decisions rather than guessing.
Sample answer
For a management or director-level role: "My first priority in the first 30 days would be listening: to the team, to key stakeholders, and to data. I would spend the first two weeks meeting every direct report and key cross-functional partner individually, with a prepared set of questions about what is working well, what the main frustrations are, and what one thing they wish the incoming manager would prioritise. I would also look at all the available performance data without forming conclusions yet. By the end of week two I would have a set of working hypotheses. Week three and four I would spend testing those hypotheses, bringing my early thinking to the team and stakeholders and explicitly asking for challenges to it. At the 30-day mark I would write a short document for my manager summarising what I had found, the two or three priorities I planned to focus on, and why. I would share it broadly and treat it as a commitment to the team about what they can expect from me."
What not to say
Do not describe yourself walking in and immediately implementing changes. Even if you can see problems from the outside, acting before you have built trust and gathered full context is a common reason new leaders fail. Do not give a generic template answer that could apply to any role at any company. Customise it to what you actually know about the specific role. Do not make the plan entirely about you proving your value: the strongest first-30-days answers focus on understanding others rather than demonstrating your own expertise.