Scribd
Upload
2 views

Crack Jack PRDV 0

a prd document

Uploaded by

sudheshna707
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
2 views

Crack Jack PRDV 0

a prd document

Uploaded by

sudheshna707
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Legend –

This format represents theory. Consider it as guiding prompts, & the ‘why’ of that section.
This format represents assumptions made.
<TBAL> – To be added later

One-liner problem statement :


When it comes to accomplishing my goals I'm investing time, and scheduling it with pen & paper, but
I'm behind my goals most of the time - how do I meet them?

Step 1.Breaking down the problem statement


Part a. Validation
 Is the problem big enough to be solved ? i.e., what is the impact? – how many users is it
impacting & to what degree?
 If there is no data for this, we can talk to the user, & pin down the numbers post a few
interactions.
For the sake of progress – let us assume it has a huge impact on the user because s/he is not able to
reach the goals despite working towards it.
Yes. The problem severely impacts the user, we need to solve for this.
Part b. User research / persona
Emulating my persona as the base template, the below statements have come up in the
conversation.
(As we go ahead on this journey, we can modify these constraints & make them more
encompassing)

<TBAL>

Statement: “I am trying to solve for my productivity gaps. Sometimes, I think I end up taking much
more time than what I have allocated to a task. Sometimes, I don’t put in the hours scheduled for
a task. I am not really sure.”
Digging deeper, there are the possible user buckets this user could fall into
Bucket 1 : The Perfectionist
The user is a perfectionist - is not happy with drafts created, & only wants to put out the best.
Here, the solution would be to draft guidelines for the release, & adhere to it – which is totally
different from the current objective, & requires a different solution.
The question is how to identify this?
Bucket 2 : The Miscalculator
Not allocating the right time needed for the task, i.e., a task in reality needs more time than has
been allocated to get the desired result considering the proficiency – basic/inter/pro
Bucket 3 : Non - Committal
Not putting in the time that has been scheduled for the tasks.
This differs from the current objective, & the problem statement would pertain to a concern with
the routine / commitment.
Bucket 4 : Non-Prioritizer
The user puts in the allocated hours, but is not prioritizing the tasks, & hence not meeting deadlines.
Part c. Current status:
 s/he uses a combination of white board, pen & paper system
 practises Pomodoro –
o has tried a few apps that favour this style of working, such as Focus-To-Do, but drops
off
o prefers using the phone clock to set pomo timers, & create focussed blocks of time
Part d. Limitations.
 Having a system of sorts shows the intent & the interest – but, it is not converting into
favourable results
 The current pen & paper can't automatically calculate or show progress.
Because of the lack of clear data, user does not know the real cause of the problem.
 There is a lack of engaging visuals.
Actually, there are no visuals - there is no color coding to motivate for progress & drive for
consistency

Part e. Key challenges.


 User doesn't want a high learning curve with a new tool - wants to use the current system
s/he is using (& is familiar with)
So, can't just refer the #1 productivity tool – maybe once success is found with the proposed
solution, user will be open to incorporating more elements to drive productivity further
 The problem statement has been broken down, but, we don't know the P0 P1 P2….- so, the
exact problem we are solving for is unclear
 We have broken down the problem statement to understand what are the areas we are
going to potentially target .
 This is important because whenever you try to solve a problem you'll be faced with multiple
factors that are attributing to the problem but you have to figure out and prioritize.

Step 2.Objective
Part a. VOC
Voice of the Customer (VoC) is a research method that's used to collect customer feedback - this'll
help to capture how your users feel about your product giving you insights that’ll help create a
stronger customer experience. It is also considered to be the foundation of product development.
For the sake of progress – let us assume the user research from Step 1.Part b is the VoC
Part b. Solution
Considering we are in the discovery phase of the product, & there is no clear data identifying the P0,
our current solution is three-pronged.
Before we build further, with the help of the user’s current system,
 we will attempt to identify the P0/1/2… by calculating the percentages against the problems
identified
 to identify the problem -
o have the user consistently log in to the MVP for 20 days
o 10 days into this habit, get the user introduced to a top-ranking desktop productivity
tool, & from the 15th day have him/her use it
 attempt to discover if there is any other unidentified problem
Part c. Success Criteria
Qualitative Quantitative
 User reports a degree of satisfaction, & is  User is able to achieve 70% - 100% of P1, P2 & P3
willing/eager to continue with the system priorities
 User is acceptive of incremental changes to o within scheduled times (30%)
system & trying other productivity tools o a few hours more than scheduled times
(30%)
o within deadlines (40%)
 User is able to keep the ‘to-do’ backlog clear at
50% - 75% to be able to incorporate incoming
tasks

Step 3.Scope
In Scope
 Digitally emulating user’s current system, with minor but effective enhancements
 This system is currently optimized for the desktop space
Out of Scope
With the current data in hand, this section is vast , so we focus on staying ‘In Scope’

Step 4.Flowchart

<TBAL>

Step 5.Functional Requirements


We are using No-Code, so this section can be detailed as we progress.

Step 6.Scenario Handling


We are currently optimising for a single user, hence we assume there is only a happy flow possible,
 as there would be no multi-user conflicts
 there are no external partners/ 3rd party APIs
As we progress, we can collate sad flows encountered, & optimise accordingly.

Step 7.Wireframes

Step 8.Version & Release Plan


ver# Planned Release Date Actual Release Date
v0 29th Sep 2022 -
v1 30th Nov 2022
v2 18th Dec 2022

Step 9.Metric Tracking


Part a. Event Creation
This usually refers to the monitoring/tracking of interactions a user undertakes while on a
website/product.
Event tracking is important because the data it provides helps you optimize your website for
conversion.
This, in turn, means more of whatever action you're trying to generate - more calls, more leads, more
orders, more of what you want.
<TBAL>
Part b. Dashboarding

<TBAL>

You might also like