Page Comparison

Objective

...

To maintain & support the existing implementation of the dashboard and construct new features to support adoption and use of the FIO dashboard for end & use by users as well as integration partners.

Primary

The primary dashboard effort will create a path to ensure:

• The dashboard is hosted, maintained and continually running.

  • Existing features are maintained, supported and evolved based on feedback.

  • Paths to adoption and use through user base growth and business partner integrations are created in concert marketing and business efforts.

Secondary

The secondary dashboard effort will create a path to ensure:

• New features are surfaced, prioritized and built to support additional use and integration opportunity

  • A scalable future for dashboard users.

  • A scalable future for the dashboard into industry segments.

Description/Mission

• Description Language

KPIs

• Operational

  • Uptime SLA

  • Bug

• Success Measurement

  • Handles

  • Domains

  • Use

• Roadmap

Budget

• Dashboard Budget

In my view the worker proposal for the dashboard consists of the following examples:The mission of the dashboard is to drive adoption by end users and integration partners with the net effect being increased use of FIO handles and domains which create direct paths to revenue for the organization as well as defining FIO as THE protocol of choice within multiple industry sectors.

Strategy

The strategy for the dashboard is founded around three main areas of opportunity; the end user, integration partners, and new opportunities. Each of these areas will have use cases which will be used to support them and serve in helping to create the KPIs for this project.

• End User

  • Increase number of and value of domain sales (103)

  • Increase number of FIO Crypto Handle registrations (86)

  • Increase awareness of FIO Protocol (113)

• Integration

  • Increase Domain & Crypto Handle Registrations and Utilization with Partners

• Opportunity

  • Support new creative ways FIO Protocol can increase usability across new segments.

Use Cases

The use cases for the dashboard provides high level guidelines and context for product use across different segments and users.

End User Segments (P2P)

• Cryptocurrency

  • Ease of Use

  • Single Source Asset Management

  • TBD

• NFTs

  • Authentication

  • TBD

Integration Partners (B2B)

• Cryptocurrency

• NFTs

Integration Partners (B2P)

• Financial

• Gaming

• Authentication

• Data

Implementation

Current

1. Strategic

   1. Roadmap Feature Specs

   2. Resource Planning

   3. Development Feature Scope

   4. Marketing Planning

   5. Educational Planning

   6. Metric

      KPI Planning

2. Tactical Implementation

   1. UX

      1. Current Roadmap

      2. QA

      3. Bug Fixes

   2. Development

      1. Current Roadmap

      2. QA

      3. Bug Fixes

      4. Marketing

      5. Educational

      Metrics

3. Ongoing

   1. Steering Committee Working Sessions and Reporting

Future

1. Strategic

   1. Product Refinement Plan (based on metrics)

   2. Future Feature Roadmap Ideation and Creation

   3. User Research

   4. Resource Planning

   5. Follow-on Marketing

   6. Continual Metric

      KPI Review

2. Tactical Implementation

   1. Existing UX Tweaks

   2. New UX

   3. New Development

   4. New Marketing Campaign

   5. Educational based on new features

3. Marketing

4. Educational

5. Metrics

6. Ongoing

   1. Steering Committee Working Sessions and Reporting

KPIs

Schedule and Topics

Dashboard KPIs must be actionable and measurable. Their success depends on objective, statement of detail and the “stake” in the ground. The following is a proposed schedule and topics for creation of initial KPIs.

1. Schedule

   1. Q3 2022

      1. Create Initial KPIs (including but not limited to)

         1. Description

         2. Label

         3. Owner

         4. Updater

         5. Calculation

         6. Frequency

         7. Scope

         8. Metrics

      2. Identify KPI Management Tools

      3. Initial Measurement Tested

   2. Q4 2022

      1. Measurement - TBD

      2. Refinement - TBD

   3. Q1 2023

      1. Measurement - TBD

      2. Refinement - TBD

   4. Q2 2023

      1. Measurement - TBD

      2. Refinement - TBD

2. Topics

   1. Lead - Predicting Future Success

      1. User

         1. New Handle Increase

         2. New Domain Increase

         3. Usage

      2. Operational

         1. Uptime SLA

         2. Bug

      3. Integration

         1. New Partner Integration Increase

   2. Lag - Past and Current Performance

      1. Roadmap Achievement ?

      2. Revenue ?

KPI Tools

1. TBD

Roadmap

• Dashboard Roadmap

Resource Allocation & Budget

It requires the following resources regardless of where it lives structurally:

1. Product Owner

2. Product Management Resource

3. SME

4. UX Resource (to ensure tactical efforts do not bottleneck development)

5. Development Resource

6. Marketing Resource

7. Educational Resource

8. Steering Committee (from a directional input perspective)

9. Potentially: Business Relationship Arm

Questions:

1. What would be the differences in the two - Standalone vs. Underneath?

   1. Is it ownership or reporting structure for example?

2. How will resources work across efforts?

3. What are the guardrails for decision making?

4. How does this work on multiple efforts? Like for example, I want to spend time on exploring new tech and opportunities

KPIs

...

The most important element

...

• Dashboard Budget (DRAFT - Needs Allocation Completed)