<?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 Eric Goldberg on Medium]]></title>
        <description><![CDATA[Stories by Eric Goldberg on Medium]]></description>
        <link>https://medium.com/@ericgoldberg?source=rss-48c44542fd49------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*afDAuc1bDCZzQxnE.jpg</url>
            <title>Stories by Eric Goldberg on Medium</title>
            <link>https://medium.com/@ericgoldberg?source=rss-48c44542fd49------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:48:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ericgoldberg/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[The Journey Of Creating a Better Task Management App from a First-Timer]]></title>
            <link>https://medium.com/@ericgoldberg/the-journey-of-creating-a-better-task-management-app-from-a-first-timer-9460f24cca5d?source=rss-48c44542fd49------2</link>
            <guid isPermaLink="false">https://medium.com/p/9460f24cca5d</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Eric Goldberg]]></dc:creator>
            <pubDate>Sun, 29 Sep 2019 22:14:58 GMT</pubDate>
            <atom:updated>2019-09-29T22:32:05.993Z</atom:updated>
            <content:encoded><![CDATA[<p>Seeing the problem many people face when managing large projects that require many steps, I created a task management app to help make the process easier. Through interviews, synthesizing data, creating a persona, I was able to develop a concept, that although flawed, is a base for an excellent way for people to manage their tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cLbb7_AEJqPaqRsCRASGnw.jpeg" /></figure><h4>Limitations, Parameters, Resources, and Materials</h4><p>Being my first UX project, my knowledge of design was minimal. I wanted to create something easy to use, understand, and execute with little help to the user.</p><p>To test these concepts, I used materials that included sharpies and note cards to create lo-fi wireframes. I used program Sketch to create mid-fi wireframes and InVision to create the prototype for user testing.</p><h4>Interviews</h4><p>Before my initial interviews, I made assumptions about the group and demographic that use task management systems on their phone. After conducting three interviews, it was clear that my assumptions were wrong.</p><p>Besides the use of their phones’ calendars, no one used an app that handled task management. Most everyone preferred the tried-and-true method of simply writing something down and being able to cross it off when completed satisfyingly. I realized that this would be a problem to solve for because replicating the feeling of pen and paper is impossible to do on a screen. One user said, “When you get to cross something off the list, it’s great. It’s great. The worst is when you finish your day, halfway done with the task, and you can only cross it off halfway. You don’t just get that feeling on the phone.”</p><p>However, despite this setback, one thing remained consistent between every person I spoke with; nobody was good at time-management when allocating tasks.</p><h4>Initial Problem Statement</h4><p>Every day a person is responsible for several obligations that they must complete in both their personal and professional lives with such little time to do so.</p><p>Dexter is overwhelmed with the number of tasks that he has to complete. How might we help him with organizing his projects in a way that is both effective and time-efficient?</p><h4>Sketches</h4><p>For my sketches, I decided to use Google Calendar as my starting point, more specifically, its day view. I liked the idea of a visual representation for the length of the event.</p><p>I wanted the user initially greeted with a day calendar home screen that had a prominent add button, similar to Google Calendar. This add button would take the user to a different screen to create a new task. Another essential aspect of what I wanted to focus on was the ability to add substeps, to break down smaller tasks in a project. After the user created a task, it would take the user back to the home screen where the task being shown along the allocated hours. It would also give the user the ability to expand the task menu to show the steps and the substeps in the calendar view, even being given the ability to add new ones. There would also be a side screen to display a list view of the tasks the user needed to completion organized by priority.</p><p><strong>Usability Testing</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oCFCIYgAer2MbStixkXf-Q.png" /></figure><p>When testing the low fidelity wireframes, each user was able to complete each test without a problem. The users knew the buttons to press, how to adjust the time frame for each task, how to create and complete each step and substep, while also being able to cross out each task when completed.</p><p>Looking back at the success of my usability testing, it had become clear to me that I was too confident in my design. I ended up relying too heavily on my lo-fi, that my mid-fi prototype suffered in the process, being too similar.</p><h4>Mid-Fi Prototype and Prototype Testing</h4><p>The creation of my Mid-Fi prototype was a mess in retrospect. There are aspects of it I love, but, as I mentioned before, I relied too heavily on my lo-fi. I faced two main issues on my prototype, spacing, and symbols. I tested three users that had three very different feelings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/468/1*G1elM4EA_r2t8A76ArHWGw.png" /></figure><p>One user I tested was a Software Engineer Student at General Assembly, who had nothing but praise for the app, “I think this useful, especially as a software engineer. As a software engineer, I have projects with little things to do. You have all these little things to do, and this app allows me to categorize those things.”</p><p>Another user had a different take. Although extremely complimentary on the aesthetic, even so much as being impressed that this was coming from a week one GA student, she was not very impressed with the functionality. She was struggling with the tasks, even some of the ones I previously thought to be straightforward.</p><p>One feature that all users loved, but didn’t find intuitive was crossing out to completed task. I wanted to add this feature to cater to the interviewees who felt the satisfaction of completing something and being able to physically cross it off. My main problem was that I only brought that function to when the final task was completed and not to the steps and subsets, that required a simple button press to check it off as complete. In hindsight, I was very foolish not to have every step being something you would have to drag your finger across to cross it out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AHJeOMVn6aMqg8re6vrPew.jpeg" /></figure><p>Overall, the ratings each of the users gave averaged out to be a three out five for both usefulness of the app and ease of use. However, the one thing that became clear between all the testers was that the font size was too small and the call-to-action buttons needed to be changed. Also, each tester preferred different looks at their calendar, like week and month, instead of the day view, which was my main focus.</p><p><a href="https://projects.invisionapp.com/d/main#/console/18523853/385283092/preview">https://projects.invisionapp.com/d/main#/console/18523853/385283092/preview</a></p><h4>Reflection</h4><p>I am very disappointed with the final design of my prototype. What I thought was straightforward ended up being confusing for the users, which is why we test in the first place.</p><p>There are noticeable changes I would have made before testing if I had more time. I would love to be able to change the font size and layout. I would also like to be able to work on different calendar views, including week and month. However, the design of my app missed the mark.</p><p>That is not to say I am disappointed with the overall concept of the app. I think, given more time, I can change the layout of the app to address the users’ and my concerns. The core concept I believe, is excellent, the execution, not so much.</p><p>I made many mistakes for my first project, but that is not to say I can’t learn from them and improve. I am at the beginning of my UX experience. As time goes on, I will use the skills I learn from the course and improve on my first project to see how I can elevate it in a way I couldn’t before.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9460f24cca5d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>