Role
UI/UX Designer
Role
UI/UX Designer
Timeline
July 2025
Timeline
July 2025
Tools
Sketch
Tools
Sketch
Improving Token Management with Saved Filter
Improving Token Management with Saved Filter
Turning a simple filter request into a reusable workflow.
Turning a simple filter request into a reusable workflow.
BACKGROUND
BACKGROUND
The Token Management Portal is an internal tool used by administrators to generate and manage tokens for TV installations.
The Token Management Portal is an internal tool used by administrators to generate and manage tokens for TV installations.
As the number of tokens grew, administrators needed a faster way to locate specific token records.
As the number of tokens grew, administrators needed a faster way to locate specific token records.
The initial request was straightforward: add filtering options above the token table.
The initial request was straightforward: add filtering options above the token table.
However, after discussing the workflow with stakeholders, it became clear that filtering was not an occasional task. Administrators frequently applied the same filter combinations repeatedly throughout their daily work.
However, after discussing the workflow with stakeholders, it became clear that filtering was not an occasional task. Administrators frequently applied the same filter combinations repeatedly throughout their daily work.
My role was to design a solution that improved this workflow while keeping the filtering experience simple and familiar.
My role was to design a solution that improved this workflow while keeping the filtering experience simple and familiar.
CHALLANGES
CHALLANGES
The request appeared simple on the surface, but the underlying workflow presented a different challenge.
The request appeared simple on the surface, but the underlying workflow presented a different challenge.
1
Understanding whether users needed a filtering feature or a faster way to repeat filtering tasks.
1
Understanding whether users needed a filtering feature or a faster way to repeat filtering tasks.
2
Reducing repetitive filter configuration for frequently used searches.
2
Reducing repetitive filter configuration for frequently used searches.
3
Designing a solution that worked for both one-time filtering and recurring workflows.
3
Designing a solution that worked for both one-time filtering and recurring workflows.
Through discussions with stakeholders, I found that the real problem was not filtering itself, but the repeated effort required to recreate the same filter criteria multiple times a day.
Through discussions with stakeholders, I found that the real problem was not filtering itself, but the repeated effort required to recreate the same filter criteria multiple times a day.
LIMITATIONS
LIMITATIONS
The design needed to work within several constraints:
The design needed to work within several constraints:
The solution had to fit within the existing token management workflow.
The solution had to fit within the existing token management workflow.
Filtering behavior needed to remain familiar to existing users.
Filtering behavior needed to remain familiar to existing users.
The feature needed to support both occasional and frequent filtering use cases.
The feature needed to support both occasional and frequent filtering use cases.
Development effort needed to remain reasonable despite the expanded scope.
Development effort needed to remain reasonable despite the expanded scope.
KEY DECISIONS
KEY DECISIONS
Token Management Table and Preview Box
Challenged the initial solution request
The original request was to add a filter feature above the token table. Before jumping into the solution, I discussed the workflow with the Product Manager to better understand the context behind the request.
While direct user access was not available, these conversations revealed that administrators frequently reused the same filter combinations. This reframed the problem from "adding filters" to "reducing repetitive filtering work."
Token Management Table and Preview Box
Challenged the initial solution request
The original request was to add a filter feature above the token table. Before jumping into the solution, I discussed the workflow with the Product Manager to better understand the context behind the request.
While direct user access was not available, these conversations revealed that administrators frequently reused the same filter combinations. This reframed the problem from "adding filters" to "reducing repetitive filtering work."
Save Filter Flow
Introduced Saved Filters
Instead of requiring administrators to recreate the same filter combinations repeatedly, I proposed a Saved Filter feature. Users could save commonly used filter configurations and reuse them whenever needed, while still retaining the flexibility to perform one-time filtering when necessary. This approach improved efficiency without changing the familiar filtering experience.
Save Filter Flow
Introduced Saved Filters
Instead of requiring administrators to recreate the same filter combinations repeatedly, I proposed a Saved Filter feature. Users could save commonly used filter configurations and reuse them whenever needed, while still retaining the flexibility to perform one-time filtering when necessary. This approach improved efficiency without changing the familiar filtering experience.
COMPROMISES
COMPROMISES
Several trade-offs were considered during the design process.
Several trade-offs were considered during the design process.
Simpler implementation
Simpler implementation
VS
VS
Better long-term workflow support
Better long-term workflow support
A standard filter would have fulfilled the original request with less effort, but would not address the repetitive nature of the task.
A standard filter would have fulfilled the original request with less effort, but would not address the repetitive nature of the task.
One-time eficiency
One-time eficiency
VS
VS
Reusable workflow improvement
Reusable workflow improvement
The solution focused on reducing repeated work over time rather than optimizing a single filtering action.
The solution focused on reducing repeated work over time rather than optimizing a single filtering action.
LEARNINGS
LEARNINGS
This project reinforced the importance of distinguishing user requests from user needs. While stakeholders initially asked for a standard filter, further conversations revealed a repetitive workflow that a one-time filter would not fully solve.
This project reinforced the importance of distinguishing user requests from user needs. While stakeholders initially asked for a standard filter, further conversations revealed a repetitive workflow that a one-time filter would not fully solve.
" It was a valuable reminder that effective design often comes from understanding the problem behind the request, not just the request itself. "
" It was a valuable reminder that effective design often comes from understanding the problem behind the request, not just the request itself. "
Role
UI/UX Designer
Timeline
July 2025
Tools
Sketch
Improving Token Management with Saved Filter
Turning a simple filter request into a reusable workflow.
BACKGROUND
The Token Management Portal is an internal tool used by administrators to generate and manage tokens for TV installations.
As the number of tokens grew, administrators needed a faster way to locate specific token records.
The initial request was straightforward: add filtering options above the token table.
However, after discussing the workflow with stakeholders, it became clear that filtering was not an occasional task. Administrators frequently applied the same filter combinations repeatedly throughout their daily work.
My role was to design a solution that improved this workflow while keeping the filtering experience simple and familiar.
CHALLANGES
The request appeared simple on the surface, but the underlying workflow presented a different challenge.
1
Understanding whether users needed a filtering feature or a faster way to repeat filtering tasks.
2
Reducing repetitive filter configuration for frequently used searches.
3
Designing a solution that worked for both one-time filtering and recurring workflows.
Through discussions with stakeholders, I found that the real problem was not filtering itself, but the repeated effort required to recreate the same filter criteria multiple times a day.
LIMITATIONS
The design needed to work within several constraints:
The solution had to fit within the existing token management workflow.
Filtering behavior needed to remain familiar to existing users.
The feature needed to support both occasional and frequent filtering use cases.
Development effort needed to remain reasonable despite the expanded scope.
KEY DECISIONS
Token Management Table and Preview Box
Challenged the initial solution request
The original request was to add a filter feature above the token table. Before jumping into the solution, I discussed the workflow with the Product Manager to better understand the context behind the request.
While direct user access was not available, these conversations revealed that administrators frequently reused the same filter combinations. This reframed the problem from "adding filters" to "reducing repetitive filtering work."
Save Filter Flow
Introduced Saved Filters
Instead of requiring administrators to recreate the same filter combinations repeatedly, I proposed a Saved Filter feature. Users could save commonly used filter configurations and reuse them whenever needed, while still retaining the flexibility to perform one-time filtering when necessary. This approach improved efficiency without changing the familiar filtering experience.
COMPROMISES
Several trade-offs were considered during the design process.
Simpler implementation
VS
Better long-term workflow support
A standard filter would have fulfilled the original request with less effort, but would not address the repetitive nature of the task.
One-time eficiency
VS
Guided flexibility with mandatory
approvers
The solution focused on reducing repeated work over time rather than optimizing a single filtering action.
LEARNINGS
This project reinforced the importance of distinguishing user requests from user needs. While stakeholders initially asked for a standard filter, further conversations revealed a repetitive workflow that a one-time filter would not fully solve.
" It was a valuable reminder that effective design often comes from understanding the problem behind the request, not just the request itself. "
Role
UI/UX Designer
Timeline
July 2025
Tools
Sketch
Improving Token Management with Saved Filter
Turning a simple filter request into a reusable workflow.
BACKGROUND
The Token Management Portal is an internal tool used by administrators to generate and manage tokens for TV installations.
As the number of tokens grew, administrators needed a faster way to locate specific token records.
The initial request was straightforward: add filtering options above the token table.
However, after discussing the workflow with stakeholders, it became clear that filtering was not an occasional task. Administrators frequently applied the same filter combinations repeatedly throughout their daily work.
My role was to design a solution that improved this workflow while keeping the filtering experience simple and familiar.
CHALLANGES
The request appeared simple on the surface, but the underlying workflow presented a different challenge.
1
Understanding whether users needed a filtering feature or a faster way to repeat filtering tasks.
2
Reducing repetitive filter configuration for frequently used searches.
3
Designing a solution that worked for both one-time filtering and recurring workflows.
Through discussions with stakeholders, I found that the real problem was not filtering itself, but the repeated effort required to recreate the same filter criteria multiple times a day.
LIMITATIONS
The design needed to work within several constraints:
The solution had to fit within the existing token management workflow.
Filtering behavior needed to remain familiar to existing users.
The feature needed to support both occasional and frequent filtering use cases.
Development effort needed to remain reasonable despite the expanded scope.
KEY DECISIONS
Token Management Table and Preview Box
Challenged the initial solution request
The original request was to add a filter feature above the token table. Before jumping into the solution, I discussed the workflow with the Product Manager to better understand the context behind the request.
While direct user access was not available, these conversations revealed that administrators frequently reused the same filter combinations. This reframed the problem from "adding filters" to "reducing repetitive filtering work."