A new leader arrives with ideas, energy, and often a mandate for change. The team watches closely, trying to read what the new person will do. The early weeks are a rare window: people are willing to explain how things work, and you have no history to defend. Spending that window on listening pays off for years.
The point is not to delay action. It is to understand the real working system, including the parts that never appear in an org chart, before you redesign any of it.
The formal and informal systems
Every team has a documented way of working and an actual one. The documented one includes roles, meetings, and processes. The actual one includes who people really ask for help, which meetings make decisions and which only report them, which rules people follow and which they route around. Changes that ignore the informal system tend to meet quiet resistance.
Questions to ask in your first conversations
Hold one-on-one conversations with each team member and key partners outside the team. Use consistent questions so you can compare answers:
- What is working well here that I should protect?
- What is the most frustrating recurring problem?
- How are decisions made on this team? Give me an example from the past month.
- Where does work get stuck or come back for rework?
- What would you want me to know about how this team works with others?
- What should I avoid changing too quickly?
Take notes and look for themes. When several people independently describe the same obstacle, you have found something worth attention.
Watch the work as well as hearing about it
Interviews tell you what people believe. Observation shows you what happens. Attend regular meetings and notice who speaks, how decisions are made, and what happens to action items. Follow one recent piece of work from start to finish and see where it waited. These observations will often differ from the stories you hear, and the differences are informative.
Map decisions and handoffs
List the five to ten decisions that matter most in your area, and for each, note who actually makes it, who is consulted, and how long it usually takes. List the main handoffs between your team and others. Where does ownership blur? Where do people say "it depends"? Those are likely places to improve first.
Identify what to keep
New leaders sometimes treat every existing practice as a problem. Some practices exist for good reasons. Write down what is working and tell the team. This builds trust and helps people see that change is selective, not a rejection of what came before.
Choose a first visible improvement
After a few weeks, pick one issue that people raised repeatedly, that you can affect, and that can show progress within a month or two. Tell the team what you heard, what you chose, and why. An early, well-chosen change shows that listening leads to action. Avoid starting with a broad reorganization before you understand the system.
Be open about your plan and your learning
Share what you have learned and what you do not yet know. A statement like "Here are three themes I heard, here is what I plan to look at first, and here is where I would like your input" gives the team a role in the change. Check in again after a few months and ask what has improved and what has not.
Reset expectations with your own manager
Agree early on what your manager expects in the first ninety days, which decisions you can make alone, and how you will report progress. This avoids a mismatch between your pace of learning and their expectation of results.
Moving into a new team is a common situation in one-on-one leadership coaching. JEM's engagement is 12 weeks, virtual-first, and built for emerging and high-potential leaders in growing roles. When an entire team is working through changed leadership, the Culture-to-Execution Sprint gives the group a shared structure around one live priority.