Technology
Barriers to adopting new technologies in the company

Barriers to adopting new technologies in the company

This survey identifies key reasons why adopting new technologies in the company slows down or fails to deliver the expected impact. It assesses how well the typical adoption conditions are provided (communication, rules, training, support, integrations, ownership, resources), which barriers employees face in practice, where the process most often breaks down, and which actions should be prioritized.

Use template

The Barriers to adopting new technologies in the company survey uncovers why technology rollouts slow down, stall or fail to deliver the expected impact. It looks across many past rollouts to find the recurring obstacles and the stage where adoption most often breaks down.

What the “Barriers to adopting new technologies in the company” survey measures

The survey establishes how often respondents deal with rollouts and how successful adoption usually is, then rates how clear goals and expectations tend to be. A matrix scores how well the standard adoption conditions are provided — clear communication, usage rules, training and materials, support, integrations and process embedding, ownership and decision-making, and dedicated time and resources. Multi-select questions capture the barriers people actually hit (no time, unclear goals, missing guides, slow help, hard access or approvals, unstable tech, missing integrations, no shared rules, resistance to change) and what most reliably helps (clear goals, a small pilot, an internal champion, ready templates, short training, fast early support, integrations). A final question identifies the exact stage — selection, setup, training, process embedding or post-launch support — where the process most often collapses.

Who the “Barriers to adopting new technologies in the company” template is for

It suits transformation and change-management leads, IT and enterprise-architecture teams, CIOs and operations directors, and anyone responsible for making technology adoption stick across departments. It is designed for organizations that repeatedly introduce new tools and want to diagnose systemic obstacles rather than one-off issues.

How to adapt the template to your needs

Because it looks across rollouts in general, keep the wording broad or narrow it to a specific initiative if you prefer. Edit the barrier and enabler lists to reflect your industry and governance, adjust the matrix conditions to match your adoption playbook, and reword the "where it breaks down" stages to your actual process. Add branching so respondents who pick a specific breakdown stage get an open follow-up about what happened there.

Questions and answer options

Question type: single choice.
Answer options:
— Often (several times per quarter or more)
— Sometimes (about once per quarter)
— Rarely (1–2 times per year)
— Almost never
— Hard to say
Question type: single choice.
Answer options:
— Successfully: adopted quickly and delivers impact
— Mostly successful, but there are challenges
— It varies by team/project
— Mostly unsuccessful: often does not deliver the expected impact
— Unsuccessful: it almost always stalls
Question type: multiple rating.
Answer options:
— Clear communication: why we are adopting it and what will change in work
— Clear usage rules (when to use, when not to)
— Training and materials (guides, examples, templates)
— Support and quick responses when issues occur
— Integrations and embedding into processes (guidelines, standards)
— An owner/responsible person and a clear decision-making process
— Dedicated time and resources for the transition
Question type: multiple choice.
Answer options:
— Not enough time to learn and transition
— Goals and expected impact were unclear
— No clear guides/examples
— Couldn’t get help quickly when issues occurred
— Hard to get access or approvals took too long
— The technology was unstable or slow
— Missing integrations; hard to embed into processes
— No shared rules and usage standards
— Resistance to change in the team / habit of old tools
Question type: multiple choice.
Answer options:
— Clear goals and measurable success criteria
— A pilot with a small group and improvements based on results
— An internal expert/champion in the team who helps colleagues
— Ready-made templates and standards for typical scenarios
— Short training and practical “how to do X” guides
— Fast support in the first weeks after launch
— Integrations with current tools and processes
Question type: single choice.
Answer options:
— Solution selection (no agreement on criteria/priorities)
— Preparation and setup (access, integrations, security)
— Training and first usage scenarios
— Embedding into processes (guidelines, standards, ownership)
— Post-launch support (issues are not resolved quickly)
— There is usually no breakdown

Similar survey templates

Frequently asked questions

Yes. A dedicated question asks at which stage adoption most often breaks down — solution selection, preparation and setup, training and first scenarios, embedding into processes, or post-launch support — so you can target the weakest link.
It deliberately looks across many rollouts to surface systemic, recurring barriers and success factors, rather than evaluating a single product — useful for improving your overall adoption approach.
It will. The matrix rates communication, usage rules, training, support, integrations, ownership and dedicated time or resources, so you can see which of these foundations are consistently under-provided.
Yes. The barriers list distinguishes human factors like resistance to change and lack of time from technical ones like instability, missing integrations and slow access, helping you address the right root cause.