只有当更新的保质期很短，并且将它们分散在其他更新中时，Twitter 可能才合适。 t 具有破坏性。
任何此类第三方服务还存在保密问题。
I would consider what the reports were meant to accomplish, and then discover a solution that accentuated that objective without being a logistical nightmare :)
Twitter might only be appropriate if the updates had a short shelf life, and if scattering them among other updates wasn't destructive.
There's also a question of confidentiality on any 3rd party service like this.
I can see the appeal of using twitter in this way. Where I work, we send a daily project "snapshot" to basically everyone else in the company. As the company grows (we are nearing 35 employees now), this is becoming a bit of a burden to read through (or at the very least file/delete) all the status emails as they arrive. I don't know that I could see Twitter replacing these emails, however, because these emails are not necessarily supposed to tell someone when something is completed, but rather to tell someone what it is I'm working on today, and what my upcoming projects are in the future.
I guess most of our project updates are actually done more frequently in person. For larger projects, we now employ what's referred to as a "burndown". This basically means we gather for a quick re-estimation of how much work is left on a project, which then results in a nice graph that should show whether the project is on track or not.
We do also throw in the occasional email when there's something more immediate, or if someone isn't available for discussion/notification.
Many of my colleagues are posting work updates on Twitter, being careful not to disclose company confidential information. From those working on open commercial development projects, I've even seen Twitter updates indicating which work item they were working on. Coolness.
We use Laconica on my team, it's very useful for those updates that you want to send to the whole team but aren't really worth wasting an email on.
Since only my team is using the installation of Laconica that we have, I take the RSS for the public feed and I integrated that into SharePoint.
So while the developers and PM's on our team use Twhirl to manage sending and recieving updates, management is still able to see the updates directly on our team site.
It's quite transparent in that nobody actually has to go to the Laconica instance I have setup to do anything except initially register.
发布评论
评论（11）
WordPress 的Prologue 主题在设计时就考虑到了这一点。
The Prologue theme for WordPress was designed with this in mind.
查看 https://presentlyapp.com/
Check out https://presentlyapp.com/
我会考虑这些报告的目的是什么，然后找到一个解决方案，既能强调这一目标，又不会成为后勤噩梦:)
只有当更新的保质期很短，并且将它们分散在其他更新中时，Twitter 可能才合适。 t 具有破坏性。
任何此类第三方服务还存在保密问题。
I would consider what the reports were meant to accomplish, and then discover a solution that accentuated that objective without being a logistical nightmare :)
Twitter might only be appropriate if the updates had a short shelf life, and if scattering them among other updates wasn't destructive.
There's also a question of confidentiality on any 3rd party service like this.
我可以看到以这种方式使用 Twitter 的吸引力。 在我工作的地方，我们基本上向公司的其他所有人发送每日项目“快照”。 随着公司的发展（我们现在员工人数已接近 35 名），在所有状态电子邮件到达时通读（或至少归档/删除）它们变得有点负担。 然而，我不知道 Twitter 会取代这些电子邮件，因为这些电子邮件不一定要告诉某人某件事何时完成，而是告诉某人我今天正在做什么，以及我即将做什么项目是在未来。
我想我们的大部分项目更新实际上都是亲自更频繁地完成的。 对于较大的项目，我们现在采用所谓的“燃尽图” ”。 这基本上意味着我们收集数据以快速重新估计项目还剩多少工作，然后生成一个漂亮的图表，显示项目是否步入正轨。
当有更直接的事情或者某人无法参与讨论/通知时，我们也会偶尔发送电子邮件。
I can see the appeal of using twitter in this way. Where I work, we send a daily project "snapshot" to basically everyone else in the company. As the company grows (we are nearing 35 employees now), this is becoming a bit of a burden to read through (or at the very least file/delete) all the status emails as they arrive. I don't know that I could see Twitter replacing these emails, however, because these emails are not necessarily supposed to tell someone when something is completed, but rather to tell someone what it is I'm working on today, and what my upcoming projects are in the future.
I guess most of our project updates are actually done more frequently in person. For larger projects, we now employ what's referred to as a "burndown". This basically means we gather for a quick re-estimation of how much work is left on a project, which then results in a nice graph that should show whether the project is on track or not.
We do also throw in the occasional email when there's something more immediate, or if someone isn't available for discussion/notification.
或者，Laconica 上面的层称为 Identi.ca 与 Identi.ca 的创始人就此类用法进行了很好的讨论位于IT 对话。
Or, the layer above Laconica called Identi.ca There's a good talk with the founder of Identi.ca about such usage over at IT Conversations.
我的许多同事都在 Twitter 上发布工作动态，小心翼翼地不泄露公司机密信息。 对于那些从事开放商业开发项目的人，我什至看到 Twitter 更新表明他们正在从事哪个工作项目。 凉爽。
Many of my colleagues are posting work updates on Twitter, being careful not to disclose company confidential information. From those working on open commercial development projects, I've even seen Twitter updates indicating which work item they were working on. Coolness.
保密性和信息安全怎么样？ 我确信公司运营的 IM 服务将是更好的选择。
我认为 Twitter 和类似的服务可以用作吸引客户和潜在客户的营销工具。
What about confidentiality and information security? I'm certain a company run IM service would be a better alternative.
I've viewed Twitter and similar services to be used as marketing tools to engage customers and prospects.
也许尝试 campfire 或 大本营。
Maybe try campfire or basecamp.
我们在我的团队中使用 Laconica，它对于您想要发送给整个团队但不值得浪费电子邮件的更新非常有用。
由于只有我的团队正在使用我们安装的 Laconica，因此我将 RSS 作为公共源，并将其集成到 SharePoint 中。
因此，虽然我们团队中的开发人员和 PM 使用 Twhirl 来管理发送和接收更新，但管理层仍然能够直接在我们的团队网站上查看更新。
这是非常透明的，因为除了最初注册之外，实际上没有人需要去我设置的 Laconica 实例做任何事情。
查看这篇文章，了解有关如何将 Laconica 与 SharePoint 集成的信息：如何将 Laconica 更新流集成到 SharePoint 中？
We use Laconica on my team, it's very useful for those updates that you want to send to the whole team but aren't really worth wasting an email on.
Since only my team is using the installation of Laconica that we have, I take the RSS for the public feed and I integrated that into SharePoint.
So while the developers and PM's on our team use Twhirl to manage sending and recieving updates, management is still able to see the updates directly on our team site.
It's quite transparent in that nobody actually has to go to the Laconica instance I have setup to do anything except initially register.
Check out this post for information on how I integrated Laconica with SharePoint: How can I integrate Laconica update stream into SharePoint?
尝试 Laconica：一个类似 Twitter 的开源系统，您可以在自己的服务器上运行。
Try Laconica: An open source Twitter-like system you could run on your own servers.
请访问 http://www.yammer.com 了解 Twitter 的企业版本。
Look at http://www.yammer.com for a corporate version of twitter.