Messenger apps are huge already

Granted, we also believe this, that’s why we are investing in building Kezmo, a customizable messaging platform that can be setup on premises, so Enterprises can get the best of both worlds.

Chatbots are going to be huge (yyuuuuge)

We believe that chatbots will play a major role in the future of human computer interactions, and yes we think they are going to act as the trojan horse for the arrival of artificial intelligence. Still, the hype around the subject does not quite match the fundamentals. I don’t on a daily basis use or interact with any chatbot. The people I know don’t. Every chatbot interaction I’ve had has been in the context of toying with a new technology. I have not adopted it in any scenario yet, and I don’t know anyone who has. So, while I’m bullish on bots, and Kezmo will serve as the foundation for the deployments of bots either the technology is not quite there yet, or otherwise

It doesn’t seem that far ago when free apps were able to generate hundreds of downloads per day just by the mere fact that they were free, and the app store was new. This dynamic is dead. If you are publishing anything to the app store, make sure to generate traction for it independently, relying only on the app store for marketing an app is not an option anymore, no matter how much app store search optimization time you put in.

Closing thought: are we comparing apples to oranges?

We can all agree the app store user experience is a mess, and both Apple and Google need to make changes asap to inject some life back in the app ecosystem. On the other hand chatbots seem like a promising investment despite imho the lack of true traction yet. To what extent are these two phenomenons related? Are we comparing apple to oranges?

We will be showcasing Kezmo to the world, in the startup alley, in the Uruguay pavillion. Kezmo is an enterprise chat and collaboration platform to help teams get things done. Yes, we too are trying to to kill email, but we will succeed were others have miserably failed. We are experimenting with visual ways to navigate contents which we believe is critical for handling and prioritizing large volumes of interactions.

Kezmo is available in the cloud or you can set it up on premises. It’s localized in several languages, which is not a minor thing when fostering adoption of these type of tools in the enterprise environment.

While Kezmo is still in a closed beta phase, if you stop by our booth we just might hand out an invitation to you 🙂

We are working hard, jumping through hoops and loops to have everything ready for the event. So if you are at the TechCrunch Disrupt please do stop by the Alley to say hi and get some of the gifts and surprises we are given out!

Email collaboration is broken, still to this date a lot of companies base their online digital collaborations on email. Typically for external collaborations, but sometimes even for internal ones. Even if it’s not THE technology sponsored for that end it coexists with a number of email alternatives in the organization, and it usually works as the fallback enterprise collaboration technology.

The good things about email

While a lot of people have been prophesying it’s death the truth is that email has some very good points going for it. It definitely has some advantages, such as:

It’s simple and widely adopted. It’s a very basic paradigm based on the notion of sending, replying and forwarding messages. Additionally it’s among the most widely adopted technologies of the internet. Everyone has an email address. So there are network effects at work here, an example of a technology whose value increases with it’s rate of adoption, and in this case almost every internet user has adopted so go figure it’s value.

It’s reliable and relatively inexpensive. Email messages arrive regardless of the distance involved, and setting up a mail server is a very documented procedure. There are several open source, and off the shelf alternatives, both on premises, and on the cloud.

It’s an open garden. Provided you have someone’s email address you can message with him, you don´t have to provide further personal information, there are no registrations involved, no setups, no hassles. While there´s a dark side to this, for beginners and spreading adoption is great.

It enables work/life balanced time management. In terms of managing expectations for turn around times common network etiquette allows you to wait a few hours, or even days before replying an email. It’s not real time. Plus you can turn auto respond for vacations. Point being that from a work/life balance and time management perspective it allows for a much needed wiggle room to put work stuff on hold.

What’s broken about email collaboration?

Among email shortcomings when it comes to enterprise collaboration are:

SPAM. The same open garden quality mentioned above enables strangers to contact you for whatever reason, such as trying to sell you something. It’s like a cognitive tax you have to pay to sort through all the messages you get to filter and categorize. It’s such an issue that a whole industry of spam filters was born to attempt to fix this problem, but at it’s core is still present. Anyone can pass along your email address to another stranger allowing them to contact you without your consent.

Email is really a bad fit for conversation type of interactions. Particularly among several people. Before you know it you have tens of unread emails, some of them which are one liners, with “Me too” responses and it can take really a long time before you figure out where’s the substance, or agreements that were reached as part of the exchange. It’s just not a good medium for conversations, and that sucks because team collaboration is to a good extent a ongoing conversation.

You don’t have confirmation of delivery and read from the other part. Unless the recipient is kind enough to reply with some form of acknowledgment message, the sender does not know whether the message has been read or if has fallen through the cracks of spam. Sometimes in corporate scenarios it’s not just a nice to have feature, but an audit level required by the business process.

It really is horrible for team collaborations and document collaborations. For instance if several people have to collaborate on document, it’s normal for everyone to send their version of the modified document, sometimes including previous work from someone else, but sometimes not. Leading to a number of email threads all with attached versions of the document in question. It can quickly become an nightmare to determine what’s the latest version, or what are the differences between these versions to consolidate everyone’s work.

Turn around time is awful for remote teams. It’s not real time, or close to. In some contexts, specifically for remote teams that are not in a call conference that requires constant interactions, but they are working on the same thing. It’s good to be able to exchange perspectives, and shoot quick questions and get a yes or no answer within minutes, in “close to real time’ time frames.

No support for complex types. Everything is a message. Why typing content is important you may ask. Well, different types of content involve different presentations, and enable different behaviors, and actions. Different types enable different life cycles. For events you need a reminder and will probably want to see it in a calendar. For tasks you will want to see who it is assigned to, it’s due date, and will probably need to be able to mark them as completed. For purchase orders you will want to approve them or reject them, etc. A lot of vendors have implemented applications attempting to attach, or meta morph an email message into something else, and had to cope with the fact that at it’s core that remains an email message which you can reply and forward.

The inbox as a sink for everything. The email inbox as the sink where all content flows no matter it’s nature can be a problem. Even if you try to have different email accounts for different purposes, you can only separate things so far. In most companies you will only get one email account, which will act as an inbox of all work related communications. Jokes from your workmates, with me too one liners, with important client exchanges are all in the same place. If the amount of emails arriving is high, it is a matter of time before you miss an important message. Because the platform does not make it easy to separate the wheat from the chaff, to separate the signal from the noise.

What’s next for enterprise collaboration? There has to be a better way

Well collaboration in the workplace is changing. A number of new consumer technologies have appeared over the past years which have generated different use patterns. While email is not dead yet, young generations are less ready to write page long emails and more prone to have spontaneous chat interactions. It’s the facebook, whatsapp & snapchat generation.

There’s a new wave of business applications that attempt to address this challenge by leveraging a conversation centric paradigm for collaborations in the workplace. Among them applications such as HipChat, and Slack.

We are building an email alternative of our own design. It’s called Kezmo, and it’s designed to achieve the best of both worlds. Conversation based (near real time) interactions while enabling good expectation management of turn around times. For instance providing feedback on whether or not a message has been delivered and read. Allowing users to structure content with different types, enabling different displays and behaviors for them.

After over a year of effort we are approaching the release date for our enterprise messaging and collaboration application, which we have named Kezmo (how and why that name could be the topic for a couple of posts on itself).

There are a number of reasons why we believe we may have something to add of value to the enterprise collaboration and content management market segment, among them our experience as consultants implementing SharePoint solutions for years, and later implementing leading mobile client for that platform.

The enterprise collaboration market is huge and is going through massive changes, which spans risks and opportunities. Some of the conceptual foundations we’ve been building on are the following:

Group chats are ubiquitous. Whatsapp has managed to change how the world communicates, it’s become a game changer. User experience expectations in the workplace are changing accordingly to their consumers day to day experience.

The group chat dynamic has been proven useful in the work environment. There are several high profile collaboration applications, Slack, and HipChat among them, that are making clear that the conversation centric collaboration model is here to stay.

The pendulum is swinging far to the chat side of things. Currently in most systems everything is a chat message which creates a number of challenges, such as: finding content, avoiding misunderstandings, staying up with the latest status of things.

Offline and nearby support is being overlooked in most collaboration solutions out there. Data entry and even collaboration capabilities without connectivity is key to a lot of business scenarios. The technology is slowly getting there for nearby networking.

There’s a backlash to the massive migration to the cloud based on security concerns. Corporations need more control over where and how their data is storaged. A cloud only application does not make the cut for big companies.

The information overload is such that we need new, more visual ways to navigate shared content.

Mobile has taken over the world. Enterprise information systems must be mobile first, and have mobile clients as first class citizens.