I never thought I’d be such a huge fan of team retrospectives. I used to dismiss them as irrelevant for non-engineering teams, or as a twin of the post-mortem (which typically only takes place when something goes wrong, and too often involves feelings of regret and blame). But my attitude changed immediately when I started taking part in retros at Miro.

Let’s track the timeline of responses over the last twenty years… IDC reports that workers who manage, create, or edit documents for a company were spending up to 2.5 hours per day searching for what they needed.

When Mattermost first started, it didn’t make sense for us to have an office; it was just myself and one other person. They were writing code the whole time, and I was on the phone the whole time, and being in the office we ended up interrupting each other. So eventually we started working from our homes and only got together when we needed to catch up.

I’m very excited to announce the general availability of Mattermost Cloud starting today. The new offering brings Mattermost’s industry-leading open-source, self-managed collaboration platform to the cloud as a SaaS platform.

“It was the best of times, it was the worst of times, it was the age of wisdom, it was the age of foolishness…” So begins the classic novel, A Tale of Two Cities, by Charles Dickens. It refers to the premise of the story: A time of despair and suffering on one hand, and joy and hope on the other.

One of Teamwork CRM’s guiding principles is to allow our customers map Teamwork CRM to how they work, rather than having our customers change the way they work to accommodate Teamwork CRM. For that reason, we put significant emphasis on giving users the power to customize Teamwork CRM, whether it is their pipelines, stages, rotting periods, activity types, or, of course, custom fields.