Carbon Capture via GMO Bananas

The prompt was to find something interesting at the intersection of carbon capture and synthetic biology. We already knew it before the hackathon started, which meant we could get a head start.

We landed on genetically modifying banana plants to absorb more CO2 than they naturally would. Bananas are fast-growing, tropical, and globally cultivated at massive scale, making them a plausible delivery mechanism for enhanced carbon uptake if the biology could be made to work.

The night before our working session, we mapped each team member's skills and assigned roles accordingly. It sounds simple, but deliberately aligning strengths before starting saved us significant time. Rather than figuring out who does what while the clock is running, we started executing immediately.

Once together, we used a structured research sprint: set a timer, go wide, stop. Whatever we found was our working set. This forced us to synthesize from a fixed information base rather than spiraling into endless research. The constraint made us more decisive.

We allocated about an hour to the presentation itself, balancing visual design with the actual research. Time-boxing each phase kept us from over-investing in any one part.

The core argument: a genetically engineered banana plant that fixes more atmospheric carbon per hectare than current varieties, deployed at scale across existing agricultural land without displacing food production. The technical feasibility was the open question, which is exactly where we wanted to push the conversation.

---

Outcome: Developed and presented a synthetic biology carbon capture concept: engineered banana plants as a scalable CO₂ sink deployed through existing agriculture.

What I took from it:

• Assigning roles before you start, not during, is one of the simplest habits that saves the most time. We hit the ground running because we weren't still figuring out who does what when the clock started.
• Structured time-boxing (set a timer, go wide, stop) produces cleaner synthesis than open-ended research. The constraint forces you to work with what you have instead of chasing the perfect source.
• Knowing where your argument is uncertain and leaning into it is stronger than pretending you have all the answers. The technical feasibility was our open question, and making that explicit made the pitch more credible, not less.