project from a variety of other organisations and stakeholders. See Section 4.5.4 (Project Engagement) and Section 4.5.8 (Acceptability Summary). What worked well?  We were able to demonstrate the value of using data in a different way, evidenced by pilot workshops scenarios (data retrieval tasks and ecomaps) as well as the positive feedback and enthusiasm from users and other organisations  The opportunity to test and trial something in a ‘low risk’ setting provided a space to innovate  Different directorates and job roles worked well together to deliver the products  Engagement with a variety of sectors in different settings  Early engagement and co-production allowed for user-centric design  The project won the iStandUK award for innovation at the iNetwork awards in March 2024  A Senior Data Protection Officer was part of the project team who contributed to regular reviews and updates of the Data Protection Impact Assessment What didn’t work well?  Delays in the development have meant the tool is not as feature complete, refined or tested as anticipated  The focus on achieving the deliverables despite significant delays meant stretch goals were only explored to a small extent  Repurposing some of the budget allocation for external support necessitated legal support and time taken to agree the contract deliverables and terms (this took place during the delivery stage) What could have been improved?  At the start of the project the emphasis should have been more on secure cloud infrastructure rather than user requirements functionality  The requirement to agree deliverables far in advance, as part of the bid application was challenging when working in an exploratory context What can be learned from the delivery methods used?  Failure is okay and to be expe