Descript: collect recordings, then edit video like a document
Descript is a creation tool for editing audio and video through text. Podcasters and content teams can collect footage, change the order of a story, and deliver the finished work for others to watch.
Form your own approach first, then explore the reasoning to check trade-offs and validation you may have missed. There is no single right answer.
01
DESIGN QUESTIONIntermediate
Make recording and review states clear to a team
Design an async recording collection page for a training team. This is an independent teaching proposal, not an existing Descript interface.
- Scenario. An editor invites three colleagues to record different parts of one tutorial. A has finished uploading, but processing continues. B's recording is playable. C's invitation has expired. The editor may mark B's footage “ready for the video” only after checking its content.
- Constraints. Only successful processing can produce “playable.” “Ready for the video” requires the editor's confirmation. Sending a new invitation does not reactivate an expired link. No response does not mean someone has declined.
- Deliverables. Draw a three-person status list and a detail page. State the next action available to the editor and contributor. Show state changes for one processing failure and one replacement invitation. Compare a single progress bar with separate recording, processing and content-review states, and design an observation task that can reveal misunderstanding.
Explore the reasoning
- Separate facts by participant and stage. The system confirms file processing; the editor confirms whether the content is suitable.
- Check the list using A, B and C. A participant should identify whose footage cannot yet be edited, whose needs a content check and who needs a new invitation.
- Walk through a processing failure and a replacement invitation. Check that the old record remains understandable and the new invitation is not mistaken for revival of the old link.
- Ask a participant to plan the next actions. Record confusion between “playable” and “the video is finished.” Compare the designs on both information load and the cost of mistakes.