Project Report: Write a short report documenting your design and testing on your process blog. This should be neat and clear, not overly designed, but suitable for a process portfolio artifact. The report should stand on its own as a communication about your prototype and cover the following elements:
- Design: description of the website’s purpose and basic functionality. Be sure to include a site map that documents the interactive architecture. Include sketches to show your basic layouts and wireframes of key pages.
The purpose of this project and wireframes were to create a task managing tool. I took the initial idea from bullet journalling, something I currently practice and write down in a physical paper notebook. I therefore wanted to try and translate this idea into a web tool for both desktop and mobile.
On the home webpage you’ll find a holistic view of everything. The Future Log in journalling helps for jotting down quick dates and things you hear and want to include in your calendar. This page typically becomes the first page you look to for any events you are thinking about and or have scheduled. The container on the right shows you monthly log. This log shows everyday of the month so a user can see some of the events they included in their future log and be populated in their monthly log. Finally clicking on the monthly log days brings up the Daily Log which is the daily tasks that an individual might have including, feed the dog, grab coffee, mail letter, etc. The purpose of the Daily Log is to have a place where someone can see and populate their tasks for the day without it convoluting and or crowding the monthly log area.
First I started with research. I wanted to know who currently uses an tools to help them remember their tasks but also keep track of their events. Amongst the individuals I talked, I found that many have an online platform like google calendar for which they can sync with their phone and remember any upcoming events and important dates. To manage their tasks some rely on a physical calendar/agenda/notebook in order to write down and attend to their daily tasks. From this research I felt I could combine the two in order to create a system that integrated both.
I then created both a quick outline site map and content inventory to determine what was to be included in this wire frame. I took many of the content ideas from bullet journalling and tried to incorporate the same terminology and vocabulary for those familiar with this analog system. This site map and content inventory allowed me to process the different elements that makes journalling or task managing important to productivity and success.
I proceeded with creating some layout template sketches on paper to be translated into my skeletal and interactive wireframes. Using sketched layout templates are low cost methods for developing fast and efficient methods for getting ideas for the flow and feel of the application. Through this layout templates I was able to get a better visual idea for how this application might work for an individual.
I understood my wire frames were going to be a really rough representation for my task manager, however, I noticed a huge bias that I let interfere with the overall design and content of the product. Since I have been using a physical journal in similar manners I was already familiar with vocabulary and terminology used. I found that this terminology such as Future Log, Monthly Log, and Daily Log had really different meanings during testing and got wonderful insight that these terms need to be changed. I found that my Daily Log was hidden in the Monthly Logs and it was intuitive for how to access this feature of the application.
Another big finding was that many of the content ideas used in bullet journalling are designed and made for the specific use of that type of system. For example Future logs are meant to be a place to write down any upcoming events that you want to keep track of, almost as a event dump or event pile. Because this system on paper doesn’t auto populate like a computer it makes sense that this type of future log helps to facilitate the monthly log and further the daily log. For further iterations and redesign of the system I will look into include different terminology that can support what users expect to do given the features and functionality, and at the same time I after testing I believe I have to redesign many of the initial ideas I had to fit more of the expectation for online based task managers such as a traditional calendar instead of the list of days and numbers, as well as pushing the daily log to the forefront of the app rather than hidden in the monthly log.
Can’t wait to share this updated project stay tuned for more! Cheers!