Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

CAN DRUPAL BE A DISRUPTIVE FORCE IN SOCIAL BUSINESS SOFTWARE?

Whether you call it an intranet, a portal, social software or a collaboration tool, chances are your organization has some internal web accessible content system designed to help foster knowledge management. The bad news is that it may fail.
by

Jeff Walpole

on 8 July 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of CAN DRUPAL BE A DISRUPTIVE FORCE IN SOCIAL BUSINESS SOFTWARE?

Oh yeah, and one more BIG thing...
Mobile.
It comes down to this:
What Clients are REALLY Shopping For
Usability
Organization
Search
1. is increasingly diverse
2. is becoming more saturated
3. has formidable market forces in Sharepoint, as well as Google and Salesforce
4. it can drive you crazy.
the social collaboration landscape:
The needs are changing, the features are growing, and the market is transforming...fast.

And that's just what
open source does best.
The Final Word:
... requires you to look beyond what vendors are offering, toward what your users value most.

... should include considerations for usability, organization, search, flexibility, cost, & integration

.... must, must, must include mobile.
Navigating this landscape...
But choosing software isn't all about features and cost. Most clients forget to ask themselves five important questions.
Navigating this complex landscape means thinking carefully about what your users value most -- not what vendors offer.
80% of social business efforts fail. Without a solid information strategy (and clear knowledge of your intentions), yours could fail too.
the (really) bad news:
Lack of revenue generation has kept social collaboration software in the “world of IT” where saving costs and improving efficiency are all people are expecting to gain from it.
The trouble is believing the hype that we can achieve our wildest dreams and falling into common traps.
Don't build a wiki without a culture where teams can contribute knowledge that is used.
Don't invest in project management software that doesn't follow your PM methodology.
Don't waste time on doc management if you don't have sharing policies.
Don't choose a social-media-for-business tool if you don't want your teams posting pictures of cats.
Do not ask of your collaboration software what you are not asking of your organization's collaborators:
Are we asking too much of our social collaboration software?
"a dynamic, confusing, and converging market"
Social Collaboration Software
pricing: per project? per user per month? per gigabyte of storage?
SaaS or Installed?
Open source or commercial?
what's a microblog?
do I need a social network for my office? do I want one?
asset management? or asset collaboration?
what about security?
how will it work with what I already have?
platform? or product?
how many licenses do I need?
can we customize?
wiki
project tracking
document management
asset management
what makes a portal a portal?
discusssions
microblogs
social networking
friending
LDAP
expertise finding
contact management
the landscape.
the players
the features
the playing field
asset focus
communication focus
purpose-built solutions
platform solutions
$2 billllllion dollar market
investing heavily in asset & communication features
not. going. anywhere.
navigating the space.
Flexibility
Cost
Integration
Governance
Training
Maintenance
Security
Usability
You don't have any "NEW" problems.
you are going to find plenty of solutions.
the key is understanding your own environment (or your client's), so that you're driving the decision based on true needs, not available features.
Who is going to own and manage your software, even as policies and procedures adapt and change?
Who is going to show everyone how to use it, and ramp up new users?
What happens when something isn't working, needs customization, or requires upkeep?
Are we comfortable with access control and infosec here?
Can all of our team members both present and future easily access and use this software, despite any language or accessibility limitations?
Your teams can make good use of software. Your software cannot create productive people.

building
the right
plan.

content
communication
collaboration
activity
culture
Our circles are expanding.
Organizations are now:
more dispersed geographically
relying more on virtual teams and offices
producing lots and lots of digital content
According to James Robertson, intranets have five building blocks:
social software promises to organize, project manage, and outfit us for full collaboration.
authorship
connections
but the social web adds two more ingredients:
So, do these bind together content with social context?
Or do they just complicate an already complex problem?
what's (really) behind the scenes:
a goal to "escape email"
the dream of "serendipitous connections and ideas" emerging
a hope that a good tool will create culture
a belief that with all this info, trends will emerge
a need to CYA through public forum
the right solution unlocks the knowledge that sits in the brains of an organization's employees.
So, your company's processes must drive the tool.
making the
space work better.

Can open source be a disruptive force in social business software?
mobile
locate
socialize
search
doc mgt
timekeeping
discuss
notify
calendar
identity
news
vote & poll
team mgt
social collaboration
wiki
portals
intranets
microblog
doc mgt
Jeff Walpole April.13.13
Let's review:
1. This landscape is a dynamic, confusing, changing market. It's hard to navigate, but it's full of promising tools.

2. This space requires organizations to truly know the problems they're trying to solve.
Can it be better?
1. the ROI is better.
2. flexibility is essential.
3. their way is not your way.
4. glue works better.
5. innovation matters.
Why Open Source Works Best:
1. Vendor Lock-In
2. Over-customization
3. Paving the cowpath
4. Internal system competition
5. Lack of user buy-in
Consider building things that truly fit; rather than just buying into
what's "already built."
Social media is moving really fast.

Great for our personal lives
(& attention spans).
Really tough when you're trying to run a business, not just manage your social life.
First, know that you can build a solution in a lot of different ways. There is no one best way.
Consider Opening It Up.
Commons
Open Atrium
Distros & Modules
Totem
RedHenCRM
ERPAL
DrupalWiki
OpenIdeaL

Workbench
Messaging API
Organic Groups
Social business tools, focused on forums & communications
Based in Organic Groups, Spark
And there will be more to come!
Collaboration platform
Plugin structure for integration with third party functionality
Uses Organic Groups & Panopoly
Open source solutions give you a platform you can extend and customize without fear of lock-in. They let you build what you need and keep it current.
Consider the trends in the web content management system (WCMS) space over the last 5 years. Commercial and proprietary vendors have fallen victim to a widespread movement towards open source.
WHY?
In the business context, we have to settle on concrete gains that relate to our business goals. So far the best chance of success for these types of solutions lies in our ability to use these tools to:
Reduce cost
Achieve greater productivity
Leverage insights and gain a competitive advantage
What do business/IT need?
We have to pick and choose what we expect to gain;
target the approach that is best for us and prove it.
Look out for common
pitfalls
Full transcript