/
Platform: User Classification

Platform: User Classification

Owned by Caleb Paul
Last updated: Feb 14, 2023 by Jillian Glassett (Deactivated)
2 min read

 

Created Date

Nov 2, 2022

Target PI

 

Jira Epic

 

Document Status

Draft

Epic Owner

@Caleb Paul + Chayce Kowalski

Stakeholder

 

Engineering Team(s) Involved

Analyst

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

Talent Analyst is too big for new users to navigate easily. Its user base is diverse enough to make it difficult to have standardized UI/UX and onboarding. There have been attempts to classify users ourselves with limited success. The best system would be to have users classify themselves by company name, job function, level, use-case. This will allow us to further develop customized UX for each user based on their classification.

Value to Customers & Users

In the JTBD framework, these are the “pains” and “gains” your solution will address. Other ways to think about it: What’s the rationale for doing this work? Why is it a high priority problem for your customers and how will our solution add value?

 

Value to Lightcast

Sometimes we do things for our own benefit. List those reasons here. 

  •  

Target User Role/Client/Client Category

Who are we building this for?

  •  

Delivery Mechanism

How will users receive the value?

  •  

Success Criteria & Metrics

How will you know you’ve completed the epic? How will you know if you’ve successfully addressed this problem? What usage goals do you have for these new features? How will you measure them?

  •  

Aspects that are out of scope (of this phase)

What is explicitly not a part of this epic? List things that have been discussed but will not be included. Things you imagine in a phase 2, etc.

  •  

Solution Description

Early UX (wireframes or mockups)

 

Non-Functional Attributes & Usage Projections

Consider performance characteristics, privacy/security implications, required copy translations (mostly surveys), mobile requirements, accessibility requirements

 

Dependencies

Is there any work that must precede this? Feature work? Ops work? 

 

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

  • Initial rollout to [internal employees|sales demos|1-2 specific beta customers|all customers]

    • If specific beta customers, will it be for a specific survey launch date or report availability date 

  • How will this guide the rollout of individual stories in the epic?

  • 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

 

Risks

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

 

Open Questions

What are you still looking to resolve?

  •  

 

Related content