I'm Ken Lengel.

Thirty years of watching technology succeed and fail

I've spent more than three decades in IT and artificial intelligence, most of it leading digital transformation inside Fortune 50 organizations — Bank of America, Wells Fargo, and Capital One among them.

Financial services is an unforgiving place to deploy technology. Everything is audited. Nothing ships without a documented owner, a defined control point, and a way to prove it worked. That environment teaches you something that's easy to miss elsewhere: the difference between a technology initiative that produces results and one that produces activity almost never comes down to the technology.

Since 2017 I've run my own practice, and I've guided hundreds of executives through AI implementations. The same pattern shows up nearly every time.

The pattern

Companies between 20 and 200 people aren't behind on AI because they lack talent or ambition. They're behind because the decisions in front of them are genuinely hard, the vendor market is deliberately confusing, and nobody on staff has the time or the mandate to sort it out.

Meanwhile, the discipline that makes AI work at a Fortune 50 bank isn't proprietary and isn't expensive. Data classification. A vendor question list. A two-page use policy. Defined review points. A baseline measurement captured before you start. Perhaps two days of focused work — and it's most of what separates the companies getting real returns from the ones getting a subscription bill.

It just has to be somebody's actual job. That's the work I do.

How I work

I'm not an agency and I don't build custom models. At your size, almost everything worth doing should be bought or configured rather than built, and a great deal of what gets proposed shouldn't be done at all. A significant part of my value is telling you which is which.

Every engagement runs through a structured assessment and prioritization system I built — it scores opportunities, weighs them against your actual budget and your team's real readiness, and produces explicit build, buy, or partner recommendations rather than a list of possibilities.

Then I own the result. Consultants deliver recommendations and leave. The reason AI stalls in most companies is that nobody owns it once the deck is delivered.

Why this role

Because it sits exactly where I'm most useful.

I develop strategy and I implement it tactically — and those two skills don't often live in the same person. Most strategists hand off before the hard part. Most implementers never got to shape what they were handed. Transformation work demands both, and the gap between them is where initiatives usually die.

The honest answer is that I like the problems. Transformation is mostly a sequence of difficult, specific questions — what has to change first, who will resist it and why, what can we prove, what are we prepared to stop doing. After thirty years those are still the problems I find interesting, which is a reasonable thing to want from your work.

I'm based in Charlotte, North Carolina, and work with companies locally and remotely.