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

As a user, I would like to see more migration insight when using Lightcast’s datasets. Currently, I only see information on migration at the county-to-county level, and I would like to get more granular/broader as I try to understand migration patterns in my region.

As a community organization (who maybe read the Talent Attraction Scorecard), I would like to have an understanding of how my community is doing at attracting or losing talent.

I would like workflows that enable me to understand

1. whether I’m net gaining or losing people, and whether that is within my state or to other states

2. where they are going,

3. who is leaving.

I would like to develop targeted strategies to either recruit more talent to my region, or to stop the outflow of talent.

Value to Customers & Users

Our customers are asking about migration, especially with the annual publication of the Talent Attraction Scorecard. But our current delivery in the tool is limited.

1. It is a single large table, which only provides county-to-county level migration data

2. There are no headline numbers to direct customers' use of the table

3. There is no ability to segment the data at all. It is simply the IRS migration numbers - no insights on who, or what occupations or skills are coming/leaving, or from what institutions.

Hypothesis: Our customers would have much more usage out of our migration data if it was enabled across multiple levels (i.e. MSA and State). They would be able to answer more questions about:

1. Overall net migration

   1. Trend

      1. In-state / Out-of-state?

      2. Increasing / Decreasing?

2. Talent loss by:

   1. Occupation

   2. Degree

   3. Skill

Value to Lightcast

We can provide more robust data and reports that provide more detail to our Lightcast customers.
We can more directly leverage the excitement of the Talent Attraction Scorecard by revealing workflows within the product

Target User Role/Client/Client Category

Target users include:

• Economic developers

• Workforce agencies

• Real estate (i.e. Analysts, GIS researchers, Brokers)

Delivery Mechanism

Reports that currently contain migration data at the county-to-county level will also have the option to choose among MSA-to-MSA and state-to-state levels as well.

• Migration Map (comparable to toggling within Occupation Map)

Success Criteria & Metrics

• Tagging this migration report/dashboard 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 migrations report.

• User interviews/questionnaires through CS teams

Aspects that are out of scope (of this phase)

Solution Description

Early UX (wireframes or mockups)

<FigmaLink>

Non-Functional Attributes & Usage Projections

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

Dependencies

Reach out to the Data/API team (we already map this within Occupation Map)

Legal and Ethical Considerations

No

High-Level Rollout Strategies

• Work with the Data/API team(s) to figure out what data/API we currently have within Lightcast

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

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

• The rollout strategy should be discussed with CS, Marketing, and Sales.

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

• Monitor usage and feedback from customers

Risks

Focus on risks unique to this feature, not overall delivery/execution risks. 

Open Questions

Do we need to change the Economy Overview to include MSA-to-MSA or State-to-State levels? Any other reports?

Complete with Engineering Teams

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.