Posts tagged ‘information architecture’

March 3, 2012

Top 3 Considerations for Deploying Social Technology in the Enterprise

New article on CMSWire:

http://www.cmswire.com/cms/social-business/top-3-considerations-for-deploying-social-technology-in-the-enterprise-014670.php

While we might expect social within the enterprise to be easy as Facebook or Twitter, it’s not.  Deploying social technology within the enterprise is a journey filled with organizational hurdles that include compliance, security, culture change, executive sponsorship, budget and integration challenges to name just a few.  In some organizations, this social journey begins when the business wants to embrace social before corporate IT is ready…..It’s important to ask the right questions and make an informed decision when it comes to social technology in the workplace.  So what are the top considerations both business and IT should think about before jumping on the social bandwagon and making an enterprise technology purchase?  Read more…

December 17, 2010

So what’s your New Year’s Resolution for 2011 to clean up this information mess?

I work with many organizations with SharePoint intranet sites that are simply a MESS!   Yes, that’s you and your intranet!   Admit it — your intranet sites look like they were built in 1999 with big fonts, bigger graphics, static and outdated links & content, and absolutely no organization of the information and navigation presented to the end user.

Over the last decade perhaps small enhancements or attempts at redesign evolved your intranet incrementally.  You now have some level of standards and branding at a global level. Perhaps your organization has finally consolidated and standardized on SharePoint and are even thinking about upgrading to 2010 in the next year or two.  You’re also focused on the latest buzz words like “social” and “collaboration” – baking them into your overall strategy.   However, down in the trenches you still have sites for functional areas or business units or regions that remain an unorganized mess of stale information.

I bet dozens of so-called team sites have also popped up with the intent of providing a better place for your organization to manage and update important content that really should be out on the intranet site for everyone to consume.  However, those team sites also added to the mess.  There’s even morenoise and confusion by limiting access and navigation to information with redundant content and links.

We call this information overload and have all read the stats on the hidden costs and wasted productivity because knowledge workers spend too much time looking for information.   With the amount of digital information continuing to increase beyond expectations, it’s now even more difficult to search, browse, filter, and find the information than it was a decade ago.  The year 2010 is coming to an end with over a decade of internet evolution and you ask yourself “Am I more productive today than I was 10 years ago?”

So what’s your New Year’s Resolution for 2011 to clean up this information mess?

Now I’m sure you’re reading this post and immediately are Googling “New Year’s Resolutions” which returns top ten lists containing the resolution to: “Get Organized”.    No doubt you also Google “clean up information mess” and you find  a helpful article on Oprah.com about cleaning up clutter in your life.  One interesting comment the organizational expert on Oprah.com made was how he defined clutter:  ”anything that stands between you and the vision you have for your best life.”   You can’t go wrong if you quote Oprah.com and this statement is so true — especially in our professional lives.   Clutter is not necessarily an individual issue, but an organizational issue.  And if your SharePoint implementation is a cluttered mess of information, then SharePoint stands between you and the vision you have for your business.  And I have to highlight that the mess is not just something IT needs to address.  The business users owns the information inside of SharePoint and the clutter is a shared responsibility.  So what can you do?  What can the champions, managers, power & end users of SharePoint do in 2011 to get organized?

There are 3 keys to get organized and clean up the SharePoint clutter:

1. Information Architecture. A somewhat abstract concept for non-technical people.  This is not only about figuring out what you want your website to look like — the UI design perhaps.  It includes identifying the intended audience and the inventory of content you intend on managing within the site and the users intend on consuming.  It’s also about the underlying structure of the site or site collection and the images, documents, links, lists, and libraries you plan on managing and maintaining. Yes, it’s about metadata and your user’s ability to search, browse, filter, and find information.   So start by:

“categorizing your information and blueprint how content should be structured and stored within SharePoint and presented to the end user”

2. Security. Once you have an understanding of the information architecture, you can then ensure your information is secure.  Do you know if the content in your sites is secure right now?   Are you absolutely sure with 100% confidence?  Difficult questions to ask sometimes as politics always seem to play a part in the discussion with IT and Business here.  It’s amazing how SharePoint forces the conversation about ownership, roles, and responsibilities.  So sit down in 2011 and look at your security and answer the questions:

“In your SharePoint site(s), who owns what and who should have access to what?”

3. Governance. While governance is always a hot topic, the usual reference to this term is the overall SharePoint deployment with sub-topics such as backups, site creation, etc…  However, this also refer to site owners and site collection administrators.  Do they have a plan to ensure specific content has owners and is continually updated?   What the process to source new content and ensure that information is posted in a timely manner to those individuals who should consume it?   Who maintains membership to your site or site collection?  So…

Define what governance means to you in 2011 and start governing your SharePoint Sites!

For those fans of Dexter…”tick, tick, tick”….that’s the sound of 2010 coming to an end.  It’s time to get your information organized inside of SharePoint and focus on a clutter free world of sharing and pointing!!!

 

Follow me on twitter….

October 27, 2010

What’s information architecture & why is it important anyway?

In many organizations, SharePoint has emerged as a multi-purpose platform to manage information and automate business processes and activities.  It’s often times easy to rush into building a solution without thinking enough about something called “information architecture” (IA). 

IA is a term that most of us probably haven’t heard of before SharePoint.  In traditional content management system implementations, the focus was on developing a taxonomy as part of the solution.  Rarely was the term IA used.  So what is information architecture anyway?  According to our friend Wikipedia, information architecture refers to the analysis and design of the data stored by information systems, concentrating on entities, their attributes, and their interrelationships. While that may sound synonomous to taxonomy, the categorization of the information is really only part of developing a sound information architecture for SharePoint.  When it comes to SharePoint, IA is essential and provides a necessary foundation for everything we do and every solution we develop on the platform. 

So why is IA important?  A solid approach starts with the end in mind and there are 3 key drivers to think about when designing your information architecture for SharePoint:

1. Findability (search)

2. Usability (reporting/browsing/filtering)

3. Security

It doesn’t matter if your looking to leverage SharePoint for your intranet portals, for collaborative team spaces, ECM, web 2.0, business process workflows or business intelligence.  Before you jump into the solution and start created sites, you’ll want to first think about what information is being stored, who has access to this information, and how will people find what they’re looking for.  As I mentioned before, developing a taxonomy for the a SharePoint document library or content types may only part of large IA approach.  At a broader enterprise or solution focus, three key things should be considered:

1. Sites

2. People

3. Content

Is there specific metadata you want to associate with your sites (or site collections) that relate to how they’re provisioned or secured or that map to your organizational structure?  Do you intend to have a site directory to make it easier for people to navigate and browse for what they’re looking for?   If you plan on leveraging SharePoint to search for people, what metadata will help users find someone they’re looking for?   Will individuals have certain security classifications that prevent them from accessing certain areas of the installation (e.g. a farm or site collection)?    Of course content is more obvious and is where content types and taxonomies come into play.

No matter how you intend to use SharePoint or what solution you plan to develop, start by addressing your information architecture needs.  Those “information architecture” related questions I outlined will definitely have an impact your deployment and ultimate adoption of the technology.

July 28, 2010

Great AIIM webinar…Optimizing SharePoint IA, Governance, & Overall Investment

In case anyone missed this …. download the slides from this AIIM webinar….great stuff….check it out and download it.

http://www.slideshare.net/getrichieb/072810aiimwebinar-share-point-and-your-information-architecture


Share/Bookmark

Don’t forget to follow me on Twitter

Follow

Get every new post delivered to your Inbox.