Product Requirements Document

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

  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 & 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

  1. Select Campaign Type

  1. Assign Campaign Name

  1. Set Campaign Dates

  1. Configure Boundary Data

  1. Configure Facilities

  1. Configure Users

  1. Set Rules for Delivery

Specifications

Question

Input Field Type

Validations/Limitation

  1. 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.

  1. What is the name of your campaign?

Open text field

Limit of 50 characters.

  1. 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.

  1. 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 & 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.

Last updated

Was this helpful?