Plan your first ninety days in a new role

Start with the right question

Begin with understanding before promising transformation.

Learn the team’s priorities, decision process, users, and operating constraints. Ask your manager what a useful first contribution looks like and how progress should be communicated.

See the idea in practice

This example illustrates the approach. Adapt it to your circumstances and replace any sample detail with evidence you can verify. The wording is less important than the relationship between the problem, your action, and the result.

First month: map the workflow and complete a small task. Next: own a bounded improvement. Then: evaluate impact and agree on the next responsibility.

Try this next

Keep a learning log of terms, open questions, decisions, and commitments. Review it weekly with your manager so assumptions do not silently become expectations.

Make one revision at a time and compare it with your starting point. Ask a reader who does not know your background what they understand from the new version. Their questions can help you identify missing context.

Watch for this common mistake

Avoid rigid plans that ignore the organization’s actual needs. Treat a ninety-day plan as a conversation and revise it with evidence.

Before you move on

Check that the final version is specific, truthful, and relevant to your intended audience. Keep a note of the evidence behind important claims so you can explain them in a conversation. Save the version with a clear name before creating another variation.