PI2: Asynchronous File Loading Research

PI2: Asynchronous File Loading Research

 

Created Date

Oct 26, 2022

Parent Initiative

https://economicmodeling.atlassian.net/wiki/spaces/DPM/pages/2612789278

Target PI

2023Q1P1 PI-2 2023

Target Release

March 31, 2023

Jira Epic

https://economicmodeling.atlassian.net/browse/ARK-9138 https://economicmodeling.atlassian.net/browse/ARK-9139 https://economicmodeling.atlassian.net/browse/ARK-9602

Document Status

Draft

Epic Owner

@Jeff Blasbalg (Deactivated)

Stakeholder

@Ben Bradley @Tim Delcourt (Deactivated) @Josh Wright (Deactivated) @John Hunt @Jennifer (Deactivated)

Engineering Team(s) Involved

Customer/User Job-to-be-Done or Problem

As a user, I would like to access Lightcast data so I can derive more in-depth insights across many regions, data types and for all historic years for my organization. Currently, the data that we can download is limited by geography and segmented by data making it inherently hard to select many data points for all regions (and subregions) or unselect them at once. 

 

Value to Customers & Users

There are limitations to the existing reports and users have left Lightcast for more robust data access provided by our competitors. The user needs a better tool because:

  1. They can’t perform analysis/modeling type of work

  2. They can’t compare regions or data on any scale

  3. They can’t graph trends over all periods

  4. They can’t easily couple types of data (within or outside of the platform)

  5. They are not sophisticated enough for our API or aren’t willing to pay for our API

 

Value to Lightcast

Community’s top competitor offers a more robust data downloader that is frequently cited as a reason for loss - direct competitive impact.

We have lost a number of clients to our competitors because they provide users with the ability to customize their data downloads. While we have an existing data downloader, our users say that we could make it better by improving their customized data pulls.

We can charge a premium for clients that require access to more data but aren’t sophisticated enough or willing to pay for our API.

 

Target User Role/Client/Client Category

Primary target users include:

  • Real estate/asset management

  • Workforce agencies

  • Economic developers

Additional value becomes available across markets:

  • Institutional researchers

  • Companies

 

Delivery Mechanism

Users will be able to access this data and report via front-end - it is still TBD whether this will be delivered via Analyst.

 

Success Criteria & Metrics

For PI 2…

  • success will be measured by completion of full UX/UI designs, full function and specifications, and full documentation

  • Proof of concept completion

  • Customer feedback validating UX/UI designs

  • Sales commitments that are pending delivery

 

Aspects that are out of scope (of this phase)

Actual front-end development will not start during PI 2.

 

Solution Description

Early UX (wireframes or mockups)

<FigmaLink>

<MiroLink>

 

Non-Functional Attributes & Usage Projections

Consider performance characteristics, privacy/security implications, localization requirements, mobile requirements, accessibility requirements

 

Dependencies

  • If we choose to further develop Data Downloader 2.0, we need to verify whether or not we are breaking contract terms for Developer.

  • Tagging the tool within Pendo is a good way of measuring the usage of the tool.

  • It’s important to apply user testing (i.e. Playbook UX) in order for us to understand how our users feel when using our demographics report/dashboard.

  • User interviews are important - it would be good to spend time with CS folks

 

Legal and Ethical Considerations

Yes

Have you thought through these considerations (e.g. data privacy) and raised any potential concerns with the Legal team?

High-Level Rollout Strategies

  1. Figure out our contract terms and get feedback from CS, Marketing, and Sales on driving this new initiative

  2. Interview clients who left Lightcast for a competitor’s data downloader OR check Salesforce for feedback as to why these clients left for our competitors

  3. Create a prototype and get feedback from stakeholders, teams, etc.

  4. Work with the Engineering team on estimated timelines and LOE to create the tool within Analyst

  5. How long we would tolerate having a “partial rollout” -- rolled out to some customers but not all

  6. Monitor usage and feedback from customers

 

Risks

  • Do we provide access to all Lightcast data? Here are some risks we run into:

    • There is time-value of our labor cost for pulling the data

    • The question of whether there is use for CS with this feature

    • Cutting off potential API sales

    • Cutting off potential consulting sales

 

Open Questions

  • How else do our competitors outperform us with their version of a data downloader?

  • How much can we charge for this tool as an upsell where it provides enough monetary value to Lightcast, without matching the cost of selling our API?

  • Would Talent provide additional resources to expedite the timeline on this project?

 


Complete with Engineering Teams

 

Effort Size Estimate

Estimated Costs

Direct Financial Costs

Are there direct costs that this feature entails? Dataset acquisition, server purchasing, software licenses, etc.?

 

Team Effort

Each team involved should give a general t-shirt size estimate of their work involved. As the epic proceeds, they can add a link to the Jira epic/issue associated with their portion of this work.

Team

Effort Estimate (T-shirt sizes)

Jira Link

Team

Effort Estimate (T-shirt sizes)

Jira Link

Micro

XS

N/A - only doing consulting

 

 

 

 

 

Related content