Editing content files

4 files changed, 73 insertions, 174 deletions

diff --git a/exampleSite/content/360pro.md b/exampleSite/content/360pro.md
index 5190309..92ad8e9 100644
--- a/exampleSite/content/360pro.md
+++ b/exampleSite/content/360pro.md
@@ -1,186 +1,85 @@
 ---
 weight: 2
-title: "Cope | Alexis Collado"
-description: "I set a direction for the branding and identity of the product and crafted a functioning prototype ready for usability testing and development."
-nav_heading: "Cope Case Study"
-thumbnail: "cope.jpg"
-case_title: "Cope iOS App"
-case_subtitle: "Mobile App Design"
-case_description: "Cope is a mobile app that allows mental health help seekers track their symptoms and medication. I helped them create a minimum viable product for testing."
-case_feature_img: "featured-cope.jpg"
-case_summary: "Cope is an application that helps users track their mental health. Progress is measured through the use of a check-in system, calendar, medicine tracker and a summary dashboard. I created a minimum viable product for this application."
-team: ["Alexis Collado", "Carlos Arcenas", "Kat Uytiepo", "John Palomo"]
-roles: ["Branding and Identity", "User Interface Design", "Prototyping", "User Research"]
-methods: ["Sketching", "Mockups", "Guerilla Testing"]
+title: "360 Pro | Alexis Collado"
+description: "We designed for an experience that cuts testing time significantly, enables group testing, and automates athlete leaderboards."
+nav_heading: "360 Pro Case Study"
+thumbnail: "360.jpg"
+case_short_title: "360 Pro Tracker"
+case_title: "360 Pro Performance Tracking System"
+case_subtitle: "Web App Design"
+case_description: "The 360 Pro Tracker is a performance tracking system for the 360 Pro gym. It tracks an athlete’s statistics and calculates his or her pro score."
+case_feature_img: "featured-360.jpg"
+case_summary: "My team and I designed a usable system with a core experience based on 360 Pro's performance testing framework. We were awarded as the best team in the whole batch for our Systems Analysis and Design course."
+team: ["Alexis Collado", "Johannah Miralles", "Jacob Purificacion", "Jacob Chua", "Galen Evilla]
+roles: ["Project Management", "Systems Analysis", "User Interface Design", "User Research"]
+methods: ["Contextual Inquiry", "Field Immersion", "Systems Analysis and Design"]
 button_links:
-    - link: "https://marvelapp.com/g4b64e/screen/14364499"
-      img: "eyeball.svg"
-      text: "View Prototype"
-    - link: "http://copenow.co/"
-      img: "eyeball.svg"
-      text: "View Landing Page"
-    - link: "cope.pdf"
+    - link: "SAD_FinalDeliverable.pdf"
       img: "download.svg"
-      text: "Download Feature Sets"
-testimonial: "Alexis designed everything for Cope from the ground up. What I really like about him is his true understanding and grasp of what makes a great UI great. He knows that the user experience needs a lot of refining from customers and he isn't shy to take feedback even if it's critical. Alexis is one of those rare people who just gets it."
-testimonial_photo: "john.jpg"
-testimonial_author: "John Robert Palomo"
-testimonial_subtitle: "Co-founder, Cope"
+      text: "Download Final Deliverable"
+    - link: "https://drive.google.com/file/d/0Bxn4bwjLduRhLS1KVGt6NUkyZDg/view"
+      img: "eyeball.svg"
+      text: "Current Process Video"
+testimonial: "We are a strength and conditioning institute that specializes in training elite athletes. As such, we need to keep track of the smallest changes in their physical abilities. We developed a system called a PRO score which is a battery of tests for this need. The theory was sound but it took us forever to administer the tests. The prototype that Alexis designed will be able to help us automate these tests and shrink testing time by half. He was able to listen to our needs and address it directly. I'm confident that when the final product comes in, it will help us a great deal in terms of our operations."
+testimonial_photo: "chappy.jpg"
+testimonial_author: "Chappy Callanta"
+testimonial_subtitle: "Head Coach, 360 Pro Gym"
 date: 2017-10-15T03:29:08-07:00
 draft: false
 ---
 
 # The Challenge
 
-![](//localhost:1313/cope/img/persona.png)
-
-A startup called Cope hired me to create a **minimum viable product**
-for their new idea — tracking mental health. It was the first project
-where I handled mobile app design, and I was very excited to learn the
-intricacies of the iOS platform.
-
-My clients John and Kat have done some preliminary interviews
-with psychologists and psychiatrists to get their side of the picture.
-They have established a user persona, a business model canvas, and
-several startup prep work for the product to take off. My job was to
-actually create the experience for their users and make sure they are
-represented in the design process.
-
-The design I created was a result of self-started questions,
-validating assumptions, benchmarking,  and guerilla testing. I could
-have done some more usability studies early in the process, however.
-
-# Informal Competitive Analysis
-
-We checked the App Store for similar applications, and we found
-out that there were no well-designed niche applications for handling
-mental health. We found another app called Cope as well, but their
-solution was more of a community-based social sharing platform. We saw
-this as an opportunity for our own version of Cope to solve a unique
-problem in the space.
-
-![](//localhost:1313/cope/img/competition-cope.jpg)
-
-Instead, we drew inspiration from applications that feature the
-design components we needed: menstrual cycle management apps that have
-good summaries and calendars, emotion tracking apps, medicine tracking apps.
-
-I used the concepts gained from these applications to study how
-they understood the mental models of their own users and hopefully
-replicate that kind of empathy whenever I create design decisions for Cope.
-
-# Pivoting
-
-We had feature changes and a lot of design decisions cancelled.
-Before, we had different modules for the design: forums, mental health
-doctor search, messaging.
-
-![](//localhost:1313/cope/img/discarded.jpg)
-
-We finalized the components of Cope that we wanted to build and
-we decided that we wanted to focus on tracking their progress for
-mental health. I had to drop some UI explorations I did for the first
-version of Cope we were building.
-            
-# Ideation and Feature Prioritization
-
-How do we exactly track one's progress in mental health? How do
-we make sure that the design is as usable as possible? What specific
-things should we track? How do we gauge someone's well-being in as few
-questions as possible? How do we design an efficient system for tracking
-and managing medication, and how does it tie up with the overall
-well-being score and progress of the user? How do we make a
-habit-forming product?
-            
-![](//localhost:1313/cope/img/sketch.png)
-
-There were so many questions we had to answer going into the
-project, but we decided on four key features that will serve as the
-solution to the mental health tracking problem: a self-report check-in
-system, medicine tracker, calendar overview, and summary dashboard. All
-modules work together to form a cohesive whole as a mental health
-tracking platform.
-            
-![](//localhost:1313/cope/img/summary.png)
-
-# Assumptions and Considerations
-
-**The boundaries of self-reporting and analysis** 
-<br>We cannot really derive a diagnosis from the self-report component of
-the application because doctors are the only ones qualified to do it.
-There are so many factors that relate to mental health, and we realized
-as a team that the last thing that our app would want to do is to guess.
-The design decision is to tally user's progress based on his or her own
-input, and we would assign a total well-being score based on the
-aggregate of their answers.
-            
-![](//localhost:1313/cope/img/calendar.png)
-
-**Frequency of data collection**
-<br>How exactly do we know if the emotion that was self-reported persisted all throughout
-the day? As human beings, our emotions constantly change. We can't do a
-self-check just once a day because the data becomes inaccurate. We
-decided to have multiple check-ins as the solution. That changed the
-initial design I created for the calendar screen.
-            
-# User Flow Brainstorming
-
-![](//localhost:1313/cope/img/flow.png)
-
-**Designing the onboarding process**
-<br>The onboarding process starts with the user signing up or logging in and
-keying important data. The user then performs his or her first symptoms
-check-in. This is essential so there could be a baseline for his or her
-data in the calendar and summary screens. He or she is led to an empty
-state of the medicine tracker screen. From there, the user could add
-medicine or check out his summary or calendar.   
-         
-# Hi-Fidelity Design
-
-After asking so many questions about the product and validating
-our assumptions with experts, I created different screens using Sketch.
-There were multiple versions and ideas that I had to validate, and
-frankly, I feel like I haven't tested the solutions that I created yet.
-During this phase, I got advice from a data visualization desginer if I
-were designing the graphs correctly. I created a quick [landing page as well.](http://copenow.co)
-            
-![](//localhost:1313/cope/img/add-medicine.png)
-
-**Design Intentionality**
-<br>There are so many nuances during the high fidelity design phase
-and so we kept on going back to sketching all the time. I tried to be
-smarter in thinking about the usability of each design. My focus was to
-be more intentional in all of the affordances I create within the application.
-            
-# Prototyping
-
-I built [the prototype](https://marvelapp.com/g4b64e/screen/14364499) 
-with Invision first but I encountered some problems with the tool.
-MarvelApp proved a better choice. After building the prototype with
-normal hotlinks, I believe we were ready to try it out with some users.
-                                      
-# Guerilla Testing
-
-I tested the application with 7 college students from Ateneo de
-Manila University with convenience sampling. The results revealed some
-usability questions for the app. What would the users actually do after
-keying in their symptoms for the day? What if they do not have
-medication ready? How can we get them to come back and actually use it
-again? Indeed, there are many more things to design for the product that
-we have not explored yet.
-            
+Meeting with Chappy Callanta of 360 Pro led us to discover the root problem — the implementation of their performance testing framework. The gym uses a Numbers document on one iPad to record all tests, and relies on inefficient manual procedures to do the work. The document calculates a total pro score based on an athlete's performance for specific exercises, but the coach using it has to refer to several norms before assigning a pro score.
+
+![](//localhost:1313/360pro/img/dfd.png)
+
+Group testing is impossible to do. Chappy says "I need to duplicate the Numbers document again and again for each testing session. It's not ideal for groups of people who want to get tested." In the end, the performance framework does not work because a unique tech solution to their problem does not exist.
+
+# Contextual Inquiry
+
+To begin our systems analysis, we conducted site visits to 360 Pro. What we did was to get to know their process as much as possible and map out the actual data flows that happen. After interviewing their member coordinator and coaches, we discovered all the documents they use for a workout program for any athlete to begin. A more important issue was that Chappy was the only one using the performance framework, because they simply "didn't get it" using the iPad Numbers document. It was a relatively new system and there was no way they would be able to grasp it right away.
+
+At this point, we knew that the solution was making the performance system more accessible to all coaches at the gym, and create a system that is possibly scalable across future branches of the gym.
+
+# Feature Prioritization
+
+I've done research on how personas and user stories might carry too many assumptions and have loopholes. I came across [job stories](https://blog.intercom.com/using-job-stories-design-features-ui-ux/)
+some time before and I wanted my team to implement it. According to Paul Adams of Intercom, "Job Stories are a different way of thinking about defining features, UI, and UX." And so, being adventurous and a bit skeptical, we came up with our own. I think it helped us figure out the features we needed even more.
+
+![](//localhost:1313/360pro/img/jobstories.jpg)
+
+This was very early on in the process and it helped my team empathize with our primary users. This wasn't really required by our instructor, we just went ahead and did it. The result was great for us, because we decided as a team on the design components we wanted to roll out: the performance testing core functionality, a leaderboard, a digital version of the gym's Workout of the Week whiteboard, and general athlete user management.
+
+# Field Immersion
+
+![](//localhost:1313/360pro/img/field.jpg)
+
+I learned about field immersion during my visit to UX Singapore 2016. I wanted to try out the idea for our project so I invited my teammates to actually try a gym session out, just to go to an extra level of empathy. Jacob Chua and I underwent the trial program, and we tried out best to empathize with the coach who was teaching us what to do. At that point, I was thinking of the possible ways I could make the system of testing easier, considering the situation we faced. I tried to create a mental model for the coach embedded into my subconscious.
+
+# Systems Analysis
+
+We created a lot of data flow diagrams for the project, considering each process very carefully. We asked ourselves, how could we would create a usable and delightful product for the end-users, considering all these data flows? How would it actually translate to the product design? Considering the feature sets we decided on, what will be the best way to design them?
+
+We also created logic models, use case diagrams and other documentation. This was all bulk of the coursework we were required to do, and I was more than excited to create the screens after all the prep work we were doing. During this process however, I felt that we could have done more user research really geared towards understanding the user more, like a usability test using low-fi prototypes.
+
+# Design Decisions
+
+![](//localhost:1313/360pro/img/testing.png)
+
+**Making Testing Easier**
+<br>Since testing was the main problem, we concentrated on designing that experience first. Using exercise cards that automatically compute pro score based on raw data while also considering gender norms, we focus the experience on actually just filling out information easily for the primary user. We wanted to eliminate cognitive load as much as possible.
+
+**Testing Summaries**
+<br>The summaries should indicate whether an athlete has improved his pro score. We used a variety of visual design communication techniques to convey this.
+
+![](//localhost:1313/360pro/img/starttest.png)
+
+**Tracking Performance**
+<br>Leaderboards and member dashboards will fulfill this aspect of the product. Search definitely plays a major role in the user experience of the app, and almost always populates all design components.
+
 # Next Steps
 
-The project is actually in development now and the next step is
-to conduct usability tests, install analytics and use new insights to
-inform new iterations of the product. Design a better onboarding
-process. Design for empty states. Design copywriting and strategy for
-push notifications as trigger. Integrate a social aspect into the
-application. All these will be helpful to create a better design for the app.
-            
-![](//localhost:1313/cope/img/cope-final.png)
-
-In reality, product design is the easy part. The real problems
-we're facing involve fighting a stigma around mental health, building an
-open, supportive and vulnerable community, and creating a sustainable
-business model for the product.
\ No newline at end of file
+I will have to create a FramerJS prototype to simulate microinteractions. Though that might not be useful anymore since we can go straight to development. Another challenge is using the right front-end and back-end frameworks to build the platform.
+
+The gym uses an iPad for testing so further refining the responsiveness of the designs, and also optimizing for tablets would be a good idea. We will probably conduct more usability research for the project and iterate on whatever current mockups we have.
\ No newline at end of file
diff --git a/exampleSite/static/360.jpg b/exampleSite/static/img/360.jpg
index 4cb454a..4cb454a 100644
--- a/exampleSite/static/360.jpg
+++ b/exampleSite/static/img/360.jpg
diff --git a/exampleSite/static/cope.jpg b/exampleSite/static/img/cope.jpg
index 54cbbde..54cbbde 100644
--- a/exampleSite/static/cope.jpg
+++ b/exampleSite/static/img/cope.jpg
diff --git a/exampleSite/static/tedx.jpg b/exampleSite/static/img/tedx.jpg
index 08e3168..08e3168 100644
--- a/exampleSite/static/tedx.jpg
+++ b/exampleSite/static/img/tedx.jpg