Your SlideShare is downloading. ×
Toolkit meeting presentation uwic
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Toolkit meeting presentation uwic


Published on

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Work Based Learning Maturity Toolkit:
    UWIC Pilot.
    Andrew Haldane
    Loretta Newman-Ford
  • 2. Why use the WBL Maturity Toolkit?
    • Test the Toolkit to establish whether it is fit-for purpose, robust and user-friendly before advertising it to the wider UWIC community
    • 3. explore how the toolkit could help to formulate an institutional WBL strategy.
    • 4. A way of assessing UWIC’s current state of play in terms of WBL and to inform future developments in this area.
  • Area of focus
    The toolkit was piloted at:
    • Institutional level
    • 5. School level
    • 6. Programme level
    Our own focus was also to consider:
    • how well the toolkit described WBL maturity (from the user perspective)
    • 7. ways in which the toolkit could be used/customised
    • 8. what actions could be taken to improve WBL at UWIC
  • Methodology
    Conduct face-to-face meetings with stakeholders using a semi-structured interview approach
    Approach key stakeholders
    Develop action plan to address areas of ‘immaturity’ and also for strategising WBL
    Send Toolkit URL
  • 9. Customisation of the Toolkit
    • Informal customisation of the Toolkit
    • 10. Re-phrasing statements as questions to prompt discussion and reflection around criteria
  • Outcomes
    Pilot findings:
    • WBL at UWIC is currently fragmented
    • 11. We need to formalise WBL activities
    • 12. A single WBL policy with high level objectives, but with enough scope for localised planning and implementation, is needed.
    • 13. Staff need to feel ownership
    • 14. The Toolkit was found to be unsuitable for use with large groups of stakeholders
    • 15. There was consensus that the toolkit was an accurate, comprehensive representation of WBL maturity
    Resulting actions:
    • Development of an institutional strategy
    • 16. Work with Schools to create localised plans and activities, structured around the strategy
    • 17. Generate procedures for WBL to inform staff about how to develop and deliver high-quality WBL
  • Lessons learnt and future plans
    • Explore ways of making the Toolkit more usable by groups of stakeholders
    • 18. Compare a well-established WBL programme with newly validated programme and facilitate support and collaboration between teams
    • 19. Use the Toolkit , a document which clearly and comprehensively illustrates WBL readiness, to inform the development of a UWIC strategy
    • 20. Establish the process for strategy development
    and take steps to achieve this
    • The Toolkit could be more user-friendly
    • 21. The Toolkit could facilitate the evaluation and
    action planning processes more effectively
    • The Toolkit would be more useful in an online form
  • Suggested updates for the Toolkit
    Based on the UWIC pilots, it is recommended that the following updates be made to the WBL Maturity Toolkit:
    Re-work the Toolkit into an online format
    Categorise statements into ‘core’ and ‘supplementary’.
    Present maturity indicators as questions rather than statements
    Use a 3-point traffic light system to illustrate the level of ‘maturity’
    Introduce spaces for users to record their responses, reflections, strengths or concerns in relation to criteria, or perhaps a SWOT analysis
    Create an action plan section where stakeholders can begin to develop ideas for development, etc.
    Reduce the amount of jargon used. This was found to be off-putting to users