Business Environment · Topic 8 of 8

Organizational Change and Environment

Support organizational change with readiness, communication, training and reinforcement, and track external shifts in markets, law and technology.

  • 5 min
In a nutshell
  • Delivery does not equal benefit, because people must adopt the change.
  • Change management and project management are linked but different.
  • Assess readiness and impact, then plan communication, training and support.

What it is

Projects exist to create change, and a project is only valuable if the organization actually adopts what it delivers. Supporting organizational change means helping people and teams move from the old way of working to the new one. Evaluating the external business environment means watching forces outside the organization that could affect the project or its value.

Both topics link the project to the wider business. The project manager works with the sponsor and change specialists, because delivery alone does not guarantee benefits.

Outside forcesmarket law technologyImpact assessmenteffect on projectResponseadjust plan or backlogOrganizational changeadoption by people

How it works

Supporting organizational change

Change management is the approach to moving people, teams and the organization from a current state to a future state. It is related to project management but is not the same, because the project builds the solution and change management helps people adopt it.

Typical steps include:

  1. Understand the change. Clarify what will be different and for whom.
  2. Assess impact and readiness. Identify who is affected, how much, and how ready they are.
  3. Plan the change approach. Set out communication, training, support and timing.
  4. Engage stakeholders. Involve sponsors, managers and affected groups, and address resistance.
  5. Deliver and support. Provide training and help during the transition.
  6. Reinforce. Measure adoption, recognize progress and fix barriers.

Assessing organizational culture

Culture shapes how people react to change, so assess it before planning the change approach. Look at shared values, how hierarchical the organization is, its attitude to risk, how earlier changes went and how ready people are for this one. Interviews, surveys and workshops give evidence, and observing how decisions are made adds to it.

Then adapt the approach. A hierarchical, cautious culture may need visible sponsor backing and a phased rollout, while an open culture may adopt change faster through involvement and experimentation.

Models of change

Several models describe how people move through change. The exam needs the idea more than the detail.

ModelMain idea
LewinUnfreeze the current state, make the change, then refreeze the new state
ADKARIndividuals need awareness, desire, knowledge, ability and reinforcement
KotterA staged approach that begins by building urgency and a guiding coalition

All three agree that people need a reason to change, support while they learn, and reinforcement afterwards.

Sponsorship and resistance

Visible sponsor support is one of the strongest factors in successful change. Resistance is natural and often carries useful information.

Listen to concerns, explain the reasons and benefits, involve people in the design and provide training. Forcing change without these steps often leads to quiet non adoption.

Change in agile and hybrid projects

Agile delivery can ease adoption because users see increments early and give feedback. Frequent releases, however, can overwhelm users, so plan communication and training for each release. In hybrid projects, a predictive change plan with a go live date may sit alongside iterative development.

Evaluating the external environment

External factors can alter the project's value, risks or constraints. A common checklist is PESTLE: political, economic, social, technological, legal and environmental. Others include competitors, customers, suppliers and market trends.

Example changePossible effect
New regulationAdded compliance work, scope change
Competitor launchHigher priority for some features
Currency or price shiftBudget pressure
New technologyChance to simplify or risk of obsolescence
Supplier failureSchedule delay, need for alternatives

Responding to external change

Monitor sources regularly through news, market analysis, regulators, stakeholders and risk reviews. When a change appears, assess its impact on scope, schedule, cost, risk and expected benefits. Then decide whether to adjust the backlog or plan, submit a change request, escalate to the sponsor or even revisit the business case.

Monitorsources and reviewsDetect changenew factorAssessimpact on valueDecideadapt or escalate
Exam tip

When an external event threatens the business case, the right step is usually to assess impact and inform the sponsor, not to continue unchanged or to stop the project alone.

What to remember for the exam

  • Delivery does not equal benefit, because people must adopt the change.
  • Change management and project management are linked but different.
  • Assess readiness and impact, then plan communication, training and support.
  • Sponsor visibility is a strong success factor, and resistance should be understood.
  • Lewin uses unfreeze, change and refreeze, and ADKAR has awareness, desire, knowledge, ability and reinforcement.
  • Reinforcement after go live helps changes last.
  • PESTLE is a prompt list for external factors.
  • Assess external changes for effect on scope, schedule, cost, risk and benefits.
  • The business case may need revalidation after a major external change.

Common mistakes

Assuming go live means done. Adoption can lag far behind delivery.

Treating resistance as a nuisance. It often shows real problems with the design or the plan.

Training too late. Users need time to learn before they have to use the new system.

Ignoring the outside world. A project can be well run yet become irrelevant if the market has moved.

Reacting without assessing. Impact analysis comes before changes to scope or the baseline.

Watch out

Do not decide alone to cancel or reshape the project because of an external event, since major decisions belong to the sponsor and governance body.

Check yourself

  • What does ADKAR stand for?

    Awareness, desire, knowledge, ability and reinforcement.

  • What does the PESTLE checklist prompt you to scan?

    Political, economic, social, technological, legal and environmental factors outside the organization.

  • What should you do first when a new regulation affects the project?

    Assess its impact on scope, schedule, cost, risk and benefits, then raise a change request or inform the sponsor as needed.

Topic 8 of 8 in Business Environment

Test yourself on Business Environment

The full PMI PMP question bank has 1,463 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by PMI. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.