Companies keep talking about AI as a way to make people more productive. But after years of building enterprise systems and automation, I think we’re asking the wrong question. Good automation should remove unnecessary work, not give organizations an excuse to pile more onto people. A woman studies a digital workflow diagram showing a simple successful automation on one side and a tangled network of errors, loops, and broken processes on the other. Read the full article on M

A trip to Spain for a total solar eclipse turned into a front-row seat to what happens when one failure cascades through a complicated system. Weather started the problem. Everything that happened afterward was about technology, automation, and customer experience. One of my photos from the total solar eclipse of 2026 Read the full article on Medium → https://medium.com/@nicole.builds.tech/five-hours-and-58-minutes-8caa2bdc07d0 Categories: Customer Experience, Enterprise S

There’s a human being behind every optimized résumé, application and rejection email. (Every day kinda feels like Groundhog Day) I wrote about job searching, layoffs, resilience, and what gets lost when hiring becomes another system designed for scale. The groundhog statue in Woodstock, Illinois, depicts the town’s famous groundhog mascot, Woodstock Willie Read the full article on Medium → https://medium.com/@nicole.builds.tech/i-need-a-job-e902a0fcc354 Categories: Future

For a while, my website was trying to be too many things at once. Part portfolio. Part resume. Part job-search landing page. Part consulting site. And eventually, it stopped feeling like me. So I decided to rebuild it around a much simpler idea: Nicole Builds Tech is a consultancy. The work I love most sits at the intersection of systems, process, product, automation, and customer experience. I like complicated problems. I like figuring out why something is harder than it sho

If you had told me years ago that I would build a career around product, systems, automation, technology, and making complicated things work better, I probably would have laughed. Mostly because I did not consider myself a “tech person.” I wasn't writing code in my basement as a teenager. I didn't study computer science. I didn't have a five-year plan that involved enterprise platforms, automation, product strategy, or any of the other phrases that would eventually make their