Introduction
We are Team Eastern Phoebes, a group of students working on a short-term physical computing design project focused on identifying and addressing real-world problems through rapid prototyping.
We conducted a client interview with Jason, an HVAC mechanic with over 16 years of experience in the trade, including 12 years working at Carnegie Mellon University. The meeting took place during the first week of our project timeline and was aimed at understanding Jason’s daily workflow, challenges, and opportunities for improvement within his work environment.
Our team members present were:
Tiffany (Main Interviewer)
Jessica (Note Documenter)
Tim (Recorder / Sub-Interviewer)
The purpose of this meeting was to identify a specific, actionable problem that we could address with a medium-fidelity prototype within four weeks, focusing on practical, and even fun solutions to Jason's everyday work.
Interview Agenda
Group Name: Eastern Phoebes
Interviewee: HVAC Mechanic
Role assignments
Main Interviewer - Tiffany
Asks questions from document, introduces meeting, gives overview of the process
Note Documentor - Jessica
Documents the interview for the group to have reference
Takes quotes of interviewer
Recorder / Sub Interviewer - Tim
Asks supporting, clarifying questions, records key details, takes photos on site
Interview Outline
Introductions (All team members and interviewee) (~5 minutes)
What we each specialize in, what we enjoy doing, etc.
Verbal Terms and Conditions (~2 minutes)
Notifying the interviewee that we are taking pictures and recording notes of the interview for documentation purposes
Explain process/what we do (~5 minutes)
Interviewee’s professional background (~3 minutes)
State deliverables, expectations (~2 minutes)
Explain that our goal is to make a working prototype at medium-fidelity
Given only four weeks
Avoiding engineering/high-tech solutions to problems
Solving for the specific problem, and not inventing something new
Limited by resources, knowledge
Questions: (~15 minutes) *asking additional clarifying questions if needed
The scope of work the interviewee often deals with
Technical skills the interviewee must use on the day to day that we might not know about
The interviewee’s daily routine
Delve into pain points, time wasted, what is already streamlined
Any common difficulties/issues
Categorize difficulties and problems, narrow down
Anything they wish they had known about the job/career/industry before joining
Once settled on a problem (~10 minutes)
How the interviewee currently deals with the problem
Particular things that interviewee needs accommodations for / features that would be nice to have
Rough ideas & problem solving methods
Q&A Opportunity (0-5 minutes)
Allow for the interviewee to us any questions they might have regarding our background, project, timelines, etc
Meeting summary and major takeaways
Jason described his work as highly reactive and variable:
Issues arise unexpectedly (e.g., leaks, temperature complaints, equipment failures)
Urgent Priority (UP) calls require immediate responses
Preventative maintenance is ongoing but difficult due to staffing shortages
“You come in and don’t know what happened overnight.”
Additionally, staffing shortages (currently ~2.5 workers instead of 4) make it difficult to keep up with both urgent and preventative work.
Communication systems exist but are inconsistently used:
Texting and phone calls are most common
Google Chat is used for broader communication
EZMaxMobile exists but workers operate independently
Key issue:
Workers don’t consistently communicate updates, leading to inefficiencies
“Communication is pretty bad… people don’t take the time to update each other.”
A critical recurring issue was the difficulty of transporting tools:
Workers walk everywhere across campus carrying tools and equipment often requiring multiple trips
Ladders are especially problematic:
Hard to carry alone
Difficult to find (no tracking system)
Sometimes taken by others or contractors
This creates:
Time inefficiency
Physical strain
Delays in urgent repairs
Another key issue is lack of accountability and tracking:
No system to track ladder locations
Shared tools frequently go missing
No centralized real-time visibility
Potential opportunity:
A tracking or visibility system for shared equipment
Work is constrained by:
Class schedules (rooms unavailable at certain times)
Crowded campus transitions (between classes)
Elevators and stair limitations when moving equipment
“Worst walk is during class changes when hallways are so crowded.”
These constraints are not always known in advance, leading to wasted trips.
Jason highlighted issues with outdated and complex systems:
Older HVAC control systems still exist
Limited access to certain control settings
Poor documentation of parts and systems
To compensate:
Workers rely on:
Prior experience
Existing parts
Google/vendor support
From the discussion, several potential problem areas emerged:
High-potential focus areas:
Ladder transport (handle, strap, portability solution)
Equipment tracking (especially ladders)
Tool carrying efficiency
Spatial awareness / navigation challenges
Reducing repeated trips
How each work order looks on FMS' end. There isn't a lot of detail provided, me
The work order tracking app currently in place
Your thoughts after holding the meeting and discussing as a team
Tiffany: I found the meeting to be very insightful and a lot different from what I expected. We went in with a set list of questions that we wanted to ask, but we ended up asking many many follow up questions sometimes leading into different directions. For example, we had a whole discussion about ladders and how Jason wanted to find a device that helped him carry ladders around campus. He also discussed with us how ladders go missing, and that there is a lack of ladders problem in his job, which is a problem that technically we could not solve for him. But this discussion was insightful and allow us to better understand how we can serve him as students. The interview allowed us to have additional follow up questions regarding other areas of potential improvements, such as communication systems or even something less UXUI design.
Tim: I thought that the meeting was pretty helpful and provided us a lot of information to work with. We received very detailed answers for all of our questions, and by the end of the interview we had a clear picture of how his daily routine goes and what he does in HVAC. For example, one of our biggest takeaways was the role of communication in his work. Each member of the team works by themself most of the time, and works within a specific area of the school. Beyond that there isn't much communication within each day. Another big challenge is the lack of a system to track ladders, which causes Jason to bring a ladder with him everywhere he goes. Although we can't really help with this problem within the scope of the project, there are meaningful ways to alleviate other parts of his work to make this problem less severe. With the information we got from the interview, we decided to email him with follow-up questions to see if there's a specific direction towards which we could help.
Jessica: The meeting was overall very productive and largely followed our planned agenda, allowing us to gather detailed insights into the interviewee’s daily workflow and challenges. Our structured roles helped keep the conversation organized, while still giving us flexibility to explore unexpected but valuable topics, especially around tool transport and communication issues. One of the biggest strengths of the meeting was how clearly we were able to identify specific, actionable pain points, particularly the difficulty of carrying ladders and tools across campus. However, in hindsight, we could have asked more targeted follow-up questions to better quantify these problems and prioritize which issues impact the interviewee the most. There were also moments where we could have more deliberately steered the conversation toward narrowing down a single focus area. As a team, we felt the meeting gave us a strong foundation, and moving forward, we would aim to ask more precise, evaluative questions and validate potential solutions more directly during the conversation.