10 ms·
Mise-en-place for knowledge workers
- jamestimmins 5y agoInteresting comparison. Heads up for the author that this skips #6, and goes from 5 to 7.
- mberning 5y agoThe author would be surprised how variable and not at all standardized tasks such as welding a seam or putting in an IV are. Sometimes requirements and or regulations (organizational or governmental) create dramatically different practices.
- clipradiowallet 5y ago> standardized tasks such as welding a seam I came to comment on this as well... there is an entire industrial workforce of CWIs(certified welding inspectors), who exist because welding a seam is not as easy as youtube would lead people to believe. It's easy to make it look correct, but it's the attributes of the weld you cannot see that make it safe/unsafe. Doing it correctly is not something you can learn from a book or listening to someone talk about...it's something you learn by doing it over, and over, and over, until it "feels" correct. The author may as well have included "performing a quadruple heart bypass" in their list of well-understood concepts. A knowledge worker learns from repetition the "right way" to do things. Example rules like "document your work in a clear and concise manner" read a lot like "weld the seam from a consistent angle and with consistent fill material". Multiple people will follow those instructions, and you will end up with very different outcomes among the individuals doing the work. The sign of a well-seasoned craftsperson is that it "feels" right, and that only comes from long-term repetition.
- AlexCoventry 5y agoIf it looks correct, how do the CWIs identify unacceptable welds?
- krallja 5y agohttps://www.cruxweld.com/blog/quality-weld-inspection/ https://www.cruxweld.com/blog/quality-weld-inspection/ TLDR: x-rays, ultrasonic testing, and liquid penetration tests
- aksss 5y agoNot a welder, but I'm aware of inspection procedures that use gauges to determine compliance with expected "shape" and consistency thereof. Also, x-ray imaging of welds and ultrasonic inspection of welds is a thing. You said "looks correct" and visual inspection is a thing but there are a lot of facets to that visual inspection that require some experience and tooling (e.g. magnifying glass, lighting, etc).
- blakesterz 5y agoSometimes I miss restaurant work. I sit in front of a computer all day in a quiet room, it's so completely different to be on a line at a busy restaurant. It's loud and dangerous and hot and chaotic. In many ways it's the opposite of being a sysadmin. I'm not sure my body could take that kind of work now, but I do think about trying it again from time to time. I do like the concept of having Mise for us "knowledge workers" too.
- rcoveson 5y ago> loud and dangerous and hot and chaotic I was a sysadmin for an on-site HPC cluster and this sounds familiar. Compared to a restaurant, it's probably less dangerous and chaotic but more loud and hot.
- itomato 5y agoGrills & hoods and hot rows feel eerily similar, down to the din.
- slg 5y ago>I'm not sure my body could take that kind of work now People who have never worked in a busy restaurant probably underestimate the type of toll that work takes on your body. It can be grueling.
- pc86 5y agoI worked in kitchens and as a server pretty regularly from about ages 16 to 22. After several back-to-back busy shifts my joints would hurt until I got a day off. Even at 36 now as I start to feel stuff ache a little more often and a little more acutely, it was different then. It's easy to see how decades of that kind of work can really take a toll on your body.
- t0mbstone 5y agoI'm a big fan of the one-touch inbox zero flow, although the way I do it is slightly different. I have four folders that I organize all incoming email into: 1. Requires Reply 2. Requires Action 3. Keep Eyes On Anything that doesn't immediately fall into one of these categories gets archived. Any email newsletters are immediately unsubscribed from (with the exception of Ruby Weekly and Python Weekly). I also use a lot of automated filters/rules for applying organizational labels to different emails.
- joshuaheard 5y agoI use @Action, @Bills, and @Waiting. It if takes less than 2 minutes, I do it immediately upon receipt. Otherwise it goes into the Action folder. I use @ in front of the folder name so it's at the top of my subfolder list.
- mamborambo 5y agoA very good read, and indeed "mise-en-place" is a skill / philosophy / system which can greatly assist knowledge workers if they apply it. Most chefs learn how when they apprentice under a master chef, and adopt or copy what they do. These skills are seldom learned by reading a book or from an essay, because they need to become habits to be effective.0p
- bob1029 5y agoI started seeing the value of this ideology recently. I have a really strict routine before I write a single line of code on a complex issue. All of these ways of thinking ultimately came out of efficiency gains I learned on my own in the kitchen. Prepare, then work. Trying to prepare while you work is chaos (but sometimes essential). The very first thing I do after finishing a design review narrative is to type up a list of discrete tasks that I plan to execute. These don't necessarily say what to do line-by-line, but draw out a very clear picture of what code areas are edited and what the dependency graphs look like. These also highlight specific configuration or other UX points to reference during testing. These task lists are specific enough that other developers could reliably execute them without any additional guidance. Then, I take a short break and review my task list when I return. 9/10 times I find I want to tweak it a little bit. After the final confirmation, I sent notification out to my team that I intend to execute the task listing so they have a super clear idea of what functionality to expect on the other side. I have found that this reduces my anxiety/stress by orders of magnitude throughout the day. Starting with visual studio and fumbling around various parts of the code base might be a good way to get your brain warmed up in the morning, but its certainly not a rational way to go about solving a complex problem. For trivial issues, production RCAs, etc., the process is certainly a little bit more streamlined than what I note above. This is more about how to do work on big tasks.
- hinkley 5y agoI help a lot of people in a given week, and my browser tabs are out of control. What has helped a lot for me is opening all of the tabs for a particular issue in a new window, and often putting them as the only thing on my smallest monitor is a decent compromise for not losing it. Once I minimize that window it gets lost quickly, which also contributes to the tabs problem. Still need to solve that issue. To a lesser extent, the smart location bar for Firefox at least will tell you if you already have that url open elsewhere, which saves me from abandoned/divergent wiki edits and lost workflows. Not always, but routinely for sure. It also can search your bookmarks, so tagging things with the name you think they should have helps a lot there. Now if I could just get better at deleting malformed urls from my history... Except for the single window piece, these aren't exactly 'mis-en-place'. They're more second-order effects, akin to putting the common ingredients on the "right" shelf, so you can grab them quicker. The invisible ingredient in 'mis-en-place' is your head. If that's a mess at the beginning of the task then everything will be off. So you can 'mis' all you want but if you run an obstacle course to get there it's going to help but not as much as it could. Like showing up to a race tired.
- itomato 5y ago> Because of this brutal reality (In cooking, a dish that is 99% finished has zero value), chefs must adopt a “finishing mindset.” Perfect is the enemy of Done. It hurts me to read this and to think of people adopting a "finishing mindset" while also trying to get behind: (1) planning is prime (2) arranging spaces and perfecting movements (3) cleaning as you go (4) making first moves (5) finishing actions (6) slowing down to speed up (7) call and callback (8) open ears and eyes (9) inspect and correct (10) total utilization https://books.google.com/books?id=l8tUCwAAQBAJ https://books.google.com/books?id=l8tUCwAAQBAJ
- pc86 5y agoI think this is a good example of the analogy falling apart. A feature that is 99% done may actually be fine. Or it may not be much better than 0% or 50% - that sort of depends on the business side and how incremental a given feature can be and still provide value. Still, I think in general it's a good idea to be a little more on the "finishing mindset" of things than the "if it builds, it ships" side of things.
- mdoms 5y agoI think this needs to be combined with breaking things down into as small a piece of work as possible. Yes a feature may be valuable at 99% completion, but hopefully that means a whole stack of work items at 100% and a small handful of unstarted work items.
- lmilcin 5y ago> I think this is a good example of the analogy falling apart. No, it is not. It is up to you to define what is 100% of your project. If you think something is not worth it, just don't put it in the 100%. Be honest in saying "No, we are not going to do it". Too many projects linger because there is no will of getting this or that done. Either redefine the project or just f-n do it and be done with it. This helps put definitive end to the project possibly letting you call success on it. It also frees up your mind to work on other stuff.
- 5y ago
- whytaka 5y agoThis may seem obsessive-compulsive to others but the way I work on the computer, I close everything that I’m not immediately working on. No extra tabs, no bystander applications. I keep my desktop completely plain so that the only files I see are the ones I just produced/downloaded. I would rather go through the pain of reopening apps/websites than to have it lingering when I don’t need it right then. I don’t understand how people can have multiple windows of multiple browsers with multiple tabs open about things they aren’t working on while they work. The visual clutter overwhelms me quickly.
- leokennis 5y agoI almost physically cringe when for example I see people searching for the super important cost estimation of a project and finding it as “/Documents/documents/docs/Old Stuff/work/New Folder (1)/Amy/work/migration/temp18/excel/team/DO NOT DELETE/e.xlsx”
- SN76477 5y agoI work similar to this. I think you have inspired me to go full on with it.
- draw_down 5y agoSame here. If I’m not using it it’s gone. If I need it for later I’ll save it somehow. My computer should have very little local state. Losing a window with dozens of tabs shouldn’t be some devastating loss. If it’s important save it.
- johnchristopher 5y ago> I don’t understand how people can have multiple windows of multiple browsers with multiple tabs open about things they aren’t working on while they work. The visual clutter overwhelms me quickly. Well, multitasking was all the rage not so long ago. A lot of people got bombarded with blog posts and articles about it.
- catchmeifyoucan 5y agoI feel the same. It’s just way too overwhelming. Checkout Amna, it might be able to help (https://getamna.com https://getamna.com). It minimizes those browser windows away, and you can focus one thing at a time
- LunaSea 5y agoHe died at age 88 not 99.
- gumby 5y agoThe intern system at large companies is supposed to, and often does implement the same apprentice function that the trades have.
- justinator 5y agoSomewhat of a shower thought: the intern system at a large company oftentimes selects out people who cannot afford to even be interns, thus causing the class gap to be widen; the apprentice function of trades very much does not.
- gumby 5y agoThat may be true in industries that require wealthy clients (e.g. art galleries) but in computing (and the unionized trades) interns /apprentices are paid.
- justinator 5y agoI am absolutely specifically thinking of unpaid internships in the tech/startup industry. Trades are an example of getting paid as a journeyman, while doing useful work for the company from day 1. I've interned at an art gallery. I didn't mind getting paid, as I was also getting course credit (and the work wasn't all that hard anyways). But the art was sold on consignment - NO ONE got paid unless the art moved off the walls, and if I did sell a piece, I got a commission for that. But I wasn't interning for a future career working in an art gallery, I was interning as an artist. The art world is its own special type of hell for those who aren't super wealthy. To sell items that intrinsically have no utility is a pretty weird business. The unpaid intern that's watching a gallery while doing their coursework on a Thursday afternoon while no one comes in is the least of its problems.
- wheelinsupial 5y ago> Trades are an example of getting paid as a journeyman You’re correct in that trades people do get paid while working. However, to add some nuance, I think the rate is going to depend on the trade, company, location, education completed, and work hours completed. My brothers have their red seal and work as tradesmen. It’s 40-50% of the journeyman rate for 1st years. There are 4 years of schooling and something like 2,000 hours of work required between each level of schooling (there is a tolerance to early start / late start). Wages increase when the apprentice hits specific hours worked milestones or school level completion milestones. This applies to BC, Canada. As I said before, this may depend on location, so it may not be the same where you are.
- deleted 5y ago[deleted]
- Zababa 5y ago> There is no class in college on how to triage your email inbox, manage your agenda, or organize your computer files. Small nitpick, having to organize your computer files is mostly a consequence of Windows having a terrible and ineffective search. I recently realized that I don't really need to organize stuff in folders on Linux since I use meaningful names when I store files, and search when I retrieve them. On Windows, the search is unusable, and thus I spend a lot of time making a hierarchy of categories with folders, which is a waste of time. To use the kitchen analogy, the first time you use a good search is like the first time you use a good knife. It changes the way you approach things. I eat way more vegetables since now cutting them isn't a pain.
- mywacaday 5y agoI think you just hit the nail on the head why I spend so much time storing and organising in onenote, I always thought it was because onenote search is good, it's not, it's because the system search is so poor.
- nlawalker 5y agovoidtools' Everything (https://www.voidtools.com/ https://www.voidtools.com/) is one of the first things I install on a new Windows system. Instantaneous filename search.
- cton 5y agoWindows’ built-in file search becomes embarrassing once you’ve used Everything. Though Windows search does save me from having to trawl through settings/control panel.
- nyanpasu64 5y agoHow is search better on Linux? KDE's Baloo is worse than Windows Search; it's an unending trainwreck of failing to index files (whether names or contents) on some computers and going stale on other computers. Maybe GNOME's file indexing is better, I'm not sure. Do you use the (non-index-based) find and grep CLI commands? In that case you can install them on Windows too, or install fd/rg on both Windows and Linux.
- skinkestek 5y ago> [...] and this is reflected in the strictly defined roles he created for the kitchen: These days knowledge work seems to be about making everyone a "fullstacker". I love learning but I think it is more than a bit wasteful to let me do css work (I have red/green colorblindness).
- kortilla 5y agoSo little of css is work is in color picking that I don’t think color blindness matters.
- svachalek 5y agoThe long term trend is toward ever more specialization. Even a "full stacker" implies a certain subset of web tech. You wouldn't hire a "full stacker" to do your kernel work, or device driver, or likely even your mobile app. 30 years ago, programmers was programmers. There might be a momentary tick downward on this trend, like a correction in the stock market. But I don't think it changes the overall direction, and honestly I haven't even noticed a blip.
- Zababa 5y agoA better analogy for the "finishing mindset" would be that every running process takes RAM, and you can only have so much of it. This highlights the fact that finishing a task has a value regardless of the value of the task, because it frees resources that can be used for something else. I think trying to stretch the analogy too much is detrimental to the whole article. For example the reminders: a post it on my screen will remind me at all time that I should do something, because the "default mode" of the post it is existing. The default mode of the digital is not existing. I need to boot my computer to have my to-do list app, or consult my phone, or open my notebook. This is not the case with a physical reminder (sure the notebook is physical, but it needs an action to remind you of something).
- carlmr 5y agoI think the physical is actually what's missing in this article. Mise-en-place is also that you have your tools organized in front of you, having physical reminders and notes, can be helpful for the knowledge worker as well. Having "your" workspace in the office, or at home as well. I find that a huge issue with flexible workstations.
- mcbishop 5y agoThe author's PARA method for organizing / structuring digital info is helping me a lot. It gives me a solid bedrock. https://fortelabs.co/blog/para/ https://fortelabs.co/blog/para/
- sbuk 5y agoThere is a fantastic book called 'Work Clean: The Life-Changing Power of Mise-en-Place to Organize Your Life, Work and Mind' by Dan Charnas that goes into more depth about Mise-en-Place. https://www.workclean.com/ https://www.workclean.com/
- galaxyLogic 5y agoSmalltalk-80 had a fantastic work-management facility. I haven't checked lately but I think Squeak and Pharo Smalltalk environments still have it. On the desktop of Smalltalk Virtual Image you can right-click and say "New Project". This open a new window, which you can resize as you wish. Right-clicking on that allows you to "Enter Project". When you do you see a new desktop into which you can open various tool-windows, browsers, debuggers etc. And you can open nested project-windows inside a project-desktop, as deep as you wish. You can exit a (sub-) project but the (sub-)project still remains in existence, with its window in the parent-project as the handle to it. As you exit your Smalltalk session you typically choose to "Save Image" which means this tree of projects, each having its own state and set of windows, perhaps a debugger halted on a piece of code, are saved with it. (You will see them the next time you re-open that same saved Smalltalk image). When you're working on something you often discover that to do this you must first do something else. No problem, open a new "project" window on your current Smalltalk (project-) desktop. Once that sub-task is done you can exit that project and close its window. But you can have multiple (nested) sub-tasks open at the same time. The name "project" is not the best word for them I think, I think they should be called "tasks". Why does that matter? Because I think it's important to understand that this is not about Project Management. This is Task Management. Something in the spirit of mise-en-place perhaps. You could create a Smalltalk image with tree of "project windows" on it and share it with your co-workers. These sub-projects could describe the subtasks and allow you to record you progress in them, say for cooking a specific type of dinner. Smalltalk "project-windows" are such a great idea I wonder why something like them does not exist in other environments. No doubt having a "Virtual Machine" whose state is easily saved is a requirement.
- tigershark 5y agoIt doesn’t seem very helpful with modern workflows.. Usually you don’t work on several separate projects, you work on one project and you switch branches depending on the feature that you are working on. You can easily merge in your current branch the changes from another branch. With the subprojects workflow how can you import the changes of another subproject considering that you are probably in the middle of the debugging or something else?
- readonthegoapp 5y agoI feel like this is ridiculous idea with a book attached to it. Happy to be wrong But it reads like an advertorial Like a politician blowing smoke up KWs asses Look at this line: "We approach each new task and project as if it was a completely blank slate, requiring an entirely new approach." Wts? Cmon, man. Every other line is lionizing 'us' for our rugged good looks and ability to produce SUPERDUPERHIGHQUALITY ... something... in the face of almost insurmountable odds. Its a self-parody. Sorry. I'll pass. But happy other folks find value in doing first the things that... need to be done first.
- reilly3000 5y agoInformation marketing about information products for knowledge work. My head hurts.
- foxhop 5y agoIt's a repackaging of the trivium method (inputs, processing, outputs) where order of operations is key to success in manifesting the desired and ideal result. It applies to nearly all subjects.
- quickthrower2 5y agoI like to: * Have only one task in progress * Close unnecessary tabs and applications * Reread every word of the spec * Only have the relevant terminals and IDEs open * Close communication apps and email Get started!
- ilaksh 5y agoThere are some useful ideas here that can be applied, but overall the analogy is deeply flawed. Most programmers rarely spend the majority of their time on things that they have created before. Instead, most of the energy goes into understanding problems. Cooking is just not very much like programming. The chef can see exactly what the ingredients are at all times and exactly what the state is. He is making the same dishes night in and night out. If he makes a mistake and overcooks something, it is a significant time waster. Its as much a performance as anything else. Treating programming as if it were an exercise in extreme efficiency points to a misguided mindset. Like a feature mill with a clueless manager happily spewing out Jira tickets as fast as he can think of them, and some overworked outsourced staff in a sweaty room on the other side of the world cranking out features as quickly as possible with boilerplate-based code generation.
- snowwrestler 5y agoThis analogy kind of rubs me the wrong way. The whole point of knowledge work is that you are doing things that have not been done before. If they had, they would already be scaled or automated. In a chef analogy, you should be inventing new dishes, not running a meal service. A chef running a meal service is supposed to cook a meal for every order that comes back to the kitchen. A knowledge worker is not supposed to handle every little request that comes their way. As a knowledge worker, if you’re not disappointing some people, you are probably not doing your best. If you are overwhelmed with tasks as a knowledge worker, the solution is not to seek greater efficiency in handling them. The solution is to do incredible work on the ones that actually matter, and half-ass or ignore the rest. If you’re not sure which is which, finding out is job #1. People who efficiently do everything they are asked are rewarded with more asks. People who do great high-impact work are not held back because they dropped some emails along the way. I’m not saying it’s bad to be efficient at processing email and tracking requests, I’m just saying it probably matters less than many people think, and almost certainly less than this article implies.
- justinator 5y agoAt the extreme, someone behaving like this doesn't seem like a great person to work with.
- Daishiman 5y agoFor the vast majority of engineers, even writing high impact code means repeating the same request/db query/response dance, code pasting or ebuggin activity, and to be actually good and efficient at any of these means having done them plenty of times. Even understanding novel problem domains requires a certain structured approach to research, talking with users, writing out thoughts, etc. All this certainly matches the analogy laid forward.
- DomenicoMazza 5y agoThe take home from the analogy is to follow a process where delegation and hierarchy is key for efficiency. This benefits all kinds of work. Delegation or setting the right roles in a team (where possible, or making it happen) is better than half-assing or trying to do everything. I don't think there's anything admirable in being unavailable or losing opportunities to complete work due to inefficiencies that can be avoided with a bit more trust distributed throughout a team.
- rishikeshs 5y agoAnyone here building a second brain?