3 ms·
If it isn't important whether the numbers are real or fake, why show them? To intimidate people with a baseless appearance of mathematical rigor? If so, I'd s
by kragen 5y ago
If it isn't important whether the numbers are real or fake, why show them? To intimidate people with a baseless appearance of mathematical rigor? If so, I'd say the people who point out that they're fake are doing a service to the decisionmakers in the meeting, though it's unsurprising that the presenters don't appreciate it.
- curiousllama 5y agoYou've never shipped with known bugs? If someone asked you "If it isn't important whether the software works or not, why ship it?", what would your reaction be? Note: > Directional correctness facilitates the same conversation
- Jensson 5y agoA math error in a spreadsheet can change the entire conclusion to be drawn from the data, it is very different from known bugs users can work around.
- conductr 5y agoBut both can only be ascertained in hindsight and knowledge of the issue. Software issues can, and do, also cause a lot of issues with the data that spreadsheets are analyzing so I don’t necessarily see it as different. Also a lot of spreadsheet info is just info. It’s not necessarily being used as a crucial decision criteria. There’s such a wide spectrum of situations it’s hard to be too rigid with this. My software analogy was just pandering to this audience. Probably not a perfect analogy.
- kragen 5y agoI would say that most software doesn't have to be correct to be useful. There are exceptions, like anything to do with cryptography. You might say that the same can be true of calculations; after all, calculations about the contingent universe (as opposed to, say, number theory) are always based on data incorporating some uncertainty. But there are two key differences: ① I don't put up a slide showing all the intermediate values of the variables in my program in order to make an argument for something. Instead, I try to show my chain of reasoning in enough detail to be convincing and to expose any relevant potentially incorrect assumptions or reasoning steps I've made so that others can find my errors, without including trivial or irrelevant details. Including trivial and irrelevant details makes it harder, not easier, to find relevant incorrect assumptions or reasoning steps. That's why I question the motivation of people who include those in their slides: it sounds like they're attempting to make their argument so complex that there are no obvious errors, rather than so simple that there are obviously no errors. ② A 10% uncertainty in an input datum can be traced through the calculation from beginning to end and will often result in a 10% or 21% uncertainty in the result, or even less. (And where that's not the case the sensitivity should be called out.) A calculation that's simply incorrect—for example, treating millions as thousands, or forgetting to divide by the relevant denominator—commonly produces results that are off by multiple orders of magnitude.
- ALittleLight 5y agoOne 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.
- treeman79 5y agoFor a couple of years I would always include an obvious UI fix in my presentations with senior management. I always got my plans approved the first time. Management was always so happy to contribute something that they didn’t question anything I actually wanted. They never caught on. This was for CEO of a fortune 100
- nayuki 5y agoRelated: https://blog.codinghorror.com/new-programming-jargon/#5 https://blog.codinghorror.com/new-programming-jargon/#5 , https://softwareengineering.stackexchange.com/questions/168146/what-is-the-term-for-a-decoy-feature-or-intentional-bug https://softwareengineering.stackexchange.com/questions/1681...
- conductr 5y agoYeah on the flip side of my comment I’ve known some finance guys that bury in mistakes just to see if anyone catches them. Obviously not on super official filings. But internal management stuff. One boss of mine early on in my career gave out prizes. It was their way of making interactive
- conductr 5y agoI have to answer in the context I’m familiar with, finance. People start aimlessly hypothesizing if you don’t show them the nonissues. Also, management is conditioned to look at certain key things in combination because they are in fact interconnected. So for example, is the core issue is profit is lower than budgeted. I will show them sales are on plan. I will show them non labor is on plan. Then I will say now labor is the problem. Overtime is immaterial , but our hours/widget KPI seem way high. We call the plant manager and find out an automation process is down. Because it’s so costly, we fly in a support tech that night to fix it. Seems simple enough but in an enterprise this could involve a dozen people and move slowly unless I craft the story of how much this issue is costing us. And since I’m not in the plant, I didn’t even know the problem that I was pointing out to begin with. I probably don’t even know who the plant manager or his boss is. So it’s not like I can just pick up the phone and figure out the whole story (but generally would try to).
- kragen 5y agoThank you for explaining! In that case it seems like it would be worthwhile to sort out the mistakes in the calculation in order to figure out which of the seemingly implausible figures are in fact correct and which are just calculation errors?
- conductr 5y agoThere’s a lot of conditions that come into play. If I’m actively in the meeting and the number is obviously wrong and I have no analyst support (usually at the point). I’ll just table it and apologize and send a follow up to the attendees after the meeting and summarize whether I feel like the correct calculation impacts our decisions/discussion. These things do have a reputational cost so it’s my job to see that myself and my team and putting out error free stuff and having it proofread and such is usually the best we can do. There are many times when the math is in fact correct and the numbers are just implausible. That’s usually the meat of the meeting and something to dig deeper on. Hopefully we noticed it, double checked it, and it’s one of my talking points to address in the meeting. Either I want to point it out and explain why or point it out and ask why depending on who I’m talking to.