Posts Tagged ‘customer’

Customer Entry – GroupSwim Improves Communication Around the Enterprise

September 23, 2008

This post was written by one of our customers (BridgeVine). It is from their blog and describes how they are using GroupSwim. Enjoy.

“Marco”

“Polo”

“Marco”

“Polo”

Too often, office communication is like a child’s game of “Marco Polo” with executives calling out blindly with initiatives or projects, and only some of the team hearing the details or reporting back on progress.

Every company suffers from “communication dissonance,” that random feeling of disconnectedness that comes from not trusting that everyone is on the same page. How may of your employees know all of your company initiatives? How often do employees get stuck using old forms or contracts? How can you monitor what remote teams are doing to collaborate on projects or programs?

GroupSwim, a great online tool, helps bring together the various forms of communication across your company and foster team awareness of issues, large and small.

My company is using GroupSwim for a Intranet Portal in order to keep everyone connected. We have two offices and a variety of remote workers, each of which has different ways to connect to our network. When that happens, we can’t always trust that having information available to the network is the same as having information available to all of our team members.

So, GroupSwim offered us a single point of virtual contact for keeping people informed and keeping information at the fingertips of all of our team members. People can log on, read updates and special messages, get progress reports on current projects, see achievement towards our corporate goals, get the latest phone list or office supply forms, even submit suggestions to our e-suggestion box.

GroupSwim offers much more, though, than just a repository for information and basic file sharing. GroupSwim has functions like a blog or electronic bulletin board where users can start discussions, contribute to projects, and collaborate on any number of programs within the company. It’s a moderated function, so managers can stay in tune with what’s going on in the enterprise.

One of the core tenets of The Business Perspective is finding low or no cost online services to improve productivity or efficiency in your business. GroupSwim offers big value, as they include a free trial, and their monthly fees are very affordable for all businesses.

I recommend GroupSwim for you to try, and I’ll keep people posted on how it works at our company in future editions of The Business Perspective.

“Creating a Vibrant Customer Community” Webinar Summary

September 11, 2008

We held our first-ever webinar yesterday with one of our customers, OpenAir.  Brian Martin, their VP of Client Management, did an awesome job describing why and how they created their customer forum using GroupSwim.  Some of the highlights were:

  • Customers demanded the forum
  • OpenAir (OA) uses it for marketing and education, gathering customer feedback and document storage including training materials and FAQs
  • Robust search and email notifications were the top features requested by the customers surveyed
  • OA selected GroupSwim based on our company culture, price, functionality and usability
  • Spent 20 hours collectively preparing the site and seeding it with content before the initial roll-out
  • Rolled-out to 100 users and formally launched at user conference late last year
  • Initial groups in community were Knowledge Base, OpenAir Functionality, Training Documents, and Other – more followed
  • Minimal effort to maintain now that they are going
  • Regular activities include processing invitation requests, answering questions and adding new content
  • Sales and prospects request access regularly
  • Results: support volume dropping, site registrations increasing, getting new product ideas, helping with sales
  • Lessons learned: Form and functionality matter, keep content fresh, marketing is key, community will be self-sustaining in time

It was a great session and we had lots of questions.  Please click here for a full recording of the session if you are interested.  Thanks again Brian and Buckley for your help.  You were both awesome!

Interning at a Start-up – Week 2

June 27, 2008

After two weeks of being an intern, I feel like I’m getting the hang of it. For starters, my feelings towards BART (Bay Area Rapid Transit, e.g. subway) have changed dramatically. What was once a form of public transportation with dirty seats and pushy people has now transformed into a convenient and affordable way of getting into the city. Although my thoughts on the germs and fellow patrons have not changed, I’ve come to accept BART in all its grunginess and be grateful for the independence it has provided me. No matter what time I leave the office, I always know there will be a Pittsburg/Bay Point train coming to take me home within ten minutes of racing down the escalator of the Montgomery Station. And as long as I text my aunt upon passing through Rockridge, I know that there is someone waiting to pick me up from the Walnut Creek station. Whether or not this makes me feel like I’m back in middle school or not is insignificant when compared to the inconvenience I get to avoid every morning of searching for an open parking spot – which does not exist – in the parking structure at 9:30. The icing on the cake is the seemingly foreign thought – to a native of Dallas, where bikes are for recreation not transportation – that I make an effort to “free the air” everyday that I ride BART.

Besides my growing familiarity with BART, I’ve also become used to an “office life.” I’ve learned to expect a cry for lunch once the clock strikes twelve. I’ve watched the minutes crawl past two o’clock when my food coma (from lunch) officially sets in. I’ve also learned that seven-ish hours in front of a computer can make the thought of getting on Facebook at night revolting – a feeling I never thought I’d experience at the thought of logging onto the beloved Facebook.

So, I’ve gotten used to getting to the office and being at the office. But what exactly am I doing at the office you might be wondering? In the absence of my GroupSwim mentors, Tom and Jason, while they were at Enterprise 2.0, I explored GroupSwim by making my own trial site. I also helped out with a project the team was hired to do, which involves the use of the GroupSwim technology. I did a great deal of research, observed meetings, and sat in focus groups. With no prior experience with focus groups, I had no idea what to expect, but I found them to be very interesting; what I found to be especially interesting was how the participants interacted with each other and how these interactions sometimes swayed the opinions of all involved.

My current task is creating a customer database to help GroupSwim take on a marketing campaign with hopes of expanding their current pool of customers. In order to do this, I am using current lists of high tech companies, researching these companies to find the information I need about them, and loading them into Salesforce.

I have also been threatened many a time with familiarizing myself with this vague thing called “testing” so don’t be surprised if I start talking about this in upcoming weeks.

Wikis not ideal for external customer collaboration

May 12, 2008

Personally, I’m a big fan of Wikis (when used in the right circumstances). Coming from a consulting background, I like to collaborate on web documents with my teams and customers. It is a great tool that saves significant time and produces high quality results. HOWEVER, wikis are not great for everything. I run into customers every day who have published external Wikis for their customers to distribute information on their company and/or product. This is a big problem for the following reasons:

  1. Most wikis require familiarity or training to use them effectively, especially when contributing. They are not for the faint of heart and require effort to learn.
  2. Wikis are challenging to search and find information. They typically create silos of information that can confuse or frustrate a customer.
  3. Wikis are not good for ill defined or generic collaboration.
  4. They take significant effort to monitor. I would love to see an analysis on how much time the Wiki Editors spend managing Wikipedia. I suspect the answer would be stunning. Most companies couldn’t afford the proportional time and effort necessary to keep up with an evolving wiki.

Many of these customers are now dropping their external-facing wikis, or at the very least, augmenting them with other tools to address customer needs.

There are cases where wikis work well. Customers are:

  1. Extremely engaged with you and each other
  2. Work well together as a team
  3. Focus on specific topics

If a situation meets the criteria above, wikis are fantastic.

I think many companies rolled out Wikis for their customers and incorrectly assumed they were ideal because they give the company one place to go to maintain information. As usual, this is right and wrong. For the company, it might appear to be low maintenance. However, this is a fallacy because the maintenance load grows substantially as the Wiki grows.  For the customers, it is not ideal and leads to frustration and antipathy. My advice is to use a Wiki selectively, but don’t make it the central tool to collaborate with your customers.