This is a tricky one. I'm not 100% sure how the different ratios are calculated, so I'll need to think it through step-by-step. My best guess is that the cost-to-income ratio would be the most directly impacted, but the other two could also be affected. I'll have to make an educated guess on this one.
A 100% availability target? Good luck with that! I'd like to see the engineer who can code a service that never, ever goes down. Maybe they can also make a car that never needs gas and a toaster that never burns the bread.
A 100% availability target? Good luck with that! I'd like to see the engineer who can code a service that never, ever goes down. Maybe they can also make a car that never needs gas and a toaster that never burns the bread.
I like C. Leaving room for improvement is crucial. If you hit 100% right away, where do you go from there? You need some wiggle room to keep getting better.
Option B makes sense to me. If you set the bar so high, you're almost guaranteed to fail. That's not a great way to run a service. Realistic targets are key.
A 100% availability target is simply not realistic. As the question states, the complexity and scale of modern services make that an unachievable goal. I'll go with A on this one.
Reita
4 months agoDawne
5 months agoMagda
5 months agoJudy
5 months agoNathan
5 months agoMartin
6 months agoNa
6 months agoThurman
6 months agoDalene
6 months agoBrock
6 months agoTarra
6 months agoShawna
6 months agoCatalina
6 months agoCraig
6 months agoOcie
11 months agoNovella
10 months agoLatricia
10 months agoLizette
10 months agoMiss
10 months agoBette
11 months agoHyman
11 months agoAvery
11 months agoWayne
10 months agoMollie
10 months agoKayleigh
10 months agoKatie
11 months agoHermila
10 months agoCiara
10 months agoParis
10 months agoDelbert
1 year agoTamar
1 year agoAnnabelle
1 year ago