Kris Nolen
I build and fix real systems, step in when things get messy, and stay hands-on because that’s how problems actually get solved.
About
I’ve spent a long time working in real, operational IT environments; the kind where systems are already live, outages are costly, and decisions have consequences. I’m comfortable in critical situations, staying calm under pressure, and working methodically when things are broken and time matters.
I don’t live in theory or perfect-state designs. I work in what actually exists. That means digging into logs, tracing traffic, reading packet captures, and understanding how systems behave when they fail. I’m often brought in when complexity has piled up, ownership is unclear, or a project or environment needs to be stabilized and made understandable again.
Over the years, I’ve worked across a wide range of environments and industries; including financial services, transportation, education, manufacturing, retail, healthcare, and legal; each with different constraints, risk profiles, and tolerance for downtime. I’ve worked in environments that must be available 24/7/365 as well as those where everything can be shut down at 5, and I know how to design and operate systems appropriately for both.
I started in IT early, running a hobby BBS as a teenager on a 486 with a 2400 baud modem, and I never stopped building or tearing things apart to understand how they work. Today, I use automation and modern tooling; PowerShell, scripting, and increasingly AI; to amplify impact, reduce friction, and help teams solve real problems faster and more consistently.
How I Work
I start with reality. I look at what exists, how it’s actually being used, and where it breaks under pressure; not how it was supposed to work.
I stay calm when things are on fire. During outages or critical issues, I focus on isolating variables, restoring service, and communicating clearly; panic and noise slow everything down. I’m often the person called when previous attempts haven’t worked.
I dig until I understand. Logs, metrics, packet captures, and configs tell the truth. I’m comfortable going as deep as necessary to get real answers.
I design for the environment, not ideals. Always-on systems, business-hours systems, regulated environments, and scrappy shops all require different tradeoffs; I design accordingly.
I use automation and AI to amplify impact. PowerShell, scripting, and modern tooling reduce friction, eliminate repeat work, and let teams focus on problems that actually need human judgment.
I teach where and when it makes sense. I explain what I’m doing and why, so people can learn, grow, and handle the next problem with more confidence.
I leave things better than I found them. That means clearer ownership, better documentation, fewer sharp edges, and systems people can support after I step away.
Current Focus
Right now, my focus is on improving how technical work gets delivered; from onboarding and project execution to escalation paths and long-term support. I spend a lot of time reducing friction, increasing clarity, and making outcomes more predictable for both teams and the people who rely on the systems.
I’m also investing in automation and tooling that scales good decisions. That includes scripting, standardization, and thoughtful use of AI to handle repeatable work, surface insight faster, and free people up to focus on the problems that actually need experience and judgment. I’m particularly interested in where automation and AI can meaningfully improve reliability and decision-making without replacing human responsibility.