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
3 months agoDawne
3 months agoMagda
3 months agoJudy
4 months agoNathan
4 months agoMartin
4 months agoNa
4 months agoThurman
4 months agoDalene
5 months agoBrock
5 months agoTarra
5 months agoShawna
5 months agoCatalina
5 months agoCraig
5 months agoOcie
9 months agoNovella
8 months agoLatricia
9 months agoLizette
9 months agoMiss
9 months agoBette
9 months agoHyman
10 months agoAvery
10 months agoWayne
8 months agoMollie
8 months agoKayleigh
9 months agoKatie
10 months agoHermila
8 months agoCiara
8 months agoParis
9 months agoDelbert
10 months agoTamar
11 months agoAnnabelle
11 months ago