Understood, but still if XYZ is down at 9AM and you don't need to go there untill 11AM, you're not likely going to check. So then, you go about doing PQR task all morning, to then find out its still F@cked at 11AM. So, the cost is not the 30 seconds to figure it out, but the whole AM you wasted.
Or alternatively, all the time you pre-emtively are checking all over the place at T-1 for using it at T. Depending upon the resolution of this, that can be a PITA and a waste of time. Far more than you skipping over 1/30 of a page on the internet.
Alternatively, there may be some better way to do it. There could be a list/screen for relevance to the community or a seperate page or whatever. But one needs to address or dimensionalize the tension between information flow and efficiency a bit more than your first formulation.
Comments
Understood, but still if XYZ is down at 9AM and you don't need to go there untill 11AM, you're not likely going to check. So then, you go about doing PQR task all morning, to then find out its still F@cked at 11AM. So, the cost is not the 30 seconds to figure it out, but the whole AM you wasted.
Or alternatively, all the time you pre-emtively are checking all over the place at T-1 for using it at T. Depending upon the resolution of this, that can be a PITA and a waste of time. Far more than you skipping over 1/30 of a page on the internet.
Alternatively, there may be some better way to do it. There could be a list/screen for relevance to the community or a seperate page or whatever. But one needs to address or dimensionalize the tension between information flow and efficiency a bit more than your first formulation.