Skip to content
English
  • There are no suggestions because the search field is empty.

Technical Readiness Template

Please see below the brief for Technical Readiness for this moving forward along with some guidelines in these types of meetings. Technical Readiness sessions only need 2 x verbal participants from SBS and anyone else is simply observing. (i.e. Account Manager/Sales or Project Manager drives the meeting and documents discovery, Technical works with Clientside IT and software. Training or Sales observe if PM is present.) The purpose of the technical readiness meeting is: How do they currently use their target application and does DMO work in their target application. Document what the clients current workflow is (end-to-end) What is their target application and how does it work. How does DMO operate in their Target Application Test Autotext and step by step commands Is there any other additional information (hardware, footpedals etc) that may have been missed in the Sales Discussions. Meeting Guidelines: ** 1 person to drive the meeting ** No interruptions across the customer during the session **Ask the customer questions and let them answer ** Give clear instructions. **Keep it simple and succinct. **Be mindful of when the mic is still on **Don’t ask questions to improve your understanding of the technology during the customer session – take that off line and internal. **Don’t interrupt each other **Clear stages of the session – i.e. discovery at the beginning on workflow, how they use the software then formal handover to support to work with Clientside IT to see if the discovery that has been witnessed can be implemented PREP: Work with IT to ensure that DMO is installed on Devices/Assets relevant to Tech Ready session.