The G7 lead I supported required a system to track project progress and provide them with greater insight for reporting purposes. I took this as an opportunity to upskill in M365. Following research, I created a Microsoft Form for colleagues to complete and submit weekly. The advantage of this was it synced to an Excel Spreadsheet which collated the inputted data from the Forms. This provided the G7 an overall progress picture in one place stored in SharePoint. This process was initially met with resistance. Upon reflection I should have discussed the tool within the team, I could have pre-empted the resistance. To combat this and support colleagues with the new process, I used the team meeting to explain the purpose of the tool and give a demonstration. I also created a visual aid clarifying how to complete the Form, what SLT required in the updates and the resulting spreadsheet. This meant colleagues could better engage with this new process and support one another in their projects. My actions meant colleagues felt more confident using the tool leading to its success. The new process gave the team's SLT greater oversight of different tasks within the team. This resulted in the G7 efficiently updating SLT from one snapshot document instead of 1:1 discussions, allowing the G7 more time to focus on their priorities. The tool supported the team to work more collaboratively with one another and enriched their 1:1 discussions with the G7, as the G7 could see their latest update., Following feedback, I was tasked with reviewing the products to improve accessibility. Time was short because the lengthy 30-page M365 Governance Document itself had been updated and a Team Talk was ready for publication. I began by making a list of documents that required changes and assessed the time required. Recognising the challenge to meet the timeframe alone, I liaised with a colleague to help. The team had little experience with the accessibility tool previously. I upskilled them in its use as they were struggling. I kept a log of all changes made and how I did it, for future use and to support colleagues with future products. I began by updating the guidance that would require the least changes. Once completed, I reviewed timings for the remaining more complex guidance. Prioritising and engaging support meant I could complete this project without impacting any of my other duties. It also meant I could upskill colleagues which benefits to team. I consulted with a stakeholder who used accessibility software daily. By engaging the stakeholder, I was able to get guidance reviewed and take onboard feedback before submitting. My actions resulted in the guidance being updated on time and shared across 28,000 CCG staff supporting them with M365 policies, data protection compliance, UK GDPR, and best practice. Analytics following publication showed increased engagement with the CCG Information and Records Management Site. Now by having one document accessible to all meant our team had resource available to focus on priority work., I saw my new role supporting a G7 as an opportunity to explore smarter and more impactful working methods. I was tasked with presenting ways for us to work effectively together. I began by discussing what the G7 thought they needed the most support with and how they preferred to work. I researched tools available and presented possible solutions to the G7. Looking at their diary I knew their time management could be improved. I created a task tracker where the G7 could delegate tasks, we could communicate with one another. I also decided, after discussing this with their team and the G7, to reduce the weekly 1:1s to every other week. I also encouraged the G7 to make time for well-being breaks to support them at work. I also created a Managers Assurance Programme where we tracked colleagues' responses to quarterly checks and any important reminders such as Carer's Passport reviews. This meant I could be proactive in planning important meetings with their team. A successful trial of my programmes resulted in the G7 feeling less overwhelmed. Concentrating on well-being made their tasks appear more manageable. By changing the 1:1s from weekly to fortnightly meant the G7 was more time effective and the team able to focus on their deliverables. The decision to create the MAP meant I could take responsibility and support the G7 with admin management requests. I could easily pre-plan and organise the important meetings between the G7 and their team., In a previous role, I was new to the civil service and the team was new with roles not yet clearly allocated. Colleagues and I were inducted at different times, which meant we all had varying levels of ability and training. A colleague had confided in me that, they were frustrated with other colleagues who led on SharePoint creation requests, inbox queries and security incidents as it meant they couldn't develop their skills. None of this work was distributed amongst the team, which was becoming an issue. I decided to approach our team leader about this and provide a solution, so we all had equal opportunity. The solution was to create a weekly rota of when each colleague lead or deputised on our tasks. The rota allocated a colleague to leading on security incidents, SharePoint creation requests, our inbox requests. The team leader agreed and began to implement it. It was met with resistance as colleagues did not like the changes, but it was important that our whole team could develop and be confident on their work. My suggestions led to the rota being implemented. This meant all of the colleagues in our team had equal opportunity for tasks. Each lead was set up with a deputy alongside them which acted as a way to ease pressure if there was an influx or priority incident. The rota led to better team cohesion, and all our team being able to feel confident using the security tool and investigating different incidents., I was asked to support an SO with delivering awareness presentations about Records Management. This work supported the SO in completing the Information Management Report. I had more capacity than the SO and I took the lead with managing the sessions. I created MS Forms and support documents. I created a separate spreadsheet, and this is how I tracked attendance and sent invites. We kept this on our team's SharePoint so we both had access. Storing in SharePoint meant the G7 could share updates to SLT on the success of the presentations. The support document which detailed the tasks the support role needed to complete to support the SO and successful delivery. The document included meeting invites, when to include links for each slide and the MS feedback forms. By doing this, it meant the SO could focus the presentations and the support would be seamless as it was all written down and easy to follow. The actions I took led to the presentations being a success. I supported delivery of 14 sessions to 430 CCG colleagues. My actions meant I could track the registered attendees; I could provide support and meet my priorities outside of support work. By creating the feedback form, I pulled analysis from it, and this led me to suggesting improvements our presentations and further boost engagement on the sessions and our SharePoint. It also meant the SO successfully completed the Information Management Report with added detail of how we were supporting colleagues with records management.