![The first page of Thomas Paine's pamphlet Common Sense The first page of Thomas Paine's pamphlet Common Sense](../images/common-sense.png)
The first page of Thomas Paine's pamphlet "Common Sense," which appeared in 1776. In the first three months of publication, it sold 120,000 copies, which is impressive when one considers that the entire population of the Colonies at the time was under 3 million, many of whom were illiterate. That's one copy for every 25 inhabitants. Common Sense became the best-selling printed work by a single author in American history up to that time, illustrating the power of the written word.
Your internal newsletter isn't likely to achieve such broad social impact, but it can nevertheless exhibit the power of the written word by keeping your stakeholders well informed about the issues and progress of efforts for which you're responsible. Photo courtesy WikiPedia.
Whether you're responsible for a project, a department, a division, or a company, publishing an internal newsletter — by email, Web page, SharePoint, Facebook, whatever — can be an effective means of keeping stakeholders informed about what has happened, what is happening, what you believe will happen, and what you believe won't happen.
A newsletter can become the authoritative source of information about the effort. Although it can establish you as someone who truly understands the importance of stakeholder relations, there is a risk. You don't want to flood readers with information they consider irrelevant to their special interests.
Here are some tips for creating a newsletter that informs but does not overwhelm your stakeholders.
- Keeping people in the dark is expensive
- If you don't keep stakeholders informed, you're leaving space for them to make stuff up. Publishing what you do know is far more effective than letting others make up what they don't know.
- Make it a quick list of short items
- Limit the length of each item to the length of a tweet — about 140 characters. Most people don't want to read long dissertations.
- Make each item a headline, nothing more
- Full explanations are unnecessary. Each item can be little more than a teaser to let the reader know what the impact is. Use the "So What?" test to develop a headline. See "Deliver the Headline First," Point Lookout for May 3, 2006, for more.
- Include a link to a more detailed explanation
- Since some people do need more detail, you must provide it, but don't subject everyone to the full story. Write a more detailed explanation for your intranet site and link to it in the newsletter.
- Squelching rumors is perfectly acceptable
- Some people feel that denying rumors gives them wider circulation, but if you've heard the rumor, almost everyone else has, too, and thus wider circulation isn't really an issue. Squelch rumors, but be right about what you say. See "There Is No Rumor Mill," Point Lookout for March 26, 2003, for more.
- Get out in front of rumors
- If you'll Some people feel that denying
rumors gives them wider circulation,
but if you've heard the rumor,
almost everyone else has, toobe doing something that you expect will be controversial, why wait for rumors to form? If you get there first with real information, you're less likely to have to deal with rumors. - Feature people and teams who contribute to success
- Short features describing the talents and contributions of key people are interesting to your stakeholders for the same reasons that features are interesting to news consumers in the media generally. Give the enterprise the information they need to gain a true appreciation of the efforts of the people you feature.
- Feature new people
- Use your newsletter to introduce people who are new to the effort. Tell your stakeholders about their background and about the contributions you anticipate.
Whatever you decide to do, have your newsletter reviewed by someone who has a grasp of good writing, relevant content, and the needs of your readers. Top
Next Issue
Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!
Your comments are welcome
Would you like to see your comments posted here? rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.comSend me your comments by email, or by Web form.About Point Lookout
Thank you for reading this article. I hope you enjoyed it and
found it useful, and that you'll consider recommending it to a friend.
This article in its entirety was written by a human being. No machine intelligence was involved in any way.
Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.
Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.
Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.
Related articles
More articles on Effective Communication at Work:
Dismissive Gestures: I
- Humans are nothing if not inventive. In the modern organization, where verbal insults are deprecated,
we've developed hundreds of ways to insult each other silently (or nearly so). Here's part one of a
catalog of nonverbal insults.
Have a Program, Not Just an Agenda
- In the modern organization, it's common to have meetings in which some people have never met —
and some never will. For these meetings, which are often telemeetings, an agenda isn't enough. You need
a program.
Some Truths About Lies: III
- Detecting lies by someone intent on misrepresentation is an important skill for executives, managers,
project managers, and just about anyone involved in knowledge-oriented organizations. Here's Part III
of our little collection of lie detection techniques.
Exasperation Generators: Irrelevant Detail
- When people relate stories at work, what seems important to one person can feel irrelevant to someone
else. Being subjected to one irrelevant detail after another can be as exasperating as being told repeatedly
to get to the point. How can we find a balance?
Reframing Revision Resentment: II
- When we're required to revise something previously produced — prose, designs, software, whatever,
we sometimes experience frustration with those requiring the revisions. Here are some alternative perspectives
that can be helpful.
See also Effective Communication at Work and Project Management for more related articles.
Forthcoming issues of Point Lookout
Coming July 3: Additive bias…or Not: II
- Additive bias is a cognitive bias that many believe contributes to bloat of commercial products. When we change products to make them more capable, additive bias might not play a role, because economic considerations sometimes favor additive approaches. Available here and by RSS on July 3.
And on July 10: On Delegating Accountability: I
- As the saying goes, "You can't delegate your own accountability." Despite wide knowledge of this aphorism, people try it from time to time, especially when overcome by the temptation of a high-risk decision. What can you delegate, and how can you do it? Available here and by RSS on July 10.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout are available in six ebooks:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, )
- Get 2003-4 in Why Dogs Wag (PDF, )
- Get 2005-6 in Loopy Things We Do (PDF, )
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
- Get 2009-10 in The Questions Not Asked (PDF, )
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )
Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info
Follow Rick
![Send email or subscribe to one of my newsletters](../images/social-icons/email-32.png)
![Follow me at LinkedIn](../images/social-icons/linkedin-reg-32.png)
![Follow me at X, or share a post](../images/social-icons/x-32.png)
![Subscribe to RSS feeds](../images/social-icons/feed-icon-32.png)
![Subscribe to RSS feeds](../images/social-icons/facebook-icon-32.png)
Recommend this issue to a friend
Send an email message to a friend
rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
![Technical Debt for Policymakers Blog](../images/logos/techdebtpolicy-logo-sm-1.png)