The Future of Information Delivery

1

• The Future of Information Delivery

Enterprise RSS
November 15, 2009
2
What Your Users Want

Access to critical information and assurance that
relevant content will be delivered when and where
they want it
Relevancy

• Breadth

• Relevancy

Immediacy

• Personalization

• Flexibility

• Immediacy

3
What They DONT Want

Confusion

• Information overload
• Corporate email spam
• Confusing applications
• Siloed content repositories
• Content recreation

Inaccuracy
Unavailability
4
The Way it Is Today

• How users find information
• Ask the librarian
• Search the Web
• Visit premium content sites
• Via portals or content repositories
• Subscribe to emails and alerts

• Whats the Result?
• Information overload
• Email spam
• Diminished client service
• Overtaxed KM/library staff

5
Complaints from Stakeholders

Confusion

• I cant find that document you sent me!
• The portal doesnt have useful information!
• The e-mail summaries are too broad!
• That new system is too hard to use!

Inaccuracy

• I cant get what I need fast enough!

Unavailability
6
What is RSS?

• Lightweight method of delivering information
• Based on XML standard
• Uses publish and subscribe model
• Enables easy content syndication/reuse

7
What is Available in RSS?

• Premium content
• Thomson, LexisNexis, Factiva, BNA etc
• Mainstream and niche news sites
• Fortune, Washington Post, Law.com etc
• Internal content
• Blogs, applications, portals etc
• Blogs and wikis

8
Why RSS?

• The RSS paradigm is
• Information is brought to the user
• Receiver of content has control
• Only relevant content is delivered
• New information is automatically pushed to users
• Delivered to multiple devices and formats
• No spam/spam filters

• RSS Adoption
• 12 of online users employ RSS Aggregators
  (Jupiter)
• 31 access RSS feeds (Pew Internet)
• 5 know they are accessing RSS feeds (IPSOS)

9
RSS via MyYahoo
10
RSS via NewsGator Online
11
RSS via NewsGator Inbox
12
RSS via FeedDemon
13
RSS via NewsGator Go!
14
Top 10 Most Read Feeds

• Engadget
• Feld Thoughts
• Boing Boing
• Slashdot
• Digg
• LifeHacker
• TechCrunch
• New York Times (Top Stories)
• ESPN (Top Stories)
• BBC (Top Stories)

15
Enterprise RSS
16
Enterprise RSS
17
Individual Readers vs. Enterprise RSS

• Individual Readers
• Users find content on their own
• Single platform/interface
• Default or no taxonomy
• No central index of feeds
• Limited publishing tools
• No reporting

• Enterprise RSS
• Subscribe users and groups to content
• Multiple interfaces- all synchronized
• Customized taxonomy
• Searchable central index of feeds
• Useful publishing tools
• Detailed reporting

18
Serving All Users

• Power Users/Information Resources Staff
• Very familiar with RSS, subscribe to 50 feeds
• Often disseminate information to others
• Need desktop application
• Knowledge Workers
• Somewhat familiar with RSS, subscribe to 10
  feeds
• Usually customer-facing, sometimes disseminate
  information to others
• Live in e-mail client, mobile devices
• Casual users
• Unfamiliar with RSS
• Require others to hand-hold them
• Need content placed in the easiest access points

19
Typical Use Cases

• Human Resources Training, policy and benefit
  information distribution
• Internal Communications- Executive
  communications, company news and information
  distribution
• Marketing Industry tracking, competitive
  intelligence, brand monitoring
• Public Relations Coverage tracking, crisis
  control
• Professional Services Project/client status
  updates
• Research and Development Project status updates,
  wiki/blog updates
• Sales Client opportunity monitoring, new
  opportunity discovery

20
Industry-Specific Use Cases

• Aerospace/Defense Project updates, competitive
  data
• Executive Search Company, industry, executive
  news
• Financial Services HQ-branch communication,
  market and company tracking, industry news, blog
  chatter,
• Government Project updates, crisis management
• Health Care Medical news, patient information
• Higher Education Coursework updates, faculty
  blogs
• High Tech Development blogs, competitive
  intelligence
• Law firms Matter tracking, Lexis-Nexis/WestLaw
  searches
• Pharma/Chemical Clinical trial and regulatory
  information, internal blogs
• PR Agencies Client and competitor coverage,
  industry news

21
NGES Demonstration
22
Pilot Project

• Identify most acute problems
• What has the greatest impact on the business?
• Select users for pilot
• Extend beyond library staff
• Dont include most difficult stakeholder
• Define a 30-day action plan before starting
• What are the metrics for success?
• Use a hosted version if possible
• Doesnt burden IT staff, but make them of desktop
  software installations
• Quicker deployment process
• Get detailed feedback from users
• Access, finding content, relevancy etc

23
Building the Business Case

• Find out what content is available in RSS
• Find out whether internal XML content can be
  transformed
• Talk to premium content vendors about delivery
  roadmap
• Involve stakeholder groups early
• Try to quantify impact of information delivery
  problems
• Ask if there is a Web 2.0 initiative
• Sometime driven out of IT, other times from
  marketing
• Talk to IT
• Determine deployment model (hosted vs.
  on-premises)
• Stress the low entry-costs
• Applications are far less expensive than premium
  content
• See about content/application bundles

24
Deploying the Real Thing

• Learn from pilot project feedback
• Focus on the taxonomy
• Integrate with portal (if possible)
• Set up live/recorded training sessions
• Roll it out in stages
• Make modifications after each rollout
• Pay close attention to reports

25
Questions and Answers
26
Thank You!

• Inquire about beta testing NewsGator Enterprise
  Server On-Demand
• Ask for a 11 Webinar for your organization
• Contact me with any questions
• toddb_at_newsgator.com
• 303-552-2046