Doing the work of the post does result in effective exchange.

An org board is a list of hats with seniorities. The hats are in flow sequence.

If one confronts his post he will see there are things to do. These things result in both morale and viability.

A hat is a duty. It outlines the actions necessary to accomplish a production and receive what’s needed, change and route it.

„Do“ is often defined as „talk“ or „refer.“ But that doesn’t get anything done. Do is the action which leads to DONE.

In theory the I/C holds all functions. When he doesn’t fully outline them they can’t be hatted. If they’re not hatted he wears them as an unknown fog. Simple as that.

Doing something else does not lead to any done.

What defines a hat is a product.

Do your jobs and get dones.

If you count up the expected products you get the minimum number of hats. The steps to get the product is the hat. Products are also composed of lesser products, so hats can be enlarged. It’s what you designate as a product that makes a hat. It’s the importance of that product to others on the line that makes the hat’s importance.

The completeness and size of the product make the seniority of the hat.

The overall product of a division determines the hat of the divisional officer. The lesser products that when combined make the overall product determine the rest of the division hats.

Until you can define in one go the overall product of a division you aren’t likely to be able to post any real part of its org board. For the product of hats of that div add up to the div product.

When you see an unposted or unreal org board, the head of the div is not producing a product with that div, no matter how busy it all looks or how exhausting.