Turning a foreman's spoken workday into an audit-ready, manager-facing report
Team
Designer(me), Product Manager,
Engineer, Sales Consultant
Tools Used
Claude Code, Linear, Figma
Timeline
11 weeks (Jun 15 - Present)
BYTE-SIZED INFO
tl;dr
Construction crews log hours on paper, on a clipboard, on a job site. That paper trail is slow, error-prone, and painful for the super (the manager) to convert into invoice-ready reports.
TimeTracer is a voice-first app to solve that. A crew member logs their day from the truck, gloves still on, in about 30 seconds. That log becomes a structured, exportable timesheet.
As the only designer on the team, I owned the two surfaces that turn raw field entries into something a general contractor or auditor will accept: Reports and Calendar, plus the capture flow leading to them.
IMPACT
From ICP discovery to shipping features, I helped land our first client call in under three months.
THE WORK
Identifying cracks in the existing journey.
iHeartRadio serves hundreds of millions of listeners every month. At that scale, even tiny moments of hesitation compound into millions of abandoned listening decisions.
USER INTERVIEW QUOTE
MY RESEARCH IDEALOGY
Listening to the noise.
To better understand the factors driving churn, my team and I used several methodologies to gather deeper insights.
Led foundational research, conducting a Heuristic Evaluation and 5 in-depth user interviews.
Analysed 500+ user reviews from various sources like Reddit and App Store.
Research led me to prioritize an engagement-first strategy: optimizing onboarding and adding social features.
HE WORK
11 weeks of pure grind.
#1 Voice Capture, Translated
Voice-based project creation, built for someone standing on a job site, not sitting at a desk. Added a language switcher, then extended translation across Reports, Materials, and Tools, so non-English-speaking crews (a real presence on almost every job site) don't need a supervisor to translate for them. The tools and materials they used will automatically be synced to their recording and added to the report.
#2 Reports, Scope & Period
Turned a single "export CSV" button into a real report builder: custom date ranges, multi-select scope across sites and crew members, and batch export so a contractor can push invoices for every crew, every site, in one pass. Also fixed hour-rounding and sync bugs that were quietly turning into paycheck disputes.
#3 The Org Dashboard
The first screen an owner running multiple crews and sites opens: total hours, billable split, active members and projects, and a daily trend. Paired with site/crew filters that drive every other view in the app.
TESTING v1
Room to rethink.
Through testing, we discovered four key areas where the users struggled with interaction.
Location: Expectation to find the Location setting in the account section, but finding it hidden under Advanced Settings.
Dedication: Assumption that the Song Dedication feature only applied to the song currently playing on the station.
Button Functions: The Plus button and Transcript button were confusing, with the Plus button's function being the non-obvious "Marked as Played."
Device Transition: Users expected easier and more direct access to output music and transition playback across multiple devices.
INCORPORATING CHANGES
The outcome, revisited.
My key takeaway from testing was the need for clarity and discoverability. For example, users struggled to find hidden functions like "Mark as Played" or change their location settings.
I advocated for moving critical controls (like Location Settings) from an obscure "Advanced" menu to the main "My Profile" page, a small change with a massive impact on user autonomy and successful content delivery.
CHALLENGES
Design limitations.
My team didn't just build the solution. We went a step further and critically examined its boundaries.
Within the live radio interactions, some users might feel a little hesitant about directly calling the Radio Jockey because of privacy issues.
At the time, the company did not have the resources to incorporate a moderator
for the live chat/community discussion board features.
The design was also unable to resolve the overload of advertisements on the app due to
business constraints.
What stayed with me.
Teamwork
I learned that real teamwork requires understanding and adapting to each other’s working styles while collaboratively figuring out methods that fit the team as a whole.
Taking Ownership
Actively stepping up and taking ownership allows us to experience the joy of success.
Empathy
I recognized the importance of empathy, not only towards our users but also towards each other.
