It will be found that hatting rules and procedures apply to the Esto himself.

In orgs while under training he himself is hatted and produces alternately, doing better and better.

He must NOT be let off hatting until he is fully hatted.

And he shouldn’t, especially when being trained in an org by an Esto I/C, be let off establishing on the excuse he is not yet fully hatted.

It will be found that some Estos back off from an area because “they do not know all the tech lines and hats in that area.”

The reason they give for this back-off is the wrong Why. They back off or fumble when they are not hatted as Estos! Not because they are not hatted on the area’s hats.

Just like the housewife who criticizes her neighbor for a cluttered back yard while standing in a more cluttered one of her own, hatting begins at home.

If an Esto knows his business he could straighten up a huge corporation using the Esto system with never a whisper of their business!

It would be tough. But it shows where the importance lies.

There is Esto tech. When it is not known or used, then an Esto can just sink down into a division puzzled and apathetic, thinking its tech is what is bogging him.

He daily sees and talks to people swamped in dev-t, unsure, nervous and wide-eyed with problems and questions.

If an Esto does not at all times KNOW HE IS AN ESTO and ACT LIKE AN ESTO he can easily slide into these confusions and try to handle production- performance problems that are outside the Esto’s line of duty.

FIRST, LAST AND ALWAYS IT IS THE ESTO HAT THAT MUST BE WORN IN ANY GIVEN SITUATION.

Thus the A (own hat) and B (div tech and hats) differences of hats is important to know.

It’s great to know and one should know a division’s tech and hats. But this is something one learns as he goes along.

It’s a matter of THE MOST VITAL IMPORTANCE that the Esto wears his Esto hat.

That’s the hat he has to have down cold.

Then he will find that org and division confusion is nothing to him.

HE HANDLES THINGS LIKE THAT!

HE IS AN ESTO!