Stables, kitchens, jobsites, help desks, government offices, classrooms, and hospital hallways. Different rooms, same instinct: watch how the work actually happens, fix what's broken, and teach the people around you to do it without me.
It started early: a toddler, at best, taking a telephone apart with a screwdriver, just to see how it worked. Playing with Legos and K'Nex. Dad teaching carpentry, basic electrical work, and general handyman skills. All of it built the foundation and, maybe even more importantly, taught how even the smallest things can be the most important.
Training horses at a stable meant learning to read a creature that can't tell you what's wrong, only show you. Patience wasn't a virtue there; it was the entire method. The same discipline showed up working in a restaurant, where timing is everything, and a team either moves together or falls apart in front of the customer. Cohesion wasn't just important; it was crucial. Construction and demolition added even more: the work is unforgiving, but learning how to build or destroy something safely, and in the right order, pays dividends in transferable knowledge.
That same attention eventually turned toward systems instead of structures: how software gets built, how a support ticket turns into a fixed problem, how a request moves through a government office instead of stalling in it, how a private company decides what to build next.
Customer support taught what training horses had already taught: watch closely, ask the right question, and don't assume the first explanation is the real one. Working across government and public-sector settings alongside private companies added something else: an ear for how differently the same problem sounds depending on who's asking and who's accountable for the answer. Technology work tied it together. The tools changed; the underlying job didn't. Notice what's actually broken, and fix it in a way that holds.
Education and healthcare are where all of it converges: environments where the stakes are real, the rules matter, and the people in the room are rarely the ones who designed the system they're working inside of. Teaching, training, and advising in those settings is the same job as training a horse or running a line: meet people where they are, and help them get one step better than where they started.
The path from there ran through software engineering into operations leadership: building the tools first, then owning how the teams and processes around those tools actually ran.
Consulting today is the natural next chapter, not a break from any of it. Every engagement draws on the same instinct built in a barn, a kitchen, a jobsite, a help desk, a classroom, and a hospital hallway: find the real problem, not just the symptom, and build something that still works after I've left the room.
WCAG 2.2 AA audits of web products, with a completed VPAT (ACR) you can hand to procurement or a government buyer. Findings come with remediation guidance your engineering team can act on, not just a pile of flagged nodes.
Move beyond the hype. Build an AI strategy grounded in people, process, and execution. When your industry or your data demand it, run the whole thing on infrastructure you control.
Find the automation with the best return-on-investment and implement it. Skip the rest.
Get audit-ready without grinding your team to a halt. Scope the effort, write the policies you'll actually follow, pick tooling that fits, and coordinate with the auditor or regulator on the other side.
Managing contractual obligations across their full lifecycle, from defining what "done" looks like in an SLA to tracking performance and obligations until the engagement closes.
Turn the data you already have into reports and dashboards that actually inform decisions, not just decorate slide decks.
Technology modernization isn't just about the technology; it requires organizational change. It must be considered from day one, and implemented with technology solutions your team will actually use.
More than a decade building, implementing, and advising on K-12 and higher-education technology, including the interoperability standards that make disparate EdTech platforms actually work together.
Whether a proposal is coming in or going out, making sure it fits your expectations and needs.
Utilizing cross-industry pattern analysis, I work with leadership teams to identify proven strategies from other fields and adapt them to yours.
Hands-on build work, either as an individual contributor or leading the team that does.
Training your employees and end users on the tools, processes, and products they actually use. Either I build the materials from scratch, or I take what you already have and turn it into something people learn from; then I deliver the sessions.
An independent read on the people and organizations you're about to commit to, before you sign. Same analytical lens whether the subject is a candidate, a contractor, or a vendor.
Coaching, advisory, a fractional seat, or just a good conversation. I read every message.
Get in touch