View/Export Results
Manage Existing Surveys
Create/Copy Multiple Surveys
Collaborate with Team Members

OR

Sign inSign in with Facebook

Sign inSign in with Google

The technology survey questions worth asking your own staff

Not the help desk, and not one product. Fourteen questions about the whole set of tools somebody works with: what they sign into, what gets in the way, and whether the last thing you rolled out is being used. Answer them below, copy any block, or open it in the editor.

14questions
About 4 minto complete
5-point agreeon the rating block
No nameasked

Use this template Take the survey first

Technology Survey · answer to move through it

Use this template

Question 1 of 14 Who is answering

Which best describes the work you do?

Operations, production or service delivery

Sales, marketing or something customer facing

Finance, HR or administration

Engineering, technical or IT

Management

Something else

Question 2 of 14 Who is answering

Where do you do most of your work?

At a desk on one of our sites

At home or remotely

A mix of the two

On the move, between sites or with customers

On a floor, ward, vehicle or plant

Somewhere else

Question 3 of 14 What you actually use

In a normal working week, how many different applications or systems do you sign into?

One or two

Three to five

Six to ten

Eleven to twenty

More than twenty

I could not say

Question 4 of 14 What you actually use

Which of these do you use for work at least once a week?

A laptop or desktop computer

A phone or tablet provided by work

My own phone or tablet

A shared or fixed device at a work station

Specialist equipment for my role

None of these

Question 5 of 14 What you actually use

In the last three months, have you used an application or service you found yourself rather than one provided here?

Yes, and I believe it is approved

Yes, and I do not know whether it is approved

No

I would rather not say

Question 6 of 14 Whether it works

The applications I use for work respond quickly enough that I am not left waiting.

1

2

3

4

5

Strongly disagreeStrongly agree

Question 7 of 14 Whether it works

I can find the information I need without asking somebody where it is kept.

1

2

3

4

5

Strongly disagreeStrongly agree

Question 8 of 14 Whether it works

Moving a piece of work between the different systems I use is straightforward.

1

2

3

4

5

Strongly disagreeStrongly agree

Question 9 of 14 Whether it works

The tools I am given make my job easier to do than the way we worked before.

1

2

3

4

5

Strongly disagreeStrongly agree

Question 10 of 14 Whether it works

When a new system is introduced here, I am shown enough to use it properly.

1

2

3

4

5

Strongly disagreeStrongly agree

Question 11 of 14 Whether the last rollout landed

Think of the most recent new system or tool introduced where you work. Which is closest to how you use it?

I use it for everything it was meant for

I use part of it and work around the rest

I tried it and went back to the old way

I have not started using it

Nothing new has been introduced that I know of

Question 12 of 14 Whether the last rollout landed

What has held that back, either for you or for the people around you?

Nothing, it went fine

It is slower than what it replaced

It does not do something we need

Nobody showed us how

The old way still works

Other people have not moved across

I do not know

Question 13 of 14 The number and the open box

Overall, how satisfied are you with the technology you are given to do your job?

Very satisfied

Satisfied

Neither satisfied nor dissatisfied

Dissatisfied

Very dissatisfied

Question 14 of 14 The number and the open box

What is the one thing about the technology here you would change first?

What a technology survey asks that the other ones do not

Technology survey is a broad phrase, and most lists published under it are really about something narrower. Here is the line this one draws.

Every neighbouring survey is scoped to one object. One help desk, one product you are buying, one screen, one release, one risk. Each of those is a good survey and each is a different page. None of them asks the broader question: across the whole set of tools somebody works with, what do they use, what gets in the way, and did the last thing you rolled out get used.

That gap is the reason this template is fourteen questions rather than forty. The published lists on this subject fold the help desk, security awareness, onboarding, training and remote-working kit into one long menu. Each of those is a survey with its own respondents and its own reporting, and a menu that contains all of them is a document nobody sends.

A single figure at the centre of a wide field of small abstract application windows, three of them close and solid and the rest faded and drifting outward — The estate somebody is issued and the handful of tools they actually work in are rarely the same set. The survey asks about the second one.

If the question is really about	Send this instead	Because it asks
The people who fix things when they break	The internal IT survey	Response, resolution and what the desk is like to deal with.
Which product to buy next	The software evaluation scorecard	A scored comparison between named options, not a picture of what is already in use.
Whether one screen is usable	The interface design survey	Task-level judgements about a single interface.
Whether a release is fit to go out	The UAT questionnaire	Scripted checks by named testers, ending in a go or no-go call.
How people behave around risk	The security awareness questionnaire	What people do with passwords, links and reporting, not what they think of the tools.

The 14 technology survey questions, and what each one tells you

Every question, its scale, and how to read an answer. Copy one block, copy all fourteen, or open the survey and rewrite the wording to suit your own organization.

Plain text, one question per line, with the answer scale.

Who is answering, in two taps

Two cheap questions first, because they are the splits that make every rating below readable. Where somebody works matters more than what they do here: a driver between sites and an analyst at a desk are not rating the same estate.

Which best describes the work you do?Choose oneThe function split. Use your own department names, and merge any group small enough that a written answer would identify its author.
Where do you do most of your work?Choose oneThe split that usually does the work. A poor score concentrated in one row here is an estate problem, not an application problem.

What is actually in use, including what you did not issue

Three questions about the real inventory rather than the licence list. The third is the one almost nobody asks, and it is worded so that answering it honestly costs nothing.

In a normal working week, how many different applications or systems do you sign into?Choose oneA band, not a number, because nobody counts their own logins. The interesting cell is people in the high bands who also disagree that moving work between systems is straightforward.
Which of these do you use for work at least once a week?Tick all that applyWhat they touch in a week. The personal phone option is the one to watch, because a device you did not issue is a device you cannot support.[2]
In the last three months, have you used an application or service you found yourself rather than one provided here?Choose oneThe tools people found for themselves. Asked without accusation, with an approved option, a do-not-know option and an opt-out, because a question that feels like a trap gets answered with a no.

Whether the tools work, on one scale

The only rating block on the page: five statements, one 5-point agree scale, one idea each. Speed, findability, moving between systems, whether the tools help, and whether a rollout came with enough support.

The applications I use for work respond quickly enough that I am not left waiting.5-point agree, Strongly disagree to Strongly agreeResponse time, framed as waiting rather than as performance, because a respondent knows they are waiting and does not know what the system is doing.
I can find the information I need without asking somebody where it is kept.5-point agree, Strongly disagree to Strongly agreeFindability. Before you treat a low score as a search problem, check whether the same information lives in three places and none of them is the one people are told to use.
Moving a piece of work between the different systems I use is straightforward.5-point agree, Strongly disagree to Strongly agreeThe seam between systems, which is where re-keying, copy-paste and spreadsheets get invented. Cross this with question 3.
The tools I am given make my job easier to do than the way we worked before.5-point agree, Strongly disagree to Strongly agreePerceived usefulness: the degree to which a person believes that using a particular system would enhance his or her job performance.[3]
When a new system is introduced here, I am shown enough to use it properly.5-point agree, Strongly disagree to Strongly agreeWhether the rollout came with enough support to be usable. Read it beside question 11, which it is there to explain.

Whether the last rollout actually landed

The pair that separates this survey from every other technology question list. Both ask what somebody does, not what they think, because a rollout is judged by use.

Think of the most recent new system or tool introduced where you work. Which is closest to how you use it?Choose oneAdoption in one tap, on a five-step ladder from full use to no use. The two middle answers are the useful ones: partial use and reversion are both live problems and they have different fixes.
What has held that back, either for you or for the people around you?Tick all that apply, optionalThe reason, in the respondent's own account. It carries its own nothing-went-wrong and do-not-know options, so it never leans on a particular answer above.

The one number, and the one open box

A single satisfaction item on five worded levels, then somewhere to say the thing the other thirteen missed.

Overall, how satisfied are you with the technology you are given to do your job?Choose one, five worded levelsWorded levels rather than a bare one to five, so the score is a share of people rather than an average of numbers. Report the top two boxes.
What is the one thing about the technology here you would change first?Open text, optionalOne open question, which is the floor the public service standard sets for feedback of this kind: at minimum, ask how to improve the thing.[4] Read these before the ratings.

All fourteen are built and running in the preview above, so you can design a survey online from this template in a couple of minutes and change the department names before you send it.

One edit to make before you send it. If a specific rollout is the reason you are running this, put its name into question 11 rather than leaving it as the most recent one. A named system produces a usable answer; the most recent one produces five different systems in the same column.

Whether the last rollout landed, and how to ask

The two questions that make this a technology survey rather than a satisfaction survey with a laptop in it.

A rollout is judged by use, so ask about use. Question 11 puts the most recent new system on a five-step ladder: full use, partial use, tried it and went back, never started, nothing new introduced. The two middle answers are the ones worth having. Partial use points at a tool that does most of a job while a spreadsheet covers the rest. Reversion says it was worse than what it replaced, at least for that person, and neither shows up in a licence report.

Ask what held it back in the same breath. Question 12 offers six accounts and a do-not-know, and the split between them routes the work: slower than what it replaced is an engineering problem, does not do something we need is a scoping problem, nobody showed us how is a rollout problem, and other people have not moved across is a sequencing problem. Whichever answer the most people picked is the one to fix first.

The literature behind this is older than the software. The long-running account of why systems get used or ignored rests on two beliefs a person holds: perceived usefulness, the degree to which a person believes that using a particular system would enhance his or her job performance, and perceived ease of use, the degree to which a person believes that using a particular system would be free of effort.[3] Question 9 asks the first in plain words, and reprints no item from that instrument.

Expect the tools you did not issue to show up. A workplace survey of 10,080 full-time employees found that over half of respondents used applications or web services they had personally obtained, most of them employer-sanctioned, for collaborating with other workers, and that 55 per cent used personally owned devices for work at least some of the time.[2] Question 5 asks about that directly, worded so that a yes costs the respondent nothing.

Reading the answers without over-reading them

One number, three splits, and an honest account of what this instrument cannot settle.

Satisfaction is a share of people, not an average of ratings. Question 13 offers five worded levels rather than a bare one to five, so count everybody who chose satisfied or very satisfied, divide by everybody who answered, and report that. An average of five arbitrary numbers moves when the wording moves, so it cannot be read against anything, including your own result from last year.

Cut it three ways before you read the total. By where people work, from question 2, because an estate problem looks like an application problem until you split it. By how many systems they sign into, from question 3, because the top bands are where the seams show. And by whether they use tools they found themselves, from question 5, because that group marks where the provided set stopped being enough.

Read the open box first. One free-text question is the floor rather than a nicety: the public service standard for feedback of this kind sets no formal list of questions you must ask, and says you should at least have an open-ended question about how to improve the thing.[4] The closed answers size a problem; the open one usually names it.

Two things this cannot tell you. It measures what people say, not what they did, so it will not reconcile with any log you hold. And whether a score is good is a question about your own trend: published satisfaction figures for work applications exist, but what counts as normal moves with the wording, the year and the population.[1]

Technology survey questions: FAQ

What questions should a technology survey ask?

Three groups and one number. What people actually use, including tools they found themselves. Whether those tools work, on one rating scale covering speed, findability, moving between systems, usefulness and rollout support. Whether the last new system is being used, and what held it back. Then one satisfaction item and one open box.

How many questions should a technology survey have?

Fewer than the published lists suggest. The menus on this subject run past forty and nobody sends a forty-item tool audit to a whole workforce, while the instruments people actually field are six to eleven. Fourteen is the compromise here, because the subject has three separate parts: what is in use, whether it works, and whether the last change stuck.

How do you measure technology adoption in a survey?

Ask what somebody does, not what they think. Question 11 puts the most recent rollout on a five-step ladder from full use through partial use and reversion to no use at all, and question 12 asks what held it back. The research tradition behind this sits on two ideas, usefulness and ease: whether a person believes the system would enhance their job performance, and whether they believe using it would be free of effort.[3] Question 9 asks the first of those in plain words.

Should a technology survey be anonymous?

Yes, and say so before people answer. It asks for no name and no email address, and the answers arrive in the account it was made in. Questions 1 and 2 are the only things that could narrow anybody down, so merge any group small enough that a written answer would name its author. Question 5, on tools people found for themselves, only gets an honest answer under that promise, which is why it also carries an opt-out.

What is the difference between a technology survey and an IT survey?

What is being judged. An IT survey judges a service and the people who run it: response, resolution, the desk. A technology survey judges the tools themselves and whether they fit the work, whoever supplies them. Run both, and run them separately, because a workforce that rates the desk highly can still be losing an hour a day to an application that does not talk to the next one.

Methods and sources

Survey methodology and questionnaire design, SuperSurvey

Survey methodologist and editor since 2003: wording, response scales, reliability checks, reporting that maps to a decision.

Fourteen questions written for this page, carrying no item from the Technology Acceptance Model, UTAUT, the System Usability Scale or any other published instrument
Question count and completion time read off the survey running on this page
Every capability described here is an ordinary link or an embed, checked against what the editor can do

Updated 9 September 2026 · How templates are reviewed

What this template is based on

The adoption pair is built on the two beliefs that the long-running acceptance literature places at the centre of whether a system gets used, quoted from an academic review of the original paper.[3] The expectation that people arrive with tools nobody issued, and the 55 per cent figure for personally owned devices, come from a published workplace survey of 10,080 full-time employees.[2] The point that a satisfaction figure for work applications has to be read with its year and its population attached is drawn from a later release by the same publisher.[1] The floor of one open-ended improvement question follows the public service standard for feedback of this kind.[4]

Question licensing

Nothing here reproduces a licensed, paid or standardised instrument. The Technology Acceptance Model and UTAUT are named and cited only: their items sit inside copyrighted journal articles and the UTAUT model carries an explicit copyright line permitting adaptation by permission, so the two TAM constructs are quoted as definitions and no item from either is reprinted. The System Usability Scale is not used here at all. The two figures taken from press releases are published statistics quoted with their publisher, sample size and field dates; no toolkit, benchmark table, chart or item from that publisher is reproduced. The GOV.UK material is Crown copyright under the Open Government Licence v3.0. Every question here was written for this page and is free to copy, edit and send anywhere.

Limits and disclosure

This is a survey behind a link, not an audit. It does not read device inventories, licence counts, sign-in logs or an MDM, so it records what people say they use rather than what they opened. The two published figures quoted are from 2020 and 2024 field dates and are stated with those attached rather than as what normal looks like now. No response-rate figure is offered: the ones circulating for internal technology surveys are self-reports with no method or sample size. Two widely repeated figures attached to the same publisher, on the number of applications a knowledge worker uses and on the share who struggle to find information, are deliberately absent: neither appears in either release that was fetched.

SuperSurvey makes the editor this template opens in. Everything here works with or without it.

References

Gartner, Inc. Gartner Predicts Over 20% of Workplace Apps Will Use AI-Driven Personalization Algorithms for Adaptive Worker Experiences by 2028. Press release, 12 March 2025. Figures from a Gartner survey of 5,141 employees fielded April to July 2024. gartner.com
Gartner, Inc. Gartner Survey Finds 1-in-5 Workers Consider Themselves Digital Technology Experts Since COVID-19. Press release, 26 April 2021, reporting the Gartner 2021 Digital Worker Experience Survey: 10,080 full-time employees at organizations with 100 or more employees in the US, Europe and Asia-Pacific, fielded November to December 2020. gartner.com
TheoryHub, Newcastle University. Technology Acceptance Model, an academic review of Davis, F.D., "Perceived Usefulness, Perceived Ease of Use, and User Acceptance of Information Technology", MIS Quarterly 13(3), 1989. open.ncl.ac.uk
Government Digital Service. Measuring user satisfaction, GOV.UK Service Manual. Crown copyright, Open Government Licence v3.0. gov.uk

Send the fourteen, then split the answers three ways

Fourteen questions, about four minutes, no name asked. Open it in the editor, put your own department names into question 1, and name the system in question 11 if there is one.

Use this template