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

Enterprise systems have a lot of things that need to happen. If they all happen at the same time, you’ll either overload your constrained resources or overload the budget attached to your elastic resources. Plus, some of these things are supposed to occur at a specific time, and others should happen around a specific time!
https://hackernoon.com/8-key-takeaways-from-observes-2023-state-of-security-observability-report

A product finds a thing, a situation, a problem. The queue is full! There’s a lot of high severity vulnerabilities! The message handler stopped handling messages! Now the product developers have a choice to make: should they do something, or tell someone? Unfortunately not everyone wants the same decision at this point. One type of
![Mephistopheles: [Aside] Enough of all this academic chatter, Back again to devilry!](https://monkeynoodle.org/wp-content/uploads/2023/12/mephistopheles-enough-with-academic-chatter-back-to-devilry.png?w=1000)
Process is what people do, not what they say. In other words, what we say is aspirational, what we do is factual. If you describe what the people are doing now, you’ll be very successful in establishing a process for new hires to follow. But what if some teams don’t follow the same process, and

Tasks to be done with a product can be thought of as points on a circular graph. That graph is a series of concentric bands, where each band is constituted of the people who can (have the ability and the permission to) do the task for the product. At the core of the graph, we