The reengineering of an entire tool

Executive view

The case at a glance

As UX Lead, over 12 months I led the reengineering of Cannect: from an obsolete, slow, hard-to-use web system to an end-to-end traceable product for indoor cultivation. The first milestone was closing the MVP with the team and the client.

01 — Context

Primary users

Cannect’s primary users are cannabis producers seeking to improve crop efficiency and quality through advanced real-time monitoring and control technology, enabling end-to-end traceability of the cannabis crop and, ultimately, a higher-quality product.

The challenge

Challenges and objectives

The challenge was simple yet highly complex: redesign the full experience because, in its first phase, the product did not adequately meet users’ basic needs.

This promotional video shows what the system was like before our intervention.

Understanding the pain points

The pain points at Cannect could be counted on more than two hands.

02 — Process

Antidote: redesigning the entire experience

With a large number of pain points across the entire application, every leader’s vision for this project was clear: we needed a full reengineering and UX redesign of the app. We took on the challenge.

Mapping all pain points

To tackle the project, we got to work as a team. First, we thoroughly identified and analyzed every pain point users had experienced while using the service. That analysis gave us a deep understanding of users’ difficulties and frustrations, providing a solid foundation for our improvements.

We also ran a detailed review to detect visual and functional inconsistencies in the current service. Those inconsistencies, ranging from minor design issues to critical functional failures, were catalogued and prioritized.

With that information in hand, we set a clear action plan focused on addressing these pain points and inconsistencies.

View inconsistency research

Priorizando funcionalidades

We started the project by working collaboratively with all leaders to prioritize the features that would make up the Minimum Viable Product (MVP). This phase was crucial to ensure every stakeholder was aligned and focused on the most important, highest-impact features for the end user.

During the prioritization sessions, we discussed and evaluated each proposed feature, considering factors such as relevance to the user, technical complexity, and added value to the product.

Once we established priorities, we proceeded to define the project kickoff and the first steps to follow: a detailed plan with initial tasks, timelines and responsibilities, and clear communication channels.

Defining the system architecture

The sitemap as the first artifact

We kicked off the project by setting optimization of the website structure as the first step. To achieve this, we created an essential artifact: the sitemap.

The sitemap allowed us to visualize and organize every section and page of the site in a coherent, logical way. Through that map, we identified the areas that needed restructuring and the connections between different parts of the site, making sure navigation was intuitive and efficient for users.

Ver sitemap

How we worked

The process combined empathy, definition, ideation, and validation, with the user at the center.

Implementation

With the prototypes validated and refined, we moved into implementation. The product was developed and prepared for launch, ensuring every validated piece made it to production.

Working with order

Working with order, a purpose that is not negotiated, in this project too

(In case you have not read this line in my portfolio before, visit the RUBI case study.) Just as in previous projects, the file organization was simple:

03 — Product

Closing the first MVP

Finally, after an arduous and meticulous teamwork process—with numerous discussion and analysis sessions—we completed the first stage of Cannect. This journey involved deep learning and understanding of the industry we operate in, as well as an exhaustive study of the principles that govern how the facilities involved in our project work.

Every team member contributed their experience and knowledge to understand how these plants could be traced and coordinated effectively, with the goal of delivering a final product of the highest quality. We ran multiple feature validations and detailed reviews to make sure every aspect of the project met the expected standards.

This first milestone not only marks the end of a crucial phase, but also the beginning of new stages that will let us move toward the full implementation of Cannect. Demo presentation with the client.

04 — Outcomes

Conclusion

Building the tool for Cannect was a challenging yet highly rewarding journey, marked by close collaboration with the client and rigorous testing with end users. Through this process, we designed a solution that not only meets the client’s needs but also significantly improves users’ day-to-day experience.

Bringing in technology to improve both the quality of work and the operators’ lives was a challenge we took on with a great deal of responsibility and empathy.

In short, this project has been an enriching experience that broadened our understanding of the different applications of technology and their impact on working life.

Learnings

Lessons learned: