Solution Devoid Problem Statement (SDPS)

Adolescents with asthma from lower-income families face challenges like lack of support and the high cost of medication, which can make managing their asthma difficult. In addition, if they cannot read English, proper use of inhalers can be difficult, leading to inadequate medication delivery and further challenges in managing their asthma.

Process

We mapped exploratory user journeys across three demographic groups—lower-middle class, middle class, and upper class—to pinpoint the specific touch points where adolescent asthmatics encounter challenges. Post this, we performed a why-how laddering on the pain points listed.

Stakeholder Mapping

Research & Insight gathering

Lower middle class

Middle class

Upper class

After this, we classified the stakeholders and performed a thorough user research (primary & secondary)

The detailed user research report can be viewed here

Existing journey map

At this stage, we compiled research insights to create a stakeholder journey map, and then a persona highlighting pain points and pinpointing the exact moments when issues arise.

Stakeholder Persona

Requirement generation & Prioritization

Post this, 7 requirements were derived so as to start iterating the design solutions. The requirement generation is as follows:

Since this was a user-centered process, we conducted stakeholder validation to stay on track. Research documentation confirmed that 86.3% of users agreed these requirements would simplify asthma management.

These requirements were then prioritized :

Each requirement was compared against the others to assess its relative importance. For example, when comparing R1 with each of the other eight requirements, if R1 was more important than R2 in addressing identified pain points, it was marked as 1; otherwise, it was marked as 0. The total for all requirements was then calculated (28 in this case). Finally, each requirement’s score was divided by this total to determine its relative importance, shown in the last column.

Concept Generation

Various ideas were brainstormed to address these requirements and then grouped to form cohesive concepts. Three concepts emerged (labeled yellow, blue, and purple)as a result of permutaitons and combinations of these ideas. These concepts were subsequently evaluated against each requirement to assess how well they met the prioritized needs.

Concept Selection

Finally, the scores for each concept were totaled, and the highest-scoring concept was refined further to become the final DI.

If a concept met a requirement, it was scored as 1; if it didn’t, it was scored as 0; and if it partially addressed the requirement, it received a 0.5. Each score was then multiplied by the relative importance of the corresponding requirement from the prioritization step.

This initial concept idea was then validated with stakeholders to ensure it effectively addressed their needs and aligned with the prioritized requirements, with 88.5% of users expressing approval of the concept.

Final concept detailing

In the process of detailing out the DI, we penned down

• Use case description (An ideal situation when the user would use the proposed Design Intervention)

• Use case steps — We brainstormed various ideas to address each step of the use case, then selected the most suitable idea, providing justification for why it was the best choice.

• Concept Storyboard

Following this, we validated the concept storyboard once more with both primary and secondary stakeholders where we got 85.3% acceptance. Afterward, the final storyboards were determined and documented.

Branding

Logo design

Color Palette

Wordmark

Final Design Intervention

Packaging Design