The Digital Leap: A UX Story of Reinvention
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
8 weeks
Duration
8 weeks
Duration
8 weeks
Duration
8 weeks
Duration
Figma
Stack
Figma
Stack
Figma
Stack
Figma
Stack
10 minutes
Reading Time
10 minutes
Reading Time
10 minutes
Reading Time
10 minutes
Reading Time
Quick Summary
Problem
Manual, handwritten production processes caused significant inefficiencies, including limited accountability, poorly standardized workflows, and accuracy errors. These issues led to significant financial losses.
Problem
Manual, handwritten production processes caused significant inefficiencies, including limited accountability, poorly standardized workflows, and accuracy errors. These issues led to significant financial losses.
Problem
Manual, handwritten production processes caused significant inefficiencies, including limited accountability, poorly standardized workflows, and accuracy errors. These issues led to significant financial losses.
Problem
Manual, handwritten production processes caused significant inefficiencies, including limited accountability, poorly standardized workflows, and accuracy errors. These issues led to significant financial losses.
Solution
Working alongside a multidisciplinary team, I designed an integrated software and hardware solution that integrates with the physical process to automate data collection and validation, eliminating accuracy issues.
Solution
Working alongside a multidisciplinary team, I designed an integrated software and hardware solution that integrates with the physical process to automate data collection and validation, eliminating accuracy issues.
Solution
Working alongside a multidisciplinary team, I designed an integrated software and hardware solution that integrates with the physical process to automate data collection and validation, eliminating accuracy issues.
Solution
Working alongside a multidisciplinary team, I designed an integrated software and hardware solution that integrates with the physical process to automate data collection and validation, eliminating accuracy issues.
My Role
As the sole UX designer on the project, I was tasked with bringing this abstract idea to reality. Through a user-centred design process involving stakeholder interviews, iterative prototyping, and real-world usability testing I clearly defined and designed the final system.
My Role
As the sole UX designer on the project, I was tasked with bringing this abstract idea to reality. Through a user-centred design process involving stakeholder interviews, iterative prototyping, and real-world usability testing I clearly defined and designed the final system.
My Role
As the sole UX designer on the project, I was tasked with bringing this abstract idea to reality. Through a user-centred design process involving stakeholder interviews, iterative prototyping, and real-world usability testing I clearly defined and designed the final system.
My Role
As the sole UX designer on the project, I was tasked with bringing this abstract idea to reality. Through a user-centred design process involving stakeholder interviews, iterative prototyping, and real-world usability testing I clearly defined and designed the final system.
Challenges
Unlike typical UX scenarios, our users were rural workers with low digital literacy. Combined with real-world constraints like harsh sunlight, poor connectivity, specialized hardware and gloved use, this required rethinking standard design approaches in favor of simplicity, clarity, and resilience.
Challenges
Unlike typical UX scenarios, our users were rural workers with low digital literacy. Combined with real-world constraints like harsh sunlight, poor connectivity, specialized hardware and gloved use, this required rethinking standard design approaches in favor of simplicity, clarity, and resilience.
Challenges
Unlike typical UX scenarios, our users were rural workers with low digital literacy. Combined with real-world constraints like harsh sunlight, poor connectivity, specialized hardware and gloved use, this required rethinking standard design approaches in favor of simplicity, clarity, and resilience.
Challenges
Unlike typical UX scenarios, our users were rural workers with low digital literacy. Combined with real-world constraints like harsh sunlight, poor connectivity, specialized hardware and gloved use, this required rethinking standard design approaches in favor of simplicity, clarity, and resilience.
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 centred on a key part of Alta’s operations: the production of genetic material at its Brazilian branch. Over time, a reliable system had been established to support this process. While effective, some early stages remained manual and analog, shaped by long-standing practices.
To illustrate this, let’s look at how one of the bulls providing the genetic material is identified:
That fading tattoo on the bull’s leg? That’s how identification is done, and this is a relatively clear example.
A Closer Look at the Problem
This project centred on a key part of Alta’s operations: the production of genetic material at its Brazilian branch. Over time, a reliable system had been established to support this process. While effective, some early stages remained manual and analog, shaped by long-standing practices.
To illustrate this, let’s look at how one of the bulls providing the genetic material is identified:
That fading tattoo on the bull’s leg? That’s how identification is done, and this is a relatively clear example.
A Closer Look at the Problem
This project centred on a key part of Alta’s operations: the production of genetic material at its Brazilian branch. Over time, a reliable system had been established to support this process. While effective, some early stages remained manual and analog, shaped by long-standing practices.
To illustrate this, let’s look at how one of the bulls providing the genetic material is identified:
That fading tattoo on the bull’s leg? That’s how identification is done, and this is a relatively clear example.
A Closer Look at the Problem
This project centred on a key part of Alta’s operations: the production of genetic material at its Brazilian branch. Over time, a reliable system had been established to support this process. While effective, some early stages remained manual and analog, shaped by long-standing practices.
To illustrate this, let’s look at how one of the bulls providing the genetic material is identified:
That fading tattoo on the bull’s leg? That’s how identification is done, and this is a relatively clear example.
Who is Alta Genetics?
A multinational that helps cattle producers improve herd genetics. Their work supports the global meat and dairy supply, putting food on the table for millions. Alongside their genetic products, they also build software, both for customers managing and improving herds and also for internal teams facilitating their daily tasks.
Who is Alta Genetics?
A multinational that helps cattle producers improve herd genetics. Their work supports the global meat and dairy supply, putting food on the table for millions. Alongside their genetic products, they also build software, both for customers managing and improving herds and also for internal teams facilitating their daily tasks.
Who is Alta Genetics?
A multinational that helps cattle producers improve herd genetics. Their work supports the global meat and dairy supply, putting food on the table for millions. Alongside their genetic products, they also build software, both for customers managing and improving herds and also for internal teams facilitating their daily tasks.
Who is Alta Genetics?
A multinational that helps cattle producers improve herd genetics. Their work supports the global meat and dairy supply, putting food on the table for millions. Alongside their genetic products, they also build software, both for customers managing and improving herds and also for internal teams facilitating their daily tasks.
To make everything worse...
As if the fading tattoo wasn’t enough, most records at this stage are still handwritten. And while the team is highly experienced, a single unnoticed mistake can quietly turn into a ticking time bomb. After this part of the process is done, catching errors becomes very difficult.
An example of how notes can get in a rush. Can you tell what it says?
To make everything worse...
As if the fading tattoo wasn’t enough, most records at this stage are still handwritten. And while the team is highly experienced, a single unnoticed mistake can quietly turn into a ticking time bomb. After this part of the process is done, catching errors becomes very difficult.
An example of how notes can get in a rush. Can you tell what it says?
To make everything worse...
As if the fading tattoo wasn’t enough, most records at this stage are still handwritten. And while the team is highly experienced, a single unnoticed mistake can quietly turn into a ticking time bomb. After this part of the process is done, catching errors becomes very difficult.
An example of how notes can get in a rush. Can you tell what it says?
To make everything worse...
As if the fading tattoo wasn’t enough, most records at this stage are still handwritten. And while the team is highly experienced, a single unnoticed mistake can quietly turn into a ticking time bomb. After this part of the process is done, catching errors becomes very difficult.
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 seen as a nice-to-have. The process, though imperfect, worked well enough thanks to the team's expertise, so the project never took priority.
That changed when I joined. With leadership aligned and momentum building, my supervisor saw a clear opening to show what UX could do. The goal was clear: create a digital system, integrated with mobile scanners, that would replace the patchwork of manual processes once and for all.
An Opportunity for Something Greater
For years, digitizing the workflow was seen as a nice-to-have. The process, though imperfect, worked well enough thanks to the team's expertise, so the project never took priority.
That changed when I joined. With leadership aligned and momentum building, my supervisor saw a clear opening to show what UX could do. The goal was clear: create a digital system, integrated with mobile scanners, that would replace the patchwork of manual processes once and for all.
An Opportunity for Something Greater
For years, digitizing the workflow was seen as a nice-to-have. The process, though imperfect, worked well enough thanks to the team's expertise, so the project never took priority.
That changed when I joined. With leadership aligned and momentum building, my supervisor saw a clear opening to show what UX could do. The goal was clear: create a digital system, integrated with mobile scanners, that would replace the patchwork of manual processes once and for all.
An Opportunity for Something Greater
For years, digitizing the workflow was seen as a nice-to-have. The process, though imperfect, worked well enough thanks to the team's expertise, so the project never took priority.
That changed when I joined. With leadership aligned and momentum building, my supervisor saw a clear opening to show what UX could do. The goal was clear: create a digital system, integrated with mobile scanners, that would replace the patchwork of manual processes once and for all.
Showing the Value of UX
Alta already had talented designers and engineers, but this was the first time UX was treated as its own discipline. That gave me a unique opportunity. Beyond just designing screens, I could shape how problems were framed, how teams aligned, and how solutions were built around real constraints. This wasn’t just a UX project. It was a chance to prove the value of human-centered design as a driver of clarity, collaboration, and meaningful change across the organization.
Proving UX's power
Alta already had talented designers and engineers, but this was the first time UX was treated as its own discipline. That gave me a unique opportunity. Beyond just designing screens, I could shape how problems were framed, how teams aligned, and how solutions were built around real constraints. This wasn’t just a UX project. It was a chance to prove the value of human-centered design as a driver of clarity, collaboration, and meaningful change across the organization.
Showing the Value of UX
Alta already had talented designers and engineers, but this was the first time UX was treated as its own discipline. That gave me a unique opportunity. Beyond just designing screens, I could shape how problems were framed, how teams aligned, and how solutions were built around real constraints. This wasn’t just a UX project. It was a chance to prove the value of human-centered design as a driver of clarity, collaboration, and meaningful change across the organization.
Showing the Value of UX
Alta already had talented designers and engineers, but this was the first time UX was treated as its own discipline. That gave me a unique opportunity. Beyond just designing screens, I could shape how problems were framed, how teams aligned, and how solutions were built around real constraints. This wasn’t just a UX project. It was a chance to prove the value of human-centered design as a driver of clarity, collaboration, and meaningful change across the organization.
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 a quick visit to the production floor and a briefing from my supervisor, the next steps were clear: talk to stakeholders to understand their perspectives on what needed to be done, and start shaping some assets to make the abstract feel more concrete. This would help align everyone's understanding before jumping into solutions.
This was the original user flow as it was first explained to me. I sketched it out to guide early meetings and make sure we were all seeing the same thing.
Starting with Conversations
After a quick visit to the production floor and a briefing from my supervisor, the next steps were clear: talk to stakeholders to understand their perspectives on what needed to be done, and start shaping some assets to make the abstract feel more concrete. This would help align everyone's understanding before jumping into solutions.
This was the original user flow as it was first explained to me. I sketched it out to guide early meetings and make sure we were all seeing the same thing.
Starting with Conversations
After a quick visit to the production floor and a briefing from my supervisor, the next steps were clear: talk to stakeholders to understand their perspectives on what needed to be done, and start shaping some assets to make the abstract feel more concrete. This would help align everyone's understanding before jumping into solutions.
This was the original user flow as it was first explained to me. I sketched it out to guide early meetings and make sure we were all seeing the same thing.
Starting with Conversations
After a quick visit to the production floor and a briefing from my supervisor, the next steps were clear: talk to stakeholders to understand their perspectives on what needed to be done, and start shaping some assets to make the abstract feel more concrete. This would help align everyone's understanding before jumping into solutions.
This was the original user flow as it was first explained to me. I sketched it out to guide early meetings and make sure we were all seeing the same thing.
No NDAs Were Harmed
Everything shown here is based on real project material, with a few adjustments for translation, privacy, or clarity. All content was approved before publishing.
No NDAs Were Harmed
Everything shown here is based on real project material, with a few adjustments for translation, privacy, or clarity. All content was approved before publishing.
No NDAs Were Harmed
Everything shown here is based on real project material, with a few adjustments for translation, privacy, or clarity. All content was approved before publishing.
No NDAs Were Harmed
Everything shown here is based on real project material, with a few adjustments for translation, privacy, or clarity. All content was approved before publishing.
From Assumptions to Reality
The first user flow helped kick things off, but it quickly became clear it didn’t match what was really happening.
Everyone knew their part, but no two descriptions matched. Terms shifted, routines varied, and the clean process on paper gave way to a messier reality shaped by habit and context.
We needed something to help untangle it all.
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 quickly became clear it didn’t match what was really happening.
Everyone knew their part, but no two descriptions matched. Terms shifted, routines varied, and the clean process on paper gave way to a messier reality shaped by habit and context.
We needed something to help untangle it all.
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 quickly became clear it didn’t match what was really happening.
Everyone knew their part, but no two descriptions matched. Terms shifted, routines varied, and the clean process on paper gave way to a messier reality shaped by habit and context.
We needed something to help untangle it all.
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 quickly became clear it didn’t match what was really happening.
Everyone knew their part, but no two descriptions matched. Terms shifted, routines varied, and the clean process on paper gave way to a messier reality shaped by habit and context.
We needed something to help untangle it all.
One of the first wireframes sketched for discussion. It helped spark ideas about the digital version and revealed blind spots early on.
Visualizing Complexity
To make sense of it all, I began iterating on flows and wireframes. Not to propose solutions yet, but to ground the conversation and surface inconsistencies early.
Some of the biggest insights came from edge cases. One example was a task performed under time pressure and without internet. It was initially seen as a rare detail, not worth discussing. Later we realized it was vital when it happened, and ignoring it would have made the system unusable in one of its most critical moments.
(Censored) Early service blueprint, expanded from the original flow and layered with field constraints, notes, assumptions, and emerging requirements.
Visualizing Complexity
To make sense of it all, I began iterating on flows and wireframes. Not to propose solutions yet, but to ground the conversation and surface inconsistencies early.
Some of the biggest insights came from edge cases. One example was a task performed under time pressure and without internet. It was initially seen as a rare detail, not worth discussing. Later we realized it was vital when it happened, and ignoring it would have made the system unusable in one of its most critical moments.
(Censored) Early service blueprint, expanded from the original flow and layered with field constraints, notes, assumptions, and emerging requirements.
Visualizing Complexity
To make sense of it all, I began iterating on flows and wireframes. Not to propose solutions yet, but to ground the conversation and surface inconsistencies early.
Some of the biggest insights came from edge cases. One example was a task performed under time pressure and without internet. It was initially seen as a rare detail, not worth discussing. Later we realized it was vital when it happened, and ignoring it would have made the system unusable in one of its most critical moments.
(Censored) Early service blueprint, expanded from the original flow and layered with field constraints, notes, assumptions, and emerging requirements.
Visualizing Complexity
To make sense of it all, I began iterating on flows and wireframes. Not to propose solutions yet, but to ground the conversation and surface inconsistencies early.
Some of the biggest insights came from edge cases. One example was a task performed under time pressure and without internet. It was initially seen as a rare detail, not worth discussing. Later we realized it was vital when it happened, and ignoring it would have made the system unusable in one of its most critical moments.
(Censored) Early service blueprint, expanded from the original flow and layered with field constraints, notes, assumptions, and emerging requirements.
The Outcome
With a clear picture of the real process, we could finally shift from questioning what to build toward figuring out how to build it. The service blueprint became a reference point across teams, helping turn alignment into action.
The service blueprint became more than documentation. It gave structure to messy ideas, helped teams align without getting lost in the weeds, and became a shared point of truth as we moved into design.
The Outcome
With a clear picture of the real process, we could finally shift from questioning what to build toward figuring out how to build it. The service blueprint became a reference point across teams, helping turn alignment into action.
The service blueprint became more than documentation. It gave structure to messy ideas, helped teams align without getting lost in the weeds, and became a shared point of truth as we moved into design.
The Outcome
With a clear picture of the real process, we could finally shift from questioning what to build toward figuring out how to build it. The service blueprint became a reference point across teams, helping turn alignment into action.
The service blueprint became more than documentation. It gave structure to messy ideas, helped teams align without getting lost in the weeds, and became a shared point of truth as we moved into design.
The Outcome
With a clear picture of the real process, we could finally shift from questioning what to build toward figuring out how to build it. The service blueprint became a reference point across teams, helping turn alignment into action.
The service blueprint became more than documentation. It gave structure to messy ideas, helped teams align without getting lost in the weeds, and became a shared point of truth as we moved into design.
Where are the Personas?
They didn’t make an appearance here, and for good reason. The user base was small, specific, and already well understood by the team through ongoing direct contact. That close familiarity let us move fast, validate often, and skip the extra layer of formal user models without sacrificing confidence in our decisions.
Where are the Personas?
They didn’t make an appearance here, and for good reason. The user base was small, specific, and already well understood by the team through ongoing direct contact. That close familiarity let us move fast, validate often, and skip the extra layer of formal user models without sacrificing confidence in our decisions.
Where are the Personas?
They didn’t make an appearance here, and for good reason. The user base was small, specific, and already well understood by the team through ongoing direct contact. That close familiarity let us move fast, validate often, and skip the extra layer of formal user models without sacrificing confidence in our decisions.
Where are the Personas?
They didn’t make an appearance here, and for good reason. The user base was small, specific, and already well understood by the team through ongoing direct contact. That close familiarity let us move fast, validate often, and skip the extra layer of formal user models without sacrificing confidence in our decisions.
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 foundation mapped, I created a mid-fidelity prototype in Figma based on the service blueprint and research insights. It was tested through interviews, on-site observation, and usability sessions to refine structure and detail through direct feedback.
Some ideas worked right away. Others changed after testing, sometimes more than once. What follows is a closer look at the design decisions that stayed, which held up under pressure and became the foundation of the final version.
A Design Begins to Take Shape
With the foundation mapped, I created a mid-fidelity prototype in Figma based on the service blueprint and research insights. It was tested through interviews, on-site observation, and usability sessions to refine structure and detail through direct feedback.
Some ideas worked right away. Others changed after testing, sometimes more than once. What follows is a closer look at the design decisions that stayed, which held up under pressure and became the foundation of the final version.
A Design Begins to Take Shape
With the foundation mapped, I created a mid-fidelity prototype in Figma based on the service blueprint and research insights. It was tested through interviews, on-site observation, and usability sessions to refine structure and detail through direct feedback.
Some ideas worked right away. Others changed after testing, sometimes more than once. What follows is a closer look at the design decisions that stayed, which held up under pressure and became the foundation of the final version.
A Design Begins to Take Shape
With the foundation mapped, I created a mid-fidelity prototype in Figma based on the service blueprint and research insights. It was tested through interviews, on-site observation, and usability sessions to refine structure and detail through direct feedback.
Some ideas worked right away. Others changed after testing, sometimes more than once. What follows is a closer look at the design decisions that stayed, which held up under pressure and became the foundation of the final version.
General Layout
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
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
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
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.
Streamlining Actions
Example Flow Between Pages
Show Actions
To reduce cognitive load, pages were limited to a maximum of three actions. Usability testing quickly confirmed this was essential for clarity and decision-making. Earlier versions with more actions consistently led to hesitation and errors.
Streamlining Actions
Example Flow Between Pages
Show Actions
To reduce cognitive load, pages were limited to a maximum of three actions. Usability testing quickly confirmed this was essential for clarity and decision-making. Earlier versions with more actions consistently led to hesitation and errors.
Button layout is reversed, with the cancel option styled more prominently and placed near the thumb to guide users toward reviewing rather than confirming by accident.
Streamlining Actions
Example Flow Between Pages
Show Actions
To reduce cognitive load, pages were limited to a maximum of three actions. Usability testing quickly confirmed this was essential for clarity and decision-making. Earlier versions with more actions consistently led to hesitation and errors.
Button layout is reversed, with the cancel option styled more prominently and placed near the thumb to guide users toward reviewing rather than confirming by accident.
Streamlining Actions
Example Flow Between Pages
Show Actions
To reduce cognitive load, pages were limited to a maximum of three actions. Usability testing quickly confirmed this was essential for clarity and decision-making. Earlier versions with more actions consistently led to hesitation and errors.
Button layout is reversed, with the cancel option styled more prominently and placed near the thumb to guide users toward reviewing rather than confirming by accident.
Ensuring Accuracy
Mid-fi Confirmation Pages
Key actions include confirmation screens to help users review inputs and catch mistakes before continuing. This reduced error rates in testing, especially in high-pressure tasks.
Button layout is reversed, placing the cancel option near the thumb and styling it more prominently to encourage review over accidental confirmation. This decision was based on repeated mis-taps in older versions.
Ensuring Accuracy
Mid-fi Confirmation Pages
Key actions include confirmation screens to help users review inputs and catch mistakes before continuing. This reduced error rates in testing, especially in high-pressure tasks.
Button layout is reversed, placing the cancel option near the thumb and styling it more prominently to encourage review over accidental confirmation. This decision was based on repeated mis-taps in older versions.
Ensuring Accuracy
Mid-fi Confirmation Pages
Key actions include confirmation screens to help users review inputs and catch mistakes before continuing. This reduced error rates in testing, especially in high-pressure tasks.
Button layout is reversed, placing the cancel option near the thumb and styling it more prominently to encourage review over accidental confirmation. This decision was based on repeated mis-taps in older versions.
Ensuring Accuracy
Mid-fi Confirmation Pages
Key actions include confirmation screens to help users review inputs and catch mistakes before continuing. This reduced error rates in testing, especially in high-pressure tasks.
Button layout is reversed, placing the cancel option near the thumb and styling it more prominently to encourage review over accidental confirmation. This decision was based on repeated mis-taps in older versions.
What Didn’t Quite Work
Most core ideas tested well, but a few fell short. Usability testing revealed where users hesitated, misunderstood, or made consistent errors, and these led directly to design revisions in the high-fidelity prototype.
What Didn’t Quite Work
Most core ideas tested well, but a few fell short. Usability testing revealed where users hesitated, misunderstood, or made consistent errors, and these led directly to design revisions in the high-fidelity prototype.
What Didn’t Quite Work
Most core ideas tested well, but a few fell short. Usability testing revealed where users hesitated, misunderstood, or made consistent errors, and these led directly to design revisions in the high-fidelity prototype.
What Didn’t Quite Work
Most core ideas tested well, but a few fell short. Usability testing revealed where users hesitated, misunderstood, or made consistent errors, and these led directly to design revisions in the high-fidelity prototype.
Simplifying Further
Mid-fi and Hi-fi List Page
Revised Version
Many users didn’t recognize common icons, so we replaced them with clear labels.
Repeated attempts to highlight key items failed. We later learned grey rows were a signal for importance, not for table formatting, so we followed that familiar pattern.
Too many options overwhelmed users. The final version narrows available choices while still showing upcoming ones for planning.
Simplifying Further
Mid-fi and Hi-fi List Page
Revised Version
Many users didn’t recognize common icons, so we replaced them with clear labels.
Repeated attempts to highlight key items failed. We later learned grey rows were a signal for importance, not for table formatting, so we followed that familiar pattern.
Too many options overwhelmed users. The final version narrows available choices while still showing upcoming ones for planning.
Simplifying Further
Mid-fi and Hi-fi List Page
Revised Version
Many users didn’t recognize common icons, so we replaced them with clear labels.
Repeated attempts to highlight key items failed. We later learned grey rows were a signal for importance, not for table formatting, so we followed that familiar pattern.
Too many options overwhelmed users. The final version narrows available choices while still showing upcoming ones for planning.
Simplifying Further
Mid-fi and Hi-fi List Page
Revised Version
Many users didn’t recognize common icons, so we replaced them with clear labels.
Repeated attempts to highlight key items failed. We later learned grey rows were a signal for importance, not for table formatting, so we followed that familiar pattern.
Too many options overwhelmed users. The final version narrows available choices while still showing upcoming ones for planning.
Improving Buttons
Revised Actions in Hi-fi Pages
Hide Action Overlay
To reflect system status, confirmation buttons remain disabled until a selection is made. This prevented early mis-clicks that appeared in early tests
Touch targets were enlarged for screens with single actions, reducing missed taps and matching real-world usage.
Improving Buttons
Revised Actions in Hi-fi Pages
Hide Action Overlay
To reflect system status, confirmation buttons remain disabled until a selection is made. This prevented early mis-clicks that appeared in early tests
Touch targets were enlarged for screens with single actions, reducing missed taps and matching real-world usage.
Improving Buttons
Revised Actions in Hi-fi Pages
Hide Action Overlay
To reflect system status, confirmation buttons remain disabled until a selection is made. This prevented early mis-clicks that appeared in early tests
Touch targets were enlarged for screens with single actions, reducing missed taps and matching real-world usage.
Improving Buttons
Revised Actions in Hi-fi Pages
Hide Action Overlay
To reflect system status, confirmation buttons remain disabled until a selection is made. This prevented early mis-clicks that appeared in early tests
Touch targets were enlarged for screens with single actions, reducing missed taps and matching real-world usage.
Finallized Core Principles
Intuitive Design. The interface had to be immediately usable, even for those with minimal process or digital experience.
Intuitive Design. The interface had to be immediately usable, even for those with minimal process or digital experience.
Intuitive Design. The interface had to be immediately usable, even for those with minimal process or digital experience.
Intuitive Design. The interface had to be immediately usable, even for those with minimal process or digital experience.
Error Prevention. Production mistakes are costly. The system needed clear safeguards to help users avoid errors before they happen.
Error Prevention. Production mistakes are costly. The system needed clear safeguards to help users avoid errors before they happen.
Error Prevention. Production mistakes are costly. The system needed clear safeguards to help users avoid errors before they happen.
Error Prevention. Production mistakes are costly. The system needed clear safeguards to help users avoid errors before they happen.
Usability Over Aesthetics. Design choices prioritized clarity over polish. High contrast visuals, large touch areas, and simple flows made the system practical for real-world use.
Usability Over Aesthetics. Design choices prioritized clarity over polish. High contrast visuals, large touch areas, and simple flows made the system practical for real-world use.
Usability Over Aesthetics. Design choices prioritized clarity over polish. High contrast visuals, large touch areas, and simple flows made the system practical for real-world use.
Usability Over Aesthetics. Design choices prioritized clarity over polish. High contrast visuals, large touch areas, and simple flows made the system practical for real-world use.
Work in Progress, by Design
What you’ll see below is an earlier version of this case study. It’s longer, more raw, and hasn’t yet been structured with the same level of refinement as the sections above. But instead of hiding it, I chose to keep it visible.
This is part of the design. Publishing the case study in stages reflects the same process I describe in it. It's a reflection of how I approach UX work as a whole, with a focus on iteration, transparency, and learning through real use and feedback instead of waiting for perfection.
The rest of the story is already here, just told in its original form. If you’d like to keep reading, you can. And if you have feedback, I’d love to hear it. The kind of input that shapes good design often starts with conversations like that.
Work in Progress, by Design
What you’ll see below is an earlier version of this case study. It’s longer, more raw, and hasn’t yet been structured with the same level of refinement as the sections above. But instead of hiding it, I chose to keep it visible.
This is part of the design. Publishing the case study in stages reflects the same process I describe in it. It's a reflection of how I approach UX work as a whole, with a focus on iteration, transparency, and learning through real use and feedback instead of waiting for perfection.
The rest of the story is already here, just told in its original form. If you’d like to keep reading, you can. And if you have feedback, I’d love to hear it. The kind of input that shapes good design often starts with conversations like that.
Work in Progress, by Design
What you’ll see below is an earlier version of this case study. It’s longer, more raw, and hasn’t yet been structured with the same level of refinement as the sections above. But instead of hiding it, I chose to keep it visible.
This is part of the design. Publishing the case study in stages reflects the same process I describe in it. It's a reflection of how I approach UX work as a whole, with a focus on iteration, transparency, and learning through real use and feedback instead of waiting for perfection.
The rest of the story is already here, just told in its original form. If you’d like to keep reading, you can. And if you have feedback, I’d love to hear it. The kind of input that shapes good design often starts with conversations like that.
Work in Progress, by Design
What you’ll see below is an earlier version of this case study. It’s longer, more raw, and hasn’t yet been structured with the same level of refinement as the sections above. But instead of hiding it, I chose to keep it visible.
This is part of the design. Publishing the case study in stages reflects the same process I describe in it. It's a reflection of how I approach UX work as a whole, with a focus on iteration, transparency, and learning through real use and feedback instead of waiting for perfection.
The rest of the story is already here, just told in its original form. If you’d like to keep reading, you can. And if you have feedback, I’d love to hear it. The kind of input that shapes good design often starts with conversations like that.
Step 3: Handover
Finishing Touches
Step 3: Handover
Finishing Touches
Step 3: Handover
Finishing Touches
Step 3: Handover
Finishing Touches
Making It Theirs
By now, the system worked. But for it to feel real, it had to look and behave like something built for Alta, not dropped in from outside.
We introduced Alta's visual identity: typography, brand colours, and standard icons. Placeholders were replaced with real production data. That shift changed how the tool was perceived. It stopped being "the app" and started becoming our app.
Making It Theirs
By now, the system worked. But for it to feel real, it had to look and behave like something built for Alta, not dropped in from outside.
We introduced Alta's visual identity: typography, brand colours, and standard icons. Placeholders were replaced with real production data. That shift changed how the tool was perceived. It stopped being "the app" and started becoming our app.
Making It Theirs
By now, the system worked. But for it to feel real, it had to look and behave like something built for Alta, not dropped in from outside.
We introduced Alta's visual identity: typography, brand colours, and standard icons. Placeholders were replaced with real production data. That shift changed how the tool was perceived. It stopped being "the app" and started becoming our app.
That fading tattoo on the bull’s leg? That’s how identification is done, and this is a relatively clear example.
Making It Theirs
By now, the system worked. But for it to feel real, it had to look and behave like something built for Alta, not dropped in from outside.
We introduced Alta's visual identity: typography, brand colours, and standard icons. Placeholders were replaced with real production data. That shift changed how the tool was perceived. It stopped being "the app" and started becoming our app.
That fading tattoo on the bull’s leg? That’s how identification is done, and this is a relatively clear example.
Built to Be Understood
The real test of any project isn't how well it works during design, it's how well it works after you're gone.
Every decision was captured along the way, not just wireframes or prototypes but explanations, considerations, and trade-offs to prepare for that. We documented testing results, flagged technical constraints, and outlined how the system should evolve if processes change. By the end, the team had everything they needed to keep moving without me: a high-fidelity prototype, an updated service blueprint, development specs, and internal rollout materials.
That clarity paid off. Developers jumped straight into build mode, and there were fewer meetings, fewer questions, and less risk of misalignment.
Built to Be Understood
The real test of any project isn't how well it works during design, it's how well it works after you're gone.
Every decision was captured along the way, not just wireframes or prototypes but explanations, considerations, and trade-offs to prepare for that. We documented testing results, flagged technical constraints, and outlined how the system should evolve if processes change. By the end, the team had everything they needed to keep moving without me: a high-fidelity prototype, an updated service blueprint, development specs, and internal rollout materials.
That clarity paid off. Developers jumped straight into build mode, and there were fewer meetings, fewer questions, and less risk of misalignment.
Built to Be Understood
The real test of any project isn't how well it works during design, it's how well it works after you're gone.
Every decision was captured along the way, not just wireframes or prototypes but explanations, considerations, and trade-offs to prepare for that. We documented testing results, flagged technical constraints, and outlined how the system should evolve if processes change. By the end, the team had everything they needed to keep moving without me: a high-fidelity prototype, an updated service blueprint, development specs, and internal rollout materials.
That clarity paid off. Developers jumped straight into build mode, and there were fewer meetings, fewer questions, and less risk of misalignment.
An example of how notes can get in a rush. Can you tell what it says?
Built to Be Understood
The real test of any project isn't how well it works during design, it's how well it works after you're gone.
Every decision was captured along the way, not just wireframes or prototypes but explanations, considerations, and trade-offs to prepare for that. We documented testing results, flagged technical constraints, and outlined how the system should evolve if processes change. By the end, the team had everything they needed to keep moving without me: a high-fidelity prototype, an updated service blueprint, development specs, and internal rollout materials.
That clarity paid off. Developers jumped straight into build mode, and there were fewer meetings, fewer questions, and less risk of misalignment.
An example of how notes can get in a rush. Can you tell what it says?
Delivery and Impact
The system was received better than anyone expected.
Developers immediately highlighted how much time and guesswork had been saved. Production managers saw value in how the interface matched their workflows and reduced manual input errors. Even skeptical users found themselves navigating the new system without help.
And leadership noticed. The company president called out the project during a leadership meeting, not just for how it looked, but for how it worked. The system prevented costly mistakes, reduced redundant effort, and supported teams that had historically been hard to digitize.
The result? Clear value; felt on the ground and recognized at the top. Hundreds of thousands of dollars were saved, and there is a growing belief in the value that UX could bring. It wouldn't be long before that belief was tested again, only to grow even further.
Delivery and Impact
The system was received better than anyone expected.
Developers immediately highlighted how much time and guesswork had been saved. Production managers saw value in how the interface matched their workflows and reduced manual input errors. Even skeptical users found themselves navigating the new system without help.
And leadership noticed. The company president called out the project during a leadership meeting, not just for how it looked, but for how it worked. The system prevented costly mistakes, reduced redundant effort, and supported teams that had historically been hard to digitize.
The result? Clear value; felt on the ground and recognized at the top. Hundreds of thousands of dollars were saved, and there is a growing belief in the value that UX could bring. It wouldn't be long before that belief was tested again, only to grow even further.
Delivery and Impact
The system was received better than anyone expected.
Developers immediately highlighted how much time and guesswork had been saved. Production managers saw value in how the interface matched their workflows and reduced manual input errors. Even skeptical users found themselves navigating the new system without help.
And leadership noticed. The company president called out the project during a leadership meeting, not just for how it looked, but for how it worked. The system prevented costly mistakes, reduced redundant effort, and supported teams that had historically been hard to digitize.
The result? Clear value; felt on the ground and recognized at the top. Hundreds of thousands of dollars were saved, and there is a growing belief in the value that UX could bring. It wouldn't be long before that belief was tested again, only to grow even further.
Delivery and Impact
The system was received better than anyone expected.
Developers immediately highlighted how much time and guesswork had been saved. Production managers saw value in how the interface matched their workflows and reduced manual input errors. Even skeptical users found themselves navigating the new system without help.
And leadership noticed. The company president called out the project during a leadership meeting, not just for how it looked, but for how it worked. The system prevented costly mistakes, reduced redundant effort, and supported teams that had historically been hard to digitize.
The result? Clear value; felt on the ground and recognized at the top. Hundreds of thousands of dollars were saved, and there is a growing belief in the value that UX could bring. It wouldn't be long before that belief was tested again, only to grow even further.
Reflections
Looking Back
Reflections
Looking Back
Reflections
Looking Back
Reflections
Looking Back
Before: Learning to Prepare
From the start, I knew I would be working independently. This wasn't just a design challenge; it was the company's first time bringing in someone dedicated to UX.
To prepare, I immersed myself in many books like About Face and The User Experience Team of One, studying methods, systems, and communication strategies. The theory gave me structure. But the real learning came from navigating the day-to-day decisions that no book could fully anticipate.
Before: Learning to Prepare
From the start, I knew I would be working independently. This wasn't just a design challenge; it was the company's first time bringing in someone dedicated to UX.
To prepare, I immersed myself in many books like About Face and The User Experience Team of One, studying methods, systems, and communication strategies. The theory gave me structure. But the real learning came from navigating the day-to-day decisions that no book could fully anticipate.
Before: Learning to Prepare
From the start, I knew I would be working independently. This wasn't just a design challenge; it was the company's first time bringing in someone dedicated to UX.
To prepare, I immersed myself in many books like About Face and The User Experience Team of One, studying methods, systems, and communication strategies. The theory gave me structure. But the real learning came from navigating the day-to-day decisions that no book could fully anticipate.
Before: Learning to Prepare
From the start, I knew I would be working independently. This wasn't just a design challenge; it was the company's first time bringing in someone dedicated to UX.
To prepare, I immersed myself in many books like About Face and The User Experience Team of One, studying methods, systems, and communication strategies. The theory gave me structure. But the real learning came from navigating the day-to-day decisions that no book could fully anticipate.
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. Research and design decisions had to be translated for completely different teams. Only by learning to speak everyone's language can alignment be made possible.
Communication is as important as design. Research and design decisions had to be translated for completely different teams. Only by learning to speak everyone's language can alignment be made possible.
Communication is as important as design. Research and design decisions had to be translated for completely different teams. Only by learning to speak everyone's language can alignment be made possible.
Communication is as important as design. Research and design decisions had to be translated for completely different teams. Only by learning to speak everyone's language can alignment be made possible.
The real world rewrites the rules. What makes sense on a whiteboard doesn't always survive the production floor. Testing in context is vital to finding blind spots and forcing more appropriate solutions.
The real world rewrites the rules. What makes sense on a whiteboard doesn't always survive the production floor. Testing in context is vital to finding blind spots and forcing more appropriate solutions.
The real world rewrites the rules. What makes sense on a whiteboard doesn't always survive the production floor. Testing in context is vital to finding blind spots and forcing more appropriate solutions.
The real world rewrites the rules. What makes sense on a whiteboard doesn't always survive the production floor. Testing in context is vital to finding blind spots and forcing more appropriate solutions.
Iteration drove progress. Each round of feedback improved clarity, usability, and focus. Letting the work evolve made the final result stronger than anything I could have planned from the start.
Iteration drove progress. Each round of feedback improved clarity, usability, and focus. Letting the work evolve made the final result stronger than anything I could have planned from the start.
Iteration drove progress. Each round of feedback improved clarity, usability, and focus. Letting the work evolve made the final result stronger than anything I could have planned from the start.
Iteration drove progress. Each round of feedback improved clarity, usability, and focus. Letting the work evolve made the final result stronger than anything I could have planned from the start.
After: Learning from the Handoff
When the final designs were handed off and development began, I expected the prototypes and screens to do the heavy lifting. Documentation felt important, but secondary, just a support layer for the real work.
That changed quickly. As developers moved forward, I saw how much clarity those documents provided. Questions were answered before they were asked, and dependencies were clear. Progress moved faster because the thinking was laid out, step by step.
That experience reshaped how I see documentation. It's not just a support layer; it's the structure that holds everything up. Since then, I've made it a core part of my process, knowing that good design is only as strong as its ability to be understood.
After: Learning from the Handoff
When the final designs were handed off and development began, I expected the prototypes and screens to do the heavy lifting. Documentation felt important, but secondary, just a support layer for the real work.
That changed quickly. As developers moved forward, I saw how much clarity those documents provided. Questions were answered before they were asked, and dependencies were clear. Progress moved faster because the thinking was laid out, step by step.
That experience reshaped how I see documentation. It's not just a support layer; it's the structure that holds everything up. Since then, I've made it a core part of my process, knowing that good design is only as strong as its ability to be understood.
After: Learning from the Handoff
When the final designs were handed off and development began, I expected the prototypes and screens to do the heavy lifting. Documentation felt important, but secondary, just a support layer for the real work.
That changed quickly. As developers moved forward, I saw how much clarity those documents provided. Questions were answered before they were asked, and dependencies were clear. Progress moved faster because the thinking was laid out, step by step.
That experience reshaped how I see documentation. It's not just a support layer; it's the structure that holds everything up. Since then, I've made it a core part of my process, knowing that good design is only as strong as its ability to be understood.
After: Learning from the Handoff
When the final designs were handed off and development began, I expected the prototypes and screens to do the heavy lifting. Documentation felt important, but secondary, just a support layer for the real work.
That changed quickly. As developers moved forward, I saw how much clarity those documents provided. Questions were answered before they were asked, and dependencies were clear. Progress moved faster because the thinking was laid out, step by step.
That experience reshaped how I see documentation. It's not just a support layer; it's the structure that holds everything up. Since then, I've made it a core part of my process, knowing that good design is only as strong as its ability to be understood.