---
# System prepended metadata

title: Untitled

---


## ISP-Cable
- ISP-Cable
- Team 1 - Sean, Patterson, Disha, JJ 

## Change history
- Nothing Yet

## Overview
 Validation or business case that this a problem worth solving. Why should we work on this vs other stuff?

Consider the following information when putting together the background:

- Context: How does this fit with our company/product goals, metrics, vision, roadmap? What do internal stakeholders (various business teams, support, sales, etc...) think?
- Product: What does our current feature look like? Does it work as expected? What seems compelling and what areas seem ripe for improvement (screenshots help)? What changes have been made in the past?
- Competitive: What are our competitors doing?
- Users:
    - Why is this important in helping our users win?
    - What do users who use this feature think (good/bad)?
    - What do those who don't use the feature say about why they don't use it?
- Metrics:
    - What is the current usage?
    - What % of users who can use the feature have adopted* it?
    - How do you define adoption?
    - What frequency do users use the feature?
    - What % of revenue do those users represent?
- Analysis:
    - Is this a problem worth solving? If looking at a specific feature, consider if you went back in time, would you still consider building it?
    - Based on the information gathered, what problems should we be solving?
    - What further analysis do you need to or would you like to perform?
    - What are the benefits of solving this problem? What opportunities does it create?

## Objectives
 * Explicitly list our goals for this project

## Success Metrics
 - How will we measure if our solution is successful?
 - What can we measure that shows users are using the feature in a manner that will help them win?
 - How does this tie to our product / company metrics?
 - What is the baseline?
 - What is the target?

## Messaging
 -  How will we describe this product/feature to customers?

Timeline & Release Planning
Estimate completion of design & engineering in one week
 -  11/11 - PRD completion
 -  11/14 - Finalize design by EOD
 -  11/15 - Complete front end template by EOD
 -  11/17 - Complete back end implementation by EOD
 -  11/17 - Finalize front end implementation by EOD
 -  11/18 - Present completed project

## Personas
 - This product will appeal to customers of cable providers, ISPs, and subscription service providers. It will also appeal to the providers themselves. Key attributes of the project will be the different bundle options of subscription services in addition to cable  and internet services.

## Scenarios
 - A user will be frustrated by the problem of rising costs among different subscriptions and cable and internet services and turn to our service to address their problem
 - Users will 
 - Users will use the product to select desired services and observe the value created by bundling services together
 - Consider what they’re doing now, how they find this product, what they’re trying to accomplish, how they’ll use this product to achieve their goals, potential friction they’ll encounter, and what their world is like once they’ve addressed their problem.
 - Generally have one user scenario per key product feature (epic task)


## Features In
 - Include individual features with details of how they work based on the design and discussions with engineering.
 - Include content (exact wording) and optionally have it reviewed by stakeholders.
 - Ideally include rough prioritization

## Features Out
 - Explicitly call out things you’re not doing and include why not

## Designs
 - User flows / Visual Design
 - ERD


## Open Issues
 - Nothing yet

## Q&A
 - Nothing yet

