In the fast-paced landscape of freelance work and creative services, managing portfolios and finding the right projects can be a daunting task. Recognizing the challenges faced by creative professionals, the Portal.folio application emerges as a solution designed to streamline portfolio management and facilitate efficient collaboration.
I embarked on a journey to create a user-friendly and visually cohesive platform tailored to the needs of graphic designers, web developers, photographers, writers, and other creative professionals.
In the fast-paced landscape of freelance work and creative services, managing portfolios and finding the right projects can be a daunting task. Recognizing the challenges faced by creative professionals, the Portal.folio application emerges as a solution designed to streamline portfolio management and facilitate efficient collaboration.
I embarked on a journey to create a user-friendly and visually cohesive platform tailored to the needs of graphic designers, web developers, photographers, writers, and other creative professionals.
With a focus on user-centered design principles and collaboration with stakeholders, my main goals were clear:
The genesis of the Portal.folio application stemmed from a keen awareness of these pain points and a deep understanding of the needs of creative professionals.
Through extensive digital survey, I identified several critical challenges that inspired the development of Portal.folio:
These insights became instrumental in shaping the design and functionality of Portal.folio to effectively meet the needs of its target users. By aligning the application with the preferences and behaviors of creative professionals, I could ensure that Portal.folio becomes a valuable tool for portfolio management and collaboration within the freelance community.
In developing Portal.folio, it was crucial to understand the target users and their specific needs. Through the user research process, a user persona emerged: the newly graduated individual with limited work experience but a desire to build a versatile skill set. This persona served as a guiding archetype, representing a significant segment of the target audience for the application.
Considering the outcome, the main design drivers were:
In the initial stages of the project during the sketching phase, my primary focus was on crafting a preliminary user interface (UI) tailored specifically for creators. This decision was driven by the recognition of the critical role creators play in the platform's ecosystem. As time constraints were a consideration, prioritizing the creator's UI ensured the core functionality of the application was well-defined and robust.
My intention was to address the fundamental needs of creators first, with the plan to extend the design to encompass the client-side UI if time allowed. This approach aimed to deliver a well-rounded experience for creators while allowing flexibility for potential expansion in subsequent development phases.
Once I got some idea about the app and its UI I started design process in Figma. As I had already created wireframes before and pretty much mastered vector graphics and website building-services, learning Figma was a quick process.
The prototype was also built for a user's account, where browsing and managing projects and project offers are the key features.
The purpose of this user testing was to evaluate how clear the user interface is from the creator account's point of view, and whether the user can navigate the application fluently according to given tasks. User testing was definitely the most interesting phase of the project.
I developed 7 different tasks that the user could perform with the application, and after each task the test person informed that they had completed the task. For example, "Look up a person in your network and make a phone call". This way I was able to easily get valuable insight, how the users thought the navigation would work and thus, how it should work.
All 6 test persons were involved in creative industry one way or another and they could realistically have use for this service.
The testing methods I used were observation and the test subjects were also allowed to think out loud. In addition to observation, I collected a video recording of my phone's screen to study the user behavior more carefully later.
The first testing round was completed with 2 persons. I had an opportunity to mirror my phone's screen to a smart TV to observe the test away from the test person. I observed the test progress from TV and wrote notes, while the user did the tasks in another room without any distractions.
The first round revealed couple of obvious problems in the UI, which I fixed before the next test round.
The second testing round was completed at Metropolia's campus with 4 persons and this time around I had to observe the test from up close.
The second testing revealed severe issues in project navigation.
For example, an ongoing project had all the tasks with details listed in a single page, so it was very hard for a new user to progress in the test at this specific point. The navigation was easily improved by moving task details behind a separate task card and leaving only essential information to the listing.