{"id":9,"date":"2025-09-29T14:35:22","date_gmt":"2025-09-29T14:35:22","guid":{"rendered":"https:\/\/sites.create.ou.edu\/kaitlynelliott\/?p=9"},"modified":"2026-01-24T18:05:32","modified_gmt":"2026-01-24T18:05:32","slug":"designing-viscomm-website-define","status":"publish","type":"post","link":"https:\/\/sova.ourcloud.ou.edu\/elliott\/2025\/09\/29\/designing-viscomm-website-define\/","title":{"rendered":"Designing VisComm Website: Define"},"content":{"rendered":"\n
\n

Objective<\/h2>\n\n\n\n

The Define stage was where all the interviews and research started to come together. After talking with students, parents, and faculty, I needed a way to make sense of everything I had learned. Creating personas<\/strong> and user journey maps<\/strong> became my main tools for doing this. By visualizing each user group (a student, a parent, and a faculty member), I could step into their shoes and better understand how they currently interact with the Visual Communication program, what they need, and where their frustrations lie.<\/p>\n\n\n\n

This wasn\u2019t just about collecting facts. It was about finding patterns in their experiences and turning those patterns into something meaningful that could guide the rest of the project.<\/p>\n\n\n\n

Challenges<\/h2>\n\n\n\n

One of the biggest challenges I faced was synthesizing a lot of messy interview data<\/strong> into clear personas and journey maps. At first, it felt overwhelming, there were so many different quotes, perspectives, and pain points. I had to learn how to look for patterns without losing the variety of individual experiences.<\/p>\n\n\n\n

Another challenge was making sure each persona felt realistic and grounded, not just a list of bullet points. I wanted them to feel like real people with motivations, frustrations, and goals. This took time and multiple iterations, but it was worth it.<\/p>\n\n\n\n

Going through this process pushed me to become more empathetic<\/strong> in how I analyze user research. I learned to slow down, listen carefully, and let the insights shape the problem definition instead of rushing to design solutions.<\/p>\n\n\n\n

Benefits<\/h2>\n\n\n\n

Developing these personas gave me a much deeper understanding of the users than I expected.<\/p>\n\n\n\n

For students<\/strong>, I realized how much they depend on word of mouth to figure out basic information like course structures, portfolio reviews, and career paths. This showed me that the lack of a centralized, clear online resource doesn\u2019t just inconvenience students, it shapes how they navigate the program entirely.<\/p>\n\n\n\n

For parents<\/strong>, I saw how much they value transparency. They want to understand what their child will experience, see examples of student work, and learn about alumni success stories. Without this, they\u2019re left piecing together information on their own, which can make the program feel vague and uncertain.<\/p>\n\n\n\n

For faculty<\/strong>, I learned how much time they spend repeating the same information to students and parents because the existing online resources are scattered and outdated. This not only slows them down but also highlights how much clearer the program\u2019s online presence could be.<\/p>\n\n\n\n

These insights helped me see the program\u2019s communication gaps in a new way. Instead of just hearing complaints, I could now understand how these gaps affect different people at different stages of their journey.<\/p>\n\n\n\n

\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n<\/figure>\n\n\n\n

Reflection<\/h2>\n\n\n\n

This stage taught me the value of deep understanding before designing<\/strong>. Creating personas and journey maps wasn\u2019t just a checkbox, it changed the way I saw the problem. I moved from a surface-level understanding of \u201cwe need a better website\u201d to a much clearer picture of who we\u2019re designing for and why it matters<\/strong>.<\/p>\n\n\n\n

As a designer, this was a big growth moment for me. I realized that defining the problem well sets the tone for everything that comes after. By understanding my users more deeply, I felt more confident and intentional as I moved into the next stages of the design process.<\/p>\n\n\n\n

<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

In the define stage, I organized the research into clear insights. I used personas and user journey maps to better understand the needs and challenges of students, parents, and faculty. This helped identify patterns and shape the direction for the rest of the project.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-9","post","type-post","status-publish","format-standard","hentry","category-blog"],"_links":{"self":[{"href":"https:\/\/sova.ourcloud.ou.edu\/elliott\/wp-json\/wp\/v2\/posts\/9","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sova.ourcloud.ou.edu\/elliott\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sova.ourcloud.ou.edu\/elliott\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sova.ourcloud.ou.edu\/elliott\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sova.ourcloud.ou.edu\/elliott\/wp-json\/wp\/v2\/comments?post=9"}],"version-history":[{"count":4,"href":"https:\/\/sova.ourcloud.ou.edu\/elliott\/wp-json\/wp\/v2\/posts\/9\/revisions"}],"predecessor-version":[{"id":491,"href":"https:\/\/sova.ourcloud.ou.edu\/elliott\/wp-json\/wp\/v2\/posts\/9\/revisions\/491"}],"wp:attachment":[{"href":"https:\/\/sova.ourcloud.ou.edu\/elliott\/wp-json\/wp\/v2\/media?parent=9"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sova.ourcloud.ou.edu\/elliott\/wp-json\/wp\/v2\/categories?post=9"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sova.ourcloud.ou.edu\/elliott\/wp-json\/wp\/v2\/tags?post=9"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}