Inspect and Adapt
The inspect and adapt phase is used to review collected metrics and determine any changes or improvements that can be gleaned from the data.
Inspect
Using analytics collected from Retool Platform and Retool University organizations can compare progress of a team or teams versus defined schedules.
- Retool University currently provides invididual analytics with aggregated analytics in the future.
- Retool Platform provides usage, space, and other analytics to track consumption by an organization and team.
From the information collected in the inspect phase, the COE team can review the team's progress including:
- Review team's expansion post onboarding and delivery of POC / MVP.
- How many apps have been created? (/apps)
- Are the apps being consumed? (/usage)
- How many resources have been created? (/resources)
- How many groups have been created? (/groups)
- How may users have been added to groups? (/groups/#groupid/members)
- How many folders have been created? (/folders)
- How many spaces have been created? (/spaces)
This information will provide a scaling sentiment value (e.g. increasing, stable, decreasing).
Collect Feedback
As teams complete their onboarding process, a survey should be completed electronically to determine the effectiveness of the COE, their processes, Retool platform and services.
Example Survey
Please complete the following survey to help us better understand your experience working with Retool Center of Excellence.
| Question | Example Answers |
|---|---|
| Onboarding / Intake Phase | |
| When did you first engage with the COE? | We engaged with the team on 7/1/2024. |
| What was your targeted delivery date for your first deliverable? | We were developing a POC and targeting a completion of 9/30/2024. |
| What was your actual delivery date? | We were able to complete the POC on 8/15/2024. |
| What was the app(s) / solution you were developing? | The solution we built was a Internet of Things (IoT) inventory management solution that leveraged Retool App(s), Retool Workflow(s) and Retool Database to automate inventory collection of deployed IoT devices and their status. |
| What issues impacted your team during onboarding (e.g., external delays, upskilling team, development issues, Retool issues)? | We were initially delayed by access to the IoT APIs running in AWS, requiring a IAM role to be enabled. This delay was 1 week. |
| Onboarding / Education Phase | |
| How was your team enabled on Retool (e.g. in person, company created content, Retool Technical team, Retool University)? | We brought in Retool PS to help with performing a quickstart to get us initially enabled. We then engaged with Retool Community/Retool University as we had issues/questions. We also leveraged COE office hours to raise any blocking items. |
| What educational resources would have been valuable to your team when onboarding? | Retool University provide a base level of upskilling. |
| What resources did the team use to unblock development issues (e.g. COE resources, internal team, Retool Community, other)? | COE, Retool Community |
| Onboarding / Support Phase | |
| How easy was it to engage / communicate with the team during the onboarding phase? | Our COE team established a MS Teams channel for asking questions as well as in-person office hours on Wednesday. Both were utilized during the POC. |
| What was the primary communication mechanism employed when issues occurred (e.g. in-person/office hours, email, messaging) | MS Teams Channel was mostly used to identify issues and get them escalated. |
| Did you use any Retool specific support features (e.g. Retool Community, Retool Technical Support)? | Retool Community |
| How effective was the COE in resolving technical issues? | The COE was able to intake questions and get a third of them answered, the others were forwarded to Retool to get answered. Retool Community was also leveraged to help provide solutions/direction. |
| What general feedback can you provide the team to improve support? | Retool experts in the COE would be helpful, although we are the first team so this will take some time. |
Adapt
Consider having a point of contact per team to have a dialog when teams are not expanding or usage is below anticipated thresholds.
- Is progress due to technical issues, lack of ability, external dependencies?
- Use Retool University to improve team's base knowledge.
- Use Retool Technical Account Management for specific topics.
- Use Retool Community as a knowledge base and support mechanism.
- Use Retool Customer Portal if enabled to do so to submit tickets.
- Assist team with external dependency issues if possible to do so.