Feature Brief
Context
Help the team understand the context behind why we are developing this feature.
This feature will will help users understand the grade distribution of the courses and in the end help in deciding the courses and prof. to choose.
Problem Statements
I am user who relies on past data to help me plan my courses. I am trying to choose a prof. and a course for my degree plan. But its tough to decide the prof. because there are lots of courses/prof. to choose from which makes me feel tired and frustrated.
Goals
To organize the course/prof. data in a visually appealing manner.
To help the user decide the prof/course easily using appropriate metrics easily understandable by the user.
To help user decide with ease meaning in as least time as possible.
Hypothesis
1. (Feature): Simplify the grade distribution
(User behavior): Use can easily understand without much digging around. Time saved and reduced frustration.
(Metrics): Session Time Spent, Bounce Rate, Interactions
If we <achieve/enable X>, then <user behavior Y changes in this way> leading to positive metrics <Z>. Include guesses for the size of the win on specific metrics, using past launches as a baseline.
2. (Feature): Clear Pass/Fail Representation
(User behavior): Use can easily understand how many passed/failed in the course.
(Metrics): Session Time Spent, Bounce Rate, Interactions
If we <achieve/enable X>, then <user behavior Y changes in this way> leading to positive metrics <Z>. Include guesses for the size of the win on specific metrics, using past launches as a baseline.
3. (Feature): Overall grade score
(User behavior): User can easily judge the ease of grading or ease of scoring in the course
(Metrics): Session Time Spent, Bounce Rate
If we <achieve/enable X>, then <user behavior Y changes in this way> leading to positive metrics <Z>. Include guesses for the size of the win on specific metrics, using past launches as a baseline.
4. (Feature): Overall prof. score
(User behavior): Use can easily understand the teaching style, difficulty level of the prof. at a glance.
(Metrics): Session Time Spent, Bounce Rate
If we <achieve/enable X>, then <user behavior Y changes in this way> leading to positive metrics <Z>. Include guesses for the size of the win on specific metrics, using past launches as a baseline.
5. (Feature): Course Evaluation Data Representation
(User behavior): Use can easily understand the teaching style and interest level of prof. in a detailed manner.
(Metrics): Session Time Spent, Bounce Rate
If we <achieve/enable X>, then <user behavior Y changes in this way> leading to positive metrics <Z>. Include guesses for the size of the win on specific metrics, using past launches as a baseline.
6. (Feature): Remove box and whisker plots
(User behavior): User is not confused about the plots and this prevents user from deviating from the main goals.
(Metrics): User Testing, Feedback
If we <achieve/enable X>, then <user behavior Y changes in this way> leading to positive metrics <Z>. Include guesses for the size of the win on specific metrics, using past launches as a baseline.
7. (Feature): General Coursebook information - syllabus
(User behavior): Use can easily view the syllabus contents in a single page and can have access to amount of assignments, exams, grading style and other information.
(Metrics): Session Time Spent, Bounce Rate, Interactions, Feedback
If we <achieve/enable X>, then <user behavior Y changes in this way> leading to positive metrics <Z>. Include guesses for the size of the win on specific metrics, using past launches as a baseline.
Vision Narrative
Tell your use cases in story format, starting before the user encounters your feature and including their thoughts and motivations. Show how the feature fits into the users' lives and has a significant impact.
Rough Scoping & Timeline
At a high level, what’s included in V1 vs. later versions?
How big of a project is this?
What’s the rollout/testing plan?
Key Trade-Offs & Decisions
For example, were there any alternatives considered?
Concept Mocks
Include some mocks or a prototype to illustrate the concept. (Add links)
Review Feature Brief before continuing
Feature Proposal
Proposal
Detailed mocks & feature requirements. You can start by expanding on the scoping section from the brief. Work with your engineers & designer to ensure you’ve gone into enough detail and covered all the cases.
Risks & Mitigations
Brainstorm things that could go wrong with your team and partner teams. For each risk, plan appropriate mitigations.
Open Questions
Gather open questions here while the spec is in progress.
Research
Useful research such as competitive analysis, metrics, or surveys
User testing
Customer interviews