My Process
My digital design adaptable, focusing on creativity, and discovery. It often starts with brainstorming and research, followed by sketching ideas and refining them digitally. I explore different design tools and techniques to bring the vision to life, ensuring the final product aligns with both aesthetic goals and user needs. While this process is a core part of my approach, it’s not the only method I use. I’m always open to evolving my techniques, drawing inspiration from new trends, feedback, and collaboration to deliver the best possible results for each project.
Role:
Designer
1/9
Requirements
To begin a design project, I always start by reviewing a quick design brief for documentation. This brief helps me to understand the purpose of the design piece. However, some briefs may be incomplete, so I always take the opportunity to request a complete list of requirements at this point. This is important because it allows me to visualize the project timeline and deadlines. In marketing teams, for example, some deadlines may not be reasonably aligned with IT sprints, so it’s important to be aware of this when planning the project.
2/9
Inquiries
I need to confirm my design capabilities for any given project. Am I qualified for the job? If the answer is yes, then I proceed. However, if there are any design issues or requirements that need to be considered, please communicate them to me. In cases where I need to revise an older piece, I will have to open each raw file and examine how each element was built using the correct platform, as well as identify any additional assets required, all within a reasonable timeframe.
3/9
Project Mngmt.
Personally, I am a big on gantt charts. Jira is the standard for software teams, but my preference is Wrike since the price on them have dropped to undergo more projects. I usually try to make a full week sprint for every task, unless the start of any design piece are edits. I stay away from daily tasks that require feedback the same day.
4/9
Brainstorm
When I need to come up with ideas, I find that using a mind map is very helpful. It allows me to quickly jot down ideas and organize my thoughts. Once I have a good list of ideas, I turn them into guidelines to help me create rough drafts more easily. After completing the rough drafts, I revise and refine them to produce the final draft. This process helps me stay organized and produce high-quality work.
5/9
Sketches
My usual design process involves creating several quick and rough drafts or engaging in brainstorming sessions, with up to three iterations. Afterward, I select the best design and keep two other options available in case the audience desires to see an alternative. I upload them for proofreading and maintain consistency by making up to three iterations.
6/9
Mockups
My usual design process involves creating several quick and rough drafts or engaging in brainstorming sessions, with up to three iterations. Afterward, I select the best design and keep two other options available in case the audience desires to see an alternative. I upload them for proofreading and maintain consistency by making up to three iterations.
7/9
Final Design
I design and share in Figma for feedback. After revisions, I organize and export assets.
8/9
Handoff
The handoff process is straightforward. I create the necessary artifact in the appropriate format. If transparency is required, I provide PNG or WebP files. For logos, I offer options such as the full SVG file, a CSS class name, or the direct SVG tag for use in HTML code. Regardless of the option chosen, I am proficient in handing off items and creating sprite sheets for front-end development.
9/9
QA
I open a Google Doc and create a table that compares code design and visual design. Then, I edit the CSS code and add my QA notes so that developers can easily make the necessary changes if they choose to. However, this is only applicable for smaller businesses as larger ones typically have their own QA specialists.
