After releasing Inbox in May 2015, the free supplement to Google’s primary email service, Gmail, was taken offline in April 2019. Luckily, many of the popular features found in Inbox have been integrated into Gmail, so users can still enjoy the increased productivity promoted by many of Inbox’s helpful functions. In this article, we’ll consider several Inbox features and look at how we can recreate them in Gmail.
Among other things, the social intranet suite Linchpin enhances Confluence by offering users the opportunity to receive personalized company news in a visually appealing format. Linchpin News Digest is a new extension for Confluence and Linchpin that has just been launched by the //SEIBERT/MEDIA development team. The solution has not only been created to broadcast news in Linchpin Intranet but also deliver it to users via email on a regular basis. Here we look at the various use cases.
We were delighted to have the opportunity to interview Nick Muldoon and Teagan Harbridge from Easy Agile about two very useful Jira apps, as well as the GDPR and other very topical issues in the technology sector.
You probably already know about Gmail, but are you aware of Google’s new Inbox by Gmail? Inbox is Google’s modern mail service and it’s what Gmail should have become long ago. If you use Gmail, you should definitely check out Inbox. Or maybe not? Now Google has updated its Gmail mail service with many of Inbox’s features, all while remaining true to Gmail’s philosophy. In order to help you decide whether you want to use Inbox by Gmail or the new Gmail, read ahead to find out everything you need to know about the features and possibilities of the two options.
Email continues to be the main medium for digital communication in many companies, and at the same time is one of the biggest time wasters and productivity killers. Email is fast, convenient, and normal – and is often abused to a greater degree than any other digital communications technology.
One of the biggest problems is that email communication is frequently ‘unofficial’, as the contents are not centrally documented, transparent, and available to the entire organization. This does not mean that I want to condemn email as a whole – there are good and bad emails.
We have collected 99 reasons, that speak for the implementation of HipChat in your team and in your organization – all very compact and nearly all within the length of a tweet of 140 characters.
A few days ago, I had to put up with Winfried Felser calling me a “fake.” It was meant as a joke because I had told Winfried that some of my tweets are automatically generated from a blog and our public microblog. In a way, he is right. I really did up my Twitter game in October or November last year – first via Buffer and now Hootsuite. It’s been working really well so far. And I’ve always answered and responded personally and will continue to do so.
Most people suffer from the daily load of emails. I have met people who claim that it is not a big issue, but they also tell me that it’s just because the amount of emails they receive is fairly low. We can all feel the pain that emails create. And most know that the using email is often unappropriate. But how do we know when to email and when to go for a better alternative? That’s unsolved for most people. Most of the time we don’t even know what the appropriate action is. And often we fail to act professionally, although we know better.
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?