What Objective and Key Results (OKRs) (or KPIs/Metrics) have you found are effective at communicating the impact and value of Architecture Function to the enterprise?
Sort by:
For further context I've spent the last few years rebuilding a business-outcome focused architecture team for our enterprise, which is now well respected and valued by our organisation. Our business is now moving toward a model in which all teams are effectively micro-businesses with their own OKRs that they work to achieve.
As such I'm now trying to define a set of pragmatic and useful OKRs that speak to the impact / value of our team for the enterprise and which we can track and report on effectively. In previous years we have adopted business OKRs (as a way of shared accountabilty) but have found that in these instances factors way outside our control / influence often lead to these OKRs not being achieved. As such my head is going to whether we need to define a set of 2nd order OKRs that correlate positively with business OKRs, but are more within our control to deliver upon (if that makes sense).
In any regard it would be great to understand how others have approached this problem, what OKRs have you adopted and found to be really useful, and any examples or guidance on these that we could potentially use to accelerate our work.
Thank you!
Recently it is ‘Near Fails.’ We are 12 month into a focus on continuous service improvements and transparency with PIRs and AAR helping to prioritize investments.
We have accumulated 20+ AARs and I noticed, this month, the last two are AARs for outages that never resulted in customers disruption. The was issues, but early detection, previous configurations, and anticipatory work made sure the customer did not experience it. However, the team wanted to highlight the value so they used the same AAR process they have been maturing to document previous improvements did result in reduced risks and detected possible higher value that could be reached with new improvements.
A key goal was frictionless customer experience. A mart of this is decreased MTTR and disruptions as computed by total impacted user X hours of disruption.