In this episode of the TV Matters Podcast, I’m joined by Colleen Pendergast, a product designer who helped lead design for Apple’s pro video applications, including Final Cut Pro. Before Apple, she worked as an editor on news, promos, weddings, and documentaries, and taught high school and college students at the Academy of Art in San Francisco. Today’s episode is sponsored by EditMentor, teach and learn filmmaking interactively.
Colleen Pendergast’s path into product design started in storytelling, not software. She went to college for journalism, drawn to writing and sports broadcasting, and expected to end up closer to reporting and being on-camera. That changed after a single film-class assignment—tape-to-tape-editing—when she realized editing felt like home. “It was just telling stories with pictures,” she says. She switched to media arts and began building experience the way many editors do: through internships, freelance work, and whatever projects were available.
Her first editing gig came with a steep learning curve. While she was waitressing and doing unpaid post house internships—“getting coffee… for zero dollars”—a friend’s husband handed her a Media 100 system and offered her a job cutting a four-part series for a local San Francisco TV station. She had never used the platform before. The setup was physical and intimidating—two large monitors, SCSI cables—and she remembers loading it into her Saturn, driving it home, and teaching herself the system in about a week. That job led to more work: news packages, promos, wedding videos (“where everyone starts and where everyone cries a lot”), music videos, and documentary collaborations that screened at festivals in San Francisco, along with editing work for Link TV.
Teaching entered her life through volunteering. In Oakland, she volunteered in high school media programs at Fremont High School and Oakland Tech and found she loved it—especially at a time when computer-based editing still felt new and exciting. That led to teaching at the Academy of Art in San Francisco. She describes her teaching mindset as helping students better express what they intended, rather than judging their creative voice.
From Edit Bays to Apple’s Pro Video Team
Pendergast didn’t set out to design applications. She “fell into design” through workflow work at Apple—an entry point sparked by her brother, who was on the Final Cut team in QA. He told her Apple needed a workflow expert. At the time, she was a freelance editor working from home and resisted the idea of commuting, until her brother reframed it: “Because you get a paycheck every two weeks.” She expected to stay a couple of years, get the experience, and return to editing.
Instead, Apple pulled her deeper into the product. She started on a hybrid design/QA function: bringing in her own edits, editing at Apple, and writing tickets that didn’t just report issues but explained workflow pain—what was confusing, what required too many clicks, what wasn’t intuitive. After a reorg, she and another teammate were moved into design while others shifted into QA. She credits Brian Meany—an original Final Cut figure from the Macromedia era—for recognizing what she was already doing: explaining the user story and proposing better solutions. That became her entry into writing specs and working closely with engineers to build features.
Designing for Editors, Inside Engineering
Pendergast joined around Final Cut Pro 3.5—the multicam release—and describes a team culture that was deeply editorial and unusually structured inside Apple. The Final Cut Pro design team did not report into Apple’s central HI design organization; it operated “kind of part of engineering,” reporting through an engineering director. That structure reinforced a practical standard: decisions needed to hold up in real use, not just in theory.
She worked across areas including Motion/Final Cut integration through “master templates,” marker improvements (including multicolor markers), and Cinema Tools—much of it driven by the needs she had as an editor. She also describes the pride of the tool’s peak moment in the industry, including calls connected to Walter Murch’s Cold Mountain workflow and the feeling of contributing to a system used at that level. Final Cut also carried a “rebel” identity: professional results without the price tag of traditional high-end systems, “and it’s not going to cost you $2 million.”
What “Product Design” Meant on Final Cut
A major thread of the episode is her explanation of product design in concrete terms. The title varies by company, but in her framing it combines prioritization, customer understanding, workflow definition, and collaboration. At Apple, that meant working closely with marketing and sitting in edit bays with editors to understand what mattered to customers, then translating that into priorities and design decisions.
She also breaks down how the team splits responsibilities. She describes herself as a domain expert in editing—focused on user intent and workflow—while visual designers were the “pixel people,” responsible for icons, UI states, and the visual system. Domain experts could map step-by-step workflows with boxes, arrows, and error states, then work with visual designers on layout and details such as audio role colors that wouldn’t compete with the image on screen.
Wireframes, Prototypes, and Avoiding Premature “Polish”
Pendergast offers a practical explanation of wireframes and prototypes. Wireframes are blueprints: exploring layout, navigation, and reach, iterating before committing to high-fidelity UI. She warns that designs that look too finished too early cause stakeholders to give feedback on surface choices—fonts and colors—when the real questions are whether the workflow makes sense and whether the layout works on real screens.
Prototypes simulate interaction. Her team often built them in Keynote—faking a cursor and stepping through states—to test whether users got lost, lost selection, or lost their place before engineers built anything. Today, she notes, tools like Figma make this easier, but the goal remains the same: validate behavior before implementation.
Final Cut Pro X: Why It Changed—and Why It Hurt
The centerpiece of the conversation is Final Cut Pro X: why it was rebuilt, and why the reaction was so intense. Pendergast frames it as both a technical necessity and a product bet. Technically, Apple needed to move to a 64-bit foundation: “We could not keep Final Cut 7 alive.” Product-wise, the team was looking at a changing market. She remembers marketing using a user “pyramid”: Hollywood at the top, but the largest slice being YouTube creators—shorter content, faster turnarounds, less archiving, and fewer assumptions about track-based editing.
The redesign was also driven by frustration with track-based pain: clip collisions, losing sync, and the number of steps required for basic actions. She describes making an internal video demonstrating how extending audio in Final Cut 7 could require track management and clip shuffling, risking sync problems. The team’s mindset was direct: if people have to learn something new anyway—and the product needs a new technical foundation—then the workflow should be better, not just familiar.
Even so, the launch backlash surprised them. “Everyone was nervous,” she says, but they didn’t expect it to be “as bad as it was.” She points to a major messaging issue: calling it “Final Cut Pro 10” implied an evolution from 7, when it was a fundamentally new approach. Pulling Final Cut 7 off the shelf compounded distrust. At the same time, she and Misha acknowledge real innovations: speed, background rendering, skimming, and organizational tools like keywording and smart bins—features that were ahead of where much of the industry was at the time.
Startups, AI, and Advice for Teachers and Students
After Apple, Pendergast moved into consulting and startup work, collaborating with Wes Plate and Jordan McCommons and working on products far outside video, including a medical record review application that uses AI to assemble a patient’s story from scattered documents. She describes the biggest difference between Apple and startups as process: Apple was review-heavy and deck-driven, while startups often run on trust and speed—“No, just go do it.” That also means shipping is more iterative: web products update quickly, and teams tolerate imperfections that Apple would never allow.
For students, she recommends viewing internships as a direct path into large companies like Apple, while startups are “into the fire”—learning by doing, often without onboarding. She stresses that candidates should interview teams as much as teams interview them: “Period. End of story.”
For educators, she comes back to fundamentals: storytelling matters regardless of medium, even in an AI-saturated future. Without a strong beginning, middle, and end, tools don’t matter. At the same time, she worries young creatives aren’t learning AI fast enough and predicts AI literacy will quickly become a differentiator. She’s also more interested in AI that improves craft—fixing color and audio—than AI that replaces storytelling. And in critique, she argues teachers should focus on helping students express what they intended, explaining why an edit didn’t communicate rather than judging the student’s story.
Listen to the full episode on Apple Podcasts or Spotify to hear Colleen Pendergast’s story and her perspective on how editing, teaching, and product design intersect.
