FB Twitter LinkedIn { "@context": "http://schema.org", "@type": "Organization", "url": "http://www.mazey.co", "logo": "https://static1.squarespace.com/static/58c747ca37c581e14107f015/t/5af60b592b6a287acaffc86d/1526074208107/M+Icon+White+on+Blue+1024x1024.png?format=2500w" }

The Mazey Story

We built Mazey because we believe that teams deserve a better way to communicate, share knowledge, and track tasks than email or group chat.

Our gripes with email will sound familiar.

It’s too easy to leave people out of the information flow. Important communication gets lost in crowded inboxes. Reply-all chains are a horrible way to have a conversation. There is no common, shared updateable repository of important content, and if you want to track tasks, you need a separate tool.

Multi-channel chat was supposed to be the panacea for email’s ills, but we think that it still comes up short.

While the transparency it creates is wonderful, even with many, many open channels conversation topics tend to pile on top of each other in messy ways. This makes it hard to keep discussions on-point and arrive at decisions. It also means that the team is either “always-on” or some conversations scroll away without the benefit of everyone’s thoughtful engagement. Chat also fails to solve the knowledge repository problem: sure, you can post notes and files, but they become surprisingly difficult to retrieve after they scroll off screen. Oh, and there is still no task tracking.

Mazey takes a different approach. With Mazey, you can still have tactical conversations in chat channels, but most content and discussions live in lightly structured sharing spaces called Noteboards.

In addition, chat streams are connected to each piece of content, which gives them specific framing and context. Each note or file and its attached discussion becomes a valuable, compartmentalized and atomic knowledge artifact that can be easily retrieved when needed. Also, because the conversations are much more finely threaded, they can happen more slowly and thoughtfully … even asynchronously. We also added task tracking, because, you know, it was missing.

We created Mazey for mobile users first, because teams that don’t work in front of a computer (think retail, hospitality, construction, etc…) don’t really have the luxury of stringing together Slack, Asana, Evernote and Dropbox with APIs - it’s just too hard! But we hope that any team can benefit from Mazey.

Thanks for checking us out and please let us know what you think at feedback (at) mazey.co.