effectiveness, and information security. The corresponding business value is also described.
Efficiency KPIs
Business Value KPI Current Measure Target Measure
Cost of maintaining existing content and managing new content development is reduced Cost per service request TBD TBD Effectiveness KPIs
Business Value KPI Current Measure Target Measure
Improved service levels for web content management, maintenance, and information architecture development Response time for content updates turnaround time TBD TBD Information Security KPIs
Business Value KPI Current Measure Target Measure
Improved span and degree of control over information quality, accuracy, and cross‐ agency integration TBD – working with Security team to identify appropriate metric TBD TBD
7.5 Consolidation Levels
EOEEA defines the degrees to which website information architecture and the governance thereof is consolidated in three key levels of consolidation:Level 1 Level 2 Level 3
7.9.1 Consolidation Plan – Part I of II: Decommission ‘Rogue’ Websites
Part I of II: Key Activities, Objectives, and Expected Outputs Each key activity listed in the table above is tied to those key objectives and expected outputs generated as a result of executing this activity and listed below:Key Activity Objective (Purpose) Expected Outputs
Content volume may be initially estimated by page count in the existing website system, and may be further refined after the content analysis and IA development phases are underway (e.g., some agencies ultimately do not migrate half of their content because it is not relevant to the public or is duplicated elsewhere in the Mass.Gov IA). Content complexity refers to the degree of linkages and dependencies an agency’s content may have with other agencies or external entities, in some cases. In those instances, additional working sessions are needed to negotiate the future state IA. Week 2 Week 8
Week 0 Week 4 Week 6
7.9.2 Consolidation Plan – Part II of II: Core Portalization Plan
Once a ‘rogue’ website is decommissioned, the core portalization process is followed. A “typical” portalization project lasts anywhere from 16‐ 20 weeks and typically includes six key phases: 1. Preparation and planning 2. Content analysis and information architecture development 3. Training / content / site building 4. Launch planning, usability testing, user acceptance testing and approval 5. Launch, execute communication plan 6. Post‐launch support Part II of II: Key Activities, Objectives, and Expected Outputs Each key activity listed in the table above is tied to those key objectives and expected outputs generated as a result of executing this activity and listed below:Key Activity Objective (Purpose) Expected Outputs
Key portalization activities are outlined below following the six key phases described above. The durations of each activity will differ depending on the volume of content for each agency and the content complexity. Content volume may be initially estimated by page count in the existing website system, and may be further refined after the content analysis and IA development phases are underway (e.g., some agencies ultimately
Week 4 Week 16 Week 20
Week 0 Week 8 Week 12 Week 18
do not migrate half of their content because it is not relevant to the public or is duplicated elsewhere in the Mass.Gov IA). Content complexity refers to the degree of linkages and dependencies an agency’s content may have with other agencies or external entities, in some cases. In those instances, additional working sessions are needed to negotiate the future state IA.
Key Activity Start Date End Date Proposed Owner(s) Support
