No meetings, no Jira, no text threads... and it shipped anyway.
A team successfully shipped a project in 10 weeks by eliminating traditional project management structures entirely—no meetings, Jira, documentation, or text communication. Instead, they relied solely on a 24/7 Zoom room where team members could work synchronously and asynchronously as needed.
Summary
The speaker describes an unconventional development approach that inverted the typical project management philosophy by defining the process through elimination rather than addition. The team removed all standard artifacts and communication channels: no scheduled meetings, no asynchronous text threads, no design files (Figmas), and no issue tracking system (Jira). The only structured element was a persistent Zoom room that ran continuously throughout the 10-week project. Team members had flexibility in how they used this space—some stayed in the room all day working quietly, while others popped in and out as needed. The only documentation produced was a single whiteboard. When external stakeholders or other team members asked for documentation about how the system worked, the speaker found humor in simply stating they had none. This minimalist approach seemingly contradicted conventional wisdom about documentation and process, yet the project shipped successfully.
Key Insights
- The team defined their build process by what they explicitly removed rather than what they added, eliminating meetings, text communication, design files, and issue tracking entirely.
- A single always-on Zoom room served as the only structured mechanism for the entire 10-week project, allowing flexible participation where some team members stayed continuously while others joined as needed.
- The project produced only a single whiteboard as documentation across the entire 10-week development cycle.
- External stakeholders frequently requested documentation on how the system works, revealing a disconnect between this team's practices and standard industry expectations.
- The speaker expressed pride and amusement in explicitly telling people the team had no documentation, suggesting this was viewed as a feature rather than a deficiency.
Topics
Transcript
[0:00] Our build process was more defined by what we didn't do versus what we did. We actually just zeroed everything out. We had no meetings. We had no text backs. We had no Figmas. We had no Jira board where we tracked stories or tracked work. We had nothing. We just had this Zoom room that's going 24/7 and some people like to honestly stay in there all day and just like do their [music] work. They just sit there quietly. And some people will like kind of pop in and out when they need something. That was the only structured thing that we had was this [music] Zoom. And that [0:30] whiteboard was like literally the only documentation…
Full transcript available for MurmurCast members
Sign Up to AccessMore from How I AI
GPT-5.6's video editing via Codex is genuinely one of my favorite new workflows
A product manager describes using GPT-5.6 with Codex to automate video editing for social media clips. By simply dragging a file and providing natural language instructions, the AI generated five polished, fast-paced hype videos from a long conference talk recording, dramatically reducing the time-intensive manual clipping process.
Theoretically Intelligent vs. Practically Effective: Why GPT-5.6 Sol Beats Fable for Product Work
An executive contrasts two AI models (Fable and Soul/GPT-5.6 Sol), arguing that Soul is superior for product work because it prioritizes practical effectiveness over theoretical intelligence. The speaker values the ability to ship products to customers and understand end-user goals over theoretical sophistication.
Build a harness when the same workflow needs the same setup and the same outcomes, every time
Building a harness for repetitive workflows allows you to be more prescriptive about job execution, resulting in greater efficiency, consistency, and better outcomes. Rather than explaining requirements to an AI agent each time, a harness lets you use a simpler interface like pasting a link while the agent already understands the intended task.
GPT 5.6-Sol vs. Claude Fable: Why OpenAI’s new model crushes my benchmark
Claire Vo compares OpenAI's new GPT 5.6 models (Soul, Terra, Luna) against Claude's Fable using her custom "How I AI" benchmark, finding that GPT 5.6 Soul excels at practical product work, prototyping, and natural communication, while Fable is theoretically intelligent but pedantic and difficult to collaborate with.
Context offloading is an underrated AI use case
The speaker highlights context offloading as an underrated AI use case, where AI serves as a safety net for routine cognitive tasks like email management and personal finances. Rather than adding new capabilities, AI reduces anxiety about missing important information or making mistakes by handling monitoring tasks, thereby freeing up mental bandwidth.