Visits ...

Sunday, November 25, 2012

Process A to Process B


Recently, i went into some trouble. Not for some design that i have done but design someone else has done. Yet i'm responsible, (which is something, i would like to discuss more later).
A vital process did not get executed, but was not known until months passed. Process so important, once a min owe thing has gone in to proportions, needless to say putting me in great trouble. 
My CEO taught me and/or reminded me something, that i would like to keep in mind rest of my career. Processes are sequential which means one depends on another to finish to start-up. this is a continuous process which ends when either meeting the target or ended up in error and terminates. 
What should be happened in between two processes, where one is taking control from the previous one. One thing and one thing only, it should pass the ownership. previous owner should make sure it has passed to the next with confidence of completing successfully its objective and current owner should make sure that he received the control with no strings attached, another words no errors or issues been inherited.
Suppose there are errors in one process, rather progress with hiccups, inaccuracy and inefficiently, it would stop just limiting the situation to mere convenience rather than to a cut-throat blame game and data corrections. worse things could happen to a designer.
let me summarize you in simple graphical format.



No comments:

Post a Comment