ai architecture artificial-intelligence blog blogging Book Review business career Compliance Content Corporate Life Customer Support cybersecurity data data-science DevOps education entropy fitness garmin leadership Licensing life marketing microservices Monitoring music Observability Operations Partnership philosophy Product Management Products saas Sales Security software-development technology User Experience wordpress writing

Development teams have a fondness for trying new models… for better or for worse. I’m not a fan of the current excitement around the squad model. What is it Spotify is the purest example, but the model owes a deal to Stanley McChrystal’s Team of Teams, as well as a bit of LeSS. The basic
Ever have to convert from an email system that encourages keeping everything to one with limitations? Well, here’s a way to encourage Inbox Zero. I looked at a few different scripts to start from, but this one was the most helpful. Note that this only works with “old” Outlook, new Outlook has no AppleScript support

Thesis: Organizations will continue to squeeze their highly paid people into the worst possible computing environments in order to block any accidental efficiency that might evolve in their organizations. Evidence to support that thesis: Of course the thesis is silly, no one really means to starve their organization. It just happens by accident, through shift

This post is an expansion of the concept in Valuable Jerks. Also, Nadyne Richmond. Say your team has a project that needs execution. Launching a new product? Trying to land a customer? Trying a new process improvement? If it’s at all interesting, then it’s not obvious what to do and that means leadership is trying

Question: how should your team ensure that other teams know everything you’re doing so the organization is more efficient? Answer: Use all of these tools.