Posts Tagged ‘collaboration’

Selling Sales Collaboration at Sales 2.0

March 4, 2009

It’s been a while since I’ve been able to bust out some alliteration like that.  We had a great day at the Sales 2.0 conference in San Francisco.  This is a collection of sales and marketing professionals meeting to understand and riff on how the sales process is changing, and how the tools and process everyone uses must morph as well.

We had a great time speaking with folks at the breaks.  It was a real pleasure to show GroupSwim to people who instantly understood the business problems we solve and the value we provide.  We explained that communication and collaboration with sales and marketing teams is usually bad, and mostly reliant on email.  GroupSwim provides an excellent way for everyone to collaborate as a team, in a very easy and cost effective manner.  Our integration with SalesForce was a big hit and the application sold itself once we moved into demo mode.  As usual, I got very sick of hearing myself talk by the end of the day but it was worth the sacrifice.

We are looking forward to meeting more folks tomorrow.  Swing by if you are at the conference.

Microsoft Online Success Bodes Well for SaaS

March 2, 2009

Microsoft recently announced a significant win and overall traction with their online business services offerings.  On one hand, this makes hosted Sharepoint a stronger competitor.  We don’t have any trouble finding customers who hate Sharepoint and want alternatives.  On the other hand, it shows more and larger companies are becoming increasingly comfortable with moving services and applications to the cloud.  In this case, Microsoft landed GlaxoSmithKline with over 100,000 users.  I’m thrilled to hear this.  This is very consistent with other trends where companies, given the economic pressure, are going to increasingly look offsite for solutions.  I’m happy to see Microsoft also blazing the trial that SalesForce.com started years ago.

Organize business collaboration groups using tags

February 13, 2009

Nest folders

One question I get all the time is can we organize groups in nested folders.  We are all so accustomed to this way of thinking about organization, we assume it is the right way to do it.  For example, I want to create my Sales group and have East and West under it , and so on.  Or, someone uses GroupSwim for a project and wants all technical groups under one umbrella.  We can all relate to this habit.  The problem is it doesn’t make sense.  The minute you build a hierarchy for an organization or project, it becomes out-of-date or simply wrong.  There is a better way!

From the beginning, we designed GroupSwim to define relationships between groups through tags, not hierarchy.  The tags determine how groups are related. In the previous example, I could create three groups; Sales, West, and East; each one has the “sales” tag applied to them.  I can also tag the marketing group that works with sales. In this scenario, when I search for “sales”, I get all four groups.  The benefits are legion:

  1. Tags are dynamic, just like business and life
  2. You can have as many as you want
  3. You can change them at any time

By using tags as an organizational metaphor, we allow our collaboration sites and customer communities the opportunity to evolve over time.

The other important factor here is search; it is the great equalizer.  It doesn’t matter where you put stuff if you have a good search engine, which we do.  It also allows the ultimate freedom to organize because in the end, you can find what you need quickly regardless of where it is.

Frankly, the biggest barrier and con to this approach is habit.  People are simply so used to seeing nested folders, that it seems odd to them when they don’t see them.  While we aren’t the only technology using tags versus folders, we are going to stick to our guns on this one.  It does force to do some “evangelism” on this topic, but we can take it.  What do you think?  Miss those nested folders?

Webinar: Improve Technical Team Performance Webinar

February 3, 2009

GroupSwim is pleased announce an exciting webinar on February 18th at 1PM EST / 10AM PST. Jari Koister, Chief Technology Officer for GroupSwim, will join us to discuss how using social collaboration tools and techniques has measurably improved the performance of his distributed engineering teams.

During the session, we will discuss the specific activities and processes that Jari has implemented to change how GroupSwim engineers its products. Traditional engineering tools focus on the software development process. There is a large gap in most of these tools; they do a poor job managing requirements gathering, design decisions and asking questions/providing answers. Also, engineering and highly technical teams traditionally operate in silos. By using social collaboration, Jari will illustrate how the team now more effectively engages with product management, sales and even customers. He will also explain how using a wiki and other specific tools improves the quality and speed for developing products. Jari is a highly-regarded engineering executive and earned a Phd from the Royal Institute in Sweden.

We will cover how and why social collaboration has improved the following areas during this session:
•    Organization
•    Processes
•    Tools

Jari will also review the measurable benefits associated with this change and use specific examples and a demo to illustrate.

This webinar will take place on Wednesday, February 18th at 1PM EST / 10AM PST.

Please register here to join us for this interesting and informative discussion. I hope to see you there!

Layoffs Send People and Knowledge Packing

January 30, 2009

This is also posted on ReadWriteWeb, where I occasionally write.

The scale of layoffs the past few weeks is unprecedented.  The impact on the people who are shown the door and companies that let them go will linger for years to come.  Besides the emotional damage associated with people leaving, there is a tangible cost to companies when collective knowledge and experience walk out the door.  Once it’s gone, no amount of TARP money will get it back.  The problem is it is too late for this round, but starting soon will lessen the blow in the future.  One of the few ways to address the problem is to adopt collaborative tools and processes that capture the information companies need to thrive in the future.

Every company in the world relies on bits of information that live inside employee’s heads.  The accounts payable clerk may know a small nugget on how to negotiate the best price from an important vendor.  A salesperson may use the same pitch when selling a certain kind of customer, and it works every time.  An engineer may be the only person who knows why the software was originally built using cold fusion.  Or, the branch manager may know the precise place to kick the box compactor when it acts up.  All these bits of knowledge add up and account for a vast amount of information a healthy business requires.  When people leave either by choice or not, the vast majority of companies do a poor job of gathering this information in a consistent way.  What inevitably happens is the company and future employees are forced to relearn it again through trial and error.  The same cycle repeats over and over again.  The scale of this problem is huge in the current environment.

So, what does a company do to address the problem?

1. Use tools and process. Companies must have infrastructure in place to encourage/force employees to share information.  It doesn’t matter what as long as it is at least marginally effective.  Anything is better than nothing.  How many managers around the world are at this minute digging through someone’s email folder trying to figure what they were working on and what they knew.

2. Measure collaboration. Again, it doesn’t matter how, just do something that you think has good chance for success.  I’ve seen people measure the number of contributions to a knowledge base, frequency of mentoring sessions, writing up white papers, etc..  What you measure is less important than doing it consistently over time and measuring improvement.  I’m not saying the metrics are irrelevant.  What I’m saying is don’t wait to pick or track the perfect ones.  Start small and simple and go from there.

3. Reward employees for sharing. If you don’t measure it and reward behavior, it isn’t going to happen.  Collaboration is a bit squishy and can’t be measured like the number of phone calls answered per hour, but there are ways.

4. Focus on informal information. This is often where the best information resides.  People send emails back and forth answering questions or trading best practices for example.  You need a way to harvest and capture these nuggets of information.

None of this stuff is rocket science, but I’m willing to bet few companies have this process nailed.  I recently talked with David Coleman of Collaborative Strategies.  He said only 10% of his clients focus on “back-end” collaboration.  The majority have invested in front-end collaboration technology like web conferencing, etc. to save money and reduce travel.  This is also important but won’t help companies retain information when people leave.  The present economic conditions put even more pressure on wringing out the best productivity possible from the remaining and future employees.  The important thing to do now if you are a business owner or manager is to do something before it is too late again.

Manage Collaboration Like a Project – Or Else

January 27, 2009

In order for a collaborative effort (requires more than 1 person and has an end goal) to achieve a successful outcome, it is useful to treat it like a project.  The “project” should have a goal(s), time-line, common tools and roles.  I’m not talking about creating a formal project plan, but some basic planning and organization at the front end of the collaborative effort is an excellent investment of time and potentially money.

Most collaboration is poorly managed or not at all.  While there is a HUGE variation in the level of effort, number of people involved, etc., the things good project managers do are helpful no matter how big the project is.  Even when two people are collaborating on the smallest of projects, the likelihood of success hinges on very predictable things.  First, the collaborators should agree on deadlines for when the work should be complete and if there are any interim milestones to consider.  Second, they should decide who is in charge or at least responsible for packaging up the final deliverable.  Or, they should at least give one person the responsibility for coordinating the work, even if they aren’t “in charge”.  Third, if it isn’t obvious, they should coordinate the tools or software they might use so they don’t end up with incompatible work that they need to rework in order to consolidate.  Finally, they should also agree on goals or what the end of the collaboration will achieve.  Is it a document, or a decision, or a piece of art, or meeting up at a ballgame, or some combination of many things?

Let’s review a recent example.  I led a team where we needed to collaborate on a long, multi-part document as part of a sales effort.  The content and data this document required did not exist, and it was both long and complicated.  It required focus, creativity and discipline in order to get it done by the time we needed it.

The team included 5 people in different parts of the company in different parts of the world and time zones.  We used GroupSwim Collaboration for the majority effort.  Two of us spent time mapping out the collaborative effort.  We developed the following “plan”:

  • Set deadlines over the course of 3 days, which is how long we had
  • Divided the document into separate sections
  • Assigned primary authors to each section
  • Created a wiki page for each section of the document and added the questions each author needed to address
  • Tracked people’s progress with a central wiki showing status and hand-offs
  • Reviewed each section as people completed them
  • Consolidated each section into one comprehensive document
  • Performed final edits and cleaned up language, voice, grammar, etc.
  • Formatted the document and then published

The process worked to perfection and we yielded a high quality piece of work.  It would have never worked without basic planning in the beginning to ensure everyone knew what to do, when to do it, and how to do it.  We saved countless hours of potential rework and produced a great outcome by treating the whole effort like a project.

Why GroupSwim will thrive in Enterprise 2.0 in 2009

January 14, 2009

Dion Hincliffe is a well known blogger in the Enterprise 2.0/Web 2.0 space. He recently posted an article on his predictions for Enterprise 2.0 in 2009.

One thing that struck me as I read it is GroupSwim is completely aligned with the majority of his predictions:

  1. Tight budgets will drive the adoption of low-cost Web 2.0 and cloud/SaaS solutions.
    No doubt about this one.  The current economic climate is going to require all companies to spend more wisely.  Other than “free” or consumer oriented solutions, there is no better value for money for businesses than GroupSwim.
  2. Online community and 2.0 technologies become a priority for most organizations.
    I hope he is spot-on here.  This is exactly what we have built. GroupSwim Community and Community+ were created to provide online communities that leverage web 2.0 technology and techniques.
  3. Cloud computing will remain one of the biggest new Internet developments.
    GroupSwim is a great example of cloud computing.  We use Amazon S3 to store documents and we will soon use EC2 to scale our computing power and enhance performance.  We will be able to innovate, grow and keep our prices low by taking advantage of cloud computing.
  4. Internal use of 2.0 will continue growth in large enterprises while the struggle continues with market-facing 2.0 products.
    GroupSwim Collaboration is a product directly aimed and internal use of 2.0 technology.  We hope and agree that it will continue to grow and thrive.
  5. The economic climate will at long last drive major advances towards aligning IT with business.
    Businesses can no longer afford to have IT fiefdoms.  Business will continue to drive IT more aggressively and more and more components of IT will go off-site or be outsources.  Managing email servers, databases, etc. are usually not the core competencies of companies, and there is no reason to keep them in-house when there are cheaper and better solutions elsewhere.  We see business units coming to GroupSwim for help, because they can’t get it from IT and the plethora of solutions that aren’t integrated or easy-to-use that are forced on them.

Save time by making it easy for users to contribute

January 5, 2009

One of the advantages of my position at GroupSwim is I help lots of customers plan and roll-out their sites. I get to observe what works and what doesn’t work. I’ve noticed an easy strategy that helps people collaborate effectively – using very specific group names to guide people on where to post discussions, documents or wikis.

I know this sounds simple but it isn’t. For example, if I’m creating a collaboration site for a professional services project, I might use these groups:

  1. Project Management Meeting Notes
  2. Executive Interview Results
  3. Technical Infrastructure Issues
  4. Gruntmaster 2000 Training Documents

Instead of:

  1. Project Planning
  2. Technical
  3. Training

I see this over and over again where customers using specific groups like the first list see significantly higher volume and more value than those using groups like the second list. There is a psychological barrier that people need to overcome when using a collaboration tool like GroupSwim. It is so easy to fall back into the habits of using email or nothing at all. What I’m observing is if you are proscriptive in how you want employees or customers to collaborate, they will respond. I’m not saying limit their options. If they want to create additional groups and collaborate more, by all means turn them loose. However, when getting things started, the more specific you can be, the better results you will achieve.

The first list is a good example of internal collaboration; it is the same thing with external customer collaboration. One of our clients created an external community and the groups they use are very detailed. They don’t just go by products, but have different groups for specific modules. They also have groups for roles and technologies. What this does is make it very easy for users to see where they should post content. EVERYTHING we do to encourage collaboration should remove friction from the process. This is one very easy way to do it. It reminds me of a golf swing; if you set-up correctly over the ball with the proper grip and alignment, you have a higher probability of hitting a great shot. The same thing holds true for collaboration. If you structure your groups and tools correctly, you have a higher probability of achieving great results.

Improve Project Results Webinar Video

November 20, 2008

We hosted a great webinar today with Brian Krug from newScale. He covered how their company uses GroupSwim to improve professional services projects and outcomes. They also use it during the sales process and post implementation. Here is the video of the session. Let us know what you think. My thanks again to Brian for all his preparation and excellent delivery.

[Note: I've had to remove the video unfortunately.  Appears that the software didn't record Brian's piece so it is silent after the first 10 minutes.  My apologies.]

Webinar: Improve Project Results Using Social Collaboration

November 7, 2008

I’m pleased to invite you to an exciting webinar on November 20th at 1PM EST / 10AM PST. Brian Krug, Director of Professional Services at newScale, will join us to discuss how using social collaboration technology like GroupSwim can measurably improve the results and customer satisfaction associated with large, complex projects.
During the session, we will discuss how social collaboration can get projects started on the right foot, keep consultants and customers on the same page, and reduce the frustration and errors associated with “Reply All” emails and multiple document versions.
We will cover the following topics during this session:
1.    Utilize GroupSwim during the sales cycle to set expectations and impress customers before the project even starts
2.    Provide a place to level-set and communicate before the official project kick-off
3.    Communicate effectively across relevant projects and project teams, all while creating a permanent record of knowledge and documents
4.    Leverage collaboration tools like wikis that enable “inter-creativity”, which gets consultants and customers deeply engaged and improves project deliverables and/or products
This webinar will take place on Thursday, November 20th at 1PM EST / 10AM PST.
Please register here to join us on November 20th for this interesting and informative discussion. I hope to see you there!