Chapter 3: Fundamentals of Capability 5:15

Brief

Performance Measures – Business Outcomes, Capability Health Check, Processes Encapsulated in the Capability, Roles and Skills Required to Execute, Technology to Manage the Enabling Workload.    

Abstract

Capability is a key concept in evaluating and enhancing systems performance. It is typically decomposed into several sub systems - performance measures with leading and lagging indicators, enabling processes, skills, and supporting technology. This paper outlines the basics of capability 5:15.  

Performance Measures

• Business Outcomes

  • 5-fold improvement in how organizations conceive, plan, allocate resources, execute and assess impact of change

  • 15% productivity improvement annually in Value Chain Processes’ performance

• Capability Health Metrics 

  • o   Performance Measures

    • Lived Experiences of staff and customers, other relevant stakeholders

    • Pipeline of Opportunities

    • Impact of Investments/Change  

  • o   Diagnostic Measures

    • State of Opportunities by Line of Business, and by Value Chain Process

    • Stakeholder engagement

    • Status of Pipeline of Opportunities

Capability 5:15 Governance

Typically, responsibility for the above outcomes is spread over number of different roles. To ensure timely support and accountability, we are advocating the following governance:  

• Capability Owner – This role owns the capability, need to demonstrate results to his/her superiors.   

  • CEO and CEO direct reports

  
  

• Capability Manager – This role manages the day-to-day operations of the capability, clearly has the accountability for capability’s performance and reports directly to the capability owner. The Role:

  • Director Enterprise Productivity

  • Is supported by - Enterprise PMO, Enterprise Architecture, Organization Change Management,

  • Partners with – Value Chain process owners

Capability 5:15 Encapsulated Processes

• Proactive – proactively define and maintain a pipeline of opportunities

  • Tasks

    • Capture the Lived Experiences of staff/customers with current processes, policies, procedures and systems, etc.

    • Identify potential improvements based on Experiences and industry expertise

    • Group improvements and strategies into Potential Opportunities

  • Deliverables

    • Backlog of improvements for each process and service backed by specific stakeholder’s Lived Experiences and enterprise strategies

    • Pipeline of Opportunities, Architected Roadmap and Business Case

• Pre-Project – Given level of available investment, need for improvement and willingness to accept disruption create scope for change

  • Tasks

    • Detail the selected Opportunities and develop comprehensive Roadmap and business case

    • Create detailed implementation plan

  • Deliverables

    • Detailed Architecture, Business case implementation plan for the selected scope

• Execute Change – Implement roadmap that is based on approved scope

  • Tasks

    • Change scoped processes, systems and OCM

    • Agile project delivery

  • Inputs

    • Clearly defined backlog of improvements ( Tech dependent, non tech dependent, transformational)

    • Adapted Roadmap for target improvements

    • Adapted Business Case

    • Milestone level project plan

  • Manage Project

  • Outcomes

    • Manage all resources () and deploy change to production

    • CAB – did implementation conform to approved architecture roadmap 

• Assess Impact – Post change – assess if the desired change is created both in systems and eco system

  • Tasks

    • Assess if improved processes overcame the obstacles identified through the lived experiences

    • Assess eco systems and readiness for results to materialize

  • Outcome

    • Reassess Lived Exp of impacted stakeholders and determine if obstacles are removed,

    • Assess if the change created the conditions for intended outcomes to materialize  

Technology 

Stakeholder Forum is a machine learning enabled software as a service implemented on ServiceNow platform or on Microsoft Azure cloud. The automation offers number of benefits

Key Roles and Skills 

• Product/Service Custodian – this role ensures the service readiness. This is a non managerial role and provides an objective view of service’s readiness to meet the needs of the enterprise. Typically this role reports into lines of business leadership.

• Systems Architect – this role brings deep architecture, system engineering and business skills that ensure technology capabilities are optimally aligned to business needs as well as solid understanding of ROI.

• Project Manager – this role brings deep project management skills to manage diverse set of skills and motivations to deploy architected solutions with deep focus on creating an environment for results to materialize.