KPIs
KPI | Summary | Next Steps |
---|---|---|
Integrator satisfaction |
|
|
FIO Data Services uptime |
|
|
SDK satisfaction |
|
|
SDK feature coverage | Is this a meaningful KPI? |
Survey
Overall level of difficulty of integration
1 – Very difficult
2 – Difficult
3 – Neutral
4 – Easy
5 – Very easy
Recommended improvements:
Documentation (https://developers.fioprotocol.io)
1 – Poor
2 – Fair
3 – Good
4 – Very good
5 – Excellent
Recommended improvements:
Technical support
1 – Very dissatisfied
2 – Dissatisfied
3 – Unsure
4 – Satisfied
5 – Very satisfied
Recommended improvements:
SDK
1 – Poor
2 – Fair
3 – Good
4 – Very good
5 – Excellent
Recommended improvements:
Integrator satisfaction
Question | Integrator 1 | Integrator 2 | Integrator 2 |
---|---|---|---|
Integration Features (Filled out FIO team) | |||
Overall level of difficulty of integration (1 – Very difficult, 2 – Difficult, 3 – Neutral, 4 – Easy, 5 – Very easy) | |||
Documentation (1 – Poor, 2 – Fair, 3 – Good, 4 – Very good, 5 – Excellent) | |||
Technical support (1 – Very dissatisfied, 2 – Dissatisfied, 3 – Unsure, 4 – Satisfied, 5 – Very satisfied) | |||
SDK (1 – Poor, 2 – Fair, 3 – Good, 4 – Very good, 5 – Excellent) |
Questions
Would it make sense to remove this WP and move the budget and resources into the Partner Success and Core Chain WPs?
Does the steering committee think it is important to track this project and cares about the KPIs?
Technical support and QA for partners is done in the Partner Success WP
Partners require support for their API nodes which is in the Core Chain WP
Both the API and SDKs (and the associated documentation) are used by integrators. So, why have them in separate groups?
SDK features are closely tied to API features.
Other KPIs that would be helpful