Follow

Capriza Onboarding: Steps to Go from Zero to Production

The purpose of this article is to provide a description of Capriza’s Implementation Methodology. It is intended to convey the nature of the work performed by the Capriza team during a typical implementation and the key steps required to go live.

 

 

Zapp Use Case Workshop


As a best practice, we recommend all clients begin their Capriza engagement with an on-site Zapp Use Case Workshop to fully define the scope of the engagement and their long term plans for Capriza’s solution. The workshop is broken into two sessions: Use Case Discovery & Mapping and Execution & Planning.

Once the workshop is complete, the Customer Success Manager delivers the Zapp Roadmap. This document serves as Capriza’s recommendation, feasibility assessment, and summary of what was learned during the workshop:

  • Participant Insights
  • Use Case Proposal
  • KPI Definition per Use Case
  • Recommended / Prioritized Roadmap
  • Initial Go-Forward Plan

Audience: Project Manager, Business Process Lead, Technical Lead, Customer Success Manager, Customer Success Engineer

 

 

Kick-Off Call


The client’s assigned Customer Success Manager (CSM), Customer Success Engineer (CSE), and Regional Sales Manager (RSM) organize an initial project kick-off call to confirm high level project goals and requirements, project team roles and responsibilities, communication protocols, and timeline dependencies.

During this call, we ask a series of questions that help us understand each of these components, as this will be critical to defining an overall project plan, the critical path, and timelines for key milestones. We also use this time to request appropriate user access, better understand existing infrastructure requirements, their development environment, identify potential hurdles and limitations, and communicate these to the client based on our diagnosis.

Audience: Executive Sponsor, Project Manager, Technical Lead, Customer Success Manager, Customer Success Engineer

 

 

User Experience Design

 

The CSM and Capriza’s internal Design team work with the client’s team to create design documentation. This process begins with a walkthrough session where the client demonstrates the source application that will power the Zapp and walkthrough the proposed use case, workflows, and success criteria. Based off of these inputs, the Capriza Design team creates mockups of the proposed Zapp based on our established UX Best Practices. The current design of the client’s website/application and brand standards are taken into consideration to ensure a consistent user experience during the entire process.

Customers are encouraged to send written feedback on the mockups after running them by internal stakeholders. Capriza iterates on these mockups until the scope is locked.

Audience: Project Manager, Business Process Lead, Technical Lead, Customer Success Manager, Customer Success Engineer

 

 

Technical Deployment Architecture

Capriza works with the client team to design and implement the appropriate deployment architecture necessary to integrate Capriza with your source applications and client deployment platforms. Through a series of sessions, our experts assist the client in identifying, designing, and building runtime environments, networking infrastructure, and client platform integration to satisfy corporate security policies and systems. 

Audience: Project Manager, Networking Lead, Firewall Lead, Technical Lead, Customer Success Manager, Customer Success Engineer

 

 

Implementation

Zapp Configuration

Your assigned CSM and CSE are responsible for configuring the initial Zapp based on use cases identified in the identification and design phases of the project.

Unit Testing and Zapp Iteration

Your assigned CSE validates individual Zapp components by performing unit testing. Any discrepancies, issues, or updates needed are addressed in an iterative cycle followed by regression testing to ensure continued and desired functionality of all prior capabilities.

Zapp Styling

Styling updates are incorporated into the Zapp as detailed in the Design phase. This is typically done after the core controls and screens have been built.

 

 

Zapp Review & Testing

Once the initial Zapp version is completed, the Capriza CSM and CSE QA the Zapp to ensure that they are configured and functioning properly. Capriza reviews the Zapp with your team and makes updates and troubleshoot issues as required.

We also work with you to help develop a test plan. In general, the testing phase consists of the following key steps.

Use Acceptance Testing

Your CSM works with you to put together a user acceptance testing strategy. We recommend these tests include a subset of users representing various user types and groups to account for all Zapp variations. Feedback should be solicited from these test users as it relates to overall user experience, any technical issues, and the Zapp’s overall value.

Performance Optimization

 

During this phase, our team will also ensure that the performance of the Zapp we are delivering is optimal. We will run time tests on both the source application and Zapp to establish baseline metrics and implement various caching strategies, such as first page caching and configuring login cookies, as appropriate.

 

Pre-Deployment Tests

Differences in Testing and Production environments may bring to light issues not observed during the Zapp building or UAT processes. To ensure a smooth Go Live, additional testing should be performed in the Production environment pre-deployment.

 

 

Training

Capriza provides training sessions for Zapp designers to enable them to design, build, and maintain existing and future Zapps. Training includes creation of training guides and a 2.5 Day Zapp creation training session. In addition, Capriza helps your team define the organizational functions needed to successfully manage and maintain the ongoing lifecycle of Zapps.

The Training workshop typically takes place in parallel with the implementation or testing phase.

 

 

Launch and Adoption

Launch and adoption consists of three key stages:

  1. Release to Production – Once the Zapps have been tested in the production environment they are ready for distribution to end users. Capriza assists with defining the distribution groups which should have access to the Zapps. In general, we recommend rolling the Zapp out in phases to continue collecting user feedback and iterating upon the Zapp’s design.

  2. Communicate to Target Audience – Capriza assists you in developing marketing and promotional materials to send to the target audience to raise awareness of the new Zapp.

  3. Assess Adoption – Capriza analyzes the ongoing growth of Zapp users against adoption targets, timelines, and other KPIs established at the beginning of the project and offer any recommendations for revisions that based on our learnings may increase adoption. Adoption Reviews are carried out on the following intervals:
    • 5 days Post-Launch;
    • 3 weeks Post-Launch;
    • 2 months Post-Launch;
    • Quarterly thereafter.

 

 

Revisions and Enhancements

Once the project achieves successful adoption, Capriza continues to work with your team to assist with product enhancements and apply best practices as they evolve.

 

Future Zapps



Your Customer Success Manager works with you to plan rollout of future Zapps. Capriza resources are available to support your team, including technical guidance and troubleshooting, creation of mockups, distribution best practices, and adoption evaluation.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.