I have worked where strategy becomes delivery.

My work in technology began with digital learning, information architecture and the early web.

I moved from creating tools that helped individuals learn new systems to shaping enterprise platforms and services used across large organizations. Over time, I worked across information architecture, experience design, product strategy and service design, eventually leading teams working across regions and disciplines.

At Cornerstone OnDemand, I served as Director of Product Design. The role reinforced something I had seen throughout my career: product leadership is not only about deciding what to build. It requires choices about where to focus, what not to pursue and how product, design, technology and the business will work together.

The scale increased. So did the cost of allowing assumptions to remain unexamined.

I have worked in commercial, public and not-for-profit environments, each with its own language, constraints and forms of accountability.

Across them, I found capable people working inside systems that made good judgment harder than it needed to be. Strategy became separated from delivery. Evidence arrived without changing the assumptions beneath a decision. Leadership choices remained visible, while the reasoning behind them disappeared.

This is where my work sits now: helping leaders connect direction with delivery, remain open to what the organization is learning and make choices they can continue to stand behind as conditions change.

Some organizations brought me inside to lead. Others came to Kina'ole and Follow the UX Leader for help working through a difficult problem.

Through those businesses, I worked with teams from organizations including Booking, Hootsuite, OpenText, Capital One, Rogers and Ubisoft.

Design thinking was often the entry point. The underlying questions were usually broader: how to make better choices, understand the system surrounding a problem and connect strategy with what people could actually deliver.

The work ranged from leadership sessions and facilitated working groups to longer advisory engagements. The common thread was helping people examine assumptions, work across organizational boundaries and make decisions that could withstand contact with reality.

I also use service design, systems thinking and emerging AI capabilities to accelerate the beginning of difficult work by organizing what is known, making assumptions visible and giving people something concrete to examine. Speed is useful when it creates more room for human judgment, not greater confidence in an incomplete answer.

One example is the CX Fundamentals Toolkit, created by Werner and Marta Puchert. I served as an advisor during its development, contributing perspective as customer-experience principles and practical challenges were shaped into a tool teams could use together. Difficult ideas become more useful when people can handle, question and apply them.