Product Requirement Document (PRD)

Table of Contents:

Background

Target Audience

Objectives

Assumptions and Validations

Role-Action Mapping

Specifications

Risk and Limitation

Out of Scope

Design

Background

As the adoption of the HCM app is beginning to increase, a significant piece of feedback we have received is that setting up any campaign on the HCM app currently demands a minimum of two weeks of development effort. There is a consensus that the lead time for campaign setup needs to be shortened.

The concept involves transforming the HCM app into a SaaS-like product, featuring a console that empowers the admin user, in this case, the campaign manager, to effortlessly create and execute campaigns on the HCM app. The Campaign Manager product will offer the admin user the flexibility to select and customise specific components of the HCM app according to their preferences.

Target Audience

The user persona for this product is anyone who knows how a given health campaign works on the ground. They have a decent understanding of terms and concepts such as Cycles, Deliveries, Doses, Boundaries, Hierarchy, and other Campaign-related terminologies.

The challenge is around the ability of the user to use and understand technology. The user is not tech-savvy and is not expected to know concepts of JSON Files, Schemas, APIs, MDMS, Services, and any other such terms. The user is also not expected to be well-versed in high-fidelity UX/UI and needs every bit of hand-holding possible during the process of creating and running a campaign.

Objectives (of this release)

1. Reduce set-up time for new campaigns.

2. Reduce dependence on engineering resources for setting up a new campaign.

3. Provide the power to the end user for customising campaigns.

Assumptions and Validations

Sr. No.	Theme	Assumption
1	User persona	The user is well-versed with campaign terminologies and has some level of previous campaign management experience.
2	Device type	The product will be used as a web-based application with an internet connection.

Role-Action Mapping

Sr. No.	Role	Action
1	Campaign Manager	Select Campaign Type Assign Campaign Name Set Campaign Dates Configure Boundary Data Configure Facilities Configure Users Set Rules for Delivery

Specifications

Question	Input Field Type	Validations/Limitation
Which campaign type do you want to run?	Dropdown single selection	Users can select only one campaign at a time. The entries in this drop-down will be pre loaded from the back end. Will provide the functionality of updating the list to the users from UI.
What is the name of your campaign?	Open text field	Limit of 50 characters.
Beneficiary type for the selected campaign is	Non-editable field	The answer to this question can only be household or individual based on the campaign name selected in the previous question.
Select the start and end dates of the campaign for the boundaries selected above. Note: This date range will be applicable to all boundaries selected in the previous question.	Calendar selection Icon with 2 inputs: Start Date End Date	The selection will ask for 2 inputs from the user: Start and end dates. The user cannot select start or end dates from the past. only future date selections should be allowed. By default, when the selection opens, the date should be set to today's date.

Risk and Limitations

1. Boundary data: If the boundary data is updated regularly, then the analytics for the long-term will not have data sanity.

2. Users might have issues uploading multiple Excel sheets for targets, facility, and user data.

Out of Scope for v0.1:

1. Boundary data mapping and hierarchy changes through UI will not be allowed. If the user wants to edit/add new boundary data, it will be raised through the L1 team.

2. Editing of campaign data, once the campaign is live through the HCM Console UI, is not allowed. The changes will have to be routed through the implementation team.

3. Language selection for the app will not be a part of this release.

Design

Click here to learn more.