Jobpy. Lean UX
A new meaning for professional wellness
Maslow (1943) recognized sense of belonging as a fundamental human need in terms of fitting in when interacting with communities, regions, countries, …, or feeling as an important member of something.
Belonging stimulates responsibility, loyalty, compassion and hapiness, and also reduces anxiety, loneliness and fear.
Nowadays, we have double jobs (taking care of children while working), we live in pijamas, public spaces have lost their function, social contact is nearly impossible, we buy everything online, we hide half of our faces under masks,…
Covid-19 pandemic has brought with it many challenges to face, especially in the way we interact with each other and how does this make us feel individually and as a group, so we asked ourselves:
In times of pandemic, how might we promote individual sense of belonging: with oneself’s relationship, with its spaces, its relationships, its community, the places where it lives or the planet?
Victoria Martínez, Luisa Freaza and I designed a 3 week-Lean UX process to solve this challengue. This is how we worked in the process:
FIRST STEP: ASSUMPTIONS
COLLECTING INFORMATION
After doing desk research around “sense of belonging” we agreed to approach it in the professional environment, because of the importance of feeling happy and motivated at work, as active people spend 8 years of their lives (together) working before retirement.
We used a brainstorming technique based in clouds of concepts, around the main topics of the project: Social Sustainability / Belonging to the Company / Loneliness / Socialization in the ”new normal”, and assumed positive and negative statements for each.
After that, we did a HMW Matrix to ask ourselves how could we give a solution to the assumptions stablished before, and through a Lighning Demo board we did some research to collect information of these potential solutions.
We could group these potential solutions into 5 main concepts: motivation, customizable happiness, time, communication and disconnection.
DEFINING THE PROBLEM
We proceeded to define the objective, problem and improvement:
STATEMENT OF ASSUMPTIONS
Once the problem was defined, we could state assumptions to detect which user’s needs can we solve with our MVP, by evaluating them in a Prioritization Matrix to identify the risks of the project:
SECOND STEP: HYPOTHESIS
STATEMENT OF ASSUMPTIONS
Once the problem was defined, we could state assumptions in order to detect which user’s needs can we meet with our MVP:
TRANSFORMING RISKY ASSUMPTIONS
We transformed each of the most risky assumptions into hypothesis, adding a quantitative and qualitative method:
THIRD STEP: RESULTS
WILLING TO DELIVER RESULTS IN 3 AREAS
ESTABLISHING KPI
FOURTH STEP: PROTOPEOPLE
We defined archetypes based on behavior patterns revealed during the research process.
Cristina / HR
Juan / Boss
Sandra / UI Designer
FIFTH STEP: PROTOJOURNEY
This helped us to empathize with our protopeople while they interact with our product/service, to find ways to improve their general satisfaction with it.
Cristina / HR
Juan / Boss
Sandra / UI Designer
SIXTH STEP: FUNCTIONALITIES
FUNCTIONALITIES
We created user stories by merging functionality / to (protopeople) / achievement to determine the functionalities and techniques we should develop to acquire results.
MOSCOW
To prioritize functionalities.
SEVENTH STEP: LEAN CANVAS
BUSINESS MODEL CANVAS
We merged ideas and functionalities, and identified our value proposal and business model, by collecting previous information to develop an MVP and clarify hypothesis to validate.
*See value proposal canva to understand how we defined the value proposition.
VALUE PROPOSAL CANVAS
To ensure that there is a fit between the product and market and define a unique value proposition.
EIGHTH STEP: DESIGN STUDY
LOW FIDELITY PROTOTYPES
We focused on a different protoperson and its correspondent pains and gains different and tried to solve them through low fidelity prototypes.
STYLEGUIDE
We defined the naming, logo and colors to apply in Jobpy’s styleguide.
Namming was defined by merging the words “job” and “happy”, its two main concepts.
HIGH FIDELITY PROTOTYPES
By merging the main ideas of the low-fidelity prototype, we designed a high fidelity prototype from what we considered the most likely successful idea to develop our MVP.
NINETH STEP: DEVELOP MVP
We used Wordpress to develop our MVP, and linked it to Google Analytics, Google Adwords, Mailchimp and Hotjar, in order to metric the results of the KPI established before.
