Product Innovation Leader · AI Transformation Strategist

The future belongs to organizations that learn faster than change itself.

For 25+ years I've helped organizations build products, lead design, and navigate change. Over the last 18 months I've been conducting a structured exploration across AI, product development, emerging technology, and organizational capability — building 50+ experiments to understand what leaders need to know before the future arrives.

I help organizations understand what changes when AI becomes part of how products are built, decisions are made, and teams operate. My work sits at the intersection of product strategy, design leadership, organizational change, and AI-native ways of working.

Read the Observations Work Together

25+

Years in Product & Design

52+

Products Built

Industry Domains

18mo

Structured AI Lab

The Central Question

Not what AI can do. What AI changes about how organizations create value.

"AI didn't make me smarter. It made me faster. I had to bring the smart. That changes everything about what human expertise is worth."

Most organizations approach AI as a technology problem. They buy tools, run pilots, and wait for transformation to happen. It doesn't. The bottleneck is almost never the software. It's the thinking, the process, and the people who know how to direct it.

Building was the method. 52+ products across FinTech, EdTech, PropTech, AI Agents, computer vision, spatial computing, and hardware — structured as research, not portfolio building. Every product was a hypothesis. Every outcome was a data point worth examining.

The question was never "what can AI do?" The question was: what does AI change about how organizations create value, develop capability, and make decisions? Here's what the experiments revealed.

Why This Matters Now

Leaders aren't struggling because AI is moving too fast.

They're struggling because nobody knows which changes actually matter.

Should teams be reorganized around AI workflows?

Should product discovery change entirely?

Should designers be expected to build?

Should engineers become product thinkers?

Should managers become AI operators?

Which roles still matter in five years?

The technology is changing quickly. The harder challenge is deciding how people, teams, and organizations evolve around it — and that is not a technology decision. It is a leadership one.

Key Observations

Five patterns that keep emerging across every domain.

The gap is never in the technology. It's always in the thinking.

Organizations that fail at AI transformation invested in tools before they invested in thinking. The bottleneck is sense-making — the ability to ask the right questions, interpret outputs critically, and direct AI with intent. That skill is not in the software. It has to come from someone who can see the problem clearly before the machine runs.

Experienced humans become more precious, not less.

Contrary to the anxiety narrative, AI doesn't devalue expertise — it amplifies it. A domain expert with AI works at a different order of magnitude than either alone. The people who know what good looks like, who have context, who can evaluate outputs rather than just generate them — they become the irreducible bottleneck. The Generative Human, not the AI, is the asset worth protecting.

Discovery without velocity is expensive waiting. Velocity without discovery is expensive guessing.

The biggest waste in most organizations isn't time spent on AI projects — it's time spent building the wrong things fast. The teams winning are not the fastest. They're the ones that figured out how to compress the thinking phase without skipping it. Structured discovery at AI speed — that combination separates experiments that generate institutional knowledge from ones that generate expensive noise.

AI has made the cost of learning from doing negligible. Treat experimentation as strategy, not overhead.

When prototyping costs $100 instead of $100,000, the calculus of experimentation changes entirely. Organizations building institutional knowledge at speed are not running AI pilots — they're running structured experiments with real hypotheses and real outputs. The question isn't whether you can afford to experiment. It's whether you can afford not to.

The transition is cultural before it is technical.

Every AI initiative that fails does so for the same reason: the humans in the system weren't ready to work alongside it. Not because of resistance, but because nobody designed the workflow, the handoffs, or the capability-building program. Technical implementation is the easy part. Organizational adoption is where value is either created or destroyed.

Research Through Building

50+ builds. 10 domains. Not demos — research.

Not a portfolio. Not hobby projects. Not startup ideas. A structured research program conducted through execution — because the only way to understand how AI changes product creation is to build things with it, repeatedly, across domains, and pay attention to what breaks and what holds.

AI Agents & Automation Product Discovery & Specs Computer Vision & Hardware AI Content & Creator Systems Platform & SaaS Products FinTech & PropTech EdTech & Wellness Spatial, 3D & Emerging Design Tools & Plugins GovTech & Social Impact

The constraint is never the model.

Across every domain, the bottleneck was always requirements clarity, workflow design, or the human judgment layer — never the AI capability itself.

Team size is no longer the limit.

Production-grade platforms, multi-channel content systems, hardware pipelines — all built by a single person. The new constraint on product creation is clarity of thought, not headcount.

Editorial judgment is the new scarcity.

When production becomes cheap, the people who know what good looks like become exponentially more valuable. Domain expertise doesn't depreciate — it compounds.

"The organizations that will lead the next decade are not the ones with the most AI budget. They're the ones that learn fastest from doing — and have someone who can design what they're learning toward."

Organizational Implications

What leaders should actually be asking.

Not "which AI tools should we buy?" The more important questions are about people, capability, and organizational design.

What changes about product creation?

The cost of going from idea to working product has dropped by an order of magnitude. This doesn't mean you need fewer product managers — it means the value of a good one has multiplied. The people who can direct AI with intent, evaluate outputs critically, and make judgment calls at speed become the highest-leverage asset.

What changes about team capability?

The AI skill gap in most organizations is not technical — it's directional. Teams don't need to know how to build AI. They need to know how to work with it. That means different hiring criteria, different training programs, and different workflows. Most organizations haven't started designing any of those yet.

What changes about organizational speed?

The baseline speed of building, testing, and iterating has permanently shifted. Organizations still moving at pre-AI velocity aren't falling behind on technology — they're falling behind on institutional learning. Every month of slower experimentation is a month of competitive knowledge not being accumulated.

What should leaders do first?

Run one structured experiment in a real domain with a real hypothesis. Not a pilot, not a demo — an experiment with a specific question, a measurable output, and a human who can interpret the results. More learning comes from one real experiment than from a year of AI strategy workshops.

How I Work With Organizations

Three ways I help leadership teams move faster.

The work sits at the intersection of executive AI strategy and product execution — translating AI capability into organizational decisions, capabilities, and products. Not another vendor. The person who helps leadership think clearly before they act.

Where I operate

Executive AI Strategy Product Transformation AI-Native Capability Building Innovation System Design

Advisory

AI Transformation Strategy

Working with executive and leadership teams to map where AI creates genuine organizational leverage — and where it creates risk. The goal: better questions before tool decisions. The result: an AI strategy built on evidence, not vendor promises. Grounded in 18 months of structured experimentation, not trend reports.

Leadership

Product Innovation Leadership

Leading product teams building AI-native experiences. 25 years of product and UX thinking alongside hands-on AI build depth means operating at the level of strategy, design, and execution simultaneously. Valuable for teams that need to move fast without making expensive architectural mistakes.

Capability Building

Organizational AI Readiness

Designing the workflows, training programs, and operating models that let design and product teams work AI-natively. The result: teams that know how to direct AI, not just use it. The difference between those two is where most AI transformation programs fail — and where the ones that succeed create durable competitive advantage.

The Foundation

25 years building products, leading design, and navigating organizational change.

2014–Present

Experience Director

Cognizant — Google, Disney, DirecTV, Delta, J&J, Optum, HCSC, IMF

2010–2014

Senior UX Lead

IMCS Group — Baker Hughes, Hunt Energy

2007–2009

Product Analyst + UX Designer

SumTotal Systems — SaaS HR platforms

2003–2007

Design Lead → Product Manager

Adayana — reduced dev cost 45% via component library

2000–2003

Foundation Years

DigitalThink, ZILS, Space2Host — first-generation web & interactive

25+

Years directing product and UX

52+

Products across 10 domains

350+

Courses completed — learning as practice

1st

GenAI Design Hackathon 2024

A product and organizational leader who has spent 18 months deeply studying how AI changes the way organizations create value — not from a distance, but by building. The combination of strategic altitude, design thinking, and hands-on execution is what separates useful insight from theoretical observation.