Design
Hero Alias: Product Designer
Powers: Figma, Miro
Timeline: 5 weeks
Hero Alias: Product Designer
Powers: Figma, Miro
Timeline: 5 weeks
To reduce the amount of onboarding time required to learn a new program, I looked at several Adobe programs for IA and structural insight when presenting information.
Photoshop, Illustrator, and Adobe Acrobat were my main visual references with Grammarly for IA and function.
Our goal is to enhance efficiency and streamline information retrieval processes.
How might we design a user interface for an AI model that reduces the time users spend manually searching through documents?
What tools are currently used in the review process and for proofing documents for changes?
Would it be optimal to show multiple results for each claim?
What does the output for application look like?
Does the AI algorithm scan the entire document or just what is different/not found in its database?
The user base is composed of individuals who use Adobe Acrobat daily to complete their work.
How might we design a user interface for an AI model that reduces the time users spend manually searching through documents?
?
Based on user data, the key functions needed for the application include:
Export options
Large main focus for content
Smaller half-size focus for document feedback and comments
Toolbar of common tools including a start process button
Chunk information by creating areas of focus for the document being reviewed.
Highlight comments/suggestions currently being reviewed
Large thumbnails with preview of document
Large thumbnails with preview of document
Sort and filter options
Button with noticeable visual treatment and placement for quick start for new document uploads
Icon that acts as home button bringing user back to this screen
Individual account profile to allow management of files
Tabs to switch between different views and functions
List of matched results the AI found that align with similar ones from the internal database
Return back to file directory
Clicking on a result also highlights the sentence on the document
List of matching sentences from the internal database so users can simultaneously check for changes
In a world overwhelmed by data, Prototyp emerges as a game-changing AI application. Created by a visionary developer, Prototyp scans and matches new documents to a vast digital archive, eliminating manual searches.
With the AI algorithm in its MVP state, a skilled UX designer steps in to transform raw code into an intuitive user interface. Witness the evolution of Prototyp—where cutting-edge technology meets user-friendly design, revolutionizing document management forever.
Please note that all mentions to and of clients by name have been removed or obscured to adhere to NDA
restrictions.
INtroducing the
Systematic
INtroducing the
Systematic
INtroducing the
Systematic
Top Lessons
And in our next issue...
Simplify the user journey and update flow to reflect the change from the initial application use
Decide on a visual style and aesthetic that is consistent with simple UI look of wireframes
Collaborating with others on a team of different specialties requires over communicating and asking questions repeatedly
As a designer, expectation management is important to avoid having ideas from scaling too big especially during the initial design stage
Presenting research and evidence is key to getting everyone on board with the concepts being presented
To reduce the amount of onboarding time required to learn a new program, I looked at several Adobe programs for IA and structural insight.
Photoshop, Illustrator, and Adobe Acrobat were my main visual references with Grammarly for IA and function.
Our goal is to enhance efficiency and streamline information retrieval processes.
How might we design a user interface for an AI model that reduces the time users spend manually searching through documents?
What tools are currently used in the review process and for proofing documents for changes?
Would it be optimal to show multiple results for each claim?
What does the output for application look like?
Does the AI algorithm scan the entire document or just what is different/not found in its database?
The user base is composed of individuals who use Adobe Acrobat daily to complete their work.
How might we design a user interface for an AI model that reduces the time users spend manually searching through documents?
?
Based on user data, the key functions needed for the application include:
Export options
Large main focus for content
Smaller half-size focus for document feedback and comments
Toolbar of common tools including a start process button
Chunk information by creating areas of focus for the document being reviewed.
Highlight comments/suggestions currently being reviewed
List of matched results the AI found that align with the internal database
Return back to file directory
Tabs to switch between different views and functions
Individual account profile to allow management of files
Button with noticeable visual treatment and placement for new document uploads
Large thumbnails with preview of document
Sort and view options
List of matches from the internal database so users can check for changes
Clicking a result also highlights the sentence on the document
Simplify the user journey and update flow to reflect the change from the initial application use
Decide on a visual style and aesthetic that is consistent with simple UI look of wireframes
And in our next issue...
Top Lessons
Collaborating with others on a team of different specialties requires over communicating and asking questions repeatedly
As a designer, expectation management is important to avoid having ideas from scaling too big especially during the initial design stage
Presenting research and evidence is key to getting everyone on board with the concepts being presented
Hero Alias: Product Designer
Powers: Figma, Miro
Timeline: 5 weeks
Our goal is to enhance efficiency and streamline information retrieval processes.
How might we design a user interface for an AI model that reduces the time users spend manually searching through documents?
What tools are currently used in the review process and for proofing documents for changes?
Would it be optimal to show multiple results for each claim?
What does the output for application look like?
Does the AI algorithm scan the entire document or just what is different/not found in its database?
The user base is composed of individuals who use Adobe Acrobat daily to complete their work.
To reduce the amount of onboarding time required to learn a new program...
Based on user data, the key functions needed for the application include:
Large main focus for content
Smaller half-size focus for document feedback and comments
Toolbar of common tools including a start process button
Chunk information by creating areas of focus for the document being reviewed.
Highlight comments/suggestions currently being reviewed
Export options
Design
Top Lessons
Collaborating with others on a team of different specialties requires over communicating and asking questions repeatedly
As a designer, expectation management is important to avoid having ideas from scaling too big especially during the initial design stage
Presenting research and evidence is key to getting everyone on board with the concepts being presented
And in our next issue...
Simplify the user journey and update flow to reflect the change from the initial application use
Decide on a visual style and aesthetic that is consistent with simple UI look of wireframes
2
1
1- Clicking a result also highlights the sentence on the document
2- List of matches from the internal database so users can check for changes
1- Icon that acts as home button bringing user back to this screen
2- Individual account profile to allow management of files
3- Button with noticeable visual treatment and placement for new document uploads
4- Sort and View Options
5- Thumbnail with preview of document
1
3
2
4
5
1- Return back to file directory
2- Tabs to switch between views and functions
3- List of matched results found by the AI that align with the internal database
1
3
2