About Doug
I took a nontraditional path into technology, and I’m grateful for that. Before I worked with cloud platforms, enterprise systems, and software architecture, I worked in restaurants. That taught me urgency, service, teamwork, and the cost of systems that do not work. Those lessons still shape how I lead technology work today.
Over the last two decades, I’ve moved from hospitality into enterprise IT, SaaS platforms, cloud architecture, cybersecurity, identity, and higher education technology. Along the way, I’ve learned that tools change quickly, but judgment, communication, and trust matter most.
This site is a place to share what I’ve learned, what I’m still figuring out, and how I try to make technology useful for real people and real organizations.
Where I’ve spent my time
A few of the roles and environments that have shaped how I work.
Enterprise IT and infrastructure
Keeping core systems running, supporting teams, and understanding how technology decisions ripple through an organization.
SaaS platforms and product work
Helping build and support software used by thousands of people, and learning how to balance features, reliability, and support.
Cloud architecture and modernization
Moving systems to the cloud, simplifying where possible, and respecting the constraints of real budgets and teams.
Cybersecurity and identity
Working on access, authentication, and the quiet plumbing that keeps organizations safe and usable.
Higher education and edtech
Supporting students, faculty, and staff with systems that have to work for very different kinds of users.
Consulting and advisory work
Helping leaders and teams make better technology decisions, especially when the path is not obvious.
Hospitality and restaurant management
Learning operations, service, and what happens when systems fail in the middle of a rush.
Where I tend to be useful
I am usually most helpful when the problem is not just technical. The system may be aging, the architecture may be unclear, the team may be overloaded, the vendor story may not quite add up, or the business may know where it wants to go but not how to get there.
That is the work I like: bringing structure, judgment, and forward motion to complicated technology situations.
How I try to work
I care about useful systems, honest communication, and calm leadership. I try to make tradeoffs visible, not hide them. I’d rather say ‘I don’t know yet’ than pretend to have an answer.
Good technology work is not just about picking tools. It is about understanding constraints, listening carefully, and earning trust over time. The best outcomes usually come from steady, thoughtful progress, not big dramatic moments.
These days, I spend much of my time through Formula1-IT, helping founders, small and mid-sized organizations, and education-focused teams make better technology decisions. If you’re working through a complex technology problem and want a clear, grounded perspective, I’m always open to a conversation.