Showing fragments matching your search for: <strong>""</strong>

No matching fragments found in this document.

22. BACKLOGGING

    If traffic or bodies begin to be backlogged  one  can  stall  completely
just handling
the queries about the backlog without getting anything really done.

                               23. OFF ORIGIN


                         (Statements and Despatches)


    A terminal originates something not its hat.

                                 24.OFFLINE


    Despatches or orders are passed in a manner to deny info on record.

                         25. INCORRECT ORGANIZATION


    The Comm System or procedures are not organized so as to be easily used.
They
are either not organized at all or are made too complex to be useful.

                             26. ORG BOARD DEV-T


    An out-of-date Org Board can cause Dev-T. A staff that  doesn't  have  a
well done
Org Board cannot help but make Dev-T. A staff  that  doesn't  know  the  Org
Board will
make Dev-T.

                             27. UNTRAINED STAFF


    Staff not grooved in on the lines mainly deal in Dev-T and although they
even
look busy seldom accomplish much.

                         28. UNPRODUCTIVE PERSONNEL


    Keeping a personnel on a post who is a flagrant Dev-T source.

                       29. PEOPLE WHO PRESENT PROBLEMS


    Problems presented by juniors  when  solved  by  a  senior  cause  Dev-T
because the
source of the problem usually won't use the presented solution either.

                    30. HAVING TO HAVE BEFORE THEY CAN DO


    Projects stall "because of FP" or "because it would be nice  to  have  a
_____".

                            31. PERMITTING DEV-T


    The biggest  single  goof  anyone  can  make  is  failing  to  recognize
something as
Dev-T and going on to handle it anyway. One's  basket  soon  overflows.  The
reason for
"overwork" and "heavy traffic" is usually traceable to permitting  Dev-T  to
exist
without understanding it or attempting to put the Dev-T right.

                    32. LACK OF EXECUTIVE RESPONSIBILITY


                                 Is this OK?


    Executives may not OK anything done or to  be  done  below  their  level
unless their
immediate junior has also stated or attested with an initial that it is OK.

    Unless one can fix responsibility for actions there is no responsibility
anywhere
and the whole show goes to pot.

    Never let a junior say "Is this OK?" Always make him  state  or  initial
"This is OK"
on all work, actions or projects.

    "Is this OK?" is Dev-T and should be chitted as such.