Project Context
Atoz Services SA is a Luxembourg-based tax and finance firm with 50–200 employees. Their internal intranet—built in 2010—was the operational backbone of the company. Teams relied on it for everything from audits and tax reviews to employee directories and job assignment tracking.
But over time, the platform became a bottleneck. The interface was outdated, the workflows were inefficient, and users only logged in because they had to—not because it helped them do better work.
This wasn’t just a UI problem. It was a company-wide productivity issue.
My Role
I was brought in as the lead (and sole) product designer to drive the full redesign.
This was not a superficial UI refresh—it was a ground-up rework of how the intranet functioned, looked, and supported daily operations.
I took full ownership of the product design lifecycle:
Ran discovery through UX audits and stakeholder interviews
Rebuilt the information architecture from scratch
Designed every screen and interaction pattern
Collaborated daily with frontend and backend developers
Managed stakeholder expectations and negotiated priorities
Delivered a full production-ready handoff, on time
The Challenge
The old intranet system posed several critical problems:
Clunky, outdated UI
The interface hadn’t been updated in over a decade. It wasted screen space, lacked hierarchy, and created friction across every interaction.Inefficient workflows
Users had to jump through multiple screens to complete even the most basic tasks, like assigning a job or reviewing a tax case.Poor information architecture
Navigation was unintuitive, terminology was inconsistent, and important tools were buried in illogical places.No personalization or flexibility
Different roles (auditors, tax advisors, team leads) had no tailored views or access to high-priority actions.Low engagement and trust
The general sentiment? “The tool slows me down.” People avoided it whenever possible.
The Challenge
The old intranet system posed several critical problems:
Clunky, outdated UI
The interface hadn’t been updated in over a decade. It wasted screen space, lacked hierarchy, and created friction across every interaction.Inefficient workflows
Users had to jump through multiple screens to complete even the most basic tasks, like assigning a job or reviewing a tax case.Poor information architecture
Navigation was unintuitive, terminology was inconsistent, and important tools were buried in illogical places.No personalization or flexibility
Different roles (auditors, tax advisors, team leads) had no tailored views or access to high-priority actions.Low engagement and trust
The general sentiment? “The tool slows me down.” People avoided it whenever possible.
The Challenge
The old intranet system posed several critical problems:
Clunky, outdated UI
The interface hadn’t been updated in over a decade. It wasted screen space, lacked hierarchy, and created friction across every interaction.Inefficient workflows
Users had to jump through multiple screens to complete even the most basic tasks, like assigning a job or reviewing a tax case.Poor information architecture
Navigation was unintuitive, terminology was inconsistent, and important tools were buried in illogical places.No personalization or flexibility
Different roles (auditors, tax advisors, team leads) had no tailored views or access to high-priority actions.Low engagement and trust
The general sentiment? “The tool slows me down.” People avoided it whenever possible.
Research & Discovery
Redesigning the Atoz intranet wasn’t just about improving the look and feel—it was about understanding the deep-rooted problems that made the system frustrating to use, despite being mission-critical. I approached discovery with a layered research plan, combining UX heuristics, stakeholder alignment, and real user empathy.
UX Audit: Understanding the Legacy System
I began with a full UX and UI audit of the existing intranet. The system was originally developed in 2010 and hadn’t been significantly updated since. Key findings included:
Wasted space: The layout was narrow and didn’t utilize full screen width, making dense content harder to read.
Inconsistent patterns: Button styles, field groupings, and modal behaviors varied wildly across modules.
Cluttered screens: Information was presented without hierarchy, making it difficult to scan or prioritize.
Redundant workflows: Common actions like assigning jobs or submitting audit notes required too many steps.
These insights became the baseline for performance and usability benchmarks.
User Interviews: Hearing the Frustration Firsthand
To ground my assumptions, I conducted interviews with over a dozen users across departments—auditors, managers, tax advisors, and administrative support.
Auditors wanted to quickly track assignment status and update files without jumping across modules.
Team leads needed visibility on job progress, dependencies, and internal communication.
Support staff were overwhelmed by repetitive tasks and hard-to-find data.
Role | Pain Points | Key Needs |
|---|---|---|
Auditor | Too many clicks for task updates | Inline editing, status filters |
Team Lead | Lack of overview, poor task tracking | Dashboard, bulk actions |
Tax Advisor | Cluttered layout, irrelevant data | Personalized views |
I also ran informal contextual inquiries—watching how users actually worked inside the tool versus how they described it.
“I’ve built my own folder system on my desktop just so I don’t have to touch the intranet more than I need to.”
— Tax team assistant
“Everything takes too long. Assigning a job should be two clicks, not six.”
— Senior auditor
Synthesis: Friction Everywhere
From research, a few clear pain themes surfaced:
Avoidance Behavior
Users were actively building workarounds—Excel trackers, direct messaging, shadow tools—just to bypass core features.Information Chaos
There was no clear labeling system. Pages had 10+ modules jammed together without logical grouping or priority.Workflow Inefficiencies
Key tasks like creating job assignments, tracking tax reviews, or updating audit statuses required navigating through too many unrelated screens.One-Size-Fits-None
The intranet lacked any role-based customization. Whether you were an entry-level assistant or a manager, you saw the same bloated dashboard.No Trust in the System
Frequent bugs, poor feedback loops, and visual inconsistency made users second-guess every action they took.
Key Goals I Set
I consolidated all feedback into five actionable redesign pillars:
Restructure the information architecture
Flatten the navigation and make core features accessible in 1–2 clicks.Streamline Priority Flows
Design faster, smarter workflows for job assignment, audit management, and internal search.Role-Based Dashboards
Surface relevant data and actions based on user type, cutting down on information noise.Modern UI with Real Hierarchy
Introduce modular layouts, clear typography, and consistent visual components.Rebuild Confidence
Ensure every interaction feels intentional, fast, and reliable—restoring user trust in the tool.
This phase wasn’t just about collecting feedback—it was about distilling chaos into clarity. It gave me the insight and strategic direction I needed to reimagine the intranet not as a tool users tolerated—but one they trusted and relied on.
Research & Discovery
Redesigning the Atoz intranet wasn’t just about improving the look and feel—it was about understanding the deep-rooted problems that made the system frustrating to use, despite being mission-critical. I approached discovery with a layered research plan, combining UX heuristics, stakeholder alignment, and real user empathy.
UX Audit: Understanding the Legacy System
I began with a full UX and UI audit of the existing intranet. The system was originally developed in 2010 and hadn’t been significantly updated since. Key findings included:
Wasted space: The layout was narrow and didn’t utilize full screen width, making dense content harder to read.
Inconsistent patterns: Button styles, field groupings, and modal behaviors varied wildly across modules.
Cluttered screens: Information was presented without hierarchy, making it difficult to scan or prioritize.
Redundant workflows: Common actions like assigning jobs or submitting audit notes required too many steps.
These insights became the baseline for performance and usability benchmarks.
User Interviews: Hearing the Frustration Firsthand
To ground my assumptions, I conducted interviews with over a dozen users across departments—auditors, managers, tax advisors, and administrative support.
Auditors wanted to quickly track assignment status and update files without jumping across modules.
Team leads needed visibility on job progress, dependencies, and internal communication.
Support staff were overwhelmed by repetitive tasks and hard-to-find data.
Role | Pain Points | Key Needs |
|---|---|---|
Auditor | Too many clicks for task updates | Inline editing, status filters |
Team Lead | Lack of overview, poor task tracking | Dashboard, bulk actions |
Tax Advisor | Cluttered layout, irrelevant data | Personalized views |
I also ran informal contextual inquiries—watching how users actually worked inside the tool versus how they described it.
“I’ve built my own folder system on my desktop just so I don’t have to touch the intranet more than I need to.”
— Tax team assistant
“Everything takes too long. Assigning a job should be two clicks, not six.”
— Senior auditor
Synthesis: Friction Everywhere
From research, a few clear pain themes surfaced:
Avoidance Behavior
Users were actively building workarounds—Excel trackers, direct messaging, shadow tools—just to bypass core features.Information Chaos
There was no clear labeling system. Pages had 10+ modules jammed together without logical grouping or priority.Workflow Inefficiencies
Key tasks like creating job assignments, tracking tax reviews, or updating audit statuses required navigating through too many unrelated screens.One-Size-Fits-None
The intranet lacked any role-based customization. Whether you were an entry-level assistant or a manager, you saw the same bloated dashboard.No Trust in the System
Frequent bugs, poor feedback loops, and visual inconsistency made users second-guess every action they took.
Key Goals I Set
I consolidated all feedback into five actionable redesign pillars:
Restructure the information architecture
Flatten the navigation and make core features accessible in 1–2 clicks.Streamline Priority Flows
Design faster, smarter workflows for job assignment, audit management, and internal search.Role-Based Dashboards
Surface relevant data and actions based on user type, cutting down on information noise.Modern UI with Real Hierarchy
Introduce modular layouts, clear typography, and consistent visual components.Rebuild Confidence
Ensure every interaction feels intentional, fast, and reliable—restoring user trust in the tool.
This phase wasn’t just about collecting feedback—it was about distilling chaos into clarity. It gave me the insight and strategic direction I needed to reimagine the intranet not as a tool users tolerated—but one they trusted and relied on.
Research & Discovery
Redesigning the Atoz intranet wasn’t just about improving the look and feel—it was about understanding the deep-rooted problems that made the system frustrating to use, despite being mission-critical. I approached discovery with a layered research plan, combining UX heuristics, stakeholder alignment, and real user empathy.
UX Audit: Understanding the Legacy System
I began with a full UX and UI audit of the existing intranet. The system was originally developed in 2010 and hadn’t been significantly updated since. Key findings included:
Wasted space: The layout was narrow and didn’t utilize full screen width, making dense content harder to read.
Inconsistent patterns: Button styles, field groupings, and modal behaviors varied wildly across modules.
Cluttered screens: Information was presented without hierarchy, making it difficult to scan or prioritize.
Redundant workflows: Common actions like assigning jobs or submitting audit notes required too many steps.
These insights became the baseline for performance and usability benchmarks.
User Interviews: Hearing the Frustration Firsthand
To ground my assumptions, I conducted interviews with over a dozen users across departments—auditors, managers, tax advisors, and administrative support.
Auditors wanted to quickly track assignment status and update files without jumping across modules.
Team leads needed visibility on job progress, dependencies, and internal communication.
Support staff were overwhelmed by repetitive tasks and hard-to-find data.
Role | Pain Points | Key Needs |
|---|---|---|
Auditor | Too many clicks for task updates | Inline editing, status filters |
Team Lead | Lack of overview, poor task tracking | Dashboard, bulk actions |
Tax Advisor | Cluttered layout, irrelevant data | Personalized views |
I also ran informal contextual inquiries—watching how users actually worked inside the tool versus how they described it.
“I’ve built my own folder system on my desktop just so I don’t have to touch the intranet more than I need to.”
— Tax team assistant
“Everything takes too long. Assigning a job should be two clicks, not six.”
— Senior auditor
Synthesis: Friction Everywhere
From research, a few clear pain themes surfaced:
Avoidance Behavior
Users were actively building workarounds—Excel trackers, direct messaging, shadow tools—just to bypass core features.Information Chaos
There was no clear labeling system. Pages had 10+ modules jammed together without logical grouping or priority.Workflow Inefficiencies
Key tasks like creating job assignments, tracking tax reviews, or updating audit statuses required navigating through too many unrelated screens.One-Size-Fits-None
The intranet lacked any role-based customization. Whether you were an entry-level assistant or a manager, you saw the same bloated dashboard.No Trust in the System
Frequent bugs, poor feedback loops, and visual inconsistency made users second-guess every action they took.
Key Goals I Set
I consolidated all feedback into five actionable redesign pillars:
Restructure the information architecture
Flatten the navigation and make core features accessible in 1–2 clicks.Streamline Priority Flows
Design faster, smarter workflows for job assignment, audit management, and internal search.Role-Based Dashboards
Surface relevant data and actions based on user type, cutting down on information noise.Modern UI with Real Hierarchy
Introduce modular layouts, clear typography, and consistent visual components.Rebuild Confidence
Ensure every interaction feels intentional, fast, and reliable—restoring user trust in the tool.
This phase wasn’t just about collecting feedback—it was about distilling chaos into clarity. It gave me the insight and strategic direction I needed to reimagine the intranet not as a tool users tolerated—but one they trusted and relied on.
Design Strategy & Key Decisions
Armed with a clear understanding of the pain points, I began translating insights into a tangible design strategy—one that prioritized clarity, speed, and relevance for every user across the organization. This wasn’t about adding features—it was about removing friction and restoring flow.
1. Information Architecture Overhaul
The existing IA was outdated and overly nested. I led a complete restructuring to create a flatter, more intuitive system.
Navigation Simplified: Reduced main navigation from 10+ items to 5 core categories, based on task frequency and mental models.
Smart Grouping: Related features were bundled logically (e.g., “Jobs,” “Audits,” and “Reviews” were unified under a single “Tasks” module).
User-validated structure: Tree tests and card sorting ensured users could find what they needed with fewer clicks.
2. Modular, Role-Based Dashboards
One of the biggest user complaints was seeing irrelevant data. I addressed this with personalized, modular dashboards.
Custom views: Auditors saw open cases and recent assignments; managers got progress metrics and team activity at a glance.
Widget system: Designed dashboard widgets that users could rearrange based on role and preference.
Quick actions: High-frequency tasks like “Assign Job” or “Update Audit” were surfaced immediately.
3. Full-Width, Responsive Layout
The original app used less than 60% of the screen on desktop. I redesigned the layout to be fully responsive and take advantage of modern screen sizes.
Improved scanability: Full-width content areas meant less vertical scrolling and more efficient data viewing.
Consistent grids: Introduced a flexible 12-column grid for layout consistency and future scalability.
Better readability: Upgraded typography, whitespace, and alignment for cognitive ease and scan speed.
4. Contextual, Streamlined Interactions
I reworked key flows to minimize context switching and reduce the number of steps required for daily tasks.
Inline actions: Users could assign jobs or update statuses directly from list views, without navigating away.
Progressive disclosure: Forms and filters expanded as needed, keeping screens clean by default.
Bulk actions: Enabled power users to manage large workloads more efficiently.
5. Strategic Stakeholder Alignment
Not everyone wanted change. Some stakeholders pushed to retain old modules out of habit or fear of disrupting workflows. I made it a priority to bring them into the process.
Facilitated workshops: I ran targeted sessions to surface real needs behind feature requests.
Prioritized impact: I built a scoring matrix to show which changes had the highest value-to-effort ratio.
Negotiated smart trade-offs: One key win was convincing the PM to sunset a rarely used reporting module in favor of investing in streamlined job delegation—which ended up becoming one of the most-used features post-launch.
6. Close Dev Collaboration
Working alongside frontend and backend developers, I ensured designs respected technical constraints without compromising experience.
Design/dev syncs: Joined daily stand-ups to provide implementation clarity and flag issues early.
Prototyping in Figma: Built interactive prototypes to hand off responsive behaviors, transitions, and edge cases.
Support during QA: Reviewed staging builds and gave targeted feedback to avoid UI regressions before deployment.
This design strategy was not just about polishing the surface. It was a systemic rethink of how the intranet served its people—built with business outcomes, technical feasibility, and user value in mind.
Next up: Outcomes & Impact—we’ll walk through the measurable results, adoption success, and how the redesign changed the way people worked. Ready to move forward?
Design Strategy & Key Decisions
Armed with a clear understanding of the pain points, I began translating insights into a tangible design strategy—one that prioritized clarity, speed, and relevance for every user across the organization. This wasn’t about adding features—it was about removing friction and restoring flow.
1. Information Architecture Overhaul
The existing IA was outdated and overly nested. I led a complete restructuring to create a flatter, more intuitive system.
Navigation Simplified: Reduced main navigation from 10+ items to 5 core categories, based on task frequency and mental models.
Smart Grouping: Related features were bundled logically (e.g., “Jobs,” “Audits,” and “Reviews” were unified under a single “Tasks” module).
User-validated structure: Tree tests and card sorting ensured users could find what they needed with fewer clicks.
2. Modular, Role-Based Dashboards
One of the biggest user complaints was seeing irrelevant data. I addressed this with personalized, modular dashboards.
Custom views: Auditors saw open cases and recent assignments; managers got progress metrics and team activity at a glance.
Widget system: Designed dashboard widgets that users could rearrange based on role and preference.
Quick actions: High-frequency tasks like “Assign Job” or “Update Audit” were surfaced immediately.
3. Full-Width, Responsive Layout
The original app used less than 60% of the screen on desktop. I redesigned the layout to be fully responsive and take advantage of modern screen sizes.
Improved scanability: Full-width content areas meant less vertical scrolling and more efficient data viewing.
Consistent grids: Introduced a flexible 12-column grid for layout consistency and future scalability.
Better readability: Upgraded typography, whitespace, and alignment for cognitive ease and scan speed.
4. Contextual, Streamlined Interactions
I reworked key flows to minimize context switching and reduce the number of steps required for daily tasks.
Inline actions: Users could assign jobs or update statuses directly from list views, without navigating away.
Progressive disclosure: Forms and filters expanded as needed, keeping screens clean by default.
Bulk actions: Enabled power users to manage large workloads more efficiently.
5. Strategic Stakeholder Alignment
Not everyone wanted change. Some stakeholders pushed to retain old modules out of habit or fear of disrupting workflows. I made it a priority to bring them into the process.
Facilitated workshops: I ran targeted sessions to surface real needs behind feature requests.
Prioritized impact: I built a scoring matrix to show which changes had the highest value-to-effort ratio.
Negotiated smart trade-offs: One key win was convincing the PM to sunset a rarely used reporting module in favor of investing in streamlined job delegation—which ended up becoming one of the most-used features post-launch.
6. Close Dev Collaboration
Working alongside frontend and backend developers, I ensured designs respected technical constraints without compromising experience.
Design/dev syncs: Joined daily stand-ups to provide implementation clarity and flag issues early.
Prototyping in Figma: Built interactive prototypes to hand off responsive behaviors, transitions, and edge cases.
Support during QA: Reviewed staging builds and gave targeted feedback to avoid UI regressions before deployment.
This design strategy was not just about polishing the surface. It was a systemic rethink of how the intranet served its people—built with business outcomes, technical feasibility, and user value in mind.
Next up: Outcomes & Impact—we’ll walk through the measurable results, adoption success, and how the redesign changed the way people worked. Ready to move forward?
Design Strategy & Key Decisions
Armed with a clear understanding of the pain points, I began translating insights into a tangible design strategy—one that prioritized clarity, speed, and relevance for every user across the organization. This wasn’t about adding features—it was about removing friction and restoring flow.
1. Information Architecture Overhaul
The existing IA was outdated and overly nested. I led a complete restructuring to create a flatter, more intuitive system.
Navigation Simplified: Reduced main navigation from 10+ items to 5 core categories, based on task frequency and mental models.
Smart Grouping: Related features were bundled logically (e.g., “Jobs,” “Audits,” and “Reviews” were unified under a single “Tasks” module).
User-validated structure: Tree tests and card sorting ensured users could find what they needed with fewer clicks.
2. Modular, Role-Based Dashboards
One of the biggest user complaints was seeing irrelevant data. I addressed this with personalized, modular dashboards.
Custom views: Auditors saw open cases and recent assignments; managers got progress metrics and team activity at a glance.
Widget system: Designed dashboard widgets that users could rearrange based on role and preference.
Quick actions: High-frequency tasks like “Assign Job” or “Update Audit” were surfaced immediately.
3. Full-Width, Responsive Layout
The original app used less than 60% of the screen on desktop. I redesigned the layout to be fully responsive and take advantage of modern screen sizes.
Improved scanability: Full-width content areas meant less vertical scrolling and more efficient data viewing.
Consistent grids: Introduced a flexible 12-column grid for layout consistency and future scalability.
Better readability: Upgraded typography, whitespace, and alignment for cognitive ease and scan speed.
4. Contextual, Streamlined Interactions
I reworked key flows to minimize context switching and reduce the number of steps required for daily tasks.
Inline actions: Users could assign jobs or update statuses directly from list views, without navigating away.
Progressive disclosure: Forms and filters expanded as needed, keeping screens clean by default.
Bulk actions: Enabled power users to manage large workloads more efficiently.
5. Strategic Stakeholder Alignment
Not everyone wanted change. Some stakeholders pushed to retain old modules out of habit or fear of disrupting workflows. I made it a priority to bring them into the process.
Facilitated workshops: I ran targeted sessions to surface real needs behind feature requests.
Prioritized impact: I built a scoring matrix to show which changes had the highest value-to-effort ratio.
Negotiated smart trade-offs: One key win was convincing the PM to sunset a rarely used reporting module in favor of investing in streamlined job delegation—which ended up becoming one of the most-used features post-launch.
6. Close Dev Collaboration
Working alongside frontend and backend developers, I ensured designs respected technical constraints without compromising experience.
Design/dev syncs: Joined daily stand-ups to provide implementation clarity and flag issues early.
Prototyping in Figma: Built interactive prototypes to hand off responsive behaviors, transitions, and edge cases.
Support during QA: Reviewed staging builds and gave targeted feedback to avoid UI regressions before deployment.
This design strategy was not just about polishing the surface. It was a systemic rethink of how the intranet served its people—built with business outcomes, technical feasibility, and user value in mind.
Next up: Outcomes & Impact—we’ll walk through the measurable results, adoption success, and how the redesign changed the way people worked. Ready to move forward?
Outcomes & Impact
The redesigned intranet didn’t just improve usability—it reshaped how teams at Atoz worked. By aligning user needs with business goals and navigating tight constraints, the project delivered tangible, company-wide improvements.
Measurable results
Task completion time was reduced by 30–40%
Streamlined workflows and contextual quick actions significantly sped up common tasks like assigning jobs and updating audit statuses.Support tickets dropped by approximately 50% in the first quarter
Many past tickets stemmed from confusion, inconsistent labeling, or clunky interactions. The redesign resolved most of these friction points.User engagement increased by 20%
Teams began voluntarily using the platform more, centralizing daily operations that previously lived in email, Slack, or spreadsheets.Feature adoption improved
Tools like the role-based dashboard and inline task management were quickly embraced—especially by team leads who previously avoided the platform.
User and stakeholder feedback
“I finally feel like the app works with me, not against me.”
— Team Lead, Audit Department
“Everything I need is right there on the dashboard now. No more jumping through screens.”
— Internal user
“This is the first time I’ve seen our intranet look like a product I actually want to use.”
— PMO stakeholder
Organizational shift
This redesign did more than modernize the interface—it reset expectations. The new intranet became a trusted platform, not a workaround to avoid. It also set a new UX standard inside the company, influencing how future internal tools would be evaluated and built.
Despite legacy limitations and a tight timeline, the project delivered real business value. It demonstrated how user-centered design can directly improve operations, adoption, and overall confidence in internal tools.
Outcomes & Impact
The redesigned intranet didn’t just improve usability—it reshaped how teams at Atoz worked. By aligning user needs with business goals and navigating tight constraints, the project delivered tangible, company-wide improvements.
Measurable results
Task completion time was reduced by 30–40%
Streamlined workflows and contextual quick actions significantly sped up common tasks like assigning jobs and updating audit statuses.Support tickets dropped by approximately 50% in the first quarter
Many past tickets stemmed from confusion, inconsistent labeling, or clunky interactions. The redesign resolved most of these friction points.User engagement increased by 20%
Teams began voluntarily using the platform more, centralizing daily operations that previously lived in email, Slack, or spreadsheets.Feature adoption improved
Tools like the role-based dashboard and inline task management were quickly embraced—especially by team leads who previously avoided the platform.
User and stakeholder feedback
“I finally feel like the app works with me, not against me.”
— Team Lead, Audit Department
“Everything I need is right there on the dashboard now. No more jumping through screens.”
— Internal user
“This is the first time I’ve seen our intranet look like a product I actually want to use.”
— PMO stakeholder
Organizational shift
This redesign did more than modernize the interface—it reset expectations. The new intranet became a trusted platform, not a workaround to avoid. It also set a new UX standard inside the company, influencing how future internal tools would be evaluated and built.
Despite legacy limitations and a tight timeline, the project delivered real business value. It demonstrated how user-centered design can directly improve operations, adoption, and overall confidence in internal tools.
Outcomes & Impact
The redesigned intranet didn’t just improve usability—it reshaped how teams at Atoz worked. By aligning user needs with business goals and navigating tight constraints, the project delivered tangible, company-wide improvements.
Measurable results
Task completion time was reduced by 30–40%
Streamlined workflows and contextual quick actions significantly sped up common tasks like assigning jobs and updating audit statuses.Support tickets dropped by approximately 50% in the first quarter
Many past tickets stemmed from confusion, inconsistent labeling, or clunky interactions. The redesign resolved most of these friction points.User engagement increased by 20%
Teams began voluntarily using the platform more, centralizing daily operations that previously lived in email, Slack, or spreadsheets.Feature adoption improved
Tools like the role-based dashboard and inline task management were quickly embraced—especially by team leads who previously avoided the platform.
User and stakeholder feedback
“I finally feel like the app works with me, not against me.”
— Team Lead, Audit Department
“Everything I need is right there on the dashboard now. No more jumping through screens.”
— Internal user
“This is the first time I’ve seen our intranet look like a product I actually want to use.”
— PMO stakeholder
Organizational shift
This redesign did more than modernize the interface—it reset expectations. The new intranet became a trusted platform, not a workaround to avoid. It also set a new UX standard inside the company, influencing how future internal tools would be evaluated and built.
Despite legacy limitations and a tight timeline, the project delivered real business value. It demonstrated how user-centered design can directly improve operations, adoption, and overall confidence in internal tools.
Reflection & Lessons Learned
This project was a reminder that internal tools matter just as much—if not more—than customer-facing ones. When employees struggle with the systems meant to support their work, it creates silent but costly friction across the entire organization.
Taking full ownership of the redesign—from research and IA to UI and stakeholder alignment—pushed me to think not just like a designer, but like a strategist and operator. I had to balance ideal UX with real-world constraints: legacy tech, internal politics, and a tight delivery window.
A few key lessons stood out:
Prioritize measurable baselines early
Having no benchmarks at the start made it harder to quantify certain wins. Going forward, I now push to establish SUS scores, task timing, and usage data before touching design.Bring stakeholders into the process, not just the outcomes
The turning point in the project wasn’t a screen—it was a conversation. Running alignment workshops and framing design trade-offs in terms of business value helped shift decision-making.Design for roles, not one-size-fits-all
Personalization at the dashboard level drove engagement across teams. Understanding each role’s unique context early on was key to building relevant, efficient experiences.Ship fast, but not blindly
The compressed 3-month window forced smart prioritization. I focused on solving the right problems well, rather than trying to solve everything at once.
This redesign wasn’t just a UX win—it was a turning point for how Atoz approached internal systems. And for me, it was a sharp reminder that great design isn't about pixels. It’s about making people’s work easier, faster, and more rewarding.
Reflection & Lessons Learned
This project was a reminder that internal tools matter just as much—if not more—than customer-facing ones. When employees struggle with the systems meant to support their work, it creates silent but costly friction across the entire organization.
Taking full ownership of the redesign—from research and IA to UI and stakeholder alignment—pushed me to think not just like a designer, but like a strategist and operator. I had to balance ideal UX with real-world constraints: legacy tech, internal politics, and a tight delivery window.
A few key lessons stood out:
Prioritize measurable baselines early
Having no benchmarks at the start made it harder to quantify certain wins. Going forward, I now push to establish SUS scores, task timing, and usage data before touching design.Bring stakeholders into the process, not just the outcomes
The turning point in the project wasn’t a screen—it was a conversation. Running alignment workshops and framing design trade-offs in terms of business value helped shift decision-making.Design for roles, not one-size-fits-all
Personalization at the dashboard level drove engagement across teams. Understanding each role’s unique context early on was key to building relevant, efficient experiences.Ship fast, but not blindly
The compressed 3-month window forced smart prioritization. I focused on solving the right problems well, rather than trying to solve everything at once.
This redesign wasn’t just a UX win—it was a turning point for how Atoz approached internal systems. And for me, it was a sharp reminder that great design isn't about pixels. It’s about making people’s work easier, faster, and more rewarding.
Reflection & Lessons Learned
This project was a reminder that internal tools matter just as much—if not more—than customer-facing ones. When employees struggle with the systems meant to support their work, it creates silent but costly friction across the entire organization.
Taking full ownership of the redesign—from research and IA to UI and stakeholder alignment—pushed me to think not just like a designer, but like a strategist and operator. I had to balance ideal UX with real-world constraints: legacy tech, internal politics, and a tight delivery window.
A few key lessons stood out:
Prioritize measurable baselines early
Having no benchmarks at the start made it harder to quantify certain wins. Going forward, I now push to establish SUS scores, task timing, and usage data before touching design.Bring stakeholders into the process, not just the outcomes
The turning point in the project wasn’t a screen—it was a conversation. Running alignment workshops and framing design trade-offs in terms of business value helped shift decision-making.Design for roles, not one-size-fits-all
Personalization at the dashboard level drove engagement across teams. Understanding each role’s unique context early on was key to building relevant, efficient experiences.Ship fast, but not blindly
The compressed 3-month window forced smart prioritization. I focused on solving the right problems well, rather than trying to solve everything at once.
This redesign wasn’t just a UX win—it was a turning point for how Atoz approached internal systems. And for me, it was a sharp reminder that great design isn't about pixels. It’s about making people’s work easier, faster, and more rewarding.
Other projects
Get in touch with me :)
If you’re building something meaningful and need clarity, or just want to chat, feel free to send me a message and I'll get back to you asap :)
Get in touch with me :)
If you’re building something meaningful and need clarity, or just want to chat, feel free to send me a message and I'll get back to you asap :)