This summer was a very interesting chapter in my professional career and personal development. I was consuming a lot of materials realted to busienss development, managerial skill, mostly in operations and running systems and AI of course, as this is one of my main interests right now. And I came to realize that the time and energy I am investing in trying to build this community could be spend better elsewhere with more impactful results. With the end of the month, I am considering closing this page. Using a service like Skool has a lot of benefits, one of which is an easy cancellation policy and subscription management. So the logistics will sort themselves out quite easily. The part that won't be so easy is the transition to a new venture. I am not ready to announce it yet, as I am still considering some options. But I am glad I gave this a proper go. Almost 2 years, close to 150 posts, and quite a few workshops. I am happy I was able to grow with it and see how people respond to this kind of content and how I can provide value via it. I guess the main lesson I learned from it is that it is necessesity that drives urgency, which then in terms drives engagement. Managerial or leadership skills are only applied when a true need arises; I guess I needed this community to fully realize it, for which I am grateful to you all. I will keep this page open till the end of the month and post a few thoughts to leave you all with something to ponder; I guess this was always the purpose of those posts. I hope to hear from all of you soon.

My company had an All-Hands meeting today, and the leadership team had an interesting take on productivity. In 2025, it was all about AI Adoption - the badge of honour was "we are using AI", in early 2026, the badge of honour was "I use the most tokens", and today, the new badge is "I can prove I can do the work of two employees from 2025". My team grew by 3x from early 2025, but we only added one more PM. In the workshop, I will showcase how I use Claude to automate a lot of simple tasks in a repeatable way, but I do want to drive the point home -> AI is an enabler, and you need to know how to build systems. Today I connected my Hermes Agent to Buffer, so I can post on LinkedIn in a much more seamless and straightforward way. I have zero excuse not to do it. It is a simple system but one that works. And it is the same with everything else. What system are you going to build next?

I am planning to organize two events: 1. In-person meeting just for fun and to help facilitate people meeting together - That might be right at the end of July. 2. Workshop on deploying AI Agents for managers. A few of you were interested in my setup and I would like to share it with you. Summer is a hard time to run this community, as when the weather is nice, and it is vacation time, few of us think about improving out manageril skills and grow as leaders. But I think that is what separate us from others, we grow continuesly.

Came in this morning to an outage that started over the weekend. Most of it could have been avoided if people had read the memo that was sent out. This is not the first time this has happened and I doubt it will be the last. So I'm genuinely asking - how do you get people to actually read and act on important communications before something goes wrong?

We're moving to a dedicated on-call rotation for support. Two engineers are implementing the new process and it's going well. Before this, I had a dev team that also handled support and I used my own judgment to assign work based on who was best suited for what. Now the rotation decides. I'm fine with delegating. I think it's the right move. But I'm still accountable for release management and product delivery -> the work is no longer mine but the responsibility still is. How do you handle it when you've let go of the work but you're still on the hook for the outcome?