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

As a product manager responsible for AO 2.0, I want to ensure we are promoting our partnership with the National Student Clearinghouse (NSC), including the access that all mutual customers receive to NSC’s Student Tracker Premium Service.

As a customer of AO 2.0, I want all AO 2.0 users at my insitution to be aware of and easily access all the benefits of my Lightcast purchase (including NSC’s Student Tracker Premium Service).

As a user of AO 2.0, if I want to access NSC’s Student Tracker Premium Service but don’t have a login, I am shown a name and contact information for who I can connect with at my institution to request a login.

Value to Customers & Users

As a customer of AO 2.0, I have confidence that all AO 2.0 users at my institution are aware of and can easily access all the benefits of my Lightcast purchase (including NSC’s Student Tracker Premium Service).

As a user of AO 2.0, I am made aware of all the benefits I have access to (including NSC’s Student Tracker Premium Service).

Value to Lightcast

• Differentiating AO 2.0 from AO 1.0 (with a new/unique feature)

• Promoting usage and engagement of AO 2.0 (as a jumping point to NSC StudentTracker Premium)

• Showcasing and supporting our NSC Partnership

Target User Role/Client/Client Category

Institutional Research, Academic Leadership, Enrollment Marketing, and Advancement/Foundations teams across all current Edu segments.

Delivery Mechanism

AO 2.0 will be delivered as a separate product on the Analyst platform.

Success Criteria & Metrics

Users are made aware of and connected (external link) to NSC’s Student Tracker Premium Service from the AO 2.0 interface.

Users are shown a name and contact information (email address and/or phone number) for their StudentTracker Premium Service admin (so that they can request login credentials from them, if they don’t already have them).

Pageviews (of areas in the tool where we promote this) and clicks (on external links to this) are instrumented and tracked.

Aspects that are out of scope (of this phase)

Any single sign on (SSO) like functionality that would auto log users into NSC’s (without them having to enter their credentials on a login page).

Solution Description

Early UX (wireframes or mockups)

Not yet designed – this could be it’s own section/page or it could be a banner/message of some kind.

Non-Functional Attributes & Usage Projections

Nothing unusual (in terms of performance characteristics, privacy/security implications, localization requirements, mobile requirements, and accessibility requirements)

Dependencies

Design work

Preceding AO 2.0 epic: https://economicmodeling.atlassian.net/wiki/spaces/DPM/pages/2487255106

Legal and Ethical Considerations

High-Level Rollout Strategies

• Immediate rollout to all AO 2.0 customers upon completion

• Notification to Sales and Success teams so that they can promote and support this

Risks

N/A

Open Questions

N/A

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.