About Me
Enterprise architect, systems designer, and mentor with 30+ years solving real-world technical challenges.
Veteran, USN
Cryptologic Technician Technical, Second Class (Naval Aircrewman):
Duty Stations:
What You Get Working With Me
- ✓Clear guidance grounded in 30+ years of real-world experience.
- ✓Frameworks you can apply immediately to your own challenges.
- ✓Honest feedback on your ideas, decisions, and approach.
- ✓A sounding board who understands enterprise complexity.
About Me
I didn't discover AI because it was trending.
I recognized it because I'd been solving its underlying problems for decades.
My professional foundation was forged in U.S. Navy intelligence as a Cryptologic Technician Technical (aircrew), where the work wasn't about tools — it was about signals, ambiguity, trust, and consequence. You learn quickly that information is never clean, systems are never complete, and decisions still have to be made. That mindset — systems under pressure, imperfect data, real outcomes — is the throughline of my career.
When I left the military in the early 2000s, I stepped directly into the formative years of the modern internet. Before "platforms" stabilized, I was building and managing online presence for artists and creators: moderating early YouTube communities, shaping MySpace ecosystems, and designing what we'd now call social media presence management. This was before algorithms were named, before moderation tooling existed, and before "creator" was a job title.
What we were really doing was human-AI adjacency before AI:
signal vs noise, trust at scale, behavior shaping, identity persistence, reputation systems, and content survivability. Those same problems sit at the core of modern AI systems today — just with more compute and higher stakes.
Over the years, I transitioned that perspective into enterprise architecture, working across financial services and other regulated environments where explainability, governance, and durability matter as much as innovation. I've spent my career designing systems that other people must rely on — and inherit — long after the initial build is done.
My approach to AI is not novelty-driven. It's architecture-first.
I focus on:
- Where AI belongs in a system — and where it absolutely does not
- How memory, retrieval, and context actually work over time
- How to design AI that augments human judgment instead of obscuring it
- How to make AI systems observable, governable, and survivable
Lately, my work centers on applied AI systems: long-term memory, retrieval architectures, agent orchestration, and human-facing AI designed to preserve knowledge rather than accelerate its decay. I'm particularly interested in AI as a steward of context — systems that can remember why decisions were made, not just what decisions were made.
In many ways, this is a return to first principles. The same concerns that shaped my early work — signal integrity, system fragility, human trust — are now front and center again, just wearing the label "AI."
I don't see artificial intelligence as a replacement for human thinking. I see it as infrastructure — powerful, dangerous if misunderstood, and transformative when designed with restraint.
That perspective doesn't come from demos.
It comes from time, failure, and having watched entire generations of technology rise, harden, and disappear.
Why Trust Me With AI
I didn't arrive at AI by accident.
I was trained in intelligence work, where signal is rare, noise is constant, and decisions still have consequences. That background shaped how I think about systems long before machine learning entered the conversation.
I helped invent the problems AI is now trying to solve.
In the early 2000s, I was moderating online communities, managing digital identity, and shaping creator presence at scale — before algorithms, before moderation tooling, before governance frameworks. We were dealing with trust, behavior, memory, and reputation in real time, without a safety net.
I design systems other people must inherit.
As a Principal Enterprise Architect, I build for regulated, high-stakes environments where explainability, auditability, and longevity matter. My work isn't judged by demos — it's judged by what still works years later.
I treat AI as infrastructure, not magic.
I focus on where AI belongs, where it doesn't, and how to design it so humans can understand, supervise, and correct it. Memory, retrieval, context, and governance aren't features — they're foundations.
I build for the long game.
My current work centers on AI systems that preserve context, institutional knowledge, and intent — not just outputs. Systems designed to remember why things were done, not just what was done.
Trust in AI isn't claimed.
It's architected.
Experience
Principal Enterprise Architect
I lead architecture and delivery for multi-year large-scale integration and digital transformation projects across regulated industries.
Consulting Organization History:
- Infosys (Current)
- Incapsulate/Accenture
- Gerent
- Skuid
- Traction on Demand
- Xede
- Fortimize
- Silverline
- EMS Consulting
Industry Involvement:
- 5x Dreamforce Speaker
- Higher Education Summit Speaker
- 8x Dreamin' Event Speaker
- Orlando Salesforce Developers Group Founder
- Tampa Salesforce Developers Group Founder
- Founding Slack Platform Community Leader for Central Florida
- Florida Dreamin' Founder
- Trailhead for Students Educator
- Creator of IamJarvis.me
- Creator of Solum Legacy
- Vetforce Mentor
- Merivis Mentor
- Veterati Mentor
- PepUpTech Speaker
- and more
My Mission Statement
I believe technology should earn trust, not demand it.
I believe the most important systems are built for uncertainty — for incomplete information, human imperfection, and moments when the pressure is real and the margin for error is thin.
I believe clarity is a moral obligation in complex systems, and that obscurity — whether technical or organizational — is a form of failure.
I believe AI is not a replacement for human judgment, but an amplifier of it — and that its greatest value comes from preserving context, memory, and intent rather than chasing novelty or speed.
I believe experience matters — not as ego, but as pattern recognition earned through failure, adaptation, and time.
I believe the work worth doing is the work that still holds when trends fade, platforms collapse, and the original builders are no longer in the room.
That's why I build systems designed to endure: explainable, governable, and resilient — built for people who must rely on them when conditions are far from ideal.
That's how I approach architecture, AI, and leadership: with restraint, accountability, and respect for the humans inside the system.
That's what "Built for the Storm" means to me — not surviving chaos, but designing so chaos doesn't win.
My Principles
These guide every project, conversation, and mentorship.
Build for Change
Systems must accommodate evolution. Design flexibility into architecture from the start.
Reduce Complexity
Complexity is the enemy of maintainability. Always seek the simplest solution that meets requirements.
Prefer Measurable Outcomes
Data-driven decisions beat opinions. Measure impact, iterate, improve.
Document Decisions
Decisions fade from memory. Record the why, not just the what.
Align Stakeholders Early
Misalignment kills projects. Get clarity on goals, constraints, and tradeoffs upfront.
Ship Incrementally
Small, frequent releases reduce risk and feedback loops. Perfect is the enemy of done.
Let's Connect
Interested in mentorship, architecture consulting, or just a conversation? Reach out.
Get in Touch