/
Widget Builder Improvements for Multi-Institution Clients

Widget Builder Improvements for Multi-Institution Clients

 

Created Date

Mar 23, 2023

Target PI

PI3

Target Release

May 26, 2023

Jira Epic

https://economicmodeling.atlassian.net/browse/CC20-2529

Document Status

Draft

Epic Owner

@Sandra Poisson

Stakeholder

 

Engineering Team(s) Involved

Career coach

PART 1

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

As a member of a consortium of schools, I want to ensure the programs advertised in widgets are limited to just those my institution trains for.

As a web content editor for my school which is part of a larger group of schools, I want to efficiently and easily create widgets I know are showing career data for just my institution’s programs. 

Value to Customers & Users

Value to Learners: 

  • By displaying the most relevant and actionable information within the individual college’s pages, they can utilize the correct data in their college/program decision.

Value to Customers:

  • Time Savings - Lowers the bar and effort needed to determine which programs within the Program Widget Builder, are theirs so they are displaying their mapped career outcomes for their specific programs.

    • Right now, the Programs selector only displays the first program with the name and credential combination as it’s returning only unique name/credential combinations.

  • Utilization - Clients will be able to create Assessment Widgets that only display their individual program offerings mapped to the careers of interest.

Value to Lightcast

  • New Sales: Opens the door to consortiums or state agencies with a single Career Coach instance, to provide individual colleges within that group a chance to buy and easily use the Widget Builder

    • Wyoming College Commission has voiced interest in their colleges getting this product

    • 38 Total count of CA & US sites marked multi-Institutional (13% of all sites) as of 3/13/2023

      • Currently, there are no Widget Builders activated for multi-institutional clients.

  • Retention: For the larger state deals that are at risk (specifically Iowa DOE, renewal value of $135,000.00) due to lack of continued state funding, this will provide a carrot for those participating institutions to gain access to Widget Builder. The Institutions would contribute more funding to make up for the lost grant but would receive widgets in exchange.

Target User Role/Client/Client Category

Target User Role: Career Coach/Widget Builder Admins, specifically IT or Web Content Editors 

Target Client/Client Category:  Career Coach multi-institutional customers and new multi-institutional clients

Delivery Mechanism

Career Coach Widget Builder

Success Criteria & Metrics

There’s a new setting for our Widget Builder Admins to limit their individual institution’s programs when they build their widgets.

We would determine success by looking at the:

  • Did we successfully retain the at-risk state system site? They are up for renewal in September 2023.

  • Within the next 12 months did we get at least 2 additional state systems to buy the Widget Builder?

A longer-term success metric is after a multi-institution client purchases, we’d predict to see a large increase in the widget views and user interactions due to the information being presented to many more learners.

Aspects that are out of scope (of this phase)

  • Having site settings saved for each institution in the list (colors, default locations, and selected data points)

PART 2

Solution Description

  • Add a way for the clients to select an Institution from a list and have that selection filter the Programs offered list within the Program Widget Builder

  • Have an Institutional filter in the Assessment Widget Builder that would filter the Programs Available to just the selected Institution

Early UX (wireframes or mockups)

https://www.figma.com/file/1u7N9QEr41ScI0t49EfJrQ/Career-Coach-Widget-Builder?node-id=1446-1198

 

Non-Functional Attributes & Usage Projections

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

We need to keep the same accessibility and mobile responsiveness features that we have now and all performance characteristics should be the same. We’d see more clicks and activity and will be able to report that.

Dependencies

n/a

Legal and Ethical Considerations

Just answer yes or no.

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

High-Level Rollout Strategies

  • Work with Sales & Education Success so they are aware of the new capability a month or so prior to the release to get potential clients interested.

    • Help as needed with those conversations.

  • If deemed appropriate, work with Marketing to help generate buzz.

Risks

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

 

Open Questions

What are you still looking to resolve?

 


Complete with Engineering Teams

 

Effort Size Estimate

1

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

Career Coach

Small

https://economicmodeling.atlassian.net/browse/CC20-2529

 

 

 

 

1s Epic Lookback 1-4-24

We would determine success by answering these questions:

  • Did we successfully retain the at-risk state system site? They are up for renewal in September 2023.

    • Unfortunately, they canceled due to losing a large grant that funded the project.

  • Within the next 12 months did we get at least 2 additional state systems to buy the Widget Builder?

    • At approximately 7 months post-release, we’ve had no new sales that would utilize this feature.

My conclusion that this was project is not successful. However, I’ll leave this as in feedback until the year mark to confirm that.

 

Related content