DESIGN

Generating a Solution for Radio Hosts

OVERVIEW

In the design phase, we developed preliminary ideas for what would eventually become INTUNE. First, we identified design requirements for the application based on our user research, personas, and user journey maps. This allowed us to narrow the scope of the project. We created design requirements, storyboards and information architecture to develop ideas and start conceptualizing the features and design of INTUNE.

Design Requirements

Narrowing Our Scope

Using two different methods: Action, Object, Context and Data, Functional, Contextual, we created design requirements that outlined the information and functions of our application. We created the design requirements from the research phase that helped us translate user needs into concrete interactions. The design requirements helped us determine which pain points, desires, and goals to address and which ones were out of scope. We used them to generate design ideas that we illustrated in our storyboards in the next step.

Brainstorm of Design Requirements

Preliminary ideas for design requirements

Brainstorm of Design Requirements

Preliminary ideas for design requirements

1/1

Key Design Requirements

Allow hosts to send and receive multimedia content from listeners
Allow hosts to schedule meetups with listeners
Allow hosts to search hashtags across all social media
Allow hosts to have a contact card for listeners
Allow hosts to access text threads in chronological order

Takeaways

Physical studio changes were out of scope
A multifunctional application was necessary
User needs called for a sovereign posture on a desktop

Full Document

Storyboards

Generating Design Solutions

We created storyboards to illustrate and contextualize various key path scenarios outlined in our design requirements. These storyboards helped us evaluate potential design solutions within the context of our users working environment. This stage was the first time that we started planning the layout of our application. These visual narratives helped us decide on what information was necessary and feasible to implement in the information architecture in the next step.

Brainstorming Storyboard Topics

Rough sketches of potential storyboards

Initial Design for a Storyboard

Whiteboard marker rough sketch of one possible storyboard

Brainstorming Storyboard Topics

Rough sketches of potential storyboards

1/2

Takeaways

Storyboards reinforced the multifunctionality of the application
Storyboards revealed a need for distinct sections for different functions

Sketched Storyboard

Photo Storyboard

Sketched Storyboard

Storyboard Samples

Full Document

Information Architecture

Planning Application Hierarchy

We created an information architecture flow chart to plan out the high level hierarchy of the pages of INTUNE. We used the information architecture to categorize and connect the distinct design solutions illustrated in the storyboards. At this point in the project, we returned to our users to show them our progress and get feedback on our ideas. After showing them our information architecture, we realized that the application we envisioned was much more complicated than our users wanted it to be. Iterating upon our information architecture marked a major turning point for us. The flow of the information architecture helped us determine INTUNE's visual components and the features needed to navigate between them in the paper prototypes.