Google Wave Withdrawal? Cure it with Xtrant.

When Google Wave was announced back in 2009, I will admit, we were kind of worried. Here we were translating our founding application (The Sposto Interactive Extranet – launched back in 2004) into what is now Xtrant, our goal to give the world the power of productive sharing that helped make our small firm compete on a large stage.

Then suddenly the all powerful Google announced Google Wave – and declared a similar mission – including that of being an “email killer.”  Dammit, that’s what we wanted to be – and actually are.  (In fact, one of our most active customers REQUIRES all of their clients to communicate to them only via Xtrant.  No emails allowed.  They have started over 200 projects in our system since our soft launch in November – and they aren’t the only ones killing their email with Xtrant.)

Back to Google Wave – we honestly didn’t shed many tears at it’s demise – though we hoped WE would be the ones to get it right – strike the right balance between project management, client communication, social engagement and collaboration.

From what we’re hearing from our customers, we have struck that balance – and one comment we’re repeatedly getting is “Wow, Xtrant is like Google Wave, only it’s easy to use and understand.”

Screen Shot 2013-01-24 at 8.03.25 PM

Clear and easy to follow.


A little confusing.

How is it similar?  Think of each Xtrant project as the equivalent of a WAVE…add the people you are working with, and keep all of your interactions and communications and  assets you are sharing, etc, in one place.  As that project grows – everything shared and discussed turns into a running log of your progress – a reference point for that topic.  The power of context keeps everyone, literally, on the same page.

So don’t despair – come and surf the Xtrant wave!

Using the Simple Power of Classified Content

One of the things we strive to do with Xtrant is eliminate the therbligs The fewer steps it takes to complete a task, the fewer movements–the fewer times you have to think within any process–the more efficient and natural the experience is, and the more useful and powerful the tool. Combining power with simplicity is a touchstone we judge all of our decisions against – and “classified content” is an excellent example of this philosophy in action.

Within a single project you might have team members with different levels of responsibility.  You may be collaborating between vendors, employees, clients and other stakeholders; some of whom need access to sensitive material that others within the project aren’t privileged to see. Our simple solution is to allow you to specify who can see classified content on a project by project basis, and mark P&R (Presentation & Review) Assets as classified when you post them.

For example, you might want to make your internal team classified and post iterations and process documents for discussion as classified content, while posting client-ready deliverables as non-classified that everyone (including the client) can see and discuss. Or you may make your project leads, sales people and customer leads involved with negotiations able to “view classified content,” so they can share contracts and price lists, without exposing sensitive information to vendors, contractors or non-management personnel .

The following images show how the process works.

First I’ll add Mike to the project, marking him able to “view classified content.”

Now I’ll add two assets, a photo that anyone can see, and a contract that has sensitive information in it. I mark the contract “classified.”

Since Mike can “view classified content” he can see both files.

When I add Amy to the project, I DON’T mark her able to “view classified content.”

Amy can see the “unclassified” photo in this P&R group, but not the “classified” contract.

In actuality, Amy is always allowed to see classified content, because she’s our “Director of Business Development.”  While you’re at it, do her a solid and sign up for Xtrant now - it’s getting more powerful every day.