When we launched Project Squared in November of 2014, one of the things that was really important to us was to listen to our customers, and to use the things we heard to adjust the experience. We established several “listening posts” – ways for us to get feedback. Analytics and metrics were one way. Another way was a feedback capability right within the application. We encouraged our users to use the feedback feature to report problems, but to also make feature requests or generally tell us what they think.

Within a few weeks of launch, we already started to see some trends in the feedback we were receiving. The number one requested feature that we got – by a long shot – was the ability to leave a 1-1 room. For the engineering team, this was an unexpected request. Why do users want to leave a 1-1 room? After all, if a 1-1 room has no activity, it will downwards in the room list and you won’t see it anymore. So, what is the issue?

What we learned is that other users don’t necessarily use the application in the same way that we do. For other users, a clean room list is a goal. These are also probably the same people that like the zero-inbox model. And for those people, whose goal is to keep the active room list to zero, leaving a room is how they were thinking about cleaning it up. For them, the fact that you could leave a group room, but not a 1-1 room, was a glaring omission in their ability to achieve zero-room-list nirvana.

As a result, we took this new feature request and we prioritized it very high on our backlog. We had some challenges in figuring out how to actually make this work. If a user leaves a 1-1 room, how do they get back in? If the other person sends them a message later on, is it a fresh room with none of the old content, or do they see all of the previous content? If the user searches for the other person, do they find them in the search results? After trying a few models, we settled on the idea that leaving a 1-1 room is mostly about hiding that room from the room list. The room is still searchable by the user, and if a new message is sent or received, the old room content is still there. This model gives the users what they want – the ability to clean up their room list – without losing all of the rest of the benefits of the persistence model that is built into Project Squared. Of course, like other state, the fact that you’ve left a 1-1 room is synchronized across clients. If you leave it on one device, the 1-1 room is removed from the room list on your other devices.

Then, we shipped it. This feature is now generally available within our clients. The current version in the iOS and Android app stores, along with web.projectsquared.com, supports this feature. Our continuous delivery model allowed us – within two short months – gather feedback, analyze the feedback, prioritize the new feature, design the new feature, implement it across all of our clients, built the test automation harnesses to verify it, instrument it for metrics, and then ship it to all users as generally available.

You asked, we listened, and we delivered.

And there’s more to come. Tune in to our webcast on March 17, 2015 for a special announcement.


Jonathan Rosenberg

Cisco Fellow and Vice President

CTO for Cisco's Collaboration Business