Launching a digital banking solution is a large task that requires a great deal of planning and detail. After your team has gathered all the requirements and decided on the appropriate strategy how do you ensure that your launch plan covers the needs of your users and frontline staff? The following five focus points help to manage expectations and ensure that the experience is a positive one.
Planning (12 months prior)
- Work with lines of business teams to ensure their needs are met and discover any areas of concern or confusion. This will help you pinpoint any data cleanup or expanded training materials that need to be created.
- Work with the customer experience team to ensure NPS thresholds are set to the correct sample size at least 3 months prior to launch. This will help establish a baseline score prior to launch to compare against post-launch.
Marketing (12 months prior)
- Divide campaigns into data clean up and awareness.
- For example, if you need to ensure that your customer data file isn’t missing mobile numbers or doesn’t have outdated email addresses, run a campaign that solicits updates. Clean up campaigns should be short and direct in messaging. Interstitials are great for this purpose.
- Awareness campaigns can also be instructional with screenshots of updated flows and messaging around the benefits.
- Develop a marketing plan that includes a multitude of communication mediums:
- Banner Ads
- Call Center Scripts
- IVR Scripts
- Web Micro Page or blog
- In-branch Plasma Screens or signage
- Press Releases at Key milestones (i.e. alpha or beta releases)
Training (3-6 months prior)
- Develop interactive training materials such as quiz-based evaluations and video walkthroughs.
- Conduct Lunch & Learns at Alpha & Beta Releases for your frontline users where they can see demos. This will drive project engagement and UI familiarity.
- Rollout Beta to Employees for Testing & Feedback. This will allow employees to get familiar with the new app and help discover any bugs that impact their specific product or business logic.
- Use Call Center Staff to Train Branch Staff and vice versa. For example, select training days where branch staff can beta test and run any questions or feedback back to the call center. This type of training is a good mock run at real questions based on actual usage.
- Train a group of super users to tackle questions and/or troubleshooting steps.
- Create a centralized place to gather feedback and make sure that staff is familiar with the process for submitting feedback as well as clear points of contact.
- Communicate any open defects and resolution plans openly and explain work-arounds as well as resolution timelines.
- Gather feedback from internal staff based on customer interaction or personal use to drive future updates and prioritize for backlog.
- Consider a Run & Maintain Team and a New Feature/Innovation Team.
- One team dedicated to bugs or day to day updates is a good way to ensure any post launch blips are handled quickly.
- The new feature/innovation should be comprised of UX/UI and developers that can look at user feedback and determine any updates to flows or enhancements for future releases.
- Determine a release schedule that gives users that chance to get comfortable with the product. A constantly changing experience can make users uneasy and drive lower ratings.