3 ms·
One reason I think these meetings are sometimes so boring is because there is a sense that we are looking at numbers that don't matter. That sense is reinforce
by ALittleLight 5y ago
One reason I think these meetings are sometimes so boring is because there is a sense that we are looking at numbers that don't matter. That sense is reinforced if you discover that the values of the numbers we are seeing literally don't matter.
I also think there is a difference between software and spreadsheets. At least, in the role I was in, software let us do things and spreadsheets let us reason about the business.
If there was a bug in software, say, 5% of requests to save a configuration failed, and that failure triggered an automatic retry, and the result of this bug was elevated configuration save latency at the 95+ percentile, we might decide to ship that bug (depending on other factors). On discovering the bug we would try to understand its impact and then we would reason about the impact on the software's goals. For example, we might say that people rarely change configurations, and an additional 100ms of latency for 5% of customers is something we can live with until such time as we solve the underlying cause.
What we would not do, in any software org that I've been apart of, is say "Hey, we notice some of our operations are failing sometimes, anyway - let's ship it!" To me, that seems analogous to what you are saying. You know there are errors in the spreadsheets but you ignore them on the assumption they are inconsequential, reasoning that if they were consequential you or your team would have noticed them.
There are ways for bugs to exist in software that don't block what the customer is trying to do. Maybe the bug makes it harder to accomplish a workflow, or makes it take longer, or looks silly, or something like that - and those are bugs it may be okay to ship with (depending on context).
If values are wrong in a spreadsheet, then the only way I could think that doesn't matter is if the values are unimportant. That is, either the values are important and it matters if they are wrong, or it doesn't matter if the values are wrong because they are unimportant. If the values are important, let's correct them. If they are unimportant, let's not discuss them.
- conductr 5y agoI’m with you until the last paragraph. I think I get what you’re saying but it just wouldn’t work in practice, in my experience. If I were the sole consumer of the spreadsheet, maybe. But, alas, other people have differing opinions and we have to play nice. Specifically; Important and Unimportant are subjective. Agenda for a meeting is usually not set in stone. “Business review” is fairly ambiguous. Change over time? Do you want to know something is trending poorly early or late? Keep an eye on it. Audience likes to see things a certain way, you comply. Even if some of it is repetitive or unimportant. So on.
- kragen 5y agoI see. I was imagining a much more preplanned kind of thing, with screenshots on slides. In that case it makes a lot more sense.