FYI -

Scroll below for meeting conclusion and next steps.

Marie
----- Forwarded by Marie Hejka/Corp/Enron on 11/30/2000 06:27 PM -----

	Marie Hejka
	11/30/2000 05:34 PM
		 
		 To: David Gossett/Enron Communications@Enron Communications, Anthony 
Mends/Enron Communications@Enron Communications, Brandon 
Rigney/Corp/Enron@ENRON, Allen Elliott/HOU/ECT@ECT
		 cc: Bryan Powell/HOU/ECT@ECT, George Wasaff/NA/Enron@Enron, John 
Gillespie/Corp/Enron@ENRON
		 Subject: KM Task Force Content Strategy Meeting 

Thank you for your participation in yesterday's meeting.  Please review the 
below meeting notes.

Sincerely,

Marie Hejka




  11/29/00
Content Strategy Meeting Notes

Attendees:
Allen Elliott - mynetwork.com
David Gossett - mywEBSource.com
Marie Hejka ) KM Task Force Chair
Anthony Mends - mywEBSource.com
Brandon Rigney ) my.home.enron.com

Meeting Details.

The above group met to discuss the content strategy for the KM Task Force 
portal.  Our intention is to synergize the collective intelligence of these 
teams to develop a best practices portal.  The task force is in a unique 
position because the portal we will develop from is Bryan Powell,s 
mynetwork.com which although it largely reflects Brandon Rigney,s 
my.home.enron.com, it does not reflect the characteristics requested by the 
KM pilot executive sponsors and task force members.  The question to ask is: 
are the characteristics identified by the KM pilot executive sponsors and 
task force members the characteristics we should include in a portal?  
Further analysis is required to conclude what user needs are before we can 
determine what to include in a portal. 

The team agreed that a portal is relatively easy to develop.  What is more 
important and challenging is the process, established perhaps by a 
centralized KM effort, by which information or content is made available to 
all given portals. It is the content accessible through a portal which 
determines the success of the portal.  Yahoo.com users, through a minimal 
number of starting points, may access some 6000 containers of information.  
For our project, it has not been determined what information (what content) 
needs to be accessed from a portal.  The answer to this question should 
predict what front end buttons are most important to place on the initial 
dashboard of the portal.  

Does the task force want to enter in to the business of hashing out what 
specific content to make available through the portal?  No, we have neither 
the time nor the responsibility to undertake this.  But, how then, does the 
task force determine what the initial dashboard will look like if we don,t 
have an understanding of what content users actually need most to access?  
The requirements phase should predict this.

What is most challenging about content?  The answer:  locking down the 
containerable information (content) to bridge to portals.  Information needs 
to be syndicated.  In order for it to be syndicated, it must be in an 
appropriate container.  &Containerable8 information is information that can 
be shown as a channel.  In other words, containerable information is 
information that can be accessed from the portal.  Not all information on a 
given website is containerable and available to be pulled by portals.  
Editorial assistance is required to make certain information is contained.  A 
KM strategy should propose a method to identify, develop and maintain 
information a portal can capture.  


Meeting Conclusion.

The development of any business structure should be driven by business 
needs.  Given business needs vary from Business Unit to Business Unit and 
person to person, the task of developing a portal as the single interface for 
all Enron Business Units is large.  

Consider the following diagram as a high level plan we may reference to 
develop the content strategy for a best practices portal.  

Requirements Phase	Design Phase	Build Phase	Test Phase 	Launch Phase


We are currently in the requirements phase of this project.  Although 
multiple, personalized portals have been developed, unveiled and implemented, 
we are still gathering requirements to create a best practices portal.  The 
task force is chartered with the responsibility to develop a Knowledge 
Management proposal.  In this proposal, we may consider the process through 
which containerable information is identified, developed, and maintained.  In 
the meantime, the content strategy team is available for the task force 
members to consult.  The content strategy team will help Bryan Powell,s team 
shape mynetwork.com.

With respect to content strategy, some of the responsibilities a KM proposal 
should review include:
? A plan to develop a process to determine what information is important to 
contain
? A plan to develop a process to identify owners of containers
? A plan to develop a process for teaching people how to build containers
? A plan to develop a process for cleaning up data
? A plan to develop a process for inventorying data on websites
? A plan to develop a process for inventorying data on the &O8 drive and 
other assets
? A plan to develop a process for creating a consulting portal kit whereby 
specific needs of communities are identified and reflected in a best 
practices portal
? A plan to develop a process for shutting off old channels (i.e. email from 
Office of the Chairman) and turning on new channels (i.e. portal delivery of 
Office of the Chairman information)


Next Steps.

Identify content strategy &to do,s8 for the requirements phase.
Identify owners of content strategy &to do,s8 for the requirements phase.
Establish weekly meetings for content strategy team.
Content strategy team members gain authorization from management to support 
task force.