Distributor cancelled an order and we need to move 30k bags of coffee [updated]

In college, I worked in a lab that used disposable pipette tips to measure/move samples around, which come in small "racks" like these https://www.coleparmer.ca/i/thermo-fisher-molecular-bioprodu...

We normally got a copy-paper box or two of these at a time, which lasted for a few months. However, one day one of my colleagues, who did not grow up speaking English, placed the order and asked for a huge number of cases, thinking "case" was a synonym for the individual plastic boxes that they came in.

It...was not, as we found out when a delivery man appeared up with a motorized pallet jack. He's a bit miffed too: "Is there an easier way to bring up the rest?" The order ended up filling an entire closet and then some. They were still working through them when I left a year later.

In retrospect, the price was obviously too high, but it was a small part of a big equipment order--and science stuff is often eye-wateringly expensive anyway.

In the tech side, I still think there’s a lot of value in reading through Booch and friends, even if you don’t go on to use UML in a formal way, and even old, deprecated approaches to modeling (think Shlaer-Mellor) can be valuable as an introduction to more modern (and generally more complicated) approaches to domain modeling.

For more academic and less practical works, look into philosophers of language and communication (Rorty, Habermas, Latour, etc) — if you don’t have a background there, try the “Very Short Introduction” series, which gives a good grounding before moving into further secondary or primary literature. What you get from these writers is a way to think about language, communications, and complex systems, so you’re building a conceptual toolkit. (Analytic philosophy, which is another, “mainstream” branch of philosophy, also has applications in the formal comp-sci route.)

Sociology and STS (Science and Technology Studies) kind of occupies a practical middle-ground between philosophy and design; I’ve often said that when we do service design, we’re really just doing folk sociology. There’s no shortage of textbooks, but I’d recommend looking into academic field guides for ethnographic studies (a fancy term for “going out and talking to people about what they do”) and ethnomethodological studies (a fancy term for “going out and talking to people about what they believe”). While the service design books will give you practical tools for conducting workshops and research programs, sociology books will give you a firm grounding on why those tools are used, and how to theorize effectively on what you uncover. I also like measurement theory, which is a branch of psychology concerned with understanding how to define measures and metrics — great tools for clearly defining data and reporting.

Finally, in addition to all this, consider digging into a corporate finance text or two; the three legs of the stool are product and service design; technical and operational architecture; and finance and sales. If you can read your company’s balance sheet and cash flow statements, you’ll be in a much better position to understand where you need to target investments, what the likely return on investment will be, and how much cash (or debt) is available to make things happen. Start building up a good knowledge base in all those areas, and you’ll have the tools necessary to know the “where, how, and why” to apply the “what” of technology to your organization’s problems.