My background is project management. Since 2023, my focus has shifted toward building practical systems that modernize how work runs. I work as a Project Systems Architect and Digital Transformation Consultant, and that work spans both what I do professionally at UnityPoint Health and what I test in my homelab outside of it. This site documents both.
I live in Des Moines, Iowa with my wife and our two kids. I do not separate strategy from execution. I do both.
Soccer is a core part of who I am. I played through college, and for the past six years I have coached at my high school alma mater, Dowling Catholic, as an assistant on the boys varsity staff alongside close friends and former teammates.
What I actually do
I focus on the point where projects usually stall: unclear ownership, manual handoffs, disconnected tools, and workflows that only move when someone chases status.
I design systems that make work visible and executable. That includes process architecture, automation boundaries, and operating models teams can sustain after rollout.
Work context: enterprise healthcare delivery
Inside UnityPoint Health, I work in high-stakes, compliance-sensitive environments where clarity and reliability matter more than hype.
My core stack is Microsoft 365 and Power Platform: SharePoint, Teams, Microsoft Lists, Power Automate, Power BI, Copilot, and Copilot Studio. I use these tools to move teams from meeting-heavy coordination to system-driven execution.
My focus is practical outcome: clearer accountability, fewer manual follow-ups, and workflows that hold up in real operations.
Homelab context: experimentation and validation
Outside work, I run a homelab to evaluate AI and automation tooling under real constraints.
That stack includes Ollama, Open WebUI, n8n, Vaultwarden, Cloudflare Tunnel, and Hermes Agent on makerpi. I also test Claude, Gemini, and local-model workflows to evaluate tradeoffs before bringing patterns into enterprise planning discussions.
This is experimentation, not production healthcare deployment. I keep that boundary explicit.
How I think about system design
- Build the simplest architecture that survives real usage.
- Remove handoffs before adding automation.
- Make ownership obvious inside the workflow.
- Treat AI as part of process design, not a bolt-on feature.
- Document decisions so systems outlast individual contributors.
Credentials and development
- PMP, Project Management Professional (PMI)
- Master of Organizational Leadership
- Microsoft Power Platform Fundamentals (PL-900)
- Microsoft Applied Skills in Power Apps and Power Automate
- Building AI capability in project delivery since 2023 through PMI and other industry coursework
- Former Director of Mentoring, PMI Central Iowa Chapter
- Full credential detail: Credly profile and LinkedIn certifications
Why this site exists
Most AI transformation content stays at the idea level. I use this site to document implementation-level work.
I publish what I build, what breaks, and what changed after real testing. If you are trying to modernize delivery without adding chaos, this site is for you.
Let’s connect
If you are solving workflow friction, adoption breakdowns, or cross-team execution gaps, I am always open to a practical conversation.