The first thing an Esto runs into in an area that is not hatted is DEV-T (developed unnecessary traffic).

People in an org can be working frantically, totally exhausted and yet produce nothing of value. The reason is that their actions are almost totally dev-t.

The WHY of this is UNHATTEDNESS.

The people on the posts do not know their own hats or even if some do they are dealing in the “NOISE” of other people who don’t know their own hats.

Few if any of these people know the other hats or duties of the org and so don’t know where to go for service or who to approach or despatch for what.

So it’s not an org or a division. It’s a nonproductive chaos.

The answers are three:

1. Get dev-t understood and

2. Get the staff at least instant hatted at once.

3. Chinese school (staff or div staff all together in front of a big org board chanting together the hats, duties and products of the org as visible on the org board).

In order to get anything done at all or even begin this an Esto Ethics Officer function has to be in.

A schedule has to be posted including exercise, post time and study and staff has to be mustered and handled at these periods. This gets some awareness of the org group as a team of people with similar purposes.

Dev-t packs are made up. These consist of

• HCO P/L 2 Jul 59 Issue II “Dev-t — The Delirium Tremens of Central Orgs”
• HCO P/L 29 May 63 “How to Handle Work”
• HCO P/L 21 Nov 62 “Completed Staff Work”
• HCO P/L 17 Nov 64 “Off-line and Off-policy, Your Full In-basket’
• HCO P/L 31 Jan 65 “Dev-t”
• HCO P/L 8 Feb 65 “Dev-t Analysis”
• HCO P/L 13 Oct 65 “Dev-t Data”
• HCO P/L 5 Jan 68 “Dev-t Series, Part of — Overfilled In-basket”
• HCO P/L 27 Jan 69 “Dev-t Summary List”
• HCO P/L 30 Jan 69 Issue II “Dev-t Summary List Additions”
• HCO P/L 27 Oct 69 “Admin Know-How No. 23 — Dev-t”
• HCO P/L 4 Nov 69 “Dev-t Graphed”
• HCO P/L 23 Jul 71 “Telex Comm Clarity — Dev-t Series”
• HCO P/L 25 Oct 71 Issue I “Comm Routing”
• HCO P/L 27 Feb 72 “Exec Series 9 — Routing”
• HCO P/L 29 Feb 72 “Exec Series 10 — Correct Comm”

These packs are issued to staff members and they are required to check out on them.

Each staff member keeps a dev-t log and writes down the name of anyone he is getting dev-t from and also issues dev-t chits.

The staff at the least are instant hatted at once — place on the org board, work space, supplies, what his title is and what it means, org comm system, what he is supposed to produce on his post.

He is gotten producing what he is supposed to produce in some volume at once.

Hat checklists and packs are verified as there or are gotten ready.

A full hat checkout can then begin.

Courses he needs are done in staff study time.

Actually hat study and checkout is done on the post a bit each day.

This is in fact “on-the-job training” as he is expected to go on producing while he is being hatted.

Org bds are rapidly gotten up or up-to-date in the org (in HCO) and (full org bd) in each division.

Each division is Chinese schooled first on its own org bd, then on the org as a whole, in such a way that they know the duties of divisions, departments and posts and the flow lines of the org.

Wherever an org or even a division falls apart or slows up, this campaign is repeated.

This is a sample Executive Directive (ED) giving a program written for an actual org where the above was done to cure dev-t and get the org hatted and producing:

ED______ Date______________

It has been very difficult to handle the org.

A long and intensive collection of data has finally culminated in discovering, through reports on comm and inspections by showing why the org appears fantastically busy and overworked while producing very little even when it was found the org was insolvent.

Ethics has been very heavy for some time and has not led to any spectacular recovery.

But the comm line reviews and analysis reveal INVESTIGATION:

The org and all its units are drowning in DEV-T. HCO is even generating it. This makes an appearance of frantic action and overload while little is produced.

And an analysis has produced a

The org is almost totally unhatted and untrained.

DEV-T comes only from AN UNHATTED UNTRAINED ORG.

Out the bottom and below the briny bedrock of the sea so far as finished products per man-hours and as far as GI by reason of the org are concerned.

A whole staff and the org fully hatted and producing only correct comm without dev-t and at work actually producing things of real value which will exchange for value.

THE ESTO SYSTEM AND DEV-T P/Ls HANDLE THIS.

• 1. Admin Cramming and each ESTO to be furnished with packs of dev-t policies at once including last Exec Series P/L Routing and new dev-t P/L Correct Comm. ALL HANDS DISSEM. _______
• 2. FULL Esto setup to be gotten on post at once. They go on duty and part-time train. HAS. _______
• 3. Existing Estos and those to be put on at once to hammer, hammer, hammer all posts on off-line, off-origin and other points of dev-t so they are UNDERSTOOD. EXEC ESTO. _______
• 4. Big paper org bd with new complement to be gotten up at once in HCO. HCO ESTO. _______
• 5. Big paper org bds from it to be gotten up in each div and the div Chinese schooled on it. Specializing in the div but also covering the whole org so people know where they are and what each handles and where other terminals in the org are so they can properly route to or go to them for the exact service of that exact post. DIV ESTOs under EXEC ESTO. _______
• 6. Straighten out the comm lines of each post. EXEC ESTO. DIV ESTOs. _______
• 7. Report to his div Esto (see org bd) or Ethics Officer any person originating off-line, off-origin traffic or failing to originate from his post paper or body or remark. Report by “Dev-t Chit.” EVERYONE IN THE ORG. _______
• 8. Send flagrant offenders to Admin Cramming. EXECUTIVES. _______
• 9. Put in
• 1. Instruct, and if no improvement,
• 2. Cram, and if no improvement,
• 3. Retrain and if no improvement,
• 4. Offload
• where hatting continues to fail to produce rapid comprehension of dev-t and/or persistent inability to actually DO his hat. Court of Ethics or Comm Ev on request to remedy any injustice. ESTOs. _______
• 10. Excuses concerning hatting and arbitraries like “only study hat in hatting college” to be wiped out and any barriers to getting on-policy, on-FO-FSO wiped out by ethics action or cramming. ESTOs. _______
• 11. Instant hat every staff member. DIV ESTOs. _______
• 12. Chinese school every division. DIV ESTOs. _______

LETS MAKE THIS A CRACK ORG WE CAN BE PROUD OF!

The above program can be completed in a few days.

It is followed by further programs to get in lines of the org, full hatting, and proper comm setups for each staff member, etc.

If the program falls out or dev-t flares again, (A) REHAT Estos, and (B) do the program once more.

The org will come right and begin producing PRODUCTS WHICH EXCHANGE FOR VALUABLES.

The org will become solvent.

Only the Esto system makes such a program possible.

We have long had the tech as you can see by the P/L dates. Dev-t tech has existed since the mid-1950s. But it could not be gotten in swiftly enough to make a startling change in the org morale or stats until ESTOs were on post in an org.

If it does not go in rapidly even with Estos then some of the Estos are not well enough or firmly enough hatted as ESTOs and the answer of an EXEC ESTO or Esto I/C is to very rapidly cram his Estos or following the (1) instruct, (2) cram, (3) retread, (4) offload pattern, improve his Esto team.

Fully done the program works like a beautiful breeze bringing peace and a cheerful staff.