/
EDU Analyst Diversity Overview Improvements

EDU Analyst Diversity Overview Improvements

 

Created Date

Nov 12, 2022

Target PI

PI4

Target Release

Jira Epic

Document Status

Draft

Epic Owner

@Michael Griebling (Deactivated)

Stakeholder

Engineering Team(s) Involved

Analyst

This was originally planned to be done in Q4 but will not be completed because EDU Analyst resources will be used to help with Career Pathways and HWOL work instead.

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

-I want to see if our graduates are adding matching/adding/decreasing the racial, gender, and ethnic diversity of the target occupations in our market.
-I want to see if our institution as a whole is representative of our community.
-Are we more/less diverse than our community?
-Are we more/less diverse than other institutions in our region?
-How have we improved our diversity over time compared to our market?
-How have we improved our diversity over time compared to other institutions?

 

Value to Customers & Users

Especially for community college users, these are questions that users are having to answer today but have to do it by using data from numerous tools or data sources. Even though Analyst contains all the data needed to answer these questions users would still need to run and combine numerous reports and it would still be very manual and time-consuming. Many users don’t realize that Analyst has all the data to answer these questions since it is spread across several reports.

We are saving users time and effort and giving them a visualized answer they can user for their own research or hand off to leadership at their institution.

Value to Lightcast

None of our competitors offer a similar workflow so we would gain a competitive advantage in a area that is top of mind for many institutions.

Additionally, the more research we allow users to do in Analyst and the more questions they can easily answer the more value the tool has and the more likely they are to buy and renew.

Target User Role/Client/Client Category

Institutional Researches
Marketing

Delivery Mechanism

Analyst

 

Success Criteria & Metrics

Within the first six months of release successful adoption would result in 1500 page views. This usage would put the report in the top 15 of most used EDU reports.

We also want to see 25% of report users returning to use the report again within 90 days. This indicates that after running the report users found value and are coming back to use it again.

Aspects that are out of scope (of this phase)

Solution Description

We will use the IPEDs gender/race/ethnicity data on completions and with our CIP-SOC mapping, we can then compare the makeup of the completers to the matching SOCs and the gender/race/ethnicity of those matching occupations in the geographic area the user selects.

Here is an example of what we already show users about the makeup of their graduates their entire institution or certain programs:

And here is an example of what we would need to match it to and the SOC data:

 

Early UX (wireframes or mockups)

<FigmaLink>

 

Non-Functional Attributes & Usage Projections

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

 

Dependencies

Just need Analyst front-end resources.

Legal and Ethical Considerations

No.

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

High-Level Rollout Strategies

  • In advance of rollout brief marketing on feature and use case to evaluate if we should prepare marketing collateral around the new use case and functionality.

  • Initial rollout to internal Customer Success and Sales teams in Education to prepare them on how to train or communicate this to existing users and how to pitch this to potential customers.

  • The feature will be released for all users across all BU’s.

    • Coordinate the release of the feature with a Pendo announcement that will include a short video communicating what the feature is and how we would recommend using it.

    • Will also check with Customer Success and see if this is something they think should get included in the next webinar after the feature release.

  • Monitor feature usage and any feedback from users.

 

Risks

 

Open Questions

When can we build this?

 


Complete with Engineering Teams

 

Effort Size Estimate

2

Estimated Costs

Direct Financial Costs

No.

 

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

Analyst Red

Medium

 

 

 

 

 

Related content