Supporters of End User
Web

SPC12: Day 4 - Summary of Reducing Organizational Risk Through Effective Information Management

Item is currently unrated. Press SHIFT+ENTER to rate this item.1 star selected. Press SHIFT+ENTER to submit. Press TAB to increase rating. Press SHIFT+ESCAPE to leave rating submit mode.2 stars selected. Press SHIFT+ENTER to submit. Press TAB to increase rating. Press SHIFT+TAB to decrease rating. Press SHIFT+ESCAPE to leave rating submit mode.3 stars selected. Press SHIFT+ENTER to submit. Press TAB to increase rating. Press SHIFT+TAB to decrease rating. Press SHIFT+ESCAPE to leave rating submit mode.4 stars selected. Press SHIFT+ENTER to submit. Press TAB to increase rating. Press SHIFT+TAB to decrease rating. Press SHIFT+ESCAPE to leave rating submit mode.5 stars selected. Press SHIFT+ENTER to submit. Press SHIFT+TAB to decrease rating. Press SHIFT+ESCAPE to leave rating submit mode.
Categories:Event Review; Event Type; Conference; General Knowledge

 

Editor's note: Contributor Frederik Leksell is a Consultant for Accigo AB. Follow him @LetsTalkGov

Paul Olenick, presenting.

Okay, so this is the last day of SPC12. Some of us were at the Axceller party the day before, which was a very good party!

But now we will focus on the session at hand. Paul is talking some about how risk management can lead to wellness and success.

Agenda:

  • Define it
  • Apply it
  • Wrap it up

Information Management

It comes in, it comes out, it grows, and it rests. We want to do something with it: React, Proact (iv), Find, Safe Keep, Rely. We are not just talking about documents, but also people and other context.

The IT View is: Policy, Metadata, and Search.

Paul is now describing what all of these are. It seems a little naive as most people in this room already know what it is. Information management is not a list of features Paul says, yes that is correct. It's more about reaction to data or how to get data reacted on.

  • React, Tools: Metadata
  • Proact (iv) Tools: Policy, Metadata, and Search
  • Find Tools: Search, Metadata
  • Safe Keep Tools: Policy, Metadata
  • Rely Tools: Metadata

Obvious stuff

  • Audits: Legal, Financial
  • Compliance: HIPPA, Affordable care act
  • Data security, Permissions, e-mail, print

Not so obvious stuff

  • Ineffectiveness.
  • Fundability.
  • Incorrect processes.
  • Inability to react.
  • Frustrated information workers.
  • Lack of transparency.
  • Loss of IP.
  • Productivity leak.
  • Loss of revenue.

Some of this probably applies to most organizations; it’s a good point as to what happens without IM.

Hidden Risks

Can't: React, Proact (iv), Find, Safe Keep, Rely tec... Paul didn't speak much more about this. Instead we went to a demo.

eDiscovery can make snapshots of lots of data from a search query. It can be used when you have a legal audit. SharePoint has this out of the box. It’s a very good feature in fact, I like this and it really gives business value if you have structured data.

With the auditing policy on you can create reports on document changes etc. Paul didn't talk much more about this, just explained how much he helped companies save money with this.

Now it starts to get a bit more technical, let's see if Paul can keep it a business track.

Example 2: Inability to visualize data

Data outside SharePoint in silos that are related but they could not be connected...By using search crawling they made a unique record that could help FAST search to crawl different file servers and relate data.

Hmmm, don’t know if this is correct since I don’t have the technical skills in this area.

Points that you need, a Foundation

  • Focus and define high-level business value
  • Everything should have a specific outcome
  • Know your audience
  • Find consensus and build form there. (Org buy-in)
  • Identify and quantify risk
  • Identify and quantify opportunities
  • Determine project scope
  • Build your buy-in

His point here is don’t talk to the CIO, talk to the business. It’s very good that he tells everyone that, it's a big plus!

Conceptual, not technical

  • Fear of impending business.
  • Fear of automation. This is something I have felt as well, also when talking about integrations.
  • Resistance from end-users.
  • Getting into the weeds.
  • Failure to gain consensus.
  • Understand how to quantify risks.

Wrap it up

  • Stay business focused.
  • Focus on opportunity and revenue.
  • Metadata is the fuel that drives automation and search, surfacing info.
  • Challenges will be organizational, not technical.

Some very good point here!

Now I need to get to the next session, so no more about this right now. I will create an article, later on, filling in all the gaps.

Comments

Nancy Skaggs

Good stuff!

I can't think of a concept that is more needed in the enterprise but that so few people are willing to take the time to embrace. No one wants to own this beast, so everyone suffers.
 
Is it because so much agreement is required "across party lines?" Consensus cannot be reached so everyone suffers. If a good info architecture foundation is created, though, it trickles down to enable so much value.

Posted 30-Nov-2012 by Nancy Skaggs

Notify me of comments to this article

E-mail:
   

Add Comment

Title:

 
Comment:
Email:

   


Name:

 
Url: