21.01.2013 Views

TRACOM Group Managerial Admin Kit Sneak Peek - The TRACOM ...

TRACOM Group Managerial Admin Kit Sneak Peek - The TRACOM ...

TRACOM Group Managerial Admin Kit Sneak Peek - The TRACOM ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Optional Exercises — Four-Hour Version<br />

STYLE OBSERVATION RULES<br />

Purpose<br />

• This exercise familiarizes participants with the rules for<br />

identifying another person’s SOCIAL STYLE.<br />

Recommended Time<br />

• 10 minutes<br />

Materials Needed<br />

• Applications Guide (p. 5, Rules for Observing Behaviors)<br />

• PowerPoint Slide: Style Observation Rules (PPT #23)<br />

Directions<br />

1. Ask participants to read "Rules for Observing Style" (p. 5; Applications Guide) and give<br />

participants a few minutes to review the rules.<br />

2. Explain why the Style Observation Rules are important:<br />

a. <strong>The</strong> more accurately you are able to observe your direct reports' Style, the better you will be<br />

able to adapt your behavior and “Do something for others” (the fourth of the four steps for<br />

improving your managerial effectiveness) and earn the support and respect of your direct<br />

reports.<br />

b. It is important to understand that observing your direct report's behavior in order to determine<br />

their Style is not an automatic or mechanical process. Just like any other skill, it takes practice.<br />

c. It helps to keep in mind the six rules to aid you in this process.<br />

3. Ask participants if they have any questions about the rules.<br />

4. Tell the participants that the handout can be used as a quick reference when identifying their coworkers’<br />

Styles.<br />

© <strong>The</strong> <strong>TRACOM</strong> Corporation, All All Rights Reserved.<br />

FACILITATOR<br />

GUIDE<br />

63

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!