In the old days, I used to get a memo with some newsclippings in my in-tray that we would all read and then we would initial it and pass it around. I find that emails disappear into Outlook. Begging people to read my blog isn't fun. RSS feeds have a lot of marketing junk. And just plain keeping up with the amount of content takes up a lot of time. With today's tech, what's the best way to find meaningful info about my industry, put together a quick take on things and share it with my larger team?
closed as too broad by gnat, Jim G., Michael Grubey, IDrinkandIKnowThings, Garrison Neely Aug 10 '14 at 15:20
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
With today's tech, what's the best way to find meaningful info about my industry, put together a quick take on things and share it with my larger team?
There are many, many ways to find information about your industry. Websites, blogs, Google Alerts, conferences, friends, etc, etc - all can contain information that you might find useful.
As far as sharing it with your larger team, there are also many ways. A quick email with a link to the source, an intranet page, a corporate wiki, a department newsletter - all could be a good vehicle.
You haven't indicated what your role with your "larger team" is. If you are a Manger or Lead, sending something around that you feel is useful is very reasonable.
If you are a peer, you may want to get a sense of how your peers feel about what you are sending/posting, and dial it back a bit if they start to feel "nagged".
I created a folder of industry-related information in my department's corporate intranet site (I'm the Director of the department). Before doing so, I asked my team if they would find such information useful, and if they would contribute as well. Some have contributed, some just read.
I also have a personal blog, that a few of the folks on my team read. I don't send them links to that blog, as I don't want to be pushy, although I have paraphrased items and sent them on occasion.
Create a good feedback loop for yourself, then try something. Be prepared to revise it if it isn't giving your audience what they (and you) feel they need. That way, over time, it will become more and more useful.
I believe the 21st century name for this is "curated content."
I have done this the old-fashioned way you describe -- pass around the weekly copy of EE Times with yellow sticky notes.
I've also done it with an internal wiki. That's a good way for a team to do things because anybody can contribute. But it takes real work to get an internal wiki to the tipping point, where the whole team uses it.
Blogs work. But people don't read stuff like that. If you put the following line in the third paragraph of a blog post I suspect you will be safe: "If you read this, come to me, tell me this password -- unicorn -- and I will give you x dollars."
Some colleagues are doing it with a web site called paper.li . That seems to have some power.