Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Current »

Workshop across all three TIS squads resulted in the following. Shared widely for those outside the TIS dev teams to take forward.

THE PRODUCT VISION BOARD (Team M)           (c/o Roman Pichler)

Vision

What is your purpose for creating the product?

Which positive change should it bring about?

“A national system to improve the learning journey of healthcare professionals to deliver the highest quality care.”

Target Group

Needs

Product

Business Goals

Team

Which market or market segment does the product address?

Who are the target customers and users?

What problem does the product solve?

Which benefit does it provide?

What product is it?

What makes it stand out?

Is it feasible to develop the product?

How is the product going to benefit the company?

What are the business goals?

Mugabee

  • Public sector – NHS.

  • Workforce Planning and Intelligence.

  • TIS Admins.

  • Trainees.

  • Data people.

  • Doctors.

  • Clinical staff.

  • Boris.

  • External systems – NDW / GMC / ESR…

  • Recruitment – Planning for recruitment / forecasting.

  • Manage trainees’ details and training – clear and fast in one system.

  • Save cost for the organisation

  • Improve junior doctors’ lives / morale.

  • Make things more efficient.

  • Changes and tailoring to suit business needs.

  • Ownership.

  • Software – Web application / platform / desktop / mobile elements.

  • Admin system? Content management system?

  • Cheaper, tailored, flexible, user-friendly.

  • Reducing costs.

  • Improve efficiency and management of trainees.

  • Stable and efficient – improve quality of training to enable good treatment patients.

Leeerrroooy Jenkins

  • Trainees.

  • Trusts.

  • Local Offices.

  • US!

  • GMC etc.

  • Reliable model for system integration and data management across "The Service".

  • Better interoperability.

  • Avoiding manual 'data-crunching'.

  • Unblocking people.

  • Let them trust the data.

  • Show when it hasn't worked/isn't reliable.

  • System Integration and Business Process agreement; and engagement - that just works.

  • Happy Doctors (because their data is right and have time to train and provide care).

  • Happy Admins (not having to keep numerous systems up to date).

  • Happy system experts.

  • Stop all these groups of people leaving because they are unhappy.

  • Meet Legal requirements.

Vulcan

  • Trainees and their administrators.

  • Master data source of training information.

  • Facilitation/automation of data change management.

  • Nationalisation of best practices across local offices including interoperability with external systems.

  • Focus on user-centricity.

  • Value for money - maintainable, scalable and sustainable.

  • Training management/self-management.

  • User empowerment.

  • Suite of digital tools to replace previously used off-the-shelf and paper solutions.

  • Improving data quality and integrity.

  • Enabling more accurate workforce planning.

  • Business process automation.

  • Improve user experience.

  • Improve effectiveness and efficiency of training management processes.

  • No labels