portal! an intranet game workshop on planning, design and implementation kmworld 2005 november 14,...
out of 32
Post on 24-Dec-2015
Embed Size (px)
- Slide 1
- PORTAL! An Intranet Game Workshop on Planning, Design and Implementation KMWorld 2005 November 14, 2005 Peter Jones, Nick Kizirnis Redesign Research
- Slide 2
- Getting Started Welcome, Who we Are Peter Jones, Redesign Research Nick Kizirnis, LexisNexis Getting to know you Name, Organization, and role only - Our Approach Theres simply too much to cover, so we will Simulate problems through discussion Share lessons from experience Learn from each other in small groups
- Slide 3
- About this Workshop Whats to Learn? You dont need another lecture You may need to know how to deal Objectives: We want you to come away with: I can do this. This makes more sense to me now. This helps me fit together new ideas with what I know. How? By identifying key decision points. By knowing how to leverage your priorities. Knowing that you have options.
- Slide 4
- How will this work? An Agenda Start with your business. Drivers and constraints of business A brief exercise Then Planning, Requirements, Nick, then Pete talks briefly. Another exercise (in small groups) The break for coffee Then Design, Implementation. What can we say in 20 minutes? A Design exercise, then wrap up.
- Slide 5
- What are the handouts? An outline of the content space Our outline of the problem space We look at practices team practices What to do, when, and how. These are the Big Ideas for: Leverage Making the most of your position Priorities Focus only on whats important Options - when all else fails!
- Slide 6
- Cut to the chase A definitive report on portal design, usability, & implementation: Goodwin and Nielsen (2002-2005) Building Intranet Portals - a Report From the Trenches We have learned from Nielsens work - but have our own experience to add. In each content area, we note applicable Nielsen findings and lessons learned: Endorsed Critiqued
- Slide 7
- Know your Business (Why you have this job) Business Drivers: Prime motivators for action and change. Business strategy is a coordinated response to drivers of the industry. - Competition: Strong products - Cost: Reduce systemic costs and waste - Control: Improve operational effectiveness Organizational Needs: - Efficient communication across enterprise a single portal or communications path - Self-service of employee benefits and registrations - Resource for managers - Support for each business function, operational/product/sales
- Slide 8
- Business and Organizational Issues Inquire about the real Business Needs Typical Needs as Given: - Productivity - Eliminate duplicate technology & communications - Single portal for company communication How do you measure ROI? When facing portal decisions, call on business needs!
- Slide 9
- Organizational Infrastructure Does legacy pre-determine your portal? How do you do portals? By type of technology? By function? By organization? By who pays? Project types: 1.Initial Building from scratch 2.Conversion e.g. from Intranet to Portal 3.Major Redesign Dealing with patchwork 4.Update Adding features, search, etc.
- Slide 10
- Key Portal Features 1.Search 2.Single Sign-On 3.Integration of multiple intranet sites 4.Business Process Coordination 5.Document Management 6.Self-Service (e.g.. benefits, employee data) 7.Personalization
- Slide 11
- Organizational Lessons People issues are the biggest cost in portal implementation. We agree thats why our focus on decision-making process. Involving users from an early stage eases acceptance problems. (Unhappy users mean low ROI.) Yes, but who are users? Employees? Managers? How many? Set up a cross-function steering group (users feel they have a voice, & to overcome resistance). Have 2-3 feedback groups Management steering group, Customer Advisory Board (CAB), and User Council. Stop funding non-compliant projects to speed standardization. Yes, but who, how? Portal teams do not control that funding! If a portal is good, people will see its benefits eventually. Portals take over! Resistance is futile. Benefits must be immediate. From Nielsen, 02-05
- Slide 12
- Your Exercise 1: Individual Portal Problems Work in pairs, interview each other Ask each other & take notes: 1.Tell me about your job 2.Your current problem 3.Who is/are your customers? 4.What do they (customers) want? 5.What are you able to deliver? Post your notes to flip charts by Project Type
- Slide 13
- Portal Planning Gather Your Resources Who are you and what do you? Who else is out there and how can they help? Creating the team Be a project manager Document your work Working with teams, scope, budget and schedule Be a product manager Consider the enterprise Know your audience, plan for user research Connect back to why you are building the portal Know your portal(s)!
- Slide 14
- Content Planning What is the Content? Subjects Structure Who owns the Content? Establish accountability Where is the Content? Location, location, location(s) Centralize or de-centralize Tell us all about the content Content Inventory/Audit ROT: Redundant, Out-Dated, Trivial
- Slide 15
- Technical Planning Take IT to lunch Be partners not adversaries Checks, Balances and being in the know Read the Manual (or the Cliff Notes) Potential user, technical, budget, political issues Its slow systems testing How well does the current system work? What are the issues? How much better is the solution? Really?
- Slide 16
- Planning & Content Management Lessons Portals do not solve intranet usability issues. They can create them. True has anyone launched a portal that wasnt used? Portal tech may demand tradeoff between speed & flexibility. Decide which is most important to you. (But having flexibility & lots of design options doesnt always improve user experience.) Decide on your priorities before choosing. How to determine your priorities? Think about the different ways content might be used once in portal. Dont just think about find out from your user base. You will need central guidelines to ensure usable content. Rules can make users lives easier in the long run. Consider service-level agreements for internal providers. (And how is this going?) From Nielsen, 02-05
- Slide 17
- Requirements, a dynamic vision Where you discover them: 1.Organizational Overall business and organization needs (See Section 1) 2.Team Tools, content, and resources for product teams and working groups 3.Employee Individual task needs, portlets and tools for getting job done
- Slide 18
- Enterprise portal stakeholders Corporate HR, Benefits Operations, IT, CTO Corp Communications Sales Product ManagementProjects, Development Workgroups Users 1 2 3
- Slide 19
- Requirements Gathering Team process with Project Mgt, Business unit An actively managed process be proactive. Meaning, try thinking like your customers. Practices To learn, try one for each customer: Customer Roundtables Focus Groups User Surveys Personas & Task Scenarios: Organizational line managers Employees Staff (e.g., HR, Corp Comm, Purchasing) Contextual Interviews / Observations Usability Testing (Test current & identify new)
- Slide 20
- Task & Content Requirements A strong task model simplifies everything. Trade-offs between business needs as stated & tasks. Structure content by Function not Department What are the tasks all employees will accomplish? Document your Task Model (or Use Cases) Review with stakeholders. Prioritize your features, tools, and gadgets Better to have fewer good tools - than many mixed-purpose & utility
- Slide 21
- Being Agile with Requirements? Analyzing requirements? You will not have time to analyze. Instead, creative decision-making Setting priorities within & among customers, features, user tasks Rapid, Adaptive Development Agile process (Highsmith, Cockburn) Requirements largely speculative Use prototypes, collaborative design Rapid revision, quick feedback tests See agilemanifesto.com
- Slide 22
- Being Agile means: Timeboxing Establish delivery cycles & timeboxes in each Deliver once/month Developers meet once/dayF2F Customers once/weekF2F Requirements change Since they will change, welcome change If youre collaborating, no real surprises occur Leverage your priorities to manage scope Continuous development portal is low-risk
- Slide 23
- User Experience & IA Information Architecture (IA) Task & Workflow models Content structure & guidelines Navigation and site mapping Page layout and structure Finding tools: Search, results, redirection Effective structuring of content and information for communication, usability, readability.
- Slide 24
- Information Architecture methods Constraints: Scope Search Tech Templates Size, volume Content Time Legacy data IA Methods: User models: Personas Task models: Activity maps Prototypes: - Page - Visual - Info design User Testing: Simple Usability IA Products: Personas & scenarios Tasks = Functions Prototypes = - Paper - Wireframes - Mockup - Interactive (Depending on scale/risk, use one or all)
- Slide 25
- User Experience (UX) Design considerations Site Structure Navigation Interface and Interaction Design Visual and Branding Design Content gui
View more >