I lead UX teams that build for the full arc — not just the welcome, but every stage through to the moment a person returns, recommends, and brings someone else with them.
I connect business objectives to that weight. The KPIs follow from closing the gap between what the business needs and what the person needs. When both are clear, the path between them is the strategy.
Before the workshop, before the feature list, I write the weight sentence — the specific weight of a specific human at a specific moment. It becomes the acceptance criterion for everything that follows.
As facilitator, I ensure everyone is aligned before any work begins — feature set, functionality, and the why. Consensus isn't optional; I'm accountable for the end result.
I gain empathy by understanding responsibilities, needs, and desires — then map those pain points to business strategy to create valuable, motivating outcomes.
Process is not a sequence of steps. It is a series of decisions made before the user arrives — and a discipline for catching the ones that drift after they do.
I begin where the user begins — not with their job title, but with what they're carrying the moment they open what we made. What is this person carrying while they try to use what we are about to build? That sentence becomes the acceptance criterion for everything that follows.
The brief in hand is rarely the real one. I run a Clarity Sprint — fifteen focused minutes against three questions: Who is the specific person? What moment are they in? What's the one thing that must be true if everything else fails?
The brief is the 100K. The 600K is what this project actually controls if the vision holds all the way through. My job is to make the 600K visible before the first sprint begins — so the team builds toward it, not just at it.
A prototype is how a vision becomes felt before it becomes built. The test is not does it work — it's does the person feel more capable holding it. The room can argue with words; it cannot argue with what it has already felt.
Drift arrives as small, reasonable decisions that compound until the product points where nobody chose. I run the EAR every week — Edge, Vision, Loop, Arc, Exit. Thirty minutes that prevent eighteen months of drift.
The handoff to engineering is where the work gets tested by gravity. I stay through implementation review, design QA, and the first weeks after launch. The ship date is a milestone. The return is the metric.

The building operator at 2am, alone with eight systems reporting, needs to know in one glance whether she can go back to sleep. The Digital Twin replaces the abstract dashboard with a spatial, living picture — natural-language questions, real-time visualization, what-if simulation. She doesn't read the building anymore. She walks through it.
View ProjectThe site operator walks in at 6am with a list in their head — AHUs to start, RTUs to schedule, lights for the floor that opens at 7. Site Manager strips the interface to the act itself: turn it on, turn it off, configure the page to match the building you actually run.
View ProjectThe executive who signed off on the $100K is going into a quarterly review where someone will ask whether it was worth it. The ROI Dashboard turns operational telemetry into a story they can carry into the room — identified, realized, lost, and projected savings, separated cleanly enough to defend each number.
View ProjectA building used to be a thing that broke, and breaking meant a call to someone. The Sentient Building reverses that — it notices its own faults, decides which it can fix, and surfaces the rest to the right person first. Owner, operator, technician — each receives only what they can act on.
View ProjectA customer with thirty sites cannot read thirty dashboards. The portfolio view answers one question across all of them: where is value being identified, lost, realized, and projected — across Energy, Asset Lifecycle, and Operations? The morning that used to be spent assembling that picture now opens on a single screen.
View ProjectAfter 27 years, John Bandringa was leaving — and a corporate goodbye would have missed him entirely. So we asked the team a different question: what is the moment with John you carry with you? The answers became something only the people who worked with him could have made. Not a product — a record of what they carried together.
View ProjectIn today's world
The differentiator between applications is no longer their features but the experience that the applications provide.
Senior UX Leader & Strategist