Joining a new organisation as a change practitioner can create an immediate urge to prove your value. There may already be a transformation programme under pressure, sponsors asking for a plan and teams expecting communications or training. It is tempting to reach for a familiar framework and begin producing deliverables.
The more useful starting point is to understand the organisation before trying to change how it changes. A sound method still needs local evidence. The first few weeks should help you learn how work is really delivered, how decisions are made, what people have experienced before and where current commitments are already stretching capacity.
Start with the reason you have been brought in
Clarify the problem that prompted the role. Are you supporting one defined project, several programmes or a wider change capability? Has the organisation asked for better adoption, clearer ownership, stronger sponsorship or relief from change overload? The answer shapes what you need to learn first.
Ask the sponsor what success would look like in practical terms. Listen for observable outcomes: teams using a new process correctly, managers able to support a transition, customers experiencing less disruption or benefits continuing after project closure. If the answer is mainly a list of activities, help separate the work you will produce from the result the organisation needs.
Learn the organisation's change history
People rarely meet a new initiative with a blank mind. They remember previous launches, abandoned systems, reorganisations and promises that did not translate into daily work. Those experiences affect trust and willingness to engage.
Speak with people from operations, projects, internal communications, learning, HR and frontline management. Ask which changes landed well, which created avoidable pressure and what happened after go-live. You are not looking for blame. You are gathering evidence about the organisation's ability to prepare, equip and support people through transition.
Map the work before mapping the stakeholders
A conventional stakeholder list is useful, but it can become abstract when you are new. Begin with the work. Which teams perform the process today? What decisions do they make? Which systems, policies, targets and hand-offs shape their day? Where do customers or suppliers enter the picture?
Once the work is visible, the stakeholder picture becomes more accurate. You can identify who experiences the change, who controls necessary resources, who manages the people affected and who will own the result in business as usual. This also reduces the risk of treating a senior organisation chart as a substitute for understanding operational influence.
Understand how decisions really move
Formal governance tells you where decisions should happen. Delivery experience tells you where they actually happen. Find out how sponsors, project boards, operational leaders and subject-matter experts work together. Notice which decisions require evidence, which need informal alignment first and where approval regularly stalls.
Project management disciplines help here. Existing plans, risks, issues, dependencies, benefits and tolerances show what the organisation has already committed to deliver. They also reveal whether the people side of change is connected to the delivery plan or treated as a separate stream that receives information late.
Assess readiness without turning people into scores
A readiness assessment should create a useful conversation, not a verdict on whether employees are positive enough. Look at the size and nature of the change, the number of groups affected, leadership commitment, manager capacity, competing initiatives, available capability and the residual effects of previous changes.
Prosci's Prepare Approach phase asks practitioners to define success, define impact and define the approach. Those questions are a sensible guide when you are new. They keep attention on the current state and the people who must work differently before you begin building communication, training or resistance-management plans.
Observe operational rhythms
Every organisation has periods when change activity is easier or harder to absorb. Month end, seasonal demand, regulatory deadlines, product releases and annual planning can all affect availability. Managers may support a change in principle while having no realistic time to attend workshops or coach their teams.
Place those rhythms beside the project schedule. This is where change management and project management become especially powerful together. A milestone may be technically achievable but operationally unwise. Early visibility allows the sponsor and project team to adjust sequencing, narrow a pilot or provide additional support before pressure becomes failure.
Build relationships through useful questions
You do not need to arrive with every answer. Credibility often grows faster when your questions help other people see the change more clearly. Ask managers what their teams will stop, start or continue doing. Ask operational owners what would make adoption sustainable. Ask the project manager which assumptions carry the most delivery risk.
Share back what you hear in a concise form and check it. A one-page current-state view, an initial impact summary or a short list of unanswered decisions can be more valuable than a large plan built too early. It shows that listening is leading to structure and action.
Choose the smallest useful change approach
Once you understand the organisation, scale the approach to the change. A contained process adjustment may need a clear sponsor, manager briefing, practical job aid and short adoption check. A major operating-model or technology change may require deeper impact assessment, a sponsor coalition, role-based communications, learning, coaching and structured reinforcement.
Avoid introducing terminology simply to demonstrate expertise. Use language the organisation recognises, while keeping the underlying discipline. The method should make the work clearer and more reliable. It should not require people to learn a second change before they can participate in the first.
Turn the first month into an agreed plan
By the end of the initial listening period, you should be able to explain the reason for the change, the groups affected, the main operational impacts, the readiness risks, the sponsorship needs and the decisions required next. Agree these findings with the sponsor and project lead before expanding the plan.
The aim is not to spend a month observing without contributing. It is to avoid producing confident activity on weak assumptions. A change practitioner becomes useful by connecting evidence about people and operations to the decisions, sequence and controls that shape delivery.
If you are introducing change management into a programme or strengthening the link between project delivery, operational readiness and adoption, I would be happy to discuss a practical approach that fits the organisation and the work already under way.
About Mark M Barton
I am a Change Management, Change/Internal Communications, and Project Delivery and Operations professional with over 25 years' experience helping organisations deliver complex projects, improve operations and navigate organisational change.
Certified in both Prosci Change Management and PRINCE2, I work across change management, project delivery, operational improvement, internal communications and transformation initiatives, helping organisations achieve successful outcomes through both structured delivery and effective people engagement.
If I can help you, your team, or your organisation do reach out.
