louisrosenfeld.com logotype

Home > Bloug Archive

Aug 30, 2005: Do Not Force, Obligate, Regulate, or Require...

Nice short piece by James Robertson on "losing the language of enforcement" that centralized enterprise teams often use when communicating with decentralized individuals and groups, such as content authors. James provides a nifty list of banned words (e.g., "regulations," "compliance"), and suggests taking a "leadership and coaching role" when communicating with authors.

I agree, although leadership and coaching don't come naturally to everyone. Nor does an entrepreneurial approach, where the central team approaches decentralized players as clients (anyone who has attended my EIA seminar will tell you that I'm a big proponent of this approach).

Really, the best place to start is to consider the communication strengths found among members of a central team. Play to those strengths, and balance them against the communication styles that go over best with the authors and anyone else with whom you're negotiating.

Another example of common sense stuff that's all-too-often uncommon...

email this entry

Add a Comment:

Name

Email

URL (optional, but must include http://)

Required: Name, email, and comment.
Want to mention a linked URL? Include http:// before the address.
Want to include bold or italics? Sorry; just use *asterisks* instead.

DAYENU ); } else { // so comments are closed on this entry... print(<<< I_SAID_DAYENU
Comments are now closed for this entry.

Comment spam has forced me to close comment functionality for older entries. However, if you have something vital to add concerning this entry (or its associated comments), please email your sage insights to me (lou [at] louisrosenfeld dot com). I'll make sure your comments are added to the conversation. Sorry for the inconvenience.

I_SAID_DAYENU ); } ?>