This means: getting information presented within the same context without having to move from one page to another or switch applications. The next paragraphs will show what some new features have in common with the concept context.
Of course the possibility to post Statusupdates to a particular Community helps to prevent information overload as well. Instead of posting a Statusupdate to the whole organisation (anyone who is following me), I can direct certain information to a specific target group through posting it to a specific Community.
Events are a great way of making Communities all about work. All the meetings important to Community members can be posted as an event, to which any member can subscribe. Why not just use the Lotus Notes (or Outlook) Calendar scheduling instead? I can give some arguments for working openly through Community events.
A Related Community shows up on the overview page and pulls in recent activity from one into the other. It could be that you wish to bridge two Communities on the same Connections environment. Maybe because they are covering the same or are somewhat related. It could be a project Community that wants to bridge work done in another project because what happens in one is relevant for the other. Even Communities on different Connections environments can be bridged. Thus allowing to collaborate in two environments without losing oversight. Maybe you have an internal directed Community on one server, and an external directed one on another where you collaborate with clients or partners. From the internal Community you can relate the external Community to it, so you can keep track of what's going on in both all from the same context.