Page Comparison

Objective (DRAFT)

To maintain the existing implementation and construct new features to support adoption and use of the FIO dashboard for end 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 the dashboard into industry segments.

Description/Mission

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.

Use Cases

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

KPIs

• Operational

  • Uptime SLA

  • Bug

• Success Measurement

  • Handles

  • Domains

  • Use

• Roadmap

Budget

• Dashboard Budget

...

Implementation

Current

1. Strategic

   1. Roadmap Feature Specs

   2. Resource Planning

   3. Development Feature Scope

   4. Marketing Planning

   5. Educational Planning

   6. Metric 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. Marketing

   4. Educational

   5. Metrics

Future

1. Strategic

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

   1. Is it ownership or reporting structure for example?

3. How will resources work across efforts?

4. What are the guardrails for decision making?

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

   1. Product Refinement Plan (based on metrics)

   2. Future Feature Roadmap Ideation and Creation

   3. Resource Planning

   4. Follow-on Marketing

   5. Continual Metric Review

   6. Tactical Implementation

      1. Existing UX Tweaks

      2. New UX

      3. New Development

      4. New Marketing Campaign

      5. Educational based on new features

   7. Ongoing

      1. Steering Committee Working Sessions and Reporting

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:

KPIs

...

What do you consider success and failure of the worker proposal (details, a statement, a stake in the ground) - Quarterly - Define failure and raging success - Not sufficient to just be a bucket .. 

• Operational

  • Uptime SLA

  • Bug

• Success Measurement

  • Handles

  • Domains

  • Use

• Roadmap

Budget

• Dashboard Budget

Resource Allocation

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

1. Director / WP Leader

2. CTO / Strategy

3. CPO / Strategy

4. Development

   1. Architect

   2. Engineer(s)

   3. QA

   4. Project Mgmt

   5. Ops

5. UX

   1. Jr. UX Visual/IA

6. Business ?

7. Marketing ?