Small Groups Registration
Small Groups Registration
The Small Groups Registration is a mobile app that optimizes the application and follow-up process of farmer groups accross India, Kenya, Tanzania, and Uganda to be part of the TIST program (The International Small Group and Tree Planting Program). By centralizing this process into a single mobile tool, the app reduces field costs and improves data accuracy.
The Small Groups Registration is a mobile app that optimizes the application and follow-up process of farmer groups accross India, Kenya, Tanzania, and Uganda to be part of the TIST program (The International Small Group and Tree Planting Program). By centralizing this process into a single mobile tool, the app reduces field costs and improves data accuracy.
Client
TIST
DELIVERABLES
uX design
redesign
ILLUSTRATIONS
Year
2025
Role
Jr. UX Designer
Understanding the challenge & the users
Understanding the challenge & the users
TIST is an afforestation project created in the late 1990's in Tanzania to mitigate climate change while improving the lives of people in need. By training farmers, TIST promotes the goal of conservating agricultural management and enables participants to earn income through verified carbon credits that can be turned into cash.
Since then, they have expanded to India, Uganda and Kenya- helping more than 250k farmers, planting over 28M trees and sequestred 7 million metric tons of CO2.
Due to the rapid growth, TIST introduced "Clusters", field representatives responsible for training farmers, managing registrations and payments. However, their application and verification process depended on fragmented data sources—Pendragon forms, handwritten notes and manually transcribed spreadsheets. This lack of centralization has made monitoring costly and inefficient, often requiring long verification processes to gather evidence for groups that might drop off.
TIST is an afforestation project created in the late 1990's in Tanzania to mitigate climate change while improving the lives of people in need. By training farmers, TIST promotes the goal of conservating agricultural management and enables participants to earn income through verified carbon credits that can be turned into cash.
Since then, they have expanded to India, Uganda and Kenya- helping more than 250k farmers, planting over 28M trees and sequestred 7 million metric tons of CO2.
Due to the rapid growth, TIST introduced "Clusters", field representatives responsible for training farmers, managing registrations and payments. However, their application and verification process depended on fragmented data sources—Pendragon forms, handwritten notes and manually transcribed spreadsheets. This lack of centralization has made monitoring costly and inefficient, often requiring long verification processes to gather evidence for groups that might drop off.
First steps in the field
First steps in the field
When the project was handed to us, it had already been worked by another team for almost three months, but it was approached purely from a graphic design perspective. However, after our team reviewed the prototype, we quickly realized it lacked intuitiveness, logical flow and clear feedback mechanisms, but we had a major issue, the delivery date was less than two weeks away.
We didn't need to worry about the looks, as we already had worked on a previous TIST project— TIST's learning platform — so we retrieved the look & feel of this previous learning platform as base for the new app, ensuring visual consistency with all our TIST's products.
Our main task was to rethink the user experience from the ground up — creating a flow that would guide Cluster Servants through the registration, while keeping the interface aligned with TIST’s visual identity and functional requirements.
When the project was handed to us, it had already been worked by another team for almost three months, but it was approached purely from a graphic design perspective. However, after our team reviewed the prototype, we quickly realized it lacked intuitiveness, logical flow and clear feedback mechanisms, but we had a major issue, the delivery date was less than two weeks away.
We didn't need to worry about the looks, as we already had worked on a previous TIST project— TIST's learning platform — so we retrieved the look & feel of this previous learning platform as base for the new app, ensuring visual consistency with all our TIST's products.
Our main task was to rethink the user experience from the ground up — creating a flow that would guide Cluster Servants through the registration, while keeping the interface aligned with TIST’s visual identity and functional requirements.
Rooting the vision
Rooting the vision
With the help of my team lead and the information provided by the company's instructional team, we first began mapping the user journey and reorganizing the registration process into clear, sequential sections:
With the help of my team lead and the information provided by the company's instructional team, we first began mapping the user journey and reorganizing the registration process into clear, sequential sections:
01 Group Information – name, location, and group photo.
02 Members Information – personal data, ID, photos, and phone number.
03 Grove Information – seedlings, land, and verification photos.
04 Trees and Stumps Registry – ongoing updates on tree growth and quality.
01 Group Information – name, location, and group photo.
02 Members Information – personal data, ID, photos, and phone number.
03 Grove Information – seedlings, land, and verification photos.
04 Trees and Stumps Registry – ongoing updates on tree growth and quality.
To support the navigation through the app, we added:
To support the navigation through the app, we added:




1
Bottom navigation bar
Added also as an inherited feature from the learning app, it will provide quick access to registered groups, settings and accesibility features.
2
Confirmation modals
To reassure users their information was successfully saved and to administrate apps permissions.
3
Visual examples
To provide additional information to identify species, and give instructions that need specifal requirements — ensuring consistent submissions across regions.




1
Bottom navigation bar
Added also as an inherited feature from the learning app, it will provide quick access to registered groups, settings and accesibility features.
2
Confirmation modals
To reassure users their information was successfully saved and to administrate apps permissions.
3
Visual examples
To provide additional information to identify species, and give instructions that need specifal requirements — ensuring consistent submissions across regions.
1
Bottom navigation bar
Added also as an inherited feature from the learning app, it will provide quick access to registered groups, settings and accesibility features.




2
Confirmation modals
To reassure users their information was successfully saved and to administrate apps permissions.




3
Visual examples
To provide additional information to identify species, and give instructions that need specifal requirements — ensuring consistent submissions across regions.




The first sprout
The first sprout
Once we had finished mapping the user journey, my new duty was to bring our ideas into high-fidelity interfaces. Using the learning platform screens as a design base I was able to develop base screens, modals, created illustrations and gathered images for the whole flow. I reiterated several screens as I wasn't sure they fitted the proposal's standard, so I reviewed them with my team lead and we reiterated them until we were satisfied with the final layout. We validated this mockups with the instructional design lead in charge of this project, but apart from changes in the instructions we didn't get further feedback.
Once we had finished mapping the user journey, my new duty was to bring our ideas into high-fidelity interfaces. Using the learning platform screens as a design base I was able to develop base screens, modals, created illustrations and gathered images for the whole flow. I reiterated several screens as I wasn't sure they fitted the proposal's standard, so I reviewed them with my team lead and we reiterated them until we were satisfied with the final layout. We validated this mockups with the instructional design lead in charge of this project, but apart from changes in the instructions we didn't get further feedback.
Bringing it to life
Bringing it to life
Once we had green light over the mockups, I rushed to have the protoype as soon as possible so we would be able to test if it runned smoothly from end to end for the stakeholders to try.
Once we had green light over the mockups, I rushed to have the protoype as soon as possible so we would be able to test if it runned smoothly from end to end for the stakeholders to try.
Presentating the proposal
Presentating the proposal
After the prototype passed internal validation, we were ready to show it to the project's stakeholders, as I was assigned to present the prototype during the session I practice the session with my UX lead, so we could give the flow a final check and time the whole presentation. The participants of the meeting were the Instructional Design project lead, the Development lead, one of the co-founders of Yeltic (the company I work for) and a Cambridge representative.
We addressed all the changes in the registration flow, the logic behind them and the added features compared to the actual process.
After the prototype passed internal validation, we were ready to show it to the project's stakeholders, as I was assigned to present the prototype during the session I practice the session with my UX lead, so we could give the flow a final check and time the whole presentation. The participants of the meeting were the Instructional Design project lead, the Development lead, one of the co-founders of Yeltic (the company I work for) and a Cambridge representative.
We addressed all the changes in the registration flow, the logic behind them and the added features compared to the actual process.
Iteration and feedback
During stakeholder review, we received highly positive feedback. The interactive prototype was particularly valuable, as it clearly demonstrated the intended navigation and flow of the registration process. One key insight came from the Cambridge representative:


"The app should be viewed not as a short-term form, but as a long-term record, where Cluster Servants continuously update the group’s progress over time. The trees and stumps section correspond to the registry process as this step takes time and sources that are often wasted due to the tendency of groups droping off."
This insight led to a significant design change — dividing the registration into two main sections:
Expression of Interest (initial data collection)
Registry (baseline grove information and ongoing tree data updates)
All the worked we had done, specifically corresponded to the Expression of interest.
My role as a not so junior UX Designer
My role as a not so junior UX Designer
My main responsibilities in this project included:
My main responsibilities in this project included:
01
01
User flow redesign
User flow redesign
My first steps into the project included gathering all the data needed to start designing. With my team lead, we analyzed the graphic design team's proposal to identify the pain points and proceeded to reorganize the architechture.
My first steps into the project included gathering all the data needed to start designing. With my team lead, we analyzed the graphic design team's proposal to identify the pain points and proceeded to reorganize the architechture.
02
02
UI alignment and high fidelity mockups
UI alignment and high fidelity mockups
I proceeded to apply the previous design system from TIST's learning platform, adapting it to match the new app requirements — creating and iterating the final screens to ensure their usability, validating with both development and instructional teams.
I proceeded to apply the previous design system from TIST's learning platform, adapting it to match the new app requirements — creating and iterating the final screens to ensure their usability, validating with both development and instructional teams.
03
03
Functional prototype
Functional prototype
To show the intended navigation process, I connected the mockups following the intended flow so the stakeholders could visualize the proposal in real time.
To show the intended navigation process, I connected the mockups following the intended flow so the stakeholders could visualize the proposal in real time.
04
04
Stakeholder presentation
Stakeholder presentation
For the handoff, I was asked to make a live demo with the protoype for a Cambridge representative, where I was able to explain how the added features in the proposal would simplify the registration process.
For the handoff, I was asked to make a live demo with the protoype for a Cambridge representative, where I was able to explain how the added features in the proposal would simplify the registration process.
Growing together
Growing together
The project was ultimately approved by TIST, it's under the first steps of development and it will be tested by Cluster servants for a second round of feedback and polishing. Although I'm not part of the testing process, I'm really grateful for the opportunity to participate in a project that has so much social impact as it keeps growing.
Presenting it directly to stakeholders and showcasing the flow through a functional prototype, actually opened a door for an upcoming 2026 project where it's planned to overcome the second step of the registration process… which by the way, the project was given again to my team and I'm currently working on the proposal with the guidance of my UX team lead.
The project was ultimately approved by TIST, it's under the first steps of development and it will be tested by Cluster servants for a second round of feedback and polishing. Although I'm not part of the testing process, I'm really grateful for the opportunity to participate in a project that has so much social impact as it keeps growing.
Presenting it directly to stakeholders and showcasing the flow through a functional prototype, actually opened a door for an upcoming 2026 project where it's planned to overcome the second step of the registration process… which by the way, the project was given again to my team and I'm currently working on the proposal with the guidance of my UX team lead.
Harvesting insigths
Harvesting insigths
After the positive acceptance of the project and my now relieved agenda, I was able to look back and realise how much we had achieved under 7 days.
Working on a real-life tool that is actually helping people, made me understand how empathy and functionality go hand in hand. Even under pressure (…a lot of it), I learned to:
Prioritize usability features and simplify complex processes.
Adapt an existing design system to new requirements.
Gained practical experience in building a coherent experience across multiple connected products within the same ecosystem.
Understood the value of designing scalable products for long-term user interaction, not just one-time tasks, as user needs evolve as data grows.
I also strengthened my confidence in presenting UX decisions and prototypes to senior stakeholders — receiving direct feedback from the client and seeing how our redesign was so well received, made this project's experience very valuable to me.
Eventhough I'm not always so aware of it, this little achievements make me realise my own growth.
After the positive acceptance of the project and my now relieved agenda, I was able to look back and realise how much we had achieved under 7 days.
Working on a real-life tool that is actually helping people, made me understand how empathy and functionality go hand in hand. Even under pressure (…a lot of it), I learned to:
Prioritize usability features and simplify complex processes.
Adapt an existing design system to new requirements.
Gained practical experience in building a coherent experience across multiple connected products within the same ecosystem.
Understood the value of designing scalable products for long-term user interaction, not just one-time tasks, as user needs evolve as data grows.
I also strengthened my confidence in presenting UX decisions and prototypes to senior stakeholders — receiving direct feedback from the client and seeing how our redesign was so well received, made this project's experience very valuable to me.
Eventhough I'm not always so aware of it, this little achievements make me realise my own growth.



























