Why we're writing here
I've spent thirteen years helping operations teams get real work out of their software. First Microsoft 365, now AI. Along the way I've written six books for Wiley, sat through more failed pilots than I can count, and started building AI products of my own.
This section is where the longer-form thinking goes. Three things, mostly:
What actually works in AI adoption. Not the demo, but the Tuesday-afternoon reality: who owns the change, what the team does differently, why most pilots quietly die.
Where Microsoft 365 ends and custom AI begins. Copilot solves real problems. It also gets credit for problems it can't touch. We'll draw that line honestly, because we've worked both sides of it.
Build notes. We ship products with a small, fast stack, and we'll write about what breaks, what surprises us, and what we'd do differently. No polish, just the notebook.
No schedule promises here beyond this one: nothing gets published unless we'd want to read it twice.
If something lands or you're wrestling with a version of these problems in your own operation, reach out through the main site. We read everything.