Epic Title - Your Solution Here

Column 1

Column 2

Created On

[Date]

Product Manager

[Name]

There are no rows in this table

⁠

Problem Alignment

Background

Explain the background of the need for making features. Can be narrated starting from the current condition, then the data that becomes the basis for the formulation of the problem — this section can refer to “Understanding The Market and User Needs” document.

Data Evidence

Data that can be used as suggestions for developing and helping to validate this product.

Challenge

Formulation of problems, questions/challenges that need to be answered in order to complete the background. Questions related to the objective of the feature/enhancement.

Example :

HMW help students notice there is an action to complete the current session?

HMW help students be able to see learning content while the page resized?

HMW help students feel delighted when learning in session page detail without interrupted by large tutor and description content?

Success Criteria

Outcome, criteria or matrix reference to be achieved from solutions.

Examples:

Qualitatively, we need to see students understand that they need to do an action to complete the current session and feel delighted to multitask with a resized page. We can observe this through usability testing.

Quantitatively, we need to increase the non live session (video and reading) completion by 90% after the modules have passed from 30 days after release.

Higher stakeholder satisfaction: Achieve a minimum of 85% stakeholder satisfaction with the platform's features and solutions for decision-making, as measured through user satisfaction scoring.

Increase stakeholder engagement: Achieve a minimum of 80% active (upvote & comment) participation from hiring managers, recruiters, and other stakeholders in the decision-making process under two weeks time-box after screening stage.

⁠

Proposed Solution

The proposed solution section should provide a clear and concise overview of the solution being proposed to solve the problem statement and challenge, including a breakdown of its components and the benefits it will provide to end-users and the business.

⁠

User Stories

List all Requirements as detail as possible which includes scenario role, pre-condition, action and impact.

Example for User Story, Scenario, and Acceptance Criteria

User Stories

Scenario

Acceptance Criteria

As a stakeholder, I want to leave comments on candidates' profiles to provide qualitative feedback and share additional insights that may not be captured by upvotes alone.

Stakeholder leaves a comment on a candidate's profile

Given the stakeholder has selected a specific job vacancy and viewing a candidate's profile

When the stakeholder writes a comment and submit

Then the comment should be saved and displayed on the candidate's profile

Comments must be text-based and without character limit.

Comments should be associated with the stakeholder who wrote them.

For current iteration, stakeholders unable to edit or delete the comment once it has been submitted.

Stakeholders must be logged in to leave comments on candidates' profiles.

There are no rows in this table

⁠

User Flow

Create a visual representation of the steps a user takes to accomplish their goal, including all possible paths, decision points, and user actions, to ensure a seamless and intuitive user experience.

⁠

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.