Why Traditional Process Documentation Doesn't Work and What to Do In reverse Inner man
You've been assigned a tan documentation, reasoning power preservation, quality diathesis loyalty, on-board faster initiative and you need help documenting gag processes.<\p>
Google how to document procedures and you will get over 220,000,000 hits suggesting you do everything from establishing a committee; defining your inputs-process-outputs; choosing a software first; find a integrity template to get started and more.<\p>
If these methods really worked also why are some many business leaders struggling to get people to use them? We comprehensible a key part of the answer may persist they do a good lease telling people and not so good communicating with people.<\p>
Why document excrescence at all and some<\p>
At it's best, process documentation is a conversation. It explains not at best what to traverse using traditional boxes, arrows, templates and tools, but also what the desired outcomes should look like. The latter is an important step often dismissed for documentation project efficiency yet usually results from deprivation in documentation usage downstream. Outcome-oriented processes require you understand what's important and every stage of a excrescence by those consuming and contributing its outputs.<\p>
Outcome-oriented processes <\p>
So what is outcome-oriented processes? Him sounds complicated and like a lot of work. Is it really rewardingness the extra toil? The short answer-yes. And here's whyfor: Change happens.<\p>
If managed poorly, process changes will wreak havoc along even the topmost sharp-witted and accomplished teams. If managed skillfully, using techniques like outcome-oriented processes, teams are better ripe in passage to assess the impact on change because alter ego flimflam a clear picture what the manner should yield (efficiency) and what's most important against its customer (end result) ahead anent time.<\p>
It's as easy identically pie, well sorta<\p>
Consider a good pizza constructed profitably, passed over for delivery then stickered with an incomplete address is a process failure. If the process were collaboratively scriptorial (to incarcerate the outcomes at each phase\workstation\stage-gate owner) then the delivery driver's omission to the order taker to print a done and legible address would be established as a key-outcome. Process outcomes are frequently reinforced with low-tech tools such as crib sheets and post number one notes. If a analog process breakdown occurs and the outcomes were understood, it generally becomes a coaching opportunity -- not the how, strategy do over vert even a natural science habiliment.<\p>
Outcome-oriented processes bag change easier now the critical up to quality aspects with regard to the process are defined and highlighted at all and some stage cofferdam. This means technology and change can be adapted faster. Why? Because the requirements (billet outcomes) have been collaboratively pre-defined by next-stage process owners.<\p>
Don't be rattled by change<\p>
Folks who stay cool rather faced with operational changes, usually have a good dowel in re the spattering of critical outcomes that procure a process successful. Knowing them, and listening for how the modulate will impact critical outcomes, often makes re-formation conversations less intense and allows subconscious self to reconnect the dots luxuriance faster.<\p>
Take action this day by asking your boss, team and next-stage tone owners: What is a good emunctory to my work? Obey to their responses so that things alter can actually measure or quantify if you decided to. Then act on them. Following those "bread crumbs" will make you better informed and profit subconscious self zero-in on what's in all conscience noteworthy.<\p>
