Technology
& Innovation
My work sits at the intersection of enterprise technology, operating strategy, and organizational change. As Chief Technology & Innovation Officer, I set direction across RIA enterprise systems, data, workflow, governance, security, and AI—deciding what to build, integrate, standardize, govern, or leave distributed, and how those choices support the organization over time.
I stay unusually close to architecture and implementation because strategy only becomes real when systems meet users, regulation, legacy complexity, and conditions the original design did not anticipate. That proximity helps me see both what the organization can do now and what it needs to become next.
DIRECTION
Set technology direction by translating business priorities, emerging capabilities, and organizational needs into a coherent agenda.
GOVERNANCE
Establish the controls, permissions, authorities, and boundaries that allow technology to operate responsibly.
ARCHITECTURE
Define how systems, data, identity, workflows, content, and external platforms work together as an enterprise environment.
EXECUTION
Stay close enough to implementation to test assumptions, resolve edge cases, and make the architecture work in practice.
Where this work shows up in practice
These responsibilities come together across several recurring areas of enterprise technology work.
Enterprise Systems & Architecture
Designing connected operating environments rather than isolated applications. This includes defining how applications, data, documents, identities, permissions, workflows, reporting, and external platforms work together as a cohesive whole.
The objective is not simply to digitize an existing process, but to determine what the process should become once legacy constraints are removed.
Data & Information Architecture
Enterprise systems depend on shared meaning, not merely shared access to data.
I define how critical information is structured and governed across applications: resolving identities, establishing relationships between records, determining authoritative sources, preserving historical state, normalizing inconsistent information, and identifying what should become durable, reusable enterprise data.
This becomes especially important when different systems describe the same client, person, account, relationship, or business concept in different ways.
Workflow & Orchestration
Workflow is where architecture becomes operating behavior.
I design how information, responsibility, documents, approvals, exceptions, and decisions move across people and platforms. That includes the rules, dependencies, handoffs, automation, controls, and human decision points required to make a process function coherently from end to end.
The objective is not automation for its own sake, but a system in which people know what requires their attention, what does not, and what happens next..
AI Architecture, Implementation & Governance
Enterprise AI is an architecture and governance problem before it is a model problem.
I focus on where AI should operate, what information it can retrieve, what must be standardized and governed first, how identity and permissions travel with the request, and where supervision, auditability, escalation, and human judgment remain necessary.
My approach is increasingly hybrid: standardize the information that must carry durable enterprise meaning while allowing other information to remain distributed and be retrieved from its authoritative source when needed.
Access to data and understanding data are different problems.
Technology-Enabled Organizational Change
Technology creates the most value when it changes how the organization operates, not merely when it digitizes an existing process.
The harder problems usually involve legacy systems, entrenched processes, conflicting definitions, unclear ownership, competing priorities, or assumptions that no longer fit current conditions.
My role is to connect technology choices to the operating model itself, helping the organization increase capacity, adapt, and evolve as conditions change.
Governance, Security & Operational Controls
Governance is part of the architecture, not something added after the system is built.
I set the policies and controls for identity, permissions, retention, documentation, security, supervision, exceptions, and auditability to define who can do what, with which information, and under what conditions.
In a regulated environment, those boundaries significantly affect what can be responsibly built and put into operation.
From architecture to implementation
I move between a system’s architecture and the details that determine whether it actually works.
That has kept my work unusually hands-on for an executive technology role. One moment I may define an enterprise model and, the next, work through the behavior of a workflow, an integration, a permission, a data relationship, or an exception.
For me, architecture and implementation are not separate disciplines. Implementation is often where the architecture's assumptions finally become visible.
Working inside regulated environments
Nearly two decades in financial services have given me operating and regulatory context that materially shapes how I approach technology.
In a regulated environment, architecture cannot be separated from permissions, supervision, documentation, retention, security, governance, and accountability. Those requirements are not constraints added after the design; they are part of the design.
That becomes even more consequential with AI. What can technically be automated, inferred, generated, or retrieved isn't always what we can responsibly operationalize.
The architecture has to account for both capability and consequence.
Technology leadership as orchestration
Much of technology leadership happens between disciplines.
Technology leadership often means reconciling strategic objectives, user experience, risk, product capabilities, technical constraints, and system realities. Each perspective may be valid while still representing only part of the problem.
My role is often to hold those perspectives together long enough to design something coherent.
This is where the producer’s mindset that runs through my creative work shows up: understand the whole, stay close to the details, connect people and information, solve problems as conditions change, and keep moving the work toward a finished result.
Enterprise Stewardship
My role also includes maintaining coherence across the broader enterprise technology environment, including oversight of Microsoft 365, technology policy and governance, identity and access controls, security architecture, platform standards, and the introduction of new capabilities. My focus is on the direction, architecture, policies, and controls that govern day-to-day technology operations.
I also work selectively across digital brand and communications when technology is central to the solution, including web architecture and advanced development, SEO, enterprise copy, analytics and visualization, and media production. These responsibilities extend the same objective: connecting technology, information, and communication into a coherent end-to-end environment.
Selected Writing
My published work has explored leadership, organizational change, practice design, technology, and the systems that shape how people work.
What Data Should RIAs Unify When AI Can Retrieve the Rest?
PowerAdvice · October 2026
Why agentic retrieval does not eliminate the need for governed enterprise data, and how RIAs should distinguish between information that needs durable shared meaning and data that can remain federated at the source.
Read article →
The Financial Planner’s A.I.D.E.
Journal of Financial Planning · April 2016
Co-authored with Paul R. Justin
A practice-capacity framework for aligning a planner’s professional expectations with workload, roles, staffing, and infrastructure.
Read article →
Leadership on the Line
GAMA International Journal · January/February 2017
2018 Editor’s Choice Award
Leadership, adaptability, and decision-making under complex conditions.
Read article →
Editor’s Choice profile →
Mindful Management Strategies
GAMA International Journal · November/December 2017
Teaming With Veteran Advisors to Achieve More in Their Practice
A look at how managers can move from prescriptive management toward collaboration with veteran advisors, particularly around succession, practice transition, autonomy, and desired future states.
Read article →
Mostly Sunny with a Chance of Disruption
GAMA International Journal · September/October 2019
A skeptical look at “disruption” as a business buzzword and a more practical examination of digital competition, emerging technologies, data, systems, process design, and changing financial-services business models.
Read article →
Refocusing Your Attention
GAMA International Journal · November/December 2019
A practical examination of distraction, continuous partial attention, attention residue, and how leaders can regain control of high-demand work.
Read article →