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

When using SkillsMatch on an institution’s website, I want to see program matches that are reliable and not confusing, so I can make the right decisions for my education.

Value to Customers & Users

• Confusion around program match results will be reduced

• Displayed results will be of higher relevance to the user

• Matches will be made using an up-to-date taxonomy

Value to Lightcast

• This change will highlight our proprietary LOT

• We will eliminate dependency on a model that cannot be maintained
  
  

Target User Role/Client/Client Category

Institutions and their Learners served by SkillsMatch. 

This is also being built for Lightcast to remove reliance on an unsupported dataset.

Delivery Mechanism

SkillsMatch platform update.

Success Criteria & Metrics

• Skill Clusters have been removed from all areas of the SkillsMatch platform and Skills API.

• All functionality provided by Skill Clusters has been replaced by other datasets.

• Measured by VoC work and feedback from Sales and Success

Aspects that are out of scope (of this phase)

N/A

Solution Description

Early UX (wireframes or mockups)

No UI adjustments are necessary for the work to be done in this epic

Non-Functional Attributes & Usage Projections

N/A

Dependencies

This Epic is dependent on the completion of https://economicmodeling.atlassian.net/browse/SKL-905

That epic will provide the replacement for the outcome matching currently provided by Skill Clusters.

Legal and Ethical Considerations

No

High-Level Rollout Strategies

• Communication to Sales and Success teams about the upcoming changes, with details that can be communicated to customers.

• Monitor SkillsMatch usage and any feedback from users.

Risks

• There is a risk that users coming back to the site after the release will notice differences in their matches. 

• Internal risk/cost of working on a product will be sunsetting at the end of 2024

  • Minimized by knowing we’ll be bringing a version of the functionality into the Career Coach Platform, so the work would need to be done at some point.

Open Questions

What are you still looking to resolve?

• Are we clear on the full scope of the work to be done here?

• Should this be treated like a standard data run (coming out of the Maintenance bucket) or a new feature?

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.