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:
- Saying No
- When we have to say "no" to customers or to people in power, we're often tempted to placate
with a "yes." There's a better way: learn how to say "no" in a way that moves the
group toward joint problem solving.
- Corrosive Buts
- When we discuss what we care deeply about, and when we differ, the word "but" can lead us
into destructive conflict. Such a little word, yet so corrosive. Why? What can we do instead?
- Dealing with Condescension
- Condescending remarks hurt. When we feel that pain, we often feel the urge to retaliate, even when retaliation
might not be appropriate. Our responses are more effective when we understand where condescending remarks
come from.
- Start the Meeting with a Check-In
- Check-ins give meeting attendees a chance to express satisfaction or surface concerns about how things
are going. They're a valuable aid to groups that want to stay on course, or get back on course when needed.
- The Risks of Rehearsals
- Rehearsing a conversation can be constructive. But when we're anxious about it, we can imagine how it
would unfold in ways that bias our perceptions. We risk deluding ourselves about possible outcomes,
and we might even experience stress unnecessarily.
See also Effective Communication at Work and Project Management for more related articles.
Forthcoming issues of Point Lookout
- Coming April 24: Antipatterns for Time-Constrained Communication: 1
- Knowing how to recognize just a few patterns that can lead to miscommunication can be helpful in reducing the incidence of problems. Here is Part 1 of a collection of communication antipatterns that arise in technical communication under time pressure. Available here and by RSS on April 24.
- And on May 1: Antipatterns for Time-Constrained Communication: 2
- Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 2 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing those that depend on content. Available here and by RSS on May 1.
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
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