FYI.
----- Forwarded by Marie Hejka/Corp/Enron on 12/12/2000 02:21 PM -----

	Marie Hejka
	12/12/2000 01:37 PM
		 
		 To: Brandon Rigney/Corp/Enron@ENRON, Allen Elliott/HOU/ECT@ECT
		 cc: Anthony Mends/Enron Communications@Enron Communications, David 
Gossett/Enron Communications@Enron Communications, Bryan Powell/HOU/ECT@ECT, 
John Gillespie/Corp/Enron@ENRON, Andrea Yowman/Corp/Enron@ENRON, Melissa 
Becker/Corp/Enron@ENRON, Debbie R Brackett/HOU/ECT@ECT, Pegi 
Newhouse/HOU/AZURIX@AZURIX
		 Subject: Content Strategy/User Experience Meeting Notes

  12/06/00

Thank you for your participation in last week,s Content Strategy/User 
Experience meeting.  Please review the below meeting notes.

Sincerely,

Marie Hejka




  12/06/00
Content Strategy/User Experience Meeting Notes

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

Meeting Details.
Per Allen Elliott, myportal.com is a proof of concept portal, a production 
ready prototype portal developed using Tibco Portalbuilder ) Enron,s standard 
portal development tool.  

What content is accessible from the portal needs to be decided.  Each 
Business Unit (and Functional Unit within) needs to decide the following: who 
makes this call, what is important for the BU/FU to have on a portal, who has 
responsibility for the content, who will publish it, and who will maintain 
it?  Historically, this is a challenge to determine.  Business Units and 
Functional Units typically want desired information available, but do not 
want to take any responsibility in defining, creating, or managing the 
information.  

Per Brandon Rigney, the four tabs identified by the ASE breakout group are 
organization centric.  This is a problem for users.  For example, if the 
aisles in a library were arranged by publishers (i.e. Simon & Schuster, 
Prentice Hall, McGraw Hill, etc.) one would have to know the publisher of the 
information before a subject could be located.  This would not provide easy 
access to information.  

Does the above analogy rule out the task force,s interest in unveiling a 
portal with defined areas  from which all users blast (Rick Causey,s word)?  
The Content Strategist/User Experience experts are not telling the task force 
members what to do as much as they are informing us what to expect from what 
we have been discussing to do.  If easy access to information is our 
objective, perhaps we may further discuss the implication of designated blast 
points.  

Brandon and Allen recommended using the BU/FU to determine what is accessed 
from the portal for a given business unit.  

Meeting Conclusion.
Requirements Phase	Design Phase	Build Phase	Test Phase 	Launch Phase
Even though Bryan Powell,s organization is scheduled to release the proof of 
concept portal the week of 12/11, we are still in the requirements phase of 
the project.  Again, the portal is a proof of concept for Tibco 
Portalbuilder.  The first version of the portal will reflect information 
pulled in from multiple areas of Enron.  Additional versions of the portal 
will be released reflecting a BU/FU specific content.  

Marie will work with task force members to use BU/FU contacts to define BU/FU 
portal content requirements.  

Content, content, content.  Task force members need to determine through BUs 
what to include.

Recommendations from the ASE need to be reviewed.

Next Steps.
Assign task force members to interview BU/FU contacts
Invite task force members to participate in Content Strategy/User Experience 
meetings
Task force and Content Strategy/User experience team further discuss ASE 
recommendations
Emphasize myportal.com, it is a proof of concept for Tibco and Interwoven