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

No matching fragments found in this document.

HUBBARD COMMUNICATIONS OFFICE

                  Saint Hill Manor, East Grinstead, Sussex


                    HCO POLICY LETTER OF 27 OCTOBER 1969


Remimeo



                            Admin Know-How No. 23





                                    DEV T





    The entire, complete and only major source of  Dev  T  is  ignorance  or
failure to
grasp CONFUSION AND THE STABLE DATUM as covered fully in "Problems of
Work" (and LRH Tapes of 1956).

    Unless an executive or staff member fully grasps the basic principles of
Confusion
and a Stable Datum then the org board  is  completely  over  his  head,  the
reason for
posts is not understood and Dev T becomes routine.

    A post on the org board is the STABLE  POINT.  If  it  is  not  held  by
someone it
will generate confusion. If the person  that  is  holding  it  isn't  really
holding it, the
confusion inherent in that area on the org board zooms all  over  the  place
near and
far.

    Any executive getting Dev T knows  at  once  what  posts  are  not  held
because
Dev T is the confusion that  should  have  been  handled  in  that  area  by
someone on post.
With that stable terminal not stable, Dev T shoots about.

    Excessive transfers in an org promote fantastic Dev T as  the  posts  do
not really
get held as people are on them  too  briefly.  "Musical  chairs"  (excessive
transfers) can
destroy an org or area.

    The remedy is to get people trained up (OEC) to handle their  posts,  to
get people
on post who do handle their posts.

    An essential part of such training is a study of "Problems of Work"  and
a full
grasp of how a stable  terminal  handles  and  prevents  Confusion.  If  the
person cannot
fully grasp  this  principle,  he  is  below  the  ability  to  conceive  of
terminals and barely
able to perceive lines. He cannot communicate since there are  no  terminals
to him.

                                REMOTE AREAS


    If an area remote from an executive does not contain a stable  point  to
which he
can send his comm and get it handled, then his comm only enters Dev  T  into
the area
and he gets back floods of despatches and problems  but  no  real  handling.
The area is
not organized and does not have people in it who have grasped  "Problems  of
Work" or
how it applies to an Org Board or even why there is an Org Board.

    Communicating into a disorganized area without first  organizing  it  to
have at least
one stable terminal is foolishness.

    An Org Board is that arrangement of persons,  lines  and  actions  which
classifies
types of confusions and gives a stable terminal  to  each  type.  It  is  as
effective as its
people can conceive of terminals  and  understand  the  basic  principle  of
Confusions and
Stable Data.

    A good executive arranges personnel and organization to handle types  of
actions
and confusions. He does not broadly Comm into disorganized areas  except  to
organize
them.