Stop Thinking Tech-First. Start Thinking People-First

As excitement around AI continues to grow, many organizations are asking:

“What can we do with this technology?”

“Where could we apply large language models?”

“What use cases should we explore?”

It sounds like strategic thinking. But too often, it leads to disconnected pilots, low adoption, and solutions in search of a problem.

History is repeating itself again and again (think Cloud and Mobile), when will we learn...

Tech-first thinking solves for what’s possible. People-first thinking solves for what matters.

The Problem With Tech-First Thinking

When the starting point is the tool, the ideas can sound impressive:

• Automate document classification

• Build a customer service chatbot

• Generate faster reports with LLMs

But these initiatives often:

• Solve the wrong problem

• Introduce new friction

• Fail to connect to real user outcomes

It’s not that the technology doesn’t work. It’s that the context is missing. No clear user, no urgent need, no measurable benefit.

Why People-First Wins

Instead of asking what AI can do, high-impact teams start by asking:

• Who are we trying to help?

• What are they trying to achieve?

• Where do they struggle, stall, or workaround today?

That’s where meaningful AI opportunities begin, not in the lab, but in the lived reality of the people you serve.

Three Ways to Shift from Tech-First to People-First

1. Observe Real Struggle & Challenges, Not Just Requests

AI shouldn’t be the answer to “what would be cool to build?” It should respond to real, repeatable signs of frustration, delay, or rework.

2. Map Capabilities, Not Just Features

Don’t start with “what could we automate?” Ask, “what do our people need to do better?” Example: “Faster data retrieval for customer conversations” is more useful than “add a chatbot.”

3. Validate Value Early

Ask:

• Will this reduce time, effort, or risk for someone real?

• How will we know it’s working?

• What else needs to change for this to actually deliver value?

What It Looks Like in Practice

You can see the difference in how organizations approach the same question:

Where should we apply AI?

When People-First Thinking Works:

• A customer operations team noticed agents spending 30% of their time repeatedly looking up the same policy data. Instead of building a chatbot, they used AI to surface the answers in-line, saving time, reducing errors, and improving customer experience.

• An engineering org integrated LLM-powered knowledge search directly into developer workflows, so answers surfaced in code reviews and IDEs, reducing friction without adding a new tool to learn.

When Tech-First Thinking Fails:

• A platform team spent months building a generative assistant to write Terraform templates. But no one used it, because the real need wasn’t there, and the tool didn’t handle edge cases.

• An HR team deployed a chatbot to answer policy questions. Employees ignored it. The real blocker? The policies were confusing to begin with. AI only added another layer of indirection.

The difference? One starts with a real struggle or challenge. The other starts with something shiny or tech for tech's sake.

Use AI to Augment, Not Distract

The most effective AI work doesn’t start with flashy ideas. It starts with a clear, painful need, and ends with a quietly powerful improvement.

These projects may not get the loudest applause at first. But they’re the ones that stick, scale, and strengthen trust.

Final Thought

Tech-first thinking starts with a hammer. People-first thinking starts with purpose.

If you want to use AI well, don’t just ask what the model can do. Ask what people need, where the flow is broken, and what capabilities are holding them back.

If you and your teams would like help thinking more People-first and applying AI where it really matters, connect and DM me.