[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-0-en-105":3,"doc-seo-665361-105":59,"doc-detail-665361-en":130},{"code":4,"msg":5,"data":6},0,"success",[7,13,18,23,28,33,38,43,48,51,55],{"id":8,"doc_module":4,"doc_module_name":9,"category_name":10,"show_sort_weight":11,"slug":12},1,"Document","Story & Novel",90,"story-novel",{"id":14,"doc_module":4,"doc_module_name":9,"category_name":15,"show_sort_weight":16,"slug":17},2,"Literature",80,"literature",{"id":19,"doc_module":4,"doc_module_name":9,"category_name":20,"show_sort_weight":21,"slug":22},4,"Exam",70,"exam",{"id":24,"doc_module":4,"doc_module_name":9,"category_name":25,"show_sort_weight":26,"slug":27},5,"Comic",60,"comic",{"id":29,"doc_module":4,"doc_module_name":9,"category_name":30,"show_sort_weight":31,"slug":32},6,"Technology",50,"technology",{"id":34,"doc_module":4,"doc_module_name":9,"category_name":35,"show_sort_weight":36,"slug":37},7,"Healthcare",40,"healthcare",{"id":39,"doc_module":4,"doc_module_name":9,"category_name":40,"show_sort_weight":41,"slug":42},8,"Research & Report",30,"research-report",{"id":44,"doc_module":4,"doc_module_name":9,"category_name":45,"show_sort_weight":46,"slug":47},9,"Religion & Spirituality",20,"religion-spirituality",{"id":46,"doc_module":4,"doc_module_name":9,"category_name":49,"show_sort_weight":46,"slug":50},"World Cup","world-cup",{"id":52,"doc_module":4,"doc_module_name":9,"category_name":53,"show_sort_weight":52,"slug":54},10,"Lifestyle","lifestyle",{"id":56,"doc_module":4,"doc_module_name":9,"category_name":57,"show_sort_weight":24,"slug":58},19,"General","general",{"code":4,"msg":60,"data":61},"ok",{"site_id":62,"language":63,"slug":64,"title":65,"keywords":66,"description":67,"schema_data":68,"social_meta":123,"head_meta":125,"extra_data":127,"updated_unix":129},105,"en","driver-diagram-toolkit-guide-driver-diagram-toolkit-guide","Driver Diagram Toolkit Guide - Driver Diagram Toolkit Guide","","A practical toolkit guide explaining how to create and use driver diagrams to support project improvement work. It defines driver diagrams as a visual strategy that translates a single SMART aim into drivers and change ideas, clarifying the theory of change and promoting shared team understanding. Guidance covers when to develop the diagram, how to identify primary and secondary drivers, how to map interactions, and how to refine it through testing and measurement using PDSA cycles, with a worked example and further resources.",{"@graph":69,"@context":122},[70,84,105],{"@type":71,"itemListElement":72},"BreadcrumbList",[73,77,79,82],{"item":74,"name":75,"@type":76,"position":8},"https://docshare.wps.com","Home","ListItem",{"item":78,"name":9,"@type":76,"position":14},"https://docshare.wps.com/document/",{"item":80,"name":40,"@type":76,"position":81},"https://docshare.wps.com/document/research-report/",3,{"item":83,"name":65,"@type":76,"position":19},"https://docshare.wps.com/document/driver-diagram-toolkit-guide-driver-diagram-toolkit-guide/665361/",{"url":83,"name":65,"@type":85,"image":86,"author":91,"headline":65,"publisher":94,"fileFormat":97,"inLanguage":63,"description":67,"dateModified":98,"datePublished":99,"encodingFormat":97,"isAccessibleForFree":100,"interactionStatistic":101},"DigitalDocument",{"url":87,"@type":88,"width":89,"height":90},"https://docshare.wps.com/thumbnails/driver-diagram-toolkit-guide-driver-diagram-toolkit-guide/665361.png","ImageObject",300,407,{"name":92,"@type":93},"Marglet","Person",{"url":74,"name":95,"@type":96},"DocShare","Organization","application/pdf","2026-10-30","2026-10-29",true,{"@type":102,"interactionType":103,"userInteractionCount":8},"InteractionCounter",{"@type":104},"ViewAction",{"@type":106,"mainEntity":107},"FAQPage",[108,114,118],{"name":109,"@type":110,"acceptedAnswer":111},"What is a driver diagram and what does it include?","Question",{"text":112,"@type":113},"A driver diagram is a visual tool that breaks an entire project into parts that drive completion. It is built from a single aim, broken down into drivers, followed by change ideas as potential solutions.","Answer",{"name":115,"@type":110,"acceptedAnswer":116},"When should a driver diagram be developed, and how should it change over time?",{"text":117,"@type":113},"Driver diagrams should be developed in the initial stages of a project. They are not static and should evolve as understanding improves and the theory of change develops.",{"name":119,"@type":110,"acceptedAnswer":120},"How do you use the driver diagram to plan and test improvement?",{"text":121,"@type":113},"Start with a SMART aim, brainstorm and cluster driver ideas with your team, then set out primary and secondary drivers and add change/interventions. Draw interactions between drivers and refine the diagram as changes are tested and measured using PDSA cycles.","https://schema.org",{"og:url":83,"og:type":124,"og:title":65,"og:site_name":95,"og:description":67},"article",{"robots":126,"canonical":83},"index,follow",{"doc_id":128,"site_id":62},665361,1793300052,{"code":4,"msg":5,"data":131},{"doc_id":128,"user_id":132,"nickname":92,"user_avatar":133,"doc_module":4,"category_id":39,"category_name":40,"doc_title":65,"doc_description":67,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":8,"is_deleted":4,"is_public":8,"is_downloadable":8,"audit_status":8,"page_count":34,"language":139,"language_code":63,"site_id":62,"html_lang":63,"table_of_contents":140,"faqs":141,"seo_title":142,"seo_description":67,"update_tm":129,"read_time":143},2336477982702,"https://ap-avatar.wpscdn.com/davatar_9964176cb1d06d4a9deccf72a44ae3dc","Improvement Cymru Academy  \nToolkit Guide  \nDriver Diagram  \nWhat is a Driver Diagram?  \nA Driver Diagram is a visual tool used within improvement that takes an entire project and breaks it down into a series of parts. These parts are what drive the completion of the project. It is made up of a single aim, which is broken down into drivers, followed by change ideas (potential solutions) .  \nRationale  \nIt is a visual strategy for addressing a complex problem. It enables the team to articulate what parts need changing and is an inclusive process that is split into drivers in order achieve a desired outcome called an ‘aim’.  \nWhen to use?  \nDriver diagrams should be developed in the initial stages of the project. Importantly, they are not static and should evolve with greater understanding of the project or asthe ‘theory of change’ develops. They can be used alongside your project charter so that everyone can see the thinking.  \nDriver diagrams allow the project team to see quickly and clearly the ‘theory of change’ (how the aim will be achieved) . It helps teams work collaboratively and ensures everyone has a sense of shared understanding and purpose. A Driver Diagram can show that one change may affect multiple areas and thus help to achieve the aim. Driver diagrams can support understanding in many contexts such as process reliability and enhance user experience.  \nHow to use?  \nStart with the aim (statement)– This is intended to support you set out what you wish to achieve. It must be SMART (Specific, Measurable, Achievable, Relevant, Timely) .  \nNext brainstorm potential drivers with your team – these are the parts of the system that need to be focussed on to achieve the aim.  \nThe Primary drivers are the big topics and the secondary drivers are the areas of focus. Remember Driver Diagrams should be developed as a group and generated by the subject experts or stakeholders who work closely with the system.  \nConcentrate on generating ideas for drivers at this stage; do not try to allocate into primary or secondary drivers right away.  \nOnce you’ve completed the brainstorm, cluster the ideas to create an agreed set of drivers.  \n• Primary Drivers  \nThese are the big topics or areas that you will need to work on, to achieve your aim.  \nAll key areas of the system that you will need to influence within your project, should be captured within your drivers  \n• Secondary Drivers  \nEach primary driver is made up of secondary drivers. These are what would need to be in place to positively influence the primary driver. The difference between primary and secondary drivers is one of importance. If the driver is big and critical, you should consider it as a possible primary driver.  \nYou may need to involve other people who understand the primary drivers, to identify suitable secondary drivers.  \nSet these out in the Driver Diagram format.  \n1. Add your changes/interventions, these are your change ideas, that you think will lead to an improvement.  \n2. Draw lines between the drivers to show their interactions.  \n3. Refine the Driver Diagram as changes are tested and measured using the PDSA cycle.  \nExample-Driver Diagram 1  \nThe example below demonstrates a Driver Diagram which aims to achieve a 3lb weight loss by 31st October.  \nDiagram 1: Driver Diagram  \nLook at Diagram 1 and consider the following:  \nOutcome- ‘To achieve weight loss of 3lb by 31st October’ your project aim should be SMART.  \nPrimary Drivers-we need to give attention to how the weight loss can be achieved i.e.‘Calories in’ and ‘Calories out’  \nSecondary Drivers are the areas of focus for each primary driver.  \nChange/Interventions are the ideas that the team identify to achieve the aim, for example ‘Walk 10,000 steps per day.’  \nTo help develop the diagram:  \nSecondary drivers can connect to more than one primary driver. More than one change idea can connect to a secondary driver.  \nTo show the strength of the relationship you may wish to use lines, solid if strong, ","cbCaigD7fakRs6qE","https://ap.wps.com/l/cbCaigD7fakRs6qE","pdf",434863,"English","# What is a Driver Diagram?\n# Rationale\n# When to use?\n# How to use?\n## Primary Drivers\n## Secondary Drivers\n# Example-Driver Diagram 1\n# What next?\n# The Model for Improvement\n# Helpful tips\n# Additional resources\n# Further reading","[{\"question\":\"What is a driver diagram and what does it include?\",\"answer\":\"A driver diagram is a visual tool that breaks an entire project into parts that drive completion. It is built from a single aim, broken down into drivers, followed by change ideas as potential solutions.\"},{\"question\":\"When should a driver diagram be developed, and how should it change over time?\",\"answer\":\"Driver diagrams should be developed in the initial stages of a project. They are not static and should evolve as understanding improves and the theory of change develops.\"},{\"question\":\"How do you use the driver diagram to plan and test improvement?\",\"answer\":\"Start with a SMART aim, brainstorm and cluster driver ideas with your team, then set out primary and secondary drivers and add change/interventions. Draw interactions between drivers and refine the diagram as changes are tested and measured using PDSA cycles.\"}]","Driver Diagram Toolkit Guide - Driver Diagram Toolkit Guide | PDF",18]