Great article Alex, and I'm really looking forward to the next ones in the series.
I'm a big fan of SLOs as they really help de-politicise decisions around technical investments by setting clear expectations up front.
One mistake that I've seen sometimes with SLO is that we take a too narrow definition of what they should cover, focusing mostly on infrastructural requirements and expectations.
I've seen SLOs used very effectively to measure expectations higher up in the stack, such as commitments on data freshness / latency, data quality, etc.
One small final comment: OKRs were not invented at Google but at Intel. Google though is the company that contributed the most to make them popular across the tech industry.
Great article Alex, and I'm really looking forward to the next ones in the series.
I'm a big fan of SLOs as they really help de-politicise decisions around technical investments by setting clear expectations up front.
One mistake that I've seen sometimes with SLO is that we take a too narrow definition of what they should cover, focusing mostly on infrastructural requirements and expectations.
I've seen SLOs used very effectively to measure expectations higher up in the stack, such as commitments on data freshness / latency, data quality, etc.
One small final comment: OKRs were not invented at Google but at Intel. Google though is the company that contributed the most to make them popular across the tech industry.