The $100,000 UX of ... Bulls?
Showing the value of user-centred design by turning a manual workflow into a structured digital system that helps save hundreds of thousands of dollars.
2024
Year
2024
Year
2024
Year
2024
Year
12 weeks
Duration
12 weeks
Duration
12 weeks
Duration
12 weeks
Duration
Figma
Stack
Figma
Stack
Figma
Stack
Figma
Stack
UX Team of One
Role
UX Team of One
Role
UX Team of One
Role
UX Team of One
Role
5-10 minutes
Reading Time
5-10 minutes
Reading Time
5-10 minutes
Reading Time
5-10 minutes
Reading Time
Quick Summary
Problem
Manual, handwritten production processes led to inefficiencies, limited accountability, and accuracy errors, all of which carried heavy financial costs. The workflow relied on expert intuition rather than reliable systems, making mistakes both difficult to detect and hard to rectify.
Problem
Manual, handwritten production processes led to inefficiencies, limited accountability, and accuracy errors, all of which carried heavy financial costs. The workflow relied on expert intuition rather than reliable systems, making mistakes both difficult to detect and hard to rectify.
Problem
Manual, handwritten production processes led to inefficiencies, limited accountability, and accuracy errors, all of which carried heavy financial costs. The workflow relied on expert intuition rather than reliable systems, making mistakes both difficult to detect and hard to rectify.
Problem
Manual, handwritten production processes led to inefficiencies, limited accountability, and accuracy errors, all of which carried heavy financial costs. The workflow relied on expert intuition rather than reliable systems, making mistakes both difficult to detect and hard to rectify.
Solution
I designed a digital, scanner-integrated system that replaced the manual steps with a structured and traceable workflow. The interface mirrored existing habits to simplify adoption while improving speed, accuracy, and consistency. What was once fragile and error-prone became a reliable, data-driven process.
Solution
I designed a digital, scanner-integrated system that replaced the manual steps with a structured and traceable workflow. The interface mirrored existing habits to simplify adoption while improving speed, accuracy, and consistency. What was once fragile and error-prone became a reliable, data-driven process.
Solution
I designed a digital, scanner-integrated system that replaced the manual steps with a structured and traceable workflow. The interface mirrored existing habits to simplify adoption while improving speed, accuracy, and consistency. What was once fragile and error-prone became a reliable, data-driven process.
Solution
I designed a digital, scanner-integrated system that replaced the manual steps with a structured and traceable workflow. The interface mirrored existing habits to simplify adoption while improving speed, accuracy, and consistency. What was once fragile and error-prone became a reliable, data-driven process.
My Role
As the sole UX designer, I led research, testing, prototyping, and documentation. I worked closely with developers, production staff, and leadership to align technical, operational, and strategic perspectives into a cohesive solution.
My Role
As the sole UX designer, I led research, testing, prototyping, and documentation. I worked closely with developers, production staff, and leadership to align technical, operational, and strategic perspectives into a cohesive solution.
My Role
As the sole UX designer, I led research, testing, prototyping, and documentation. I worked closely with developers, production staff, and leadership to align technical, operational, and strategic perspectives into a cohesive solution.
My Role
As the sole UX designer, I led research, testing, prototyping, and documentation. I worked closely with developers, production staff, and leadership to align technical, operational, and strategic perspectives into a cohesive solution.
Challenges
Unlike typical UX contexts, our users were workers with low digital literacy in a rural environment, not exactly what is taught in class. Every detail had to be rethought for simplicity, clarity, and resilience. Oh, and did I mention I was the sole UX designer on the project?
Challenges
Unlike typical UX contexts, our users were workers with low digital literacy in a rural environment, not exactly what is taught in class. Every detail had to be rethought for simplicity, clarity, and resilience. Oh, and did I mention I was the sole UX designer on the project?
Challenges
Unlike typical UX contexts, our users were workers with low digital literacy in a rural environment, not exactly what is taught in class. Every detail had to be rethought for simplicity, clarity, and resilience. Oh, and did I mention I was the sole UX designer on the project?
Challenges
Unlike typical UX contexts, our users were workers with low digital literacy in a rural environment, not exactly what is taught in class. Every detail had to be rethought for simplicity, clarity, and resilience. Oh, and did I mention I was the sole UX designer on the project?
Complete Process
Step 0: Context
A Project Five Years in the Making
Step 0: Context
A Project Five Years in the Making
Step 0: Context
A Project Five Years in the Making
Step 0: Context
A Project Five Years in the Making
A Closer Look at the Problem
This project focused on a key part of Alta’s operations: the production of genetic material at its Brazilian branch. Over time, a reliable system was built to support this process. It worked well overall, but some early stages still relied on manual methods rooted in long-standing practices.
To illustrate this, let’s look at how one of the bulls providing the genetic material is identified:
See that faded tattoo? That was the only official ID system, and this was one of the clearest examples.
A Closer Look at the Problem
This project focused on a key part of Alta’s operations: the production of genetic material at its Brazilian branch. Over time, a reliable system was built to support this process. It worked well overall, but some early stages still relied on manual methods rooted in long-standing practices.
To illustrate this, let’s look at how one of the bulls providing the genetic material is identified:
See that faded tattoo? That was the only official ID system, and this was one of the clearest examples.
A Closer Look at the Problem
This project focused on a key part of Alta’s operations: the production of genetic material at its Brazilian branch. Over time, a reliable system was built to support this process. It worked well overall, but some early stages still relied on manual methods rooted in long-standing practices.
To illustrate this, let’s look at how one of the bulls providing the genetic material is identified:
See that faded tattoo? That was the only official ID system, and this was one of the clearest examples.
A Closer Look at the Problem
This project focused on a key part of Alta’s operations: the production of genetic material at its Brazilian branch. Over time, a reliable system was built to support this process. It worked well overall, but some early stages still relied on manual methods rooted in long-standing practices.
To illustrate this, let’s look at how one of the bulls providing the genetic material is identified:
See that faded tattoo? That was the only official ID system, and this was one of the clearest examples.
Who is Alta Genetics?
Alta Genetics is a multinational dedicated to helping cattle producers improve herd genetics. Their innovations support the global meat and dairy supply, ultimately putting food on the table for millions. Beyond genetics, Alta also develops software: tools for farmers and vets managing herds and internal systems that streamline daily operations.
Who is Alta Genetics?
Alta Genetics is a multinational dedicated to helping cattle producers improve herd genetics. Their innovations support the global meat and dairy supply, ultimately putting food on the table for millions. Beyond genetics, Alta also develops software: tools for farmers and vets managing herds and internal systems that streamline daily operations.
Who is Alta Genetics?
Alta Genetics is a multinational dedicated to helping cattle producers improve herd genetics. Their innovations support the global meat and dairy supply, ultimately putting food on the table for millions. Beyond genetics, Alta also develops software: tools for farmers and vets managing herds and internal systems that streamline daily operations.
Who is Alta Genetics?
Alta Genetics is a multinational dedicated to helping cattle producers improve herd genetics. Their innovations support the global meat and dairy supply, ultimately putting food on the table for millions. Beyond genetics, Alta also develops software: tools for farmers and vets managing herds and internal systems that streamline daily operations.
To make everything worse...
If the fading tattoo wasn’t challenging enough, most records at this stage were still handwritten. The team’s experience kept things running, but a single unnoticed slip could quietly turn into a ticking time bomb. And once this stage was over, defusing that bomb by catching errors became nearly impossible.
An example of how notes can get in a rush. Can you tell what it says?
To make everything worse...
If the fading tattoo wasn’t challenging enough, most records at this stage were still handwritten. The team’s experience kept things running, but a single unnoticed slip could quietly turn into a ticking time bomb. And once this stage was over, defusing that bomb by catching errors became nearly impossible.
An example of how notes can get in a rush. Can you tell what it says?
To make everything worse...
If the fading tattoo wasn’t challenging enough, most records at this stage were still handwritten. The team’s experience kept things running, but a single unnoticed slip could quietly turn into a ticking time bomb. And once this stage was over, defusing that bomb by catching errors became nearly impossible.
An example of how notes can get in a rush. Can you tell what it says?
To make everything worse...
If the fading tattoo wasn’t challenging enough, most records at this stage were still handwritten. The team’s experience kept things running, but a single unnoticed slip could quietly turn into a ticking time bomb. And once this stage was over, defusing that bomb by catching errors became nearly impossible.
An example of how notes can get in a rush. Can you tell what it says?
An Opportunity for Something Greater
For years, digitizing the workflow was treated as a nice-to-have. The team’s expertise kept things running, but cracks grew harder to ignore. When I joined, leadership seized the moment to show the value of UX. The goal was simple: create a digital system with mobile scanners to replace handwritten notes and patchwork processes, preventing costly mistakes and setting the foundation for clearer, more reliable operations.
An Opportunity for Something Greater
For years, digitizing the workflow was treated as a nice-to-have. The team’s expertise kept things running, but cracks grew harder to ignore. When I joined, leadership seized the moment to show the value of UX. The goal was simple: create a digital system with mobile scanners to replace handwritten notes and patchwork processes, preventing costly mistakes and setting the foundation for clearer, more reliable operations.
An Opportunity for Something Greater
For years, digitizing the workflow was treated as a nice-to-have. The team’s expertise kept things running, but cracks grew harder to ignore. When I joined, leadership seized the moment to show the value of UX. The goal was simple: create a digital system with mobile scanners to replace handwritten notes and patchwork processes, preventing costly mistakes and setting the foundation for clearer, more reliable operations.
An Opportunity for Something Greater
For years, digitizing the workflow was treated as a nice-to-have. The team’s expertise kept things running, but cracks grew harder to ignore. When I joined, leadership seized the moment to show the value of UX. The goal was simple: create a digital system with mobile scanners to replace handwritten notes and patchwork processes, preventing costly mistakes and setting the foundation for clearer, more reliable operations.
Proving the Value of UX
Alta already had strong developers and designers, but I was their first UX hire. Bringing user focus into the mix revealed blind spots the team had never considered, helped avoid expensive rework, and showed how much could be gained from a fresh perspective.
Proving UX's power
Alta already had strong developers and designers, but I was their first UX hire. Bringing user focus into the mix revealed blind spots the team had never considered, helped avoid expensive rework, and showed how much could be gained from a fresh perspective.
Proving the Value of UX
Alta already had strong developers and designers, but I was their first UX hire. Bringing user focus into the mix revealed blind spots the team had never considered, helped avoid expensive rework, and showed how much could be gained from a fresh perspective.
Proving the Value of UX
Alta already had strong developers and designers, but I was their first UX hire. Bringing user focus into the mix revealed blind spots the team had never considered, helped avoid expensive rework, and showed how much could be gained from a fresh perspective.
Step 1: Defining
Making Sense of the Unknown
Step 1: Defining
Making Sense of the Unknown
Step 1: Defining
Making Sense of the Unknown
Step 1: Defining
Making Sense of the Unknown
Starting with Conversations
After visiting the production floor and talking with my supervisor, I started conducting stakeholder interviews with the people behind each part of the process.
What I found was a mix of overlapping stories that didn’t quite line up. It felt a bit like interviewing eyewitnesses after a minor accident. Everyone agreed on what happened, just not on when, where, or how. You know, tiny details that would never cause any real issues later.
To make those conversations more tangible, I began sketching early assets the team could point at and react to.
The first user flow, shaped by team input, helped align early meetings and make sure everyone was picturing the same thing.
Starting with Conversations
After visiting the production floor and talking with my supervisor, I started conducting stakeholder interviews with the people behind each part of the process.
What I found was a mix of overlapping stories that didn’t quite line up. It felt a bit like interviewing eyewitnesses after a minor accident. Everyone agreed on what happened, just not on when, where, or how. You know, tiny details that would never cause any real issues later.
To make those conversations more tangible, I began sketching early assets the team could point at and react to.
The first user flow, shaped by team input, helped align early meetings and make sure everyone was picturing the same thing.
Starting with Conversations
After visiting the production floor and talking with my supervisor, I started conducting stakeholder interviews with the people behind each part of the process.
What I found was a mix of overlapping stories that didn’t quite line up. It felt a bit like interviewing eyewitnesses after a minor accident. Everyone agreed on what happened, just not on when, where, or how. You know, tiny details that would never cause any real issues later.
To make those conversations more tangible, I began sketching early assets the team could point at and react to.
The first user flow, shaped by team input, helped align early meetings and make sure everyone was picturing the same thing.
Starting with Conversations
After visiting the production floor and talking with my supervisor, I started conducting stakeholder interviews with the people behind each part of the process.
What I found was a mix of overlapping stories that didn’t quite line up. It felt a bit like interviewing eyewitnesses after a minor accident. Everyone agreed on what happened, just not on when, where, or how. You know, tiny details that would never cause any real issues later.
To make those conversations more tangible, I began sketching early assets the team could point at and react to.
The first user flow, shaped by team input, helped align early meetings and make sure everyone was picturing the same thing.
From Assumptions to Reality
The first user flow helped kick things off, but it only captured how people thought the process worked.
To understand how it actually ran, I conducted field studies, observing tasks and interviewing the team as they worked.
Seeing the routine firsthand helped triangulate data and gave us the evidence we needed to start painting a clearer, bigger picture.
One of the first wireframes sketched for discussion. It helped spark ideas about the digital version and revealed blind spots early on.
From Assumptions to Reality
The first user flow helped kick things off, but it only captured how people thought the process worked.
To understand how it actually ran, I conducted field studies, observing tasks and interviewing the team as they worked.
Seeing the routine firsthand helped triangulate data and gave us the evidence we needed to start painting a clearer, bigger picture.
One of the first wireframes sketched for discussion. It helped spark ideas about the digital version and revealed blind spots early on.
From Assumptions to Reality
The first user flow helped kick things off, but it only captured how people thought the process worked.
To understand how it actually ran, I conducted field studies, observing tasks and interviewing the team as they worked.
Seeing the routine firsthand helped triangulate data and gave us the evidence we needed to start painting a clearer, bigger picture.
One of the first wireframes sketched for discussion. It helped spark ideas about the digital version and revealed blind spots early on.
From Assumptions to Reality
The first user flow helped kick things off, but it only captured how people thought the process worked.
To understand how it actually ran, I conducted field studies, observing tasks and interviewing the team as they worked.
Seeing the routine firsthand helped triangulate data and gave us the evidence we needed to start painting a clearer, bigger picture.
One of the first wireframes sketched for discussion. It helped spark ideas about the digital version and revealed blind spots early on.
Learning by the Book (Literally)
Being the UX team of one meant a lot of self-teaching, and thankfully, Leah Buley had already written the playbook. But it wasn’t the only source I turned to.
Lean UX reframed practices I was already familiar with in a way that fit this fast-paced, collaborative environment.
Meanwhile, Interaction Design: Beyond Human-Computer Interaction was a solid refresher on research and HCI principles from past classes.
Not a bad combo for someone running field studies with a notebook in one hand and a factory schedule in the other.
Learning by the Book (Literally)
Being the UX team of one meant a lot of self-teaching, and thankfully, Leah Buley had already written the playbook. But it wasn’t the only source I turned to.
Lean UX reframed practices I was already familiar with in a way that fit this fast-paced, collaborative environment.
Meanwhile, Interaction Design: Beyond Human-Computer Interaction was a solid refresher on research and HCI principles from past classes.
Not a bad combo for someone running field studies with a notebook in one hand and a factory schedule in the other.
Learning by the Book (Literally)
Being the UX team of one meant a lot of self-teaching, and thankfully, Leah Buley had already written the playbook. But it wasn’t the only source I turned to.
Lean UX reframed practices I was already familiar with in a way that fit this fast-paced, collaborative environment.
Meanwhile, Interaction Design: Beyond Human-Computer Interaction was a solid refresher on research and HCI principles from past classes.
Not a bad combo for someone running field studies with a notebook in one hand and a factory schedule in the other.
Learning by the Book (Literally)
Being the UX team of one meant a lot of self-teaching, and thankfully, Leah Buley had already written the playbook. But it wasn’t the only source I turned to.
Lean UX reframed practices I was already familiar with in a way that fit this fast-paced, collaborative environment.
Meanwhile, Interaction Design: Beyond Human-Computer Interaction was a solid refresher on research and HCI principles from past classes.
Not a bad combo for someone running field studies with a notebook in one hand and a factory schedule in the other.
Piecing the System Together
After hours of observation and taking notes, I began sketching flows and wireframes to clarify what I had observed. The goal wasn't to design solutions yet, just to turn the mountain of information into something people could point at and argue about productively.
That's when the edge cases really began to appear. One example was a task completed under tight time pressure and without internet access, which was initially dismissed as a rare situation. Later, we realized it wasn't rare at all, and could break the entire system if not addressed. Not exactly a small detail to be brushed off...
(Censored) Early workflow blueprint, expanded from the original flow and layered with field constraints, notes, assumptions, and emerging requirements.
Piecing the System Together
After hours of observation and taking notes, I began sketching flows and wireframes to clarify what I had observed. The goal wasn't to design solutions yet, just to turn the mountain of information into something people could point at and argue about productively.
That's when the edge cases really began to appear. One example was a task completed under tight time pressure and without internet access, which was initially dismissed as a rare situation. Later, we realized it wasn't rare at all, and could break the entire system if not addressed. Not exactly a small detail to be brushed off...
(Censored) Early workflow blueprint, expanded from the original flow and layered with field constraints, notes, assumptions, and emerging requirements.
Piecing the System Together
After hours of observation and taking notes, I began sketching flows and wireframes to clarify what I had observed. The goal wasn't to design solutions yet, just to turn the mountain of information into something people could point at and argue about productively.
That's when the edge cases really began to appear. One example was a task completed under tight time pressure and without internet access, which was initially dismissed as a rare situation. Later, we realized it wasn't rare at all, and could break the entire system if not addressed. Not exactly a small detail to be brushed off...
(Censored) Early workflow blueprint, expanded from the original flow and layered with field constraints, notes, assumptions, and emerging requirements.
Piecing the System Together
After hours of observation and taking notes, I began sketching flows and wireframes to clarify what I had observed. The goal wasn't to design solutions yet, just to turn the mountain of information into something people could point at and argue about productively.
That's when the edge cases really began to appear. One example was a task completed under tight time pressure and without internet access, which was initially dismissed as a rare situation. Later, we realized it wasn't rare at all, and could break the entire system if not addressed. Not exactly a small detail to be brushed off...
(Censored) Early workflow blueprint, expanded from the original flow and layered with field constraints, notes, assumptions, and emerging requirements.
Leaving the Chaos Behind
What started as a mix of conflicting accounts had finally taken shape. The first user flow helped organize assumptions, the workflow blueprint captured how things actually worked, and the wireframes turned those findings into something the team could visualize and discuss.
After weeks of questions, diagrams, and discoveries, the chaos finally came to an end. It was time to move from understanding the problem to designing the solution.
Leaving the Chaos Behind
What started as a mix of conflicting accounts had finally taken shape. The first user flow helped organize assumptions, the workflow blueprint captured how things actually worked, and the wireframes turned those findings into something the team could visualize and discuss.
After weeks of questions, diagrams, and discoveries, the chaos finally came to an end. It was time to move from understanding the problem to designing the solution.
Leaving the Chaos Behind
What started as a mix of conflicting accounts had finally taken shape. The first user flow helped organize assumptions, the workflow blueprint captured how things actually worked, and the wireframes turned those findings into something the team could visualize and discuss.
After weeks of questions, diagrams, and discoveries, the chaos finally came to an end. It was time to move from understanding the problem to designing the solution.
Leaving the Chaos Behind
What started as a mix of conflicting accounts had finally taken shape. The first user flow helped organize assumptions, the workflow blueprint captured how things actually worked, and the wireframes turned those findings into something the team could visualize and discuss.
After weeks of questions, diagrams, and discoveries, the chaos finally came to an end. It was time to move from understanding the problem to designing the solution.
Where are the Personas?
They didn’t make an appearance this time, and that says a lot about how we worked. With a small, specialized user base already in close contact with the team, we could move fast and focus on learning by doing. The process leaned on quick validation, constant feedback, and visible progress instead of lengthy documentation. It was a practical, fast-moving way of working that fit Alta’s pace perfectly.
Where are the Personas?
They didn’t make an appearance this time, and that says a lot about how we worked. With a small, specialized user base already in close contact with the team, we could move fast and focus on learning by doing. The process leaned on quick validation, constant feedback, and visible progress instead of lengthy documentation. It was a practical, fast-moving way of working that fit Alta’s pace perfectly.
Where are the Personas?
They didn’t make an appearance this time, and that says a lot about how we worked. With a small, specialized user base already in close contact with the team, we could move fast and focus on learning by doing. The process leaned on quick validation, constant feedback, and visible progress instead of lengthy documentation. It was a practical, fast-moving way of working that fit Alta’s pace perfectly.
Where are the Personas?
They didn’t make an appearance this time, and that says a lot about how we worked. With a small, specialized user base already in close contact with the team, we could move fast and focus on learning by doing. The process leaned on quick validation, constant feedback, and visible progress instead of lengthy documentation. It was a practical, fast-moving way of working that fit Alta’s pace perfectly.
Step 2: Design
Defining and Refining
Step 2: Design
Defining and Refining
Step 2: Design
Defining and Refining
Step 2: Design
Defining and Refining
A Design Begins to Take Shape
With the groundwork in place, I built a mid-fidelity prototype in Figma based on the workflow blueprint and research findings. We tested it through interviews, on-site observations, and quick usability sessions, refining structure and detail with every round of feedback.
Some ideas worked right away. Others evolved after testing, sometimes more than once. The following sections highlight the design choices that held up under pressure and became the backbone of the final system.
A Design Begins to Take Shape
With the groundwork in place, I built a mid-fidelity prototype in Figma based on the workflow blueprint and research findings. We tested it through interviews, on-site observations, and quick usability sessions, refining structure and detail with every round of feedback.
Some ideas worked right away. Others evolved after testing, sometimes more than once. The following sections highlight the design choices that held up under pressure and became the backbone of the final system.
A Design Begins to Take Shape
With the groundwork in place, I built a mid-fidelity prototype in Figma based on the workflow blueprint and research findings. We tested it through interviews, on-site observations, and quick usability sessions, refining structure and detail with every round of feedback.
Some ideas worked right away. Others evolved after testing, sometimes more than once. The following sections highlight the design choices that held up under pressure and became the backbone of the final system.
A Design Begins to Take Shape
With the groundwork in place, I built a mid-fidelity prototype in Figma based on the workflow blueprint and research findings. We tested it through interviews, on-site observations, and quick usability sessions, refining structure and detail with every round of feedback.
Some ideas worked right away. Others evolved after testing, sometimes more than once. The following sections highlight the design choices that held up under pressure and became the backbone of the final system.
General Layout
Focused on making the scanner flow feel familiar even for users with little digital literacy
Example Mid-fi Scanner Page
Instructions mirror the physical process, making adoption easier for first-time users.
Large elements and strong contrast support quick recognition and accurate input, even in harsh or distracting environments.
Fixed positions for content categories support users with lower digital fluency by reinforcing layout consistency.
General Layout
Focused on making the scanner flow feel familiar even for users with little digital literacy
Example Mid-fi Scanner Page
Instructions mirror the physical process, making adoption easier for first-time users.
Large elements and strong contrast support quick recognition and accurate input, even in harsh or distracting environments.
Fixed positions for content categories support users with lower digital fluency by reinforcing layout consistency.
General Layout
Focused on making the scanner flow feel familiar even for users with little digital literacy
Example Mid-fi Scanner Page
Instructions mirror the physical process, making adoption easier for first-time users.
Large elements and strong contrast support quick recognition and accurate input, even in harsh or distracting environments.
Fixed positions for content categories support users with lower digital fluency by reinforcing layout consistency.
General Layout
Focused on making the scanner flow feel familiar even for users with little digital literacy
Example Mid-fi Scanner Page
Instructions mirror the physical process, making adoption easier for first-time users.
Large elements and strong contrast support quick recognition and accurate input, even in harsh or distracting environments.
Fixed positions for content categories support users with lower digital fluency by reinforcing layout consistency.
Clarity Through Constraint
Example of streamlined flow between related pages
Show Actions
Early versions with more actions consistently led to hesitation and input errors, especially for first-time users.
To solve this, pages were limited to a maximum of three actions to reduce cognitive load. Usability testing confirmed this was the ideal balance for clarity, functionality, and decision-making.
Clarity Through Constraint
Example of streamlined flow between related pages
Show Actions
Early versions with more actions consistently led to hesitation and input errors, especially for first-time users.
To solve this, pages were limited to a maximum of three actions to reduce cognitive load. Usability testing confirmed this was the ideal balance for clarity, functionality, and decision-making.
Clarity Through Constraint
Example of streamlined flow between related pages
Show Actions
Early versions with more actions consistently led to hesitation and input errors, especially for first-time users.
To solve this, pages were limited to a maximum of three actions to reduce cognitive load. Usability testing confirmed this was the ideal balance for clarity, functionality, and decision-making.
Clarity Through Constraint
Example of streamlined flow between related pages
Show Actions
Early versions with more actions consistently led to hesitation and input errors, especially for first-time users.
To solve this, pages were limited to a maximum of three actions to reduce cognitive load. Usability testing confirmed this was the ideal balance for clarity, functionality, and decision-making.
Encouraging Caution
Mid-fi Confirmation Pages
Every critical action includes a confirmation screen, giving users space to double-check decisions under pressure. This approach significantly lowered error rates in fast-paced tasks.
The cancel option was made the most prominent action, both visually and in reach. This design encouraged users to review inputs before continuing, reducing accidental confirmations during testing.
Encouraging Caution
Mid-fi Confirmation Pages
Every critical action includes a confirmation screen, giving users space to double-check decisions under pressure. This approach significantly lowered error rates in fast-paced tasks.
The cancel option was made the most prominent action, both visually and in reach. This design encouraged users to review inputs before continuing, reducing accidental confirmations during testing.
Encouraging Caution
Mid-fi Confirmation Pages
Every critical action includes a confirmation screen, giving users space to double-check decisions under pressure. This approach significantly lowered error rates in fast-paced tasks.
The cancel option was made the most prominent action, both visually and in reach. This design encouraged users to review inputs before continuing, reducing accidental confirmations during testing.
Encouraging Caution
Mid-fi Confirmation Pages
Every critical action includes a confirmation screen, giving users space to double-check decisions under pressure. This approach significantly lowered error rates in fast-paced tasks.
The cancel option was made the most prominent action, both visually and in reach. This design encouraged users to review inputs before continuing, reducing accidental confirmations during testing.
What Didn’t Quite Work
Most core ideas held up in testing, but a few didn’t land as well as expected. Usability testing revealed moments of hesitation, confusion, and even seemed to make a button invisible. Each of these findings guided redesigns in the high-fidelity prototype, making the system more intuitive and resilient.
Let’s look at some of those changes.
What Didn’t Quite Work
Most core ideas held up in testing, but a few didn’t land as well as expected. Usability testing revealed moments of hesitation, confusion, and even seemed to make a button invisible. Each of these findings guided redesigns in the high-fidelity prototype, making the system more intuitive and resilient.
Let’s look at some of those changes.
What Didn’t Quite Work
Most core ideas held up in testing, but a few didn’t land as well as expected. Usability testing revealed moments of hesitation, confusion, and even seemed to make a button invisible. Each of these findings guided redesigns in the high-fidelity prototype, making the system more intuitive and resilient.
Let’s look at some of those changes.
What Didn’t Quite Work
Most core ideas held up in testing, but a few didn’t land as well as expected. Usability testing revealed moments of hesitation, confusion, and even seemed to make a button invisible. Each of these findings guided redesigns in the high-fidelity prototype, making the system more intuitive and resilient.
Let’s look at some of those changes.
Simplifying Further
Mid-fi and Hi-fi List Page
Revised Version
Icons gave way to labels after testing showed most users didn’t recognize common symbols. More on this later….
Highlighting key items didn't go as planned. We tried several ways to make important rows stand out until one test revealed the real issue: in the old physical sheets, grey cells weren't just for readability. They marked critical entries. Once we replicated that in the interface, everything clicked.
Too many visible options overwhelmed users. The final version narrows available choices while still previewing upcoming ones for better planning.
Simplifying Further
Mid-fi and Hi-fi List Page
Revised Version
Icons gave way to labels after testing showed most users didn’t recognize common symbols. More on this later….
Highlighting key items didn't go as planned. We tried several ways to make important rows stand out until one test revealed the real issue: in the old physical sheets, grey cells weren't just for readability. They marked critical entries. Once we replicated that in the interface, everything clicked.
Too many visible options overwhelmed users. The final version narrows available choices while still previewing upcoming ones for better planning.
Simplifying Further
Mid-fi and Hi-fi List Page
Revised Version
Icons gave way to labels after testing showed most users didn’t recognize common symbols. More on this later….
Highlighting key items didn't go as planned. We tried several ways to make important rows stand out until one test revealed the real issue: in the old physical sheets, grey cells weren't just for readability. They marked critical entries. Once we replicated that in the interface, everything clicked.
Too many visible options overwhelmed users. The final version narrows available choices while still previewing upcoming ones for better planning.
Simplifying Further
Mid-fi and Hi-fi List Page
Revised Version
Icons gave way to labels after testing showed most users didn’t recognize common symbols. More on this later….
Highlighting key items didn't go as planned. We tried several ways to make important rows stand out until one test revealed the real issue: in the old physical sheets, grey cells weren't just for readability. They marked critical entries. Once we replicated that in the interface, everything clicked.
Too many visible options overwhelmed users. The final version narrows available choices while still previewing upcoming ones for better planning.
The Case of The Invisible Button
The "invisible" quit button went through more redesigns than anything else. The first versions used icons, which only about 20% of users recognized. Switching to written labels doubled that number, which was an improvement but still not ideal for something that needed to be obvious.
The breakthrough came from something right in front of my face. No, literally. It was a huge red exit sign hanging above the production floor, right where I ran every test. Most of our users were Brazilian farm workers, so low digital literacy wasn't surprising. What I hadn't considered was something that I already knew: around half of that population is classified as functionally illiterate by first-world standards. They simply did not recognize the words we were using. But once we used the same word from that sign instead of a term common in digital environments, recognition jumped to 100%.
It was a humbling reminder of where I come from. My formal training in Canada had given me assumptions that clouded my view of things that should have been obvious to me. Since then, I've learned to take five steps back and always question whether things are truly as universal as they seem.
The Case of The Invisible Button
The "invisible" quit button went through more redesigns than anything else. The first versions used icons, which only about 20% of users recognized. Switching to written labels doubled that number, which was an improvement but still not ideal for something that needed to be obvious.
The breakthrough came from something right in front of my face. No, literally. It was a huge red exit sign hanging above the production floor, right where I ran every test. Most of our users were Brazilian farm workers, so low digital literacy wasn't surprising. What I hadn't considered was something that I already knew: around half of that population is classified as functionally illiterate by first-world standards. They simply did not recognize the words we were using. But once we used the same word from that sign instead of a term common in digital environments, recognition jumped to 100%.
It was a humbling reminder of where I come from. My formal training in Canada had given me assumptions that clouded my view of things that should have been obvious to me. Since then, I've learned to take five steps back and always question whether things are truly as universal as they seem.
The Case of The Invisible Button
The "invisible" quit button went through more redesigns than anything else. The first versions used icons, which only about 20% of users recognized. Switching to written labels doubled that number, which was an improvement but still not ideal for something that needed to be obvious.
The breakthrough came from something right in front of my face. No, literally. It was a huge red exit sign hanging above the production floor, right where I ran every test. Most of our users were Brazilian farm workers, so low digital literacy wasn't surprising. What I hadn't considered was something that I already knew: around half of that population is classified as functionally illiterate by first-world standards. They simply did not recognize the words we were using. But once we used the same word from that sign instead of a term common in digital environments, recognition jumped to 100%.
It was a humbling reminder of where I come from. My formal training in Canada had given me assumptions that clouded my view of things that should have been obvious to me. Since then, I've learned to take five steps back and always question whether things are truly as universal as they seem.
The Case of The Invisible Button
The "invisible" quit button went through more redesigns than anything else. The first versions used icons, which only about 20% of users recognized. Switching to written labels doubled that number, which was an improvement but still not ideal for something that needed to be obvious.
The breakthrough came from something right in front of my face. No, literally. It was a huge red exit sign hanging above the production floor, right where I ran every test. Most of our users were Brazilian farm workers, so low digital literacy wasn't surprising. What I hadn't considered was something that I already knew: around half of that population is classified as functionally illiterate by first-world standards. They simply did not recognize the words we were using. But once we used the same word from that sign instead of a term common in digital environments, recognition jumped to 100%.
It was a humbling reminder of where I come from. My formal training in Canada had given me assumptions that clouded my view of things that should have been obvious to me. Since then, I've learned to take five steps back and always question whether things are truly as universal as they seem.
Improving Buttons
Revised Actions in Hi-fi Pages
Show Action Overlay
Confirmation buttons stay disabled until a selection is made, preventing the early mis-clicks seen in initial tests. This small change made a big difference in accuracy.
Touch targets were enlarged on screens with single actions, reducing missed taps and better matching how users actually interacted with the system in the field.
Improving Buttons
Revised Actions in Hi-fi Pages
Show Action Overlay
Confirmation buttons stay disabled until a selection is made, preventing the early mis-clicks seen in initial tests. This small change made a big difference in accuracy.
Touch targets were enlarged on screens with single actions, reducing missed taps and better matching how users actually interacted with the system in the field.
Improving Buttons
Revised Actions in Hi-fi Pages
Show Action Overlay
Confirmation buttons stay disabled until a selection is made, preventing the early mis-clicks seen in initial tests. This small change made a big difference in accuracy.
Touch targets were enlarged on screens with single actions, reducing missed taps and better matching how users actually interacted with the system in the field.
Improving Buttons
Revised Actions in Hi-fi Pages
Show Action Overlay
Confirmation buttons stay disabled until a selection is made, preventing the early mis-clicks seen in initial tests. This small change made a big difference in accuracy.
Touch targets were enlarged on screens with single actions, reducing missed taps and better matching how users actually interacted with the system in the field.
Finallized Core Principles
Intuitive Design. The interface had to make sense instantly, even for users unfamiliar with the process or digital tools. If someone needed instructions, the design had already failed.
Intuitive Design. The interface had to make sense instantly, even for users unfamiliar with the process or digital tools. If someone needed instructions, the design had already failed.
Intuitive Design. The interface had to make sense instantly, even for users unfamiliar with the process or digital tools. If someone needed instructions, the design had already failed.
Intuitive Design. The interface had to make sense instantly, even for users unfamiliar with the process or digital tools. If someone needed instructions, the design had already failed.
Error Prevention. Mistakes in production are expensive, which is quite literally why this system is being made. Every interaction included built-in safeguards to help users avoid errors before they happened.
Error Prevention. Mistakes in production are expensive, which is quite literally why this system is being made. Every interaction included built-in safeguards to help users avoid errors before they happened.
Error Prevention. Mistakes in production are expensive, which is quite literally why this system is being made. Every interaction included built-in safeguards to help users avoid errors before they happened.
Error Prevention. Mistakes in production are expensive, which is quite literally why this system is being made. Every interaction included built-in safeguards to help users avoid errors before they happened.
Built for Real Use. Every decision was tested, challenged, and adjusted in the field. It wasn’t about designing for perfection, but for people doing real work.
Built for Real Use. Every decision was tested, challenged, and adjusted in the field. It wasn’t about designing for perfection, but for people doing real work.
Built for Real Use. Every decision was tested, challenged, and adjusted in the field. It wasn’t about designing for perfection, but for people doing real work.
Built for Real Use. Every decision was tested, challenged, and adjusted in the field. It wasn’t about designing for perfection, but for people doing real work.
Usability Over Aesthetics. Visual polish mattered less than practical clarity. High contrast visuals, large touch areas, and simple designs made the system much easier to use in practice.
Usability Over Aesthetics. Visual polish mattered less than practical clarity. High contrast visuals, large touch areas, and simple designs made the system much easier to use in practice.
Usability Over Aesthetics. Visual polish mattered less than practical clarity. High contrast visuals, large touch areas, and simple designs made the system much easier to use in practice.
Usability Over Aesthetics. Visual polish mattered less than practical clarity. High contrast visuals, large touch areas, and simple designs made the system much easier to use in practice.
Step 3: Handover
Finishing Touches
Step 3: Handover
Finishing Touches
Step 3: Handover
Finishing Touches
Step 3: Handover
Finishing Touches
Making It Theirs
The system finally worked as intended. But to truly feel like it belonged, it needed to look and behave like something built by Alta, not something dropped in from outside.
We introduced Alta’s visual identity: typography, brand colors, and standard icons. Real production data replaced placeholders, and that single shift changed how the tool felt.
It stopped being “an app” and started becoming our app.
The same page before and after Alta’s visual identity and real (here lightly censored) data were added.
Making It Theirs
The system finally worked as intended. But to truly feel like it belonged, it needed to look and behave like something built by Alta, not something dropped in from outside.
We introduced Alta’s visual identity: typography, brand colors, and standard icons. Real production data replaced placeholders, and that single shift changed how the tool felt.
It stopped being “an app” and started becoming our app.
Making It Theirs
The system finally worked as intended. But to truly feel like it belonged, it needed to look and behave like something built by Alta, not something dropped in from outside.
We introduced Alta’s visual identity: typography, brand colors, and standard icons. Real production data replaced placeholders, and that single shift changed how the tool felt.
It stopped being “an app” and started becoming our app.
The same page before and after Alta’s visual identity and real (here lightly censored) data were added.
Making It Theirs
The system finally worked as intended. But to truly feel like it belonged, it needed to look and behave like something built by Alta, not something dropped in from outside.
We introduced Alta’s visual identity: typography, brand colors, and standard icons. Real production data replaced placeholders, and that single shift changed how the tool felt.
It stopped being “an app” and started becoming our app.
The same page before and after Alta’s visual identity and real (here lightly censored) data were added.
"Leaving" It Clear
Something I've learned many times in my life is that the real test of a project isn't how well it works while you're there, but instead how well it continues to work once you're gone.
Every decision was documented along the way, not just wireframes and prototypes but the reasoning, trade-offs, and testing results behind them. Technical constraints were flagged, and future adaptations were outlined to help the system evolve as processes changed.
By the end, the team had everything they needed to keep moving without me: a high-fidelity prototype, an updated workflow blueprint, developer specs, and rollout materials. That clarity paid off. Developers moved straight into build mode with fewer meetings, fewer questions, and almost no misalignment.
"Leaving" It Clear
Something I've learned many times in my life is that the real test of a project isn't how well it works while you're there, but instead how well it continues to work once you're gone.
Every decision was documented along the way, not just wireframes and prototypes but the reasoning, trade-offs, and testing results behind them. Technical constraints were flagged, and future adaptations were outlined to help the system evolve as processes changed.
By the end, the team had everything they needed to keep moving without me: a high-fidelity prototype, an updated workflow blueprint, developer specs, and rollout materials. That clarity paid off. Developers moved straight into build mode with fewer meetings, fewer questions, and almost no misalignment.
"Leaving" It Clear
Something I've learned many times in my life is that the real test of a project isn't how well it works while you're there, but instead how well it continues to work once you're gone.
Every decision was documented along the way, not just wireframes and prototypes but the reasoning, trade-offs, and testing results behind them. Technical constraints were flagged, and future adaptations were outlined to help the system evolve as processes changed.
By the end, the team had everything they needed to keep moving without me: a high-fidelity prototype, an updated workflow blueprint, developer specs, and rollout materials. That clarity paid off. Developers moved straight into build mode with fewer meetings, fewer questions, and almost no misalignment.
That fading tattoo on the bull's leg? Is how we identify them, and this is a good case
"Leaving" It Clear
Something I've learned many times in my life is that the real test of a project isn't how well it works while you're there, but instead how well it continues to work once you're gone.
Every decision was documented along the way, not just wireframes and prototypes but the reasoning, trade-offs, and testing results behind them. Technical constraints were flagged, and future adaptations were outlined to help the system evolve as processes changed.
By the end, the team had everything they needed to keep moving without me: a high-fidelity prototype, an updated workflow blueprint, developer specs, and rollout materials. That clarity paid off. Developers moved straight into build mode with fewer meetings, fewer questions, and almost no misalignment.
That fading tattoo on the bull's leg? Is how we identify them, and this is a good case
No NDAs Were Harmed
Everything in this case study comes from real project material, with a few small tweaks for translation, privacy, and clarity. All content was reviewed and approved before publishing.
(That’s also why there aren’t any images for this section: most of the documentation still lives safely behind company walls)
No NDAs Were Harmed
Everything in this case study comes from real project material, with a few small tweaks for translation, privacy, and clarity. All content was reviewed and approved before publishing.
(That’s also why there aren’t any images for this section: most of the documentation still lives safely behind company walls)
No NDAs Were Harmed
Everything in this case study comes from real project material, with a few small tweaks for translation, privacy, and clarity. All content was reviewed and approved before publishing.
(That’s also why there aren’t any images for this section: most of the documentation still lives safely behind company walls)
No NDAs Were Harmed
Everything in this case study comes from real project material, with a few small tweaks for translation, privacy, and clarity. All content was reviewed and approved before publishing.
(That’s also why there aren’t any images for this section: most of the documentation still lives safely behind company walls)
Delivery and Impact
The system was received better than expected.
Developers quickly noticed how much time and guesswork had been saved. Production managers valued how the interface fit their workflows and reduced manual errors.
Leadership noticed too. The company president even highlighted the project during leadership meetings, not for its appearance, but for its effectiveness. The system was projected to save hundred of thousands of dollars, reduced redundant effort, and supported teams that had been hard to digitize.
The result was clear: value felt on the ground and recognized at the top. Hundreds of thousands of dollars were saved, and the success built new trust in UX and in me. That trust soon led to larger projects and greater responsibility.
Delivery and Impact
The system was received better than expected.
Developers quickly noticed how much time and guesswork had been saved. Production managers valued how the interface fit their workflows and reduced manual errors.
Leadership noticed too. The company president even highlighted the project during leadership meetings, not for its appearance, but for its effectiveness. The system was projected to save hundred of thousands of dollars, reduced redundant effort, and supported teams that had been hard to digitize.
The result was clear: value felt on the ground and recognized at the top. Hundreds of thousands of dollars were saved, and the success built new trust in UX and in me. That trust soon led to larger projects and greater responsibility.
Delivery and Impact
The system was received better than expected.
Developers quickly noticed how much time and guesswork had been saved. Production managers valued how the interface fit their workflows and reduced manual errors.
Leadership noticed too. The company president even highlighted the project during leadership meetings, not for its appearance, but for its effectiveness. The system was projected to save hundred of thousands of dollars, reduced redundant effort, and supported teams that had been hard to digitize.
The result was clear: value felt on the ground and recognized at the top. Hundreds of thousands of dollars were saved, and the success built new trust in UX and in me. That trust soon led to larger projects and greater responsibility.
Delivery and Impact
The system was received better than expected.
Developers quickly noticed how much time and guesswork had been saved. Production managers valued how the interface fit their workflows and reduced manual errors.
Leadership noticed too. The company president even highlighted the project during leadership meetings, not for its appearance, but for its effectiveness. The system was projected to save hundred of thousands of dollars, reduced redundant effort, and supported teams that had been hard to digitize.
The result was clear: value felt on the ground and recognized at the top. Hundreds of thousands of dollars were saved, and the success built new trust in UX and in me. That trust soon led to larger projects and greater responsibility.
Reflections
Looking Back
Reflections
Looking Back
Reflections
Looking Back
Reflections
Looking Back
Before: Learning to Prepare
Before any of this started, I knew I'd be working alone, with no UX team to lean on. So get ready, I did what any slightly terrified designer would do: I reached out to experienced designers, read books and research papers, watched talks, and learned from anything and everything that might help me navigate what was ahead.
The theory gave me confidence and an invaluable foundation that allowed me to pull this whole gambit off. Still, the real learning came from what no book could prepare me for: the unpredictable, messy, very human reality of doing the work.
Before: Learning to Prepare
Before any of this started, I knew I'd be working alone, with no UX team to lean on. So get ready, I did what any slightly terrified designer would do: I reached out to experienced designers, read books and research papers, watched talks, and learned from anything and everything that might help me navigate what was ahead.
The theory gave me confidence and an invaluable foundation that allowed me to pull this whole gambit off. Still, the real learning came from what no book could prepare me for: the unpredictable, messy, very human reality of doing the work.
Before: Learning to Prepare
Before any of this started, I knew I'd be working alone, with no UX team to lean on. So get ready, I did what any slightly terrified designer would do: I reached out to experienced designers, read books and research papers, watched talks, and learned from anything and everything that might help me navigate what was ahead.
The theory gave me confidence and an invaluable foundation that allowed me to pull this whole gambit off. Still, the real learning came from what no book could prepare me for: the unpredictable, messy, very human reality of doing the work.
Before: Learning to Prepare
Before any of this started, I knew I'd be working alone, with no UX team to lean on. So get ready, I did what any slightly terrified designer would do: I reached out to experienced designers, read books and research papers, watched talks, and learned from anything and everything that might help me navigate what was ahead.
The theory gave me confidence and an invaluable foundation that allowed me to pull this whole gambit off. Still, the real learning came from what no book could prepare me for: the unpredictable, messy, very human reality of doing the work.
The Book Stack Strikes Back
Did you think I was done listing books that helped me through all of this? Oh, far from it. I need to do justice to my saviours. During this project, I had one pile in my backpack for work and another waiting for me at home.
Beyond the ones already mentioned, there were many others, such as About Face, Articulating Design Decisions, Atomic Design, Refactoring UI, and Laws of UX. Each one was ready to answer the next question that came up: from improving research to explaining design choices to people who don't spend their lives in Figma.
But of course, that still wasn't enough. When I wasn't flipping pages, I was buried in NN Group and IxDF articles, sometimes to figure out what I even needed to search for, and other times to dive deeper into what the books had skipped. I cannot overstate the impact these authors and educators had on me throughout this process.
The Book Stack Strikes Back
Did you think I was done listing books that helped me through all of this? Oh, far from it. I need to do justice to my saviours. During this project, I had one pile in my backpack for work and another waiting for me at home.
Beyond the ones already mentioned, there were many others, such as About Face, Articulating Design Decisions, Atomic Design, Refactoring UI, and Laws of UX. Each one was ready to answer the next question that came up: from improving research to explaining design choices to people who don't spend their lives in Figma.
But of course, that still wasn't enough. When I wasn't flipping pages, I was buried in NN Group and IxDF articles, sometimes to figure out what I even needed to search for, and other times to dive deeper into what the books had skipped. I cannot overstate the impact these authors and educators had on me throughout this process.
The Book Stack Strikes Back
Did you think I was done listing books that helped me through all of this? Oh, far from it. I need to do justice to my saviours. During this project, I had one pile in my backpack for work and another waiting for me at home.
Beyond the ones already mentioned, there were many others, such as About Face, Articulating Design Decisions, Atomic Design, Refactoring UI, and Laws of UX. Each one was ready to answer the next question that came up: from improving research to explaining design choices to people who don't spend their lives in Figma.
But of course, that still wasn't enough. When I wasn't flipping pages, I was buried in NN Group and IxDF articles, sometimes to figure out what I even needed to search for, and other times to dive deeper into what the books had skipped. I cannot overstate the impact these authors and educators had on me throughout this process.
The Book Stack Strikes Back
Did you think I was done listing books that helped me through all of this? Oh, far from it. I need to do justice to my saviours. During this project, I had one pile in my backpack for work and another waiting for me at home.
Beyond the ones already mentioned, there were many others, such as About Face, Articulating Design Decisions, Atomic Design, Refactoring UI, and Laws of UX. Each one was ready to answer the next question that came up: from improving research to explaining design choices to people who don't spend their lives in Figma.
But of course, that still wasn't enough. When I wasn't flipping pages, I was buried in NN Group and IxDF articles, sometimes to figure out what I even needed to search for, and other times to dive deeper into what the books had skipped. I cannot overstate the impact these authors and educators had on me throughout this process.
During: Learning Through the Work
Everyone sees the system differently. Although bringing those perspectives together wasn't always easy, it was essential for design.
Everyone sees the system differently. Although bringing those perspectives together wasn't always easy, it was essential for design.
Everyone sees the system differently. Although bringing those perspectives together wasn't always easy, it was essential for design.
Everyone sees the system differently. Although bringing those perspectives together wasn't always easy, it was essential for design.
Plans change constantly. So, I must stay flexible and adjust quickly while keeping the user's needs at the center of every decision.
Plans change constantly. So, I must stay flexible and adjust quickly while keeping the user's needs at the center of every decision.
Plans change constantly. So, I must stay flexible and adjust quickly while keeping the user's needs at the center of every decision.
Plans change constantly. So, I must stay flexible and adjust quickly while keeping the user's needs at the center of every decision.
Communication is as important as design. Translating research and decisions for different teams was half the job. If people don’t understand the “why,” the “what” doesn’t matter.
Communication is as important as design. Translating research and decisions for different teams was half the job. If people don’t understand the “why,” the “what” doesn’t matter.
Communication is as important as design. Translating research and decisions for different teams was half the job. If people don’t understand the “why,” the “what” doesn’t matter.
Communication is as important as design. Translating research and decisions for different teams was half the job. If people don’t understand the “why,” the “what” doesn’t matter.
The real world rewrites the rules. What makes sense on a whiteboard doesn't always survive the production floor. Testing in context was what kept us in the right path.
The real world rewrites the rules. What makes sense on a whiteboard doesn't always survive the production floor. Testing in context was what kept us in the right path.
The real world rewrites the rules. What makes sense on a whiteboard doesn't always survive the production floor. Testing in context was what kept us in the right path.
The real world rewrites the rules. What makes sense on a whiteboard doesn't always survive the production floor. Testing in context was what kept us in the right path.
Iteration drove progress. Each round of feedback, every small tweak, and even the failed attempts made the final result stronger than anything I could have planned from the start.
Iteration drove progress. Each round of feedback, every small tweak, and even the failed attempts made the final result stronger than anything I could have planned from the start.
Iteration drove progress. Each round of feedback, every small tweak, and even the failed attempts made the final result stronger than anything I could have planned from the start.
Iteration drove progress. Each round of feedback, every small tweak, and even the failed attempts made the final result stronger than anything I could have planned from the start.
After: Learning from the Handoff
By the time development began, I had already come to realize that documentation mattered. What I didn't expect was how much accessibility mattered, not just for users, but for the people building the product.
Not everyone used Figma, so relying on it wasn't an option. I learned to adapt, translating design specs into formats that fit each team's workflow, including spreadsheets, visuals, and summaries, whatever made things clearer.
Good documentation doesn't reside in a single tool. It lives where people actually look. Once I understood that, collaboration became smoother, and questions turned into conversations instead of confusion.
After: Learning from the Handoff
By the time development began, I had already come to realize that documentation mattered. What I didn't expect was how much accessibility mattered, not just for users, but for the people building the product.
Not everyone used Figma, so relying on it wasn't an option. I learned to adapt, translating design specs into formats that fit each team's workflow, including spreadsheets, visuals, and summaries, whatever made things clearer.
Good documentation doesn't reside in a single tool. It lives where people actually look. Once I understood that, collaboration became smoother, and questions turned into conversations instead of confusion.
After: Learning from the Handoff
By the time development began, I had already come to realize that documentation mattered. What I didn't expect was how much accessibility mattered, not just for users, but for the people building the product.
Not everyone used Figma, so relying on it wasn't an option. I learned to adapt, translating design specs into formats that fit each team's workflow, including spreadsheets, visuals, and summaries, whatever made things clearer.
Good documentation doesn't reside in a single tool. It lives where people actually look. Once I understood that, collaboration became smoother, and questions turned into conversations instead of confusion.
After: Learning from the Handoff
By the time development began, I had already come to realize that documentation mattered. What I didn't expect was how much accessibility mattered, not just for users, but for the people building the product.
Not everyone used Figma, so relying on it wasn't an option. I learned to adapt, translating design specs into formats that fit each team's workflow, including spreadsheets, visuals, and summaries, whatever made things clearer.
Good documentation doesn't reside in a single tool. It lives where people actually look. Once I understood that, collaboration became smoother, and questions turned into conversations instead of confusion.
The Project That Made Me Certain
This was the best possible project for a first co-op. It pushed me in every direction and showed what UX and product design can really do when done with care.
I owe a huge thanks to Alta and everyone I worked with for trusting me and giving me the space to learn, experiment, and make mistakes. It’s the project that made me certain this is the kind of work I want to keep doing.
The Project That Made Me Certain
This was the best possible project for a first co-op. It pushed me in every direction and showed what UX and product design can really do when done with care.
I owe a huge thanks to Alta and everyone I worked with for trusting me and giving me the space to learn, experiment, and make mistakes. It’s the project that made me certain this is the kind of work I want to keep doing.
The Project That Made Me Certain
This was the best possible project for a first co-op. It pushed me in every direction and showed what UX and product design can really do when done with care.
I owe a huge thanks to Alta and everyone I worked with for trusting me and giving me the space to learn, experiment, and make mistakes. It’s the project that made me certain this is the kind of work I want to keep doing.
The Project That Made Me Certain
This was the best possible project for a first co-op. It pushed me in every direction and showed what UX and product design can really do when done with care.
I owe a huge thanks to Alta and everyone I worked with for trusting me and giving me the space to learn, experiment, and make mistakes. It’s the project that made me certain this is the kind of work I want to keep doing.