Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Objective

...

  • 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.

...

  • 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

...

  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

  3. Ongoing

    1. Steering Committee Working Sessions and Reporting

...

  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

    2. Success Measurement

      1. Handles

      2. Domains

      3. Use

    3. Roadmap Achievement

Budget

...

      1. Integration

        1. New Partner Integration Increase

    1. Lag - Past and Current Performance

      1. Roadmap Achievement ?

      2. Revenue ?

KPI Tools

  1. TBD

Roadmap

Resource Allocation & Budget

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

Role Type

Role

...

Time Allocation (Monthly)

Director

WP Leader

Strategy

CTO

Strategy

CPO

Core

Lead Architect

Core

Senior Engineer

Implementation

...

(Development)

Architect

Implementation (Development)

Engineer(s)

Implementation (Development)

QA

Implementation (Development)

Project Mgmt

Implementation (Development)

Release Mgmt

Implementation (Development)

Ops

Implementation (UX)

Research

0.25

Implementation (UX)

Jr. UX Visual/IA

0.25

Business

This will be supplemented by the business team within FIO

?

Marketing

This will be supplemented by the marketing team within FIO

?