Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 11, Issue 9;   March 2, 2011: Publish an Internal Newsletter

Publish an Internal Newsletter

by

If you're responsible for an organizational effort with many stakeholders, communicating with them is important to success. Publishing an internal newsletter is a great way to keep them informed.
The first page of Thomas Paine's pamphlet Common Sense

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, too
be 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. Go to top Top  Next issue: Rope-A-Dope in Organizational Politics  Next Issue

52 Tips for Leaders of Project-Oriented OrganizationsAre 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

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.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:

Dogs Fighting in a Wooded Clearing, by Frans SnydersMudfights
When we steer the discussion away from issues to attack the credibility, motives, or character of our debate partners, we often resort to a technique known as the ad hominem attack. It's unfair, it's unethical, and it leads to bad, expensive decisions that we'll probably regret.
Bill Moyers speaking at an event in Phoenix, ArizonaAsking Clarifying Questions
In a job interview, the interviewer asks you a question. You're unsure how to answer. You can blunder ahead, or you can ask a clarifying question. What is a clarifying question, and when is it helpful to ask one?
Langston Hughes, poet and leader of the Harlem RenaissanceThat Was a Yes-or-No Question: II
When, in the presence of others, someone asks you "a simple yes or no" question, beware. Chances are that you're confronting a trap. Here's Part II of a set of suggestions for dealing with the yes-or-no trap.
A dense Lodgepole Pine stand in Yellowstone National Park in the United StatesConversation Despots
Some people insist that conversations reach their personally favored conclusions, no matter what others want. Here are some of their tactics.
Desperation at workReframing Revision Resentment: I
From time to time, we're required to revise something previously produced — some copy, remarks, an announcement, code, the Mona Lisa, whatever… When we do, some of us experience frustration, and view the assignment as an onerous chore. Here are some alternative perspectives that might ease the burden.

See also Effective Communication at Work and Project Management for more related articles.

Forthcoming issues of Point Lookout

NASA's Mars Climate Orbiter, which was lost on attempted entry into Mars orbitComing May 8: Antipatterns for Time-Constrained Communication: 3
Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 3 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing past experiences of participants. Available here and by RSS on May 8.
Typing a text message on a smartphoneAnd on May 15: Should I Write or Should I Call?
After we recognize the need to contact a colleague or colleagues to work out a way to move forward, we next must decide how to make contact. Phone? Videoconference? Text message? There are some simple criteria that can help with such decisions. Available here and by RSS on May 15.

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:

Reprinting this article

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 Follow me at LinkedIn Follow me at X, or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.