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

When researching local labor demand, I want to understand the landscape of green jobs, so I can compare my region to others and train the appropriate skills for regional demand.

 Currently Find A Req is built with simple search options and is only viewable by single job reqs (postings). This is helpful for staffing sales reps, but when searching for new business, it’s more beneficial to view reqs by company, by sector, or over time. This helps them understand whether or not a company is hiring for similar positions in the same sector and if the company’s need has been a recurring hire historically.

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?

Sales reps hate wasting time, and filling one-off job reqs from random companies that don’t lead to long-lasting customer relationships is a waste of time. The goal is to build better lasting partnerships, rather than working with small companies sporadically. Giving them more data about the company’s current and historical needs allows them to make better decisions about what new business to take on.

Value to Lightcast

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

• Further distinguishes us from unintentional competitors who list single job reqs (job boards). We had one trial client who decided to discontinue with us because they could get reqs from Indeed.

Target User Role/Client/Client Category

Who are we building this for?

Account Managers/Sales/Full desk Sales & Recruiters (primary), Office leaders, division VPs (secondary). 

Delivery Mechanism

How will users receive the value?

• In Find A Req, split the page into two different tab views (“by Company” and “by Postings”) while adding extra filter/slice capabilities

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?

• When reqs can be viewed by company and filtered by sector

• “By Company” will be the default user view but we will begin tracking how often users switch to the “By Posting” view via Pendo

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.

• Creating the new SR home page

• Changing the style of Sell A Req or the nav bar

• Saved reports?

Solution Description

Early UX (wireframes or mockups)

Figma prototype: https://www.figma.com/proto/HP8inLUU9BnTipvkMR92nK/SmartReq?node-id=9249%3A27669&sc[…]-zoom&page-id=9249%3A27668&starting-point-node-id=9249%3A27669 

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? 

No

Legal and Ethical Considerations

Just answer yes or no.

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?

• How will this effect presets? Seems like adding additional filters to Find A Req requires us to add the same filters to the presets. Does it make sense to replace the idea of presets with saved reports?