All posts by Martin Seibert

Organizational differences between intranet and Internet

You do not need to be an Internet professional to recognize the basic difference between a company’s intranet and its online presence. An intranet, the internal system, is protected against external access and contains non-public information. Online content, however, can be accessed by anyone. If you take a closer look, it’s clear that many different aspects must be considered and play an important role. We will therefore turn our attention in these two articles to the question of how to differentiate between an intranet and a website. First, we will look at the organizational aspects before dealing with the technical aspects in the following article.

36 use cases for an enterprise microblog (25 – 36)

The digital form of the talk in the hallway, where employees exchange information, news, ideas and project details and receive feedback and input, are a benefit for enterprises. But what are specific use cases for an enterprise microblog? We have collected 36 use cases. After use cases 1 – 12, and 13 to 24, the remaining 12 use cases are collected here.

36 use cases for an enterprise microblog (13 – 24)

The digital form of the talk in the hallway, where employees exchange information, news, ideas and project details and receive feedback and input, are a benefit for enterprises. But what are specific use cases for an enterprise microblog? We have collected 36 use cases. After the first twelve, read more about use cases 13 to 24.

36 use cases for an enterprise microblog (1-12)

An internal microblog can become a useful channel of communication within an enterprise. Similar to having lunch or coffee together, or chatting in the hallway, employees exchange information, news, ideas or project details in a microblog. Sometimes the posts are time sensitive and important, sometimes they are just about exchanging ideas with colleagues and getting their input. Enterprises can benefit from that. What are specific use cases, and how can the internal tweeting gain strength? We have collected 36 use cases. Here are the first dozen.

Texts should be created, shared, and edited in a Wiki, not in Word or within e-mails

Within a company there can be many approaches for the development of texts as well as the sharing of texts for further revision. We could, for example, write a text in Word and then load the final version into the enterprise wiki. We could also send around texts by e-mail, asking colleagues to read them and, if necessary, to make changes. But we could also develop a text directly within a wiki. What should we think of this particular work process?