Lextech · Internal research · AI adoption

Asking our own team what they actually think about AI.

12+Interviews 30–45Minutes each 4Themes that shaped next steps

Lextech wanted to understand where its own people stood on AI. I wrote the interview script, scheduled and ran the interviews, and synthesized what I heard into a data set of the team’s willingness, concerns, and ideas for using AI.

Download as a slide deck (PDF, 158 KB)

RoleSenior Product Designer · Research lead
CompanyLextech Global Services
TimeframeLate 2025 – early 2026
MethodsInterviews · Synthesis · Documentation
The question

How willing is our team to use AI, what’s holding people back, and where do they see it helping?

My role

I ran the study end to end: script, scheduling, interviews, synthesis, and the write-up.

Where it landed

I documented the findings in Notion. Several members of leadership used them to plan the initiatives that followed.

How I ran it

01 · Script

Write the questions

A consistent interview script covering how people felt about AI, what worried them, and where they thought it could help in their own work.

02 · Interviews

Talk to over a dozen people

I scheduled and led each conversation, 30 to 45 minutes long, across the team.

03 · Synthesis

Find the patterns

I turned the notes into a data set of willingness, concerns, and ideas, then grouped it into themes.

04 · Share

Make it usable

I wrote the findings up in Notion so leadership could reference them when planning what came next.

What we heard

The concerns that came up most were practical ones: knowing where to start, protecting client data, and finding the time.

Many people

“Where do I even start?”

Many people had no idea where to begin with AI and said they needed training.

Many people

Client confidentiality

A consistent worry: what is safe to put into an AI tool when you work with client data every day?

Many people

No time to learn

Many worried about how they’d find time to learn AI on top of their daily client work.

Some people

Job security

Some people worried AI would eventually replace parts of their role, or all of it.

What I took from it

Adoption starts with training

For many people, the gap wasn’t interest. It was knowing where to start, and knowing what was safe.

Time has to be part of the plan

Asking people to learn on top of full client workloads wasn’t realistic. Any rollout needed time set aside for it.

Say the quiet worries out loud

Confidentiality and job security came up again and again. Naming them directly in the findings made them things leadership could address, not just background anxiety.

Get in touch

Working out how your team feels about AI? Let’s talk.

I love talking about design and hard problems. Drop me a line or connect on LinkedIn. I would love to hear from you.