Did you know you can let an entheta despatch drop right there and create less entheta by doing so? Try it sometime.
Or Assoc Sec London (as once happened years ago) doing business only in Australia.
On a smaller look, a staff member doing only part of his job produces a similar result.
And somebody doing another staff member's job is another version of it.
If nobody knows about an appointment, then how can anything but Dev-T occur? Thus prime preventers of Dev-T are: 1.
The originator shouldn't have originated it and also should have sent it
elsewhere if he
or she did originate it. If the HGC thinks it has to wear the Academy hat
then the
despatch should go to the Academy and nowhere else. At least send it to the
hat it
most concerns.
This gets even more snarled when it jumps an org-to wit, an HGC staff
member
originates a despatch for the Academy and sends it to, let us say, the
National Central
Org. In the other org, unfamiliarity with the org board of the originating
org can cause
action to be taken. It isn't noticed that the HGC is talking for the
Academy.
When action is taken other than returning the off-origin despatch to its
sender, a
great many evils can result. The least of them is that it gets the sender
in trouble when
acted upon.
Example: A staff auditor proposes to the Assn Sec that students be
trained better
in 8c because of a recent HGC flub. The Assn Sec jumps on the D of T. The D
of T
privately pounds the staff auditor into the ground.
Ill feeling in orgs usually stems from these off-origin despatches.
In the above example, the staff auditor should have taken it up
emphatically on
the basis of a flub in the HGC with the D of P who then would take it up
with the D of
T still on the basis of an HGC flub. Then it has a chance of straightening
out. You see,
lacking data, the person originating an off-origin despatch usually assigns
wrong cause.
In the above example it may have been certification at fault, not the
Academy at all.
One can drown in a sea of errors on these off-origin despatches. Basically
what ails
governments is their dependence on spy reports, police reports, etc. The
reporting
person does not wear the hat which should have originated.
When a staff member does not himself originate when he or she should, it
will
show up in the OIC reports and in emergencies. It is handled by putting on
the person's
hat, auditing or personnel transfers, not by off-origin despatches.
Did you know you can let an entheta despatch drop right there and create
less
entheta by doing so? Try it sometime.
Not all off-origin despatches are entheta, of course.
Part of this type of despatch is of course off-zone. Perth originating
for Sydney.
Or Los Angeles originating for New York. Or Assoc Sec London (as once
happened
years ago) doing business only in Australia. Or LA getting pcs only from
Nevada. Here
one sees somebody operating for the wrong zone or for only part of their
whole zone.
On a smaller look, a staff member doing only part of his job produces a
similar result.
And somebody doing another staff member's job is another version of it.
Off-origin despatches or work can make an awful lot of Dev-T-not always
pleasant.
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.
An Org Board is what we use instead of Appointment lists inside orgs. If
it isn't
posted on the Org Board, it hasn't been appointed. Why? Because an
appointment is
effective only if its work will be routed to it. If nobody knows about an
appointment,
then how can anything but Dev-T occur?
Thus prime preventers of Dev-T are:
1. A well done Org Board.
2. A complete Org Board containing all appointments.
3. A staff checked out on the Org Board.
4. All new staff checked out on the Org Board.