Hearth

Collaborative software for interior designers to streamline material schedules and client presentations.

Project type: Design Software

Industry: Architecture and Interior Design

Role: Research, UX/UI, Branding, Prototyping, and Testing

Please watch the product walkthrough below or continue on for the full case study.

Jump to Final Case Study >

Case Study

Hearth is the final project of my Product Design Boot-camp. As it developed, the direction of the product took many turns, while remaining focused on solving a critical need. This case study details the progression to my final product: Hearth.

Role of an Architect

The fundamental role of an architect is to facilitate the completion of a structure that meets the clients needs. To do this, they design in collaboration with a range of designers and engineers and then effectively communicate the design to the builders.

Initial Problem Statement

The practice of Architecture is a complex and dynamic process. As a project develops, Architects often struggle to keep track of the ever evolving information leading to miscommunications, errors in work, and an unhappy client. Despite advancements in design tools like 3D modeling and virtual reality, the organizational tools remain basic and underutilized.

Over 8 years as an Architectural Designer, I have seen first hand many of the challenges that industry professionals face- few of which having to do with their skill as a designer. It was important for me to take this opportunity to explore ways of improving this challenging but rewarding profession.

While my years in the field provided me a unique insight on the industry, I had to be particularly mindful of any bias as my experience in architecture is not universal.

Research Methods

To understand the nuanced challenges of my target user, I conducted individual and group interviews with Architects and Interior Designers at various levels to uncover common issues and opportunities.

Interviewee Profile

Age: 26 - 40
Industry: Architectural Designers, Licensed Architects, Project Managers, Interior Designers
Cities: San Francisco CA, Oakland CA, Tampa FL, Jacksonville FL

“With everything moving so fast to hit a deliverable, it becomes hard to track all the little changes.”

“It feels great to have a firm grasp on what’s happening in the project. It feels like it’s truly MY project!”

“I use my note pad all day, I would be so lost without it… but it can take forever to look back through and find what I’m looking for ”

Research Goals

  • Validate my perceived problem statement

  • Discover how designers currently keep track of informations

  • Understand the pro’s and con’s of currently used communication tools

  • discover additional challenges presented in the industry

Persona and Journey Map

To create a clear picture of my target user and their needs I created a persona and journey map from the amalgam of those interviewed.

Key Insights

Insight to HMWs

Using the Insights from the interviews I posed some How Might We questions in an effort to guide the product and its features.

Below is my first attempt at solving the initial problem statement. Throughout this process, I iterated ideas, conducted user testing, and received candid yet helpful feedback.

Although the initial MVP was not successful, this experience allowed me to learn from failure and thoughtfully pivot to a solution that better addresses the needs of my target users. To Jump to the Revised Product Case Study please click the button below.

Scenario: In a meeting, a Senior Architect sketches a window detail then hands it to a Junior Designer to replicate in a drafting software. First, the Junior Designer record the sketch.

Task Flow

User Testing

Wire Frames

Mockups

Home Page

Home Page

Work Space option 1

Work Space option 1

To test this idea I hosted an informal meeting with 3 local Architects.

I presented the concept and possible features, walked through wireframes and mockups, and fielded questions that challenged the product's goals, functionality, and viability.

At the end I asked “Would this product would improve your daily work-flow?”

Work Space option 2

Work Space option 2

Initial MVP

A collaborative database designed to collect and organize disjointed notes throughout the duration of a project.

For my MVP I wanted to focus on one specific method of note taking. As architects are prefer describing ideas visually I selected the ever important hand drawn sketch.

Results

“I just don’t see myself using it.”

“This just duplicates what we already do.”

What Worked

Nope! Despite its initial interest, the product failed to add any significant value to their daily workflow. I had created a redundant product that already existed and was largely overlooked. More importantly, I misunderstood the purpose of design sketches, which are meant to communicate ideas quickly and are seldom referenced beyond their initial implementation in a drawing set.

  • The concept of a central searchable database.

  • Ability to share notes with others.

  • Communal pool of notes providing more information for the team.

What Didn’t

  • The approach to the product did not notably improve the issue to be solved.

  • Product seems to be more hassle than benefit.

  • Product created duplicate file storage which could lead to miscommunication and further errors.

“I don’t look back at sketches that often.”

Product Pivot

When you hit a wall, stepping back and seeing the problem differently can be be a great approach. Another review of my preliminary interviews confirmed that designers biggest challenges are communication and information tracking.

I decided to focus on improving communication between Architects and Interior Designers. In multiple interviews, and personal experience, this stood out as the most troubled relationship in the industry.

Revised Problem Statement

Architects and interior designers often collaborate to define a space's function and aesthetic by specifying finishes, furniture, lighting, and more. The dynamic nature of design makes it challenging to track evolving information, especially when teams work at separate firms which can lead to errors, unnecessary tension, and dissatisfied clients.

Insights

  • While the Construction Document (CD) acts as the primary- and legal- interface between Architect and Contractor, the market currently lacks a reliable platform between the Architect, Interior Designer, and Client.

  • A CD consists of a series of categorized sheets linked by a system of references used to connect information across the set. This fragmented informations makes it difficult to track the numerous changes as the design evolves.

Insights to HMWs

Discussions with industry professionals revealed potential causes of strain between architects and interior designers. I used these insights to frame "How might we" questions and guide the product.

Key Terms

While floor plans and renderings are the beautiful images we associate with architectural, the essential details of a project are found in the building “specifications” and “schedules.” These schedules list the materials, lights, appliances, windows, doors, and other elements within a building.

Revised Product

A collaborative design platform for Interior Designers and Architects to create material schedules and present to clients.

Goals to Features

Site Map

The Primary Users will spend most of their time on the product in the Project Workspace. The Goal of this site map was to arrive at the workspace in as few clicks as possible.

Product Users

The product is intended for three main users: the Client, Architect, and Interior Designer. Each will interact with the program differently, but all will collaborate to achieve the same goal.

  • Input material information

  • Indicate where material occurs via tags on floor plans and elevations

  • Create material schedule to be distributed to Architect

  • Leave comments and questions

  • Add notes to backgrounds

  • Illustrate designs via shapes and overlays (beyond MVP scope)

  • Potentially provide and upload rendered images of floor plans and elevations if desired

Client

  • Primarily observational role

  • Review design and material

  • Review Floor plans and interior elevations

  • Approve/ confirm finished materials

  • Leave comments

Architect

  • Upload architectural backgrounds including floor plans, elevations, renderings etc.

  • Upload files to project

  • Potentially link with programs such as Revit and AutoCAD to ease flow when backgrounds change

  • Leave comments with questions or conflicts

  • Review material information and specifications from Interior designers

  • Add notes to backgrounds

  • Take scheduled information and design to use in construction documents for the building contractor

Interior Designer

Product Layout

To ensure an intuitive product adoption I analyzed industry-standard products and incorporated crucial elements such as workflows, layouts, and features.

Since this product is intended to be used as a professional production tool it necessitated a desktop layout.

Workspace Wireframe: Original Layout

Workspace Mid Fidelity Mockup

What Didn’t

  • Tool bars are in two different orientations

  • Currently only shows master schedule OR room schedule

  • Dueling visual hierarchy

What Worked

  • Clearly defined windows

  • Material schedule on the left that acts as a “properties” side bar similar to that used in AutoCAD and Revit, providing an intuitive operation for modern designers

Key Fixes

  • By visually dividing the screen into two sections and creating a “Back End / Front End” relationship where the “Back End” contains an index of the materials to be used while the “Front End” displays the information.

  • Provide a separate window to display room by room materials

  • Merged the editing tools with the secondary window title box

  • Throughout human history, the hearth of a home has been the social center for nourishment and exchanging information

  • The word “hearth” is associated with a warmth, connection, and support

  • In residential design, the hearth is often used to tie a space together

Color Theory

The Primary Colors of the Product needs to be muted and desaturated to allow for the colors of the materials and design to shine through in each window. This is common practice in many design products as the attention should be on the design created in the product over the product itself.

Red over Blue

The brand color and primary accent is a bold deep brick-like red (#C24B21) that evokes energy, confidence, and warmth. Most tools in the industry use the conventional blue tones, but I wanted Hearth to stand out as a more dynamic and intentional product.

Next Steps

With the Primary User shifting to the Interior Designer more research needs to be done into the inner workings of this industry. Interviews and user testing will determine what the next iteration of the product entails.

Next
Next

The Lazy Bartender