1 / 4

Commissioning Support Services: The Design of Checkpoint 2

DRAFT – RESTRICTED – NOT FOR CIRCULATION. Commissioning Support Services: The Design of Checkpoint 2. 20 February 2012. Checkpoint 2. The Purpose of Checkpoint 2:

ivie
Download Presentation

Commissioning Support Services: The Design of Checkpoint 2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DRAFT – RESTRICTED – NOT FOR CIRCULATION Commissioning Support Services:The Design of Checkpoint 2 20 February 2012

  2. Checkpoint 2 The Purpose of Checkpoint 2: • To assess whether the CSS can develop and improve to Checkpoint 3 where they will be commercially viable and able to offer commissioning services that are valued and affordable for customers. • To agree a binding development and improvement plan between the CSS and the BDU. Three fundamental assessment tests at Checkpoint 2: • Leadership. There needs to be strong leadership to drive the development of the new business and agree the improvement plan with the BDU • Customer Focus. There needs to be the basis of a constructive and mutually reinforcing customer dialogue. There will be limited time to create this post Checkpoint 2 • Business Mindset. This is about building new businesses, not new organisational forms Design of Checkpoint 2

  3. Anecdotal Evidence Post Checkpoint 1 Pre-Checkpoint 2 Some Good News: • More leaders in place • More CSS development teams with freedom to developnew ideas • Good customer engagement • Better recognition of the OD challenges Some Less Good News • Confused or fragile leadership arrangements • Problems delegating CSS development to new leaders • Weak separation of CSS development activities from core business • Customer coercion and lack of respect for customers • Slow understanding of demands of building a business • Too much focus on glossy plans and not enough on fundamental business development Design of Checkpoint 2

  4. Checkpoint 2 Philosophy BDU concerned that too many CSS are on the cusp of failing Checkpoint 2 There is an urgent need to: • Ensure CSS leaders are in place with clear authority and freedom to develop the new commissioning businesses • Ensure CSS are supporting effective conversations with CCGs • Continue the development of business planning documents but these need to be credible and consistent with the real progress in business development. Therefore, Checkpoint 2 will have significant face-to-face, will featurestrong triangulation and be a wide, deep bar. Design of Checkpoint 2

More Related