You should hold successful “Reverse – Flow” meetings


In companies that decide to communicate using the top-down approach, employees that can or even do identify problems typically do not offer solutions. This may happen for two reasons: The employees might not have the skills or there may be an ‘us vs. them’ mentality.

When employees are not involved in identifying problems or offering solutions, it falls upon the managers to resolve these issues along with their other responsibilities. Time is unkind in the business world, and problems that have no solutions usually find themselves on the back burner. When this happens repeatedly, employees learn not to bother with problems or solutions because it ‘won’t make any difference’.

Management can spend an enormous amount of time and money on planning, strategy and developing work processes. However, it’s the employees who use those plans and processes. If the plans don’t work or are ineffective or too costly, who will know first? That’s right, the employees. Yet all too often, no one asks the employees to share their experiences and ideas.

We call our improvement meetings, “Reverse-Flow Meetings”. Our observation is that in many companies, the suggestions and ideas flow down from the president to managers to employees with little to no opportunity for review and evaluation by the employees.

Our meetings Reverse the Flow of suggestions and ideas first from the employees then to the president.  Issues and solutions begin with front-line employee groups, followed by middle management, and finally reach the executive management group.

The positive results from this active form of employee involvement often begin the creation of a great ‘Company Culture’.


Next:  A final summary of the benefits.

Bookmark this post.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>