ES Chat

Designing for Adobe Summit 2024.

My Role
UX Designer

Tools
Figma

Description
For Adobe, I was tasked with redesigning the marketing pages for their online/in-person keynote event.
‍
Skills Used
Layout Design, UX/UI Design, UX Research

In comparison, Summit 2023 wasn't on par with Adobe MAX.

Visually, page layouts for Adobe Summit 2023 felt outdated and not as engaging as Adobe’s creative conference Max. Adobe Summit consists of a lot of information that can feel overwhelming to users. There are hundreds of sessions and with this being an online and in-person event, things can get a little hectic.

Looking at last year's Adobe Summit 2023 layout in order to find places where improvements can be made.

What can we learn from looking at last years layout?

The bento grid style doesn't work well here

Bento grids are great for organizing content into sections, but it feels like it does more harm than good here. There is too much visual information being squeezed into small sections and starts to make the page feel overwhelmed.

Visual Hierarchy feels off

This website feels very center heavy. Its difficult to tell what information is actually important and a lot of the important information is sectioned off in the center of the page. The page fold stops just below the headshots of the speakers and makes them feel like floating heads without much context.

There's just too much information up front

With so much trying to fit on one page, it just feels a bit overwhelming. There are a lot of photos and long lines of text and none of it brings out Adobe's creative and engaging nature.

Understanding the site flow

Adobe can expect around 12,000 people to attend the in person event and 20,000+ online viewers. Creating a site map allows me to have a better understanding of site flow and where pages have been added in comparison to last years event. It helps to understand how user's may move throughout the website and get a better understanding of how users might move through the site.

Making information more accessible.

With so much important information, how do we allow users to see all the necessary information, but keep them from being overwhelmed?

During this project, I focused a lot on balancing information. I played with different UI elements that allowed me to hide and show information.

ES Chat

Building an internal chatbot for Microsoft Teams and Azure DevOps.

My Role
UX Designer

Tools
Figma

Description
ES Chat is a new internal chat bot, that enables designers, developers, and product managers to relay project updates between Azure Dev Ops and Microsoft Teams.

‍
Skills Used
Natural Language Processing, Process Management, Layout Design, UX/UI Design, UX Research

How can we simplify the task management process for non developers?

With all its features, Azure DevOps can be confusing to non developers, but its very common for Project Managers to use the tool to help plan and manage software development projects. From there, Project Managers relay the information to other members in their team on other platforms. So how can we make this process just a little more seamless for product managers and developers?

Design constraints and considerations

When speaking with upper management, Product Managers, and Developers about the project, there were a few things that I wanted to keep in mind while working on this assignment.

ADO might change in the future

With Microsoft constantly innovating and acquiring more development tools there is a chance that ADO could be a completely different program in the future and its something we should keep in mind.

Don't alienate current users

ADO has a solid userbase and we don’t want to create any dramatic changes that would upset current usability or workflows.

This tool could become public

This current solve is to improve the workflow between product managers and software developers at Microsoft but there is a chance this could be a feature that everyone using ADO could use.

How does ADO fit into your workflow?

Reached out to Microsoft project managers and developers to get an idea of how they feel about the current ADO experience. With ADO being such a large project, I wanted to get a good idea of what pain points exist and maybe find a commonality amongst them.

What about a chatbot?

At their core, chatbots interpret information given to them, find an answer, and return it to the user in a natural language format. This reminded me a lot of a secretary or an interpreter.

But... Microsoft already has a ton of chatbots?The goal is not to create a new chatbot but create a secretary for all of the existing chatbots.

Can Communicate between the already existing Microsoft Teams integrations

ADO has a solid userbase and we don’t want to create any dramatic changes that would upset current usability or workflows.

Ability to look through previous team messages and relay info

With Microsoft constantly innovating and acquiring more development tools there is a chance that ADO could be a completely different program in the future and its something we should keep in mind.

Enhances already existing integration between

ADO and Microsoft TeamsUsers would be able to continue conversations and messages across platforms

Feedback in ADO and Teams

An important part of expanding this project and seeing if its actually feasible, is to release a simplistic version for internal use and be able and use feedback in order to make improvements in the future.  Feedback can be obtained via Azure Dev Ops and Microsoft

Teams in a few ways. We're asking users for simple thumbs up thumbs down, and then prompting if they want to give us more information from there.

ES Chat in Microsoft Teams

ES Chat works as a secretary between the user and Microsoft’s many chatbots. In teams, the focus is on helping users to summarize documents and meetings between chats and create documents. When a user asks ES Chat a question, ES Chat checks in with other chatbots (Copilot, Bing, etc.) to come back with answers.

ES Chat in Azure Dev Ops

Within Azure Dev Ops (ADO), ES Chat works through GitHub Copilot, primarily pulling information and answers from the ai chatbot as well as Bing.An important aspect of ES Chat is feedback. Within ADO, feed back is going to be one of the main drivers for how users will interact with the chatbot in the future.

Interested in learning more about me?

Here is some lorem ipsum about me.  

I couldn't compete with this so I learned to communicate through design and problem-solving. My family has always had a short fuse, and that didn't help when it came to putting things together. I remember a time when my mom brought a new vacuum cleaner and she and my aunt would argue about how to put it together. By the time they finished arguing over the instructions, I'd have put the vacuum together.Small instances like this are what piqued my interests and led me to design.

About Me