<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Brian Rojas on Medium]]></title>
        <description><![CDATA[Stories by Brian Rojas on Medium]]></description>
        <link>https://medium.com/@brianrojas_78421?source=rss-2b8e94647e95------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Sij1AHk-Rcs1pS0N.</url>
            <title>Stories by Brian Rojas on Medium</title>
            <link>https://medium.com/@brianrojas_78421?source=rss-2b8e94647e95------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 07:52:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brianrojas_78421/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Design for Well-being: Distractions]]></title>
            <link>https://medium.com/@brianrojas_78421/design-for-well-being-distractions-357ca3bf3b72?source=rss-2b8e94647e95------2</link>
            <guid isPermaLink="false">https://medium.com/p/357ca3bf3b72</guid>
            <category><![CDATA[attention]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Brian Rojas]]></dc:creator>
            <pubDate>Tue, 24 Apr 2018 03:08:37 GMT</pubDate>
            <atom:updated>2018-04-24T03:52:46.441Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LJvIwf3kkE3Oka2vBhBFQw.jpeg" /><figcaption>Distraction in the 21st</figcaption></figure><h3><strong>Introduction</strong></h3><p>The face provides a rich canvas of emotion. Humans are innately programmed to express, and communicate emotion through facial expressions. In this project, we used the Affectiva libraries to design a website that measures a users level of attention based on the head orientation. The site will continue to monitor the user and give a notification when they are distracted. Since the goal of my teams project was to design a site for the well-being of others, we wanted to help those who are easily distracted (a.k.a me) when using a computer. It is very easy for us to wander off on a Facebook feed, watch just “one more episode” on Netflix, or read other peoples experiences on Reddit. All while in the back of our mind, knowing that we have a homework assignment or deadline to meet. Here are just a few facts on distraction.</p><ul><li><em>the average time on a website is 55 seconds</em>, but over 50% of viewer/users will stop reading/watching within 5 seconds</li><li>Within <strong><em>one twentieth of a second</em></strong><em> of looking at a website</em>, your unconscious mind has <em>made a decision whether something in it appeals to you</em>.</li><li>Tabloids are the most popular type of newspaper, and for one very good reason — they get all the best headlines (attention through controversy ).</li></ul><h3><strong>Design Space</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/323/1*uuy8CZCqGJC4aaExhtL_YA.png" /><figcaption>Ideas on Ideas on Ideas</figcaption></figure><p>Our team did not initially start off with the idea of making a site based on distraction prevention. We had many ideas floating around. Our initial idea was to make a site that would give quotes/images depending on the users mood in real-time. For example,</p><ul><li>If the user was showing signs of anger, we could showcase quotes and images that would calm the user down. The Affectiva framework could pick up anger by analyzing facial features, such as eyebrows bent in towards the middle, with the combination of clenching of the jaw.</li><li>If the user was smiling, we could continuously showcase happy quotes and images to keep the user happy. We could also showcase quotes of gratefulness so that the user appreciates their situation more so. This would be analyzed by raised cheekbones and slightly closed eyes.</li><li>Sadness would be showcased by analyzing slanted lips and baggy eyes.</li><li>Excitement would be showcased by opened mouth and bigger eyes.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EFwSNQJcQxx_2v48qKw8eg.jpeg" /><figcaption>Prototype Design</figcaption></figure><h3><strong>Problems</strong></h3><p>A list of some the problems we faced at the beginning.</p><ul><li>Our limited experience in JavaScript.</li><li>Implementing feedback into our site</li><li>Users did not see a point to our site. <em>What functionality will this offer me?</em></li></ul><p>These were the main problems we were facing throughout the process, which ultimately led us to changing up our idea. This led to us developing the site into a mechanism that would pick up the users level of attention and alert them if they are going off track. The site can be put in the background and will give out notification if the user is being caught inattentive. This will allow the user to continue working on other tasks while our site continues to monitor them. Like a bad manager.</p><h3><strong>Process</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BW1TusULrP-hSdWRralDvA.png" /><figcaption>What we did.</figcaption></figure><p>As stated, the project had a big change of direction part way through production. We originally looked at a site that students from Bucknell Univeristy produced as inspiration for this idea and to build off of it: <a href="https://allanla.github.io/DesignForWellBeing/">https://allanla.github.io/DesignForWellBeing/</a>. As stated the original idea of the group was to create a website that would determine the users current emotion and give them a quote or a picture to try and make them happier. So if a user were angry, the website might give a quote that was calming or if they were sad it would give them a pick me up. We had some trouble with the affectiva library and web camera access, but as we were working on this issue we found we were getting distracted on other things here and there. So as we figured out the coding side of the problem, we made a dramatic shift in the plan for the project. We completely scraped the original idea above and went with the idea of helping people stay focused on work. For the layout of the website we wanted the user to be able to set up as fast as possible and get to work. For this reason we chose a minimalistic styling choice that was more quiet and there was not a lot of content to get distracted by. This was a drastic change as our original prototype draft showcases graphs and multiple statistics being showcased. We had the description of how to use the site on the homepage so when the user sees the streaming page, they can see what the site is looking at to keep track of attentiveness and to start and stop the program. The goal was to have the tool be simple in every way. A problem that we faced in regards to this project.</p><ul><li>Defining distraction and what the threshold between each level of distraction is.</li></ul><h3><strong>Feedback</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/291/1*9hiZ3bTUXIdjXL0N_W7j9A.png" /></figure><p>We had a good amount of feedback from both our original project and our newly implemented one.</p><p>Suggestions on first initial project.</p><p>What people liked</p><ul><li>People liked the idea</li><li>People like the prototype and black UI</li></ul><p>What people didn’t like</p><ul><li>The purpose</li><li>Buggy and camera wouldn’t show</li><li>Quotes and images wouldn’t necessarily give a purpose as to why they are being showcased. For example, why show me a happy face when I am already happy.</li></ul><p>The thing people seemed to like the most about our project was the UI and not the actual functionality. This is one reason we changed our project completely.</p><p>We again asked users to give us feedback on our newly designed and functioning project. We had a drastic change in feedback.</p><ul><li>Users thought that the purpose of the website was helpful for staying on task and that the website was easy to use.</li><li>Users thought that the purpose and usefulness of the project drastically improved and some stated that they would actually use it during their focus times.</li></ul><p>We still had some criticism.</p><ul><li>Some users thought that the notifications did not apply to all situations that most users who get distracted have.</li><li>That the project does not state what is distracting the user.</li></ul><p>The attentiveness recognition was looking for how much the user was focusing on the screen. When users looked around the room or looked to check their phone, a notification would appear reminding them to stay on task, but the recognition cannot tell the difference between someone focusing on a youtube video, or the paper that they should be working on. This is an issue that we found many users have. In the future we would look to implement some way of using emotions as well to try and determine if the user is working, generally more relaxed and not as many active emotions, or if they were messaging someone online or watching a video.</p><h3><strong>Video</strong></h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FNaKnCrqvj8A%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DNaKnCrqvj8A&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FNaKnCrqvj8A%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/914962fd4ce41890bcf060383f12a743/href">https://medium.com/media/914962fd4ce41890bcf060383f12a743/href</a></iframe><p><strong>Try it out for yourself!</strong></p><p><a href="https://dleau.github.io/design-for-wellbeing/index.html">https://dleau.github.io/design-for-wellbeing/index.html</a></p><h3>Conclusion</h3><p>The team learned a few lessons in regards to our process. We learned that getting user feedback should be something done at some of the earliest stages, even before prototype implementation. Our starting project was something that was repetitive and not very useful. For the next time, the team will definitely not just solve the problem, but make sure that we are solving the right problem.</p><p>There were also lessons learned that would be applicable to read world instances. There may be a case where you could be working in a particular industry and in some cases, you may have to throw away old work and start over. It can be painful, but its something we have to get used to as Designers/Engineers. In the end, the importance is that the product is the correct one and has purpose.</p><p>We had a lot of fun throughout the process. Even though we had bugs where the camera wouldn’t showcase, emotions weren’t being calculated, and sometimes the site just wouldn’t launch at all, we were able to prevail and end successfully. The team was able to integrate a framework and learn some Javascript along the way. I would encourage anyone to download the Affectiva Framework and give it a shot! <a href="https://www.affectiva.com/">https://www.affectiva.com/</a></p><p>Thank you for reading.</p><p><strong>References:</strong></p><p>Lindgaard, G., Fernandes, G., Dudek, C., &amp; Brown, J. (2006). Attention web designers: You have 50 milliseconds to make a good first impression! <em>Behaviour &amp; Information Technology, 25</em> (2), 115–126 DOI: <a href="http://dx.doi.org/10.1080/01449290500330448">10.1080/01449290500330448</a></p><p>Holmqvist, K., Holsanova, J., Barthelson, M., &amp; Lundqvist, D (2003). Reading or scanning? A study of newspaper and net paper reading. <em>The mind’s eye: cognitive and applied aspects of eye movement research</em>, 657–670</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=357ca3bf3b72" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bad Design — Dreaded Forms]]></title>
            <link>https://medium.com/@brianrojas_78421/bad-design-dreaded-forms-fd89109bba6c?source=rss-2b8e94647e95------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd89109bba6c</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Brian Rojas]]></dc:creator>
            <pubDate>Sat, 17 Mar 2018 02:59:22 GMT</pubDate>
            <atom:updated>2018-03-17T02:59:22.269Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g48TZPQHn-HusN1WveQEuQ.png" /></figure><p>If you read my <em>Good Design — The WPI Plan </em>you can see that I appreciate well though-out design, that is catered to its perceptive users. As a college student, in equivalence to knowing the plan ahead, making sure you have the correct forms in the system is just as important. Its happens all too often where a form you had no idea needed to be filled, and signed is due the next day and you need to search through the school’s website, find the right form, print it out, and sprint to the various offices for signatures before everyone leaves at 5:00 p.m.</p><p>Before stating the bad, I do want to say that the page at least has somewhat of a structure. If you fit into a certain section, such as First Year, all the way up to Alumni, then you may find the form you are looking for. That’s all the praise this page gets. In my opinion, I would appreciate a page where there are no more than 4 blocks that categorize where a form might be held, as showcased in my sketch down below, we can see that there are 4 blocks that in finalization, would be of the same size and would have some of the more important forms right under, or a brief description of what a specific group may entail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zt8QhNTgwPPLN26KwTqsKg.png" /></figure><p>If the user is not sure what they are looking for, they can dive deeper into a section which would showcase all the forms within that group, while hiding the other groups. This give the user a <em>Chunk-like</em> experience and the forms they are looking for are not diluted with non-relative forms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wS8StZhaFaC1y-HqGNRqlQ.png" /></figure><p>These are just a few sketches that could probably make the experience of getting a form easier and simpler. Some of the key problems that I can see and experience is that the page is not informative enough yet also intimidating in its design. This is what can happen when you do not carefully plan and test a page. This page does not carry a lot of information yet looks like it does. There is also no graphic representation dictating anything about the forms. All the information we have is that the form is of PDF or link form. It may be useful for each form to have a small description as to why a student may need this form. I believe that with this method, students would turn in forms earlier than sooner.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd89109bba6c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good Design — The WPI Plan]]></title>
            <link>https://medium.com/@brianrojas_78421/good-design-the-wpi-plan-64c2d257fbfa?source=rss-2b8e94647e95------2</link>
            <guid isPermaLink="false">https://medium.com/p/64c2d257fbfa</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Brian Rojas]]></dc:creator>
            <pubDate>Sat, 17 Mar 2018 02:10:34 GMT</pubDate>
            <atom:updated>2018-03-17T02:10:34.386Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v3Jr4AgvMxoMR52dG_UlSQ.jpeg" /></figure><p>In this post, I will explain why the WPI plan page, in my opinion, is an excellent example of a good design flow. I chose this page due to its overall flow, showcased in-order, through the shared images. My criteria for a well-designed page needed to both explain what my purpose of being on this page was, while not intimidating me with information. If there is going to be a large amount of information, I would like it to be pleasant to look at and understandable, especially if its information that will be needed for an important matter. I am typically the type of reader that will skim first, then read in detail. However, if there is an interactive slider, or bubbles that take me to different parts of the page, and these features break down the information into chunks, I will be both informed and curious as to what’s next. This leads to me staying on the page longer. If we were to skim, you can first see a warming image of WPI attendees walking on a sunny day. This gives me the image that this environment is happy, but that I will have tasks to complete. The fountain is also a nice touch. The passage underneath the image is something that I would skip, if I only had time to skim through the page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pIb0-iQm1XEONeHM0-A4bQ.png" /></figure><p>Below the passage is this slider. This slider gives both a detailed explanation of what a student should know before attending WPI. You as a user can get by with just reading the titles. For example, “We have seven-week terms”. I know right off the bat that I won’t have 16-week semesters. I can dig deeper and read the passage, but I got what I needed from the title. If you were continuing forward on the slider, you can see the repeating pattern.</p><p>Before I move forward, it is important to know who would be viewing this page and step into their shoes. All students are nervous when they are looking for colleges, first go to college, or transfer. In the mind of the designer, I want the retention rate of my user to stay as high as possible. One of my biggest factors for staying on a website is how intimidating the information looks. If I don’t need to read it, I won’t. So, for the WPI plan page to showcase its core information to its student in a way that is both friendly and informative is very important.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0KJcSkwjYQnOE5M2IwIHyw.png" /></figure><p>Continuing onward, past the slider we see that there are six key points to the WPI plan. The 6 logos are an important aspect, because they give a sense of what is happening, even if there weren’t any words tied to them. As a prospective student I would like to know how my next 4 years would look like in as simplest form as possible. Student themselves may not even know what they want, but with at least the key values listed, student can align them with their own.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*33zIaJuFB7utDquXH4Bb5Q.png" /></figure><p>In closing, the rest of the page is in this format, where a student is given an example of what some of the many possibilities there are in their first year, and onward. I appreciate this a lot, and would say that behind the slider, this is my second favorite part of the page. Some may not be fans of the time-line type format, but as a student, I can appreciate what a possible 4-year curriculum could look like if I were to follow the path of any of the students showcased. Even if I were to carve out a new path, I know from the start of the page that I would be supported through the elements of what makes a successful WPI student. The entire design almost lays it out all in front of me. The page could have easily been a long text file with what students can do, but is instead styled and formatted in a way that says, “At this school, if I put in the work, I can achieve anything!”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64c2d257fbfa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>