|
|
|
|
|
|
by JackSlateur
851 days ago
|
|
|
You failed as soon as you think "process" A process is a hardcoded way of do thing, which is deficient because it cannot react to an ever-changing world A better way to handle things is by defining "what" should be done, not "how" it should be done |
|
|
Everything you do -up to and including taking a leak- is a sort of process. Perhaps you don't think that particular example should be a corporate process, but that's not my problem :-P .
You can compose processes to get things done.
Processes can be made mutable or flexible by eg. incorporating decisions or iteration. Especially iterated processes can be very powerful (you can get a lot done with them).
Thinking of things in terms of processes instead of in terms of component steps each time frees your mind to worry about other stuff.
Compare it with dividing a program into functions. Once you've wrapped a task in a function, you can then design using the function, rather than worry about how to write the code from scratch each time. Same with process thinking: you don't have to get bogged down in particulars all the time.
That said, maybe you're thinking of the "Befehlstaktik" vs "Auftragstaktik" [1] approach to doing things. In which case we're arguing definitions instead (which can be easily resolved).
[1] https://en.wikipedia.org/wiki/Mission-type_tactics