PGP 2

Case study and rules

Assisting retail firstline workers to be more productive
As per Forbes-Microsoft research, a firstline worker (FLW) is defined as an
employee who is the first point of contact between a company and the world it
serves. They are often the first ones to engage with customers, the first to represent
a company, and the first to see its products and services in action. FLWs mainly
focus on routine work,

Research shows that that there is a positive correlation between digitally

empowering FLWs and bottom-line.

Most stores have retail associates – who work directly with the customers, and
managers – who supervise day to day activities.

Viva Insights (MyAnalytics) wants to be at the forefront when it comes to providing

solutions to tackle the problems faced by FLWs:
o lack of a stable schedule
o difficulty in managing ad-hoc tasks
o need for networking and learning
and many more.

Problem Statement
As a PM on Viva Insights (MyAnalytics) team, ideate and define the most important
features that can solve productivity challenges that retail FLWs face. Be data-driven
and back your ideas up with insights.

PGP 2 + PGPX (If applicable, please check theMwebsite

I C R O S O F T Cfor
O N Fthe
I D E N same)
T I A L – I N T E R N A L O N LY
Case study submission guidelines

Teams are expected to submit one functional spec in .doc or .pdf format, covering
the solution to the case.

How to form a team? Please note that you should form a team of 2 along with your
batchmate from the same college.

What’s not allowed:

• Team of 1
• A team with participants from 2 different colleges or batches
Where can I submit the functional spec – details will be shared soon.
By when should I submit the functional spec – 6 th Sept 2021
Which email ID can I write to incase I have doubts microsoft@acehacker.com

What should a functional spec (max 1750 words) contain?

o Problem Definition (approximately 400 words – focus on why – problem, customer value, business
value)
o Goals & Non-Goals (approximately 200 words – focus on what – requirements & user scenarios
that you aim to solve/not solve)
o Feature Description (approximately 900 words – focus on how – features leading to solutions for
user scenarios)
o Success Metrics (approximately 200 words – how to evaluate success for the features planned and
the overall product)
o Workflow (max 1 page (2 slides) – UX design, flow charts etc.)

M I C R O S O F T C O N F I D E N T I A L – I N T E R N A L O N LY