Pair Wit
Overview: Pair Wit is a mobile app that integrates machine learning, gamification and peer-to-peer interaction to help improve the mental math skills.
Project Time: 4 Weeks
Designer: Myself
Start with why
Any project for me has to start with a why. Is this an actual problem that I want or should tackle. I always had thought about creating a more personalized math program to help with kids who do not immediately connect with math. With results of EQAO testing dropping and now looking to completely eliminate the test, I wanted to help find a way to supplement that area of learning for students.
then comes how
I first came up with a basic 4 week Spring plan to keep my workflow on track and provide accountability. This was no way supposed to be set in stone but it definitely provided a direction to start moving and remain accountable. I separated my weeks into 4 general phases:
1. Research & Information Architecture,
2. Wireframing & Branding,
3. High-Fidelity & Testing
4. Case Study & Presentation Prep
finally, what i had to do
With my Sprint plan down, I had to implement what I needed to do each week while juggling when I had to take a step back. The main blocks that I had to take care of were my research, personas, user flows, low fidelity, wireframe mock ups, branding, high-fidelity and ultimately my prototype.
RESEARCH
Honestly, this phase never really ends. I did start by focusing on gathering insights from the people around me. I originally started with the idea that I wanted to make the app strictly for children who did not learn from the traditional education systems. I based my questions and research process on that while keeping track of any new developments along the way.
class interviews
I started my approaching those within my classroom to find out where they had the most difficulties in math when growing up and why.
Key Insight: Math never stops being a problem that cannot be improved upon. Abstractions are visualization of math can prove difficult at all levels of math.
student interviews
After my initial phase of gathering from people around me, I had to hear from my target audience themselves. Luckily, I had to chance to ask the kids of an old employer where they had the most difficulty in math. A bonus is that I helped with teaching them math and know they prefer gaming to math homework.
Key Insight: Division (especially long division) is a point of pain for the students I had to interview.
teachers & tutor INterviews
With an idea of what pain problems my target audience has with math, I looked into methodology of teaching to make it understandable. Having the teachers & tutors articulate how to solve problems aided in getting my project moving.
Key Insights: Students need to tackle multiple questions in order to understand and make the math automatic. Having strong fundamentals on addition and multiplication help with understanding subtraction and division.
parent interviews
My last touch point of my initial researching phase. Parents were able to articulate new ways that they got their children to be more involved in learning.
Key Insights: Parents noticed that their children respond better to educational tools that are fun, relative to their interests and have some sort of application in the world around them.
key problems to solve post research
1. Making math easier to visualize.
2. Having multiple questions to practice on.
3.questions that were relative to their interests.
Personas
The personas became a way of understanding how to solve my problems. They offered a way of being easier to empathize with my potential users.
Key Insight: Starting with these user personas allowed me to generate someone to empathize with. When I had a lack of actual flesh and body users for a certain time periods, these helped me go back to why and who I am making the application for.
inspirational teaching philosophy
After having a better understanding of who I was making my material for, I had to really figure out what the best teaching methods to use. Based on my initial stage of research, I started exploring different methods and came across Sugata Mitra's philosophies of self learning in younger student.
Key Insights: Given the change to be left along, children have an amazing ability to self learn, without the aid of an adult directing their learning path. Through peer interaction and the change to struggle with the material, students can be less restricted. The rest of my work started to be catered towards this philosophy.
Main Competitive Analysis
During my time spent analyzing people making changes in this space, I found these three particularly useful in how they get students to learn.
Key Takeaways: Taking a look at all three of these, I wanted to integrate machine learning, gamification and a learning structure that helps develop math skills while remaining interesting and fun.
User Flows
My user flow evolved throughout my work process as I continued doing testing but I had given myself a starting point to base my initial stages of my design.
The Lowest of Low Fidelity
I had gotten into the habit of blasting out low fidelity sketches. I know first hand that my illustrative skills are really **** so I just allowed for more of a focus on how to put elements together and flow in a sensical way.
Key Takeaway: I was able to get an idea of testing out concepts with individuals. By labeling my wireframes with a number system (ie. 3a(i)) I could easily re-organize my testing when going from person to person. Cut out my time needed to move into my phase of wireframing. These tests helped me to understand that there is no one right method for people to understand math.
Wireframing
After falling behind due to illness, at this point I fell behind on my Sprint plan. Luckily for me, I had tested my functionality of my lower fidelities before falling ill so I was able to plug and play my wireframes to see how much space they occupied.
Key Takeaway: I used the wireframes as a starting point for my high fidelity. I did not have to spend a lot of time in this section but it was good to have down so that I could go into my branding phase and then plug and play when I did my high fidelity.
Branding
voice & tone
- Fun but not wacky
- Informal but not infantalizing
- Helpful but not snotty
- Weird but not inappropriate
- Smart but not dull
- Confident but not arrogant
- Instructional but not monotone
Key Takeaways: The voice and tone helped within the next step of determining a mascot for Pair Wit and how we speak to our
MASCOT
With the concept of machine learning, I started researching animals that are used in the educational field.
The Winning Mascot: The parrot became a metaphor for machine learning because of their ability to imitate human language. They also inspired the name "Pair Wit" because it is a play on the word parrot and going with the core concept of pairing the user and the machine learning together. The vibrant colours also helped to inspire my colour palette.
High-Fidelity
version 1: the greyscale
During the greyscale phase, the elements and button colours were the most important.
Key Takeaway: Creating a consistency with my clickable features allowed for me to have a multiple questions. For the navigation of the application, orange became synonymous with progressin.
version 2: the presented
I took the basic functions of the greyscale and looked for well contrasted colours. Working off of the vibrancy of colours from the parrots, I chose a blue because it is widely used within the educational field.
Key Takeaways: The core concept had great feedback but the execution had people wanting more gamification and reward systems. I took the core ideas of the system and decided to revamp the idea by creating new low fidelity wireframes then moving straight to high fidelity.
The Post Presentation Pivot
prototype
key takeaways
some problems affect a wider group of users than originally intended
the idea could make a design good but the execution can make it great
test! test! test! avoid working in a bubble. you never know where you can get inspiration
the work is never done but it can be deliverable
Future Plans
ab testing of different battle menus
single player storyline
pairing with a developer