Had someone contact me because a browser interface was ‘down’ and it was actually a cert issue. It surprised me that in an IT context, this person didn’t have a basic understanding of SSL certs. They didn’t even know how to add a cert exception.
It got me thinking, what basic ubiquitous things am I a dumbass about outside of IT?
Ive seen lots of ‘fun facts’ compilations, but it would be better to get a wide range of subject suggestions that I can spend 30 minutes each or less on, and become a more capable human.
Like what subjects would plumbers consider basic knowledge? Chemical interactions between cleaning products and PVC pipes?
What would an accountant or a landscaper consider to be so basic its shocking people can live their lives without knowing any of it?
For most areas of expertise, its difficult to know even what the basics are to start with.
Could you give a brief overview (or detailed if you want, I’m curious!) of what you think makes a good process? More specifically, what makes a good process and what makes good documentation for said process?
Mostly it’s about best practices I think, and getting a feel for them. Try starting with something simple, like making a peanut butter and jelly sandwich. Describe how it’s done, each step. Think about where it’s efficient, where there’s extra wasted action, or time. By the time you’re done you’ll be considering if your butter knives are stored in the best spot, if you should get everything out at once, or one at a time. Do you have enough inventory? Is having extra inventory a waste? Is it worth washing knives afterwards or get extra so you can wash a batch at a time instead?
Then, go back through from the perspective of a child that has never seen your kitchen. Do the steps still make sense? How can you make it more simple, less effort? Finally, when I mentioned hand off… How do you ensure that your child laborer is going to deliver a pb&j of sufficient quality? Who determines quality? Production time?
Once you start thinking that way, everything is a process that could be considered, with inputs and outputs, quality control issues, potential waste, efficiency improvements, etc. It applies to data just as much as a sandwich for example, and office jobs are all about taking information, changing it a little and sending it on. Each step should transform in some way (capturing who does what, to what, at each step can help). Understanding the complexity instead of assuming simplicity so you can analyze it, but then distill it back down to something that is actually simple and understandable.
Anyway, hopefully that helps some in thinking about it a little differently.
For googling key words: quality management, process mapping, process analysis, lean, ?
Unfortunately there’s a lot of corporate shit, buzzwords, and SEO that have accumulated so it can by hard to find good info (like everything else now?)
Ho boy, I’ve been working through Goldratt’s greatest hits, and just the question of inventory opens a whole rat’s nest of considerations. Like what even is inventory? I mean, -hits pipe- even time is inventory, man.
Thank you, this was a really interesting read. Would love to see a tutorial series on processes by you!
This is really interesting and a good way to think about a bunch of things. I’ll try it out. I do pay some attention to processes, but not to granular detail.
This is a very rationalistic worldview though. Surely you don’t look at everything as a process?
Hah, no, definitely not a 24/7 thing. More that it can be a useful exercise.
Even better, just some handy keywords to plug into google and we can open up that box of knowledge ourselves!