TOSK

UX for a technical work management platform

Context

For this project, I was commissioned to design and prototype the MVP of TOSK, a platform aimed at digitalizing the management of technical field work. The assignment started from the need to structure communication and coordination between three key actors: companies, technicians, and clients.

The focus was on creating a minimum viable product that demonstrated the system's value and could evolve in later stages. For this, functionality and validation were prioritized over a finished visual design.

Problem

In the initial interviews, a common scenario was identified in small companies and independent technicians:

• Daily management depended on scattered chats, improvised spreadsheets, or even personal memory.
• This caused forgotten or duplicated tasks, in addition to the lack of a reliable historical record.
• Clients did not have a centralized channel to track or approve work, which reduced trust in the service.

The challenge was to design a simple, intuitive, and adoptable solution that offered structure and visibility without adding friction to daily operations.

Research & Insights

To fully understand the problem, I conducted interviews and exploratory dynamics with building administrators and service providers.

Main findings:

• Fragmented communication: multiple channels were used (WhatsApp, calls, emails) for the same job, causing information to be lost or repeated.
• Lack of history: without centralized records, tasks were forgotten and there was no traceability of what was done.
• Uninformed clients: the absence of visibility generated confusion about progress, costs, and approvals.

Design implications:

• Centralize all information and actions in a single space per job.
• Incorporate a unique and visible status for each task.
• Facilitate the upload of evidence (photos, files) to support work and build trust.

UX Process

The design followed an iterative approach focused on the essentials:

• Role definition: company, technician, and client, with differentiated views and permissions according to needs.
• Flow mapping: from job creation to closure, considering assignment, execution, evidence upload, and approval.
• Initial wireframes: low-fidelity with Miro and paper sketches, prioritizing validating the usage logic before investing in UI.
• Conceptual validation: review of flows with key users to ensure processes responded to day-to-day reality.

The process was guided by principles of clarity, simplicity, and consistency, ensuring that each role had a direct path to complete their most frequent tasks.

Main Features

The MVP included a limited set of features that directly respond to the initial findings:

These functionalities were designed as a validatable core before scaling to a more robust product.

MVP & Testing

The MVP was built on Firebase, leveraging authentication, real-time database, and file storage. The result was a fully functional version that allows:

• Create and assign jobs.
• Track tasks and statuses.
• Upload evidence and maintain a unique history per job.

Currently, the platform is being prepared for a closed testing phase with real users, which will allow validating usage hypotheses, observing patterns, and collecting feedback for future iterations.

Learnings

The project demonstrated the value of quickly transforming findings into a functional product, focusing on what truly impacts the user.

The next step will be to put the system in front of real users to confirm assumptions, adjust flows, and evolve both the experience and visual design. This approach demonstrates how an MVP can serve as a bridge between initial research and field validation, reducing risks and accelerating product decision-making.