Discussion about this post

User's avatar
Benta Kamau's avatar

Your piece nails it the "automation filter" isn’t about potential or promise, it’s about operational integrity when reality pushes back.

In my work advising on AI and security, and when teaching, I see the same pattern, flashy prototypes collapse under real-world loads because no one tested for resilience or real governance guardrails. It’s far easier to promise scale than to actually build capacity that can hold.

Your focus on asking "what breaks first" is a question I try to embed into every system conversation from data flows to leadership alignment. It cuts through the illusions and forces us to confront what actually matters when pressure hits.

Thanks for writing this with such clarity and honesty. It feels like a conversation worth expanding, especially as more teams race to automate without truly understanding the load they're inviting in.

Expand full comment
Subramani Aatreya's avatar

"Just because you found a cool tool doesn't mean you need to use it. Technical fascination is not business strategy." --Seems like you wrote this just for me. The more "Cool tools" I discover the more is the temptation to try it out. The only thing that is stopping me is the reality that I'm not making money to invest back into deploying tools or automation at this stage. Thanks for this enlightening post.

Expand full comment
3 more comments...

No posts