Rolling out a new tool in the team
The Rolling out a new tool in the team survey shows how a recently introduced tool is really being adopted, beyond the launch announcement. It captures who actually uses it, for which tasks, how confident people feel, and what is holding adoption back.
What the “Rolling out a new tool in the team” survey measures
The survey pinpoints each respondent's adoption stage — from daily use to "tried it and stopped" or "don't plan to use it" — and maps the tasks people apply it to (planning, collaboration and approvals, documentation, analytics, team communication, automation, client work). An overall satisfaction rating and a self-reported confidence level reveal how comfortable people are with typical workflows, while a matrix scores the rollout itself: goal clarity, access and getting started, clarity of usage rules, training materials, support and Q&A, and integration into existing processes. Barrier and enabler questions expose why some people stall (no time, unclear value, complex UI, missing integrations, access problems, no shared rules, low colleague usage) and what actually helps — onboarding sessions, step-by-step guides, templates, internal champions or office hours.
Who the “Rolling out a new tool in the team” template is for
It suits team leads and managers running a rollout, IT and operations teams introducing software, enablement and L&D specialists, and product or platform owners driving internal adoption. It works for a single team piloting a new app or a company-wide standardization on one tool across departments.
How to adapt the template to your needs
Replace the generic "new tool" with the actual product name and tailor the task list to how your team really works. Adjust the matrix rows to the parts of your rollout you own (access provisioning, training, support channel), edit the barrier and enabler options to match feedback you already hear, and use branching so that non-users are routed to the barriers question while active users go deeper on confidence and workflows.
Questions and answer options
Answer options:
— I use it regularly (almost every day)
— I use it occasionally (several times a week/month)
— I tried it a few times but don’t use it now
— I haven’t tried it yet, but I plan to
— I don’t plan to use it (I don’t need it)
— Hard to say
Answer options:
— Task planning and organization
— Collaboration and approvals
— Documentation and knowledge base
— Analytics/reporting
— Team communication and coordination
— Automating routine actions
— Working with clients/external requests (if applicable)
Answer options:
— Goal clarity: why we’re rolling it out and what results we expect
— Access and getting started (account, permissions, setup)
— Clarity of rules: when and what to use the tool for
— Materials and training (guides, examples, templates)
— Support and Q&A (channel, owners, response speed)
— Integration into processes (integrations, guidelines, typical workflows)
Answer options:
— Not enough time to learn it
— The value for my tasks is unclear
— Not enough training/examples
— Complex UI or inconvenient workflow
— Missing integrations with other tools
— Access/permission issues
— Unstable performance/low speed
— No shared rules in the team; everyone does it differently
— Colleagues rarely use it, so it’s hard to “fit it in”
Answer options:
— Fully confident
— Mostly confident
— Medium: I often need guidance
— Mostly not confident
— Not confident at all
— I don’t use it yet
Answer options:
— A short onboarding session (30–45 minutes) showing key workflows
— Step-by-step “how to do X” guides (1–2 pages)
— Templates for typical team tasks
— Examples of “how we use it in the team”
— An internal expert/champion in the team
— Regular office hours
— Quick answers in the support chat
