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 31 JANUARY 1965


Remimeo
Sthil Staff

                                    DEV-T


                     (Adds to HCO Pol Ltr Nov. 17, 1964)





    The commonest cause of OFFLINE despatches is:

    A staff member writes a despatch to himself but routes  it  to  somebody
else.

    Example: Registrar writes a despatch to the Org Sec asking how to meet a
quota
of interviews. This is Dev-T because it is offline. Why is it  offline?  The
staff member
responsible for increasing interviews is the Registrar,  not  the  Org  Sec.
Therefore the
despatch should be routed to the Registrar and routing it to anyone else  is
misrouting.
Informing the Org Sec, "I am doing so and  so  to  increase  the  number  of
interviews" is
quite in order, but it's  a  despatch  containing  a  report,  requiring  no
answer. The correct
routing of a query about increasing interviews would be  to  the  Registrar.
Thus, the
above example's routing would be the Registrar to the Registrar.

    When a staff member generates a lot of despatches about his post,  these
are
usually misrouted if they go to anyone else  but  himself.  Since  who  else
should wear
that hat? Not the Org Sec or Assn Sec. Not  the  HCO  Sec.  Only  the  staff
member
himself or herself.

    In orgs a goodly number of people think staff  members  senior  to  them
also wear
their hats. This is definitely not true. The Assn Sec or Org  Sec  does  not
wear every
other hat in the org. If he does, he is a pretty poor organizer. And  if  he
lets staff force
him to, then he isn't much of a leader.

    You can detect people who fear responsibility or consequences  of  their
most
ordinary actions by the number of despatches they send others  which  should
only have
gone to the staff member himself or herself.

    It's the figures  on  the  weekly  report  sheet,  the  volume  of  work
accomplished, the
resume of results that inform others about a  hat  and  the  activities  and
effectiveness of
the person wearing it. An Org/Assn Sec only needs to look at these  reports,
not his
in-basket, to know if posts are being held. It may make one feel  grand  and
responsible
when others must come to one for help on their  jobs  but  it  sure  doesn't
make a strong
org to have "what-do-I-dos" flying up to the head of the org day and  night.
People
exist who do their jobs without a lot of Dev-T about how to  do  them,  what
to decide,
how to think. And people exist who do their jobs  without  getting  everyone
else in
trouble.

                             OTHER PEOPLE'S HATS


    There is another type of Dev-T which one encounters.  And  that  is  the
origination
of comm that should have been originated by someone else.

    This has several guises. You see it in a usual form in  Academies  where
some
student is always asking questions "so that  the  others  will  understand".
The student
himself or herself understood the instructor but asks  a  question  so  "the
others will
understand also".  This  is,  of  course,  a  student  trying  to  wear  the
instructor's hat or
another student's student hat. I can usually detect this one  and  break  it
right there
with "Are you asking because you don't get  it  or  because  you  think  the
others
haven't?" Such a student can lengthen study hours horribly  without  helping
anyone a
bit.

    A staff member occasionally tries to originate for another hat than  his
or her own.
It is easily detected. The despatch has to do with the Academy but  is  from
the HGC,
etc.

    Such a despatch is usually misrouted also. It is sent  to  a  department
head or the
HCO Sec or somewhere. Trying to handle it  gets  pretty  deadly  as  it's  a
double snarl.