Organizational change in a technology company rarely fails at the strategy level. It tends to fail in the weeks between the announcement and the moment when the team returns to a normal way of working.
That is when it becomes clear whether people will start operating effectively in the new setup or spend the next few months in a low-energy mode: completing tasks, but without initiative, questions, or real engagement in what comes next.
In technology companies, there is an additional layer. Change affects people who professionally design and implement changes in systems, while often having very little tolerance for communication that lacks specifics.
In brief:
- technical change and organizational change are two very different experiences for IT professionals because they involve different levels of control,
- resistance in technical teams often appears as substantive questions rather than openly expressed emotions,
- what may look like a lack of engagement is often a difference in how people respond to uncertainty,
- working with CliftonStrengths gives teams and leaders a shared language for these differences and practical insight into what people may need in order to move forward,
- a CliftonStrengths session does not replace information, decisions, or well-sequenced communication – it works when those foundations are already in place.
Why change in IT is different from other industries
The technology industry often presents itself as naturally resistant to disruption. Sprints, migrations, refactoring, new technology stacks every few years – in theory, technical teams should be better equipped than most to deal with organizational change.
In practice, the opposite can happen, and there are good reasons for it.
Technical change usually comes with greater control
Technical change is often something a specialist can influence. They may have planned it, understand the dependencies, can see the expected outcome, and know the criteria for success. Organizational change works differently: the decision is often made elsewhere, information is incomplete, and the full impact may not become clear for several months.
This is not simply a question of how resilient a team is. It is a question of how much influence people feel they have.
In IT, change can also affect professional identity
In IT, expertise is a form of currency. Developers, architects, and QA specialists build their position within a team primarily around what they know and what they can deliver, not simply around tenure or organizational hierarchy.
Any change that shifts the definition of what counts as a valuable skill can therefore affect much more than a person’s formal responsibilities.
In IT outsourcing, specialists operate within two organizations at the same time
A specialist working on a client project effectively operates in two environments at once. The client may be going through a reorganization while the employer is making changes of its own, and neither side always has the full picture available at the same time.
A change of Team Leader on the client’s side or a shift in roadmap priorities can be interpreted as a signal about someone’s own professional security. This is one of the moments when losing a strong specialist becomes more likely – usually not because of the decision itself, but because of the information gap between the two organizations.
What drives change in technology companies today
Change is rarely triggered by one major decision. More often, several developments overlap at the same time.
A more cautious labor market
Employee turnover is lower than it was in 2021 and 2022, while decisions to change jobs are more cautious. People stay with organizations longer, but they also pay closer attention to what is happening around them. Silence during a meeting does not necessarily mean acceptance. More often, it means observation.
AI in the everyday work of technology teams
AI-based tools are changing how time is distributed across projects: less routine coding, more work around architecture, quality, testing, and verification. For some people this creates opportunity. For others, it raises a question about what seniority in their specialization will mean two years from now.
That question is rarely asked openly in a team meeting. It is much more likely to come up in a one-to-one conversation.
Consolidation in the IT services market
Acquisitions and company mergers lead to structural changes, aligned processes, and common standards. From an organizational perspective, this is often about creating greater consistency. From an employee perspective, every such change raises a much more immediate question: what exactly will change in my everyday work?
Regulation and changing standards of cooperation
The IT services market operates in an evolving legal and regulatory environment. A mature technology partner updates its documentation, policies, and standards of cooperation as those requirements change. This is a normal part of running the business and an important capability, particularly for enterprise clients that expect their technology partners to have these areas under control.
At the same time, employees read every document that changes the rules of cooperation very carefully. That is why such updates should be communicated in advance, with an explanation of their purpose and space for questions, rather than sent as an attachment without context.
CliftonStrengths during change: what it helps with and what it cannot replace
CliftonStrengths (Gallup) is a development tool that describes natural patterns of thinking, feeling, and behaving. It is not a clinical psychological assessment and it is not a selection tool. We do not use it to make recruitment decisions or evaluate employees. We use it to support conversations about how a specific person tends to work most effectively.
Why use it during a period of change?
It gives the team a language for differences that were previously judged.
Before a team understands its strengths, the same behaviors may be described in value-laden terms: someone “complains”, someone “doesn’t engage”, someone else “rushes ahead without a plan”. After a strengths session, those same behaviors can be understood as different ways of responding to uncertainty.
It gives leaders practical guidance for individual conversations.
Instead of delivering the same message to everyone, a leader can better understand who needs more data, who needs a concrete list of tasks for the coming week, who needs reassurance about what will remain unchanged, and who needs clarity about the people they will be working with.
It helps restore a sense of competence when many other things are uncertain.
A conversation about what someone does well and why is one of the few stable reference points during a transition. This can be especially valuable for people moving to a new project or a different role.
It highlights risks at the team level, not just the individual level.
A team strengths map can help explain why one team starts cautiously and methodically while another moves immediately and returns to corrections later. Both patterns have a cost, and both can be balanced consciously.
What this can look like in practice
Below are some patterns we commonly observe. They are tendencies, not rules, and a strengths profile should never be treated as a complete explanation of someone’s behavior.
| Strength | How it may show up during change | What may help |
|---|---|---|
| Deliberative | Asks questions about risk and may be perceived as slowing the decision down. | Access to information before the announcement and a real opportunity to raise concerns. |
| Achiever | Can lose a sense of progress when tasks and priorities become unclear. | A short list of concrete things that can be completed this week. |
| Learner / Intellection | May see a new domain or technology as an opportunity. | Dedicated learning time built into the plan rather than added on top of a full workload. |
| Belief | Quickly notices inconsistencies in rules, especially when teams are being combined. | Clear criteria and an honest explanation of temporary differences. |
| Harmony | May stay quiet in a group setting but share concerns openly in a one-to-one conversation. | An individual channel for feedback – otherwise their perspective may be missing from the overall picture. |
| Relator | May be particularly affected by the separation of an established team. | Ways to maintain relationships with people they previously worked closely with, even if the format changes. |
| Responsibility | May take on more than they should without signaling overload. | Clearly defined boundaries and regular check-ins. |
| Activator | Moves quickly and may start acting before the direction is fully agreed. | A clear first task and an explicit priority. |
When a CliftonStrengths session does not make sense
Working with strengths does not replace information or decisions.
If the team does not know what is happening, a development workshop can easily be perceived as an attempt to distract people from the real issue – and may make the situation worse. Sequence matters: first the facts and answers, then the work on how the team wants to operate in the new environment.
Such sessions also make sense when participation is voluntary and the results belong to the participant. A strengths report should not become part of a performance review or be used as an argument in employment decisions.
What else we do to help teams move through change without unnecessary losses
CliftonStrengths is one element, not the entire process. At Edge One Solutions, several practices work together when teams are going through change.
The right communication sequence.
Leaders first, with real answers and explicit permission to say, “I don’t know yet, but I’ll check by Friday.” Then teams. Then individual conversations. A leader without information has to improvise, and improvisation by a leader is one of the most expensive forms of communication during organizational change.
Preparing leaders and Team Leaders.
They need a briefing with the facts, expected questions, and clear boundaries around what can be communicated. They also need support in conducting difficult conversations, because guiding a team through organizational change requires different skills from managing a project.
One source of information and a live FAQ.
During larger changes, such as combining teams or changing standards of cooperation, one regularly updated source of truth works better than a sequence of emails. It reduces conflicting versions of the story and lowers the cost of repeatedly asking the same questions.
Individual conversations and regular check-ins.
A team meeting is rarely where people say everything they really think. It is often where they check whether the official version is consistent with what they have heard privately. The real picture of team sentiment usually emerges in one-to-one conversations.
Onboarding and re-onboarding when projects change.
A specialist moving to another client project goes through a complete environmental change: a different product, process, and team. Treating this as a simple internal rotation is one of the more common sources of quiet frustration.
Internal development around soft skills and resilience.
Feedback, communication in distributed teams, and managing workload are areas where the value becomes especially visible during periods of instability.
Employee sentiment surveys – followed by action.
A survey without shared conclusions and follow-up actions can reduce trust more than not running one at all. If the same issue with a process is raised by several teams, the answer is not another workshop. It is to fix the process.
Building a sense of community in a distributed model.
When people work within client organizations, their connection with their own employer does not build itself automatically. Team meetings, internal events, and regular contact with someone on the employer’s side are what maintain that connection when everyday work happens somewhere else.
Four mistakes that cost the most
01.
Announcing a “new chapter” without specifics.
The more enthusiasm and the fewer dates, the more room there is for speculation.
02.
Promising that nothing will change when everyone knows that something will.
One statement like this can damage trust more than the change itself.
03.
Appointing change ambassadors without giving them access to information.
A role without knowledge or authority turns someone into a spokesperson for messages they may not fully understand or believe themselves.
04.
Silence after the announcement.
This is one of the most common mistakes in outsourcing. A team working for a client without regular contact with its own organization will fill in the gaps on its own – and the assumptions are often worse than the reality.
Where to start
If your organization is planning a structural change, a new working model, or changes to team composition, a sensible minimum looks like this:
- Clarify what has been decided, what has not, and when the remaining decisions will be made.
- Prepare leaders before communicating with teams and give them permission to say, “I don’t know yet, but I’ll check.”
- Schedule individual conversations within the first two weeks, not after the first quarter.
- Only then move into team-level work: workshops, strengths sessions, and agreements on new ways of working.
- Use what you learn to improve processes, not just to work on people’s reactions.
Change rarely fails at the level of strategy. It fails somewhere between the announcement and the first Monday afterwards.
Need support in helping your teams navigate change?
If your organization is going through a reorganization, combining teams, or changing its working model and you want your technical teams to come through the transition without losing engagement, let’s talk about what could work best in your situation.
