What a 72-Session Unconference Taught Us About Running a Construction Project

Every spring, a few hundred developers, designers, makers, and assorted tinkerers descend on a venue in Bordeaux with no agenda, no keynote, and no idea what the day will look like. We watched the chatter around the most recent edition of Barcamp Bordeaux with mild curiosity — and then a reader, a project manager at a mid-sized general contractor in the Gironde, sent us a note that reframed the whole thing. He had spent two days at the event, and what stuck with him wasn't a talk. It was the scheduling wall.

The setup: an agenda that doesn't exist until the doors open

The format is simple to describe and brutal to execute. Attendees propose sessions on the morning of the event, slots get placed on a grid in real time, and the schedule is whatever the room decides it is. Organizers describe it as an unconference, and the numbers back up the ambition: 400–600 participants, up to 72 sessions chosen in real time, free entry, and no sponsored keynote. Nothing is locked a month out. Nothing is protected by seniority. If the room wants to talk about something, it happens.

Our reader, who we'll call the PM, runs commercial fit-outs. His world is the opposite: a baseline schedule approved weeks in advance, subcontractors sequenced to the day, and a change order process designed to keep surprises contained. He expected to find the unconference charming but irrelevant. He came back with a different conclusion.

Decision point one: who gets to move the schedule

The first thing he noticed was that the grid is not controlled by a single authority. A session gets proposed, a slot gets claimed, and if two topics overlap badly, the people in the room negotiate a fix. No one waits for a director to approve the reshuffle. In construction terms, that's closer to a foreman adjusting a daily log than a formal change order — and most of the time, that's the right instinct.

Where it gets interesting is the exception. When a session genuinely can't be resolved locally, it gets escalated to the organizers, who arbitrate in minutes. That's the pattern the PM took home: let the field resolve the routine, escalate only the structural. On his next project, he stopped routing every minor sequencing conflict through the office. His RFI volume for the first month dropped by roughly a third, and the ones that remained were actually worth answering.

Decision point two: the difference between a real change and a rearrangement

An unconference runs on a hard distinction. Moving a session to a bigger room because 80 people showed up is not a change — it's logistics. Cancelling a session because the proposer never arrived is a change. Getting that boundary wrong in either direction kills the day.

Construction has the same fault line, and it's where most paperwork problems start. A finish trade showing up a day late is a daily log entry. A finish trade showing up a day late because the client added a wall is a change order. Teams that blur those two end up with a change order log full of noise and a payout cycle nobody trusts. The unconference crowd, without ever using the phrase "change order management," had already solved the classification problem by making the rule public and applying it consistently.

Obstacles: the wall is the bottleneck, not the people

By mid-afternoon, the grid gets messy. Sessions collide, rooms overflow, and someone always wants a slot that doesn't exist. The organizers' response is not to add capacity — it's to keep the wall visible and current. Everyone can see the same board at the same time. That single design choice prevents most of the arguments before they start.

We've seen the opposite on job sites far too often: the schedule lives in one person's head, the field works from a printed sheet two revisions old, and the office works from a spreadsheet that was updated an hour ago. The result is not laziness. It's a visibility failure. Barcamp Bordeaux reports up to 72 sessions chosen in real time, and the reason that number doesn't collapse into chaos is that nobody is working from a private copy of the board.

Measurable results

The PM ran a three-month experiment on a 14,000-square-foot tenant improvement:

• RFIs in the first 30 days: 31, down from a 45–50 baseline on comparable jobs.
• Change orders logged: 9, with 6 of them classified as genuine scope changes rather than scheduling noise.
• Daily log entries per week per supervisor: steady at 5, but with the escalation flag used 40% less often.
• Closeout punch list walk: completed in a single day, versus the two to three days he'd budgeted.

None of that came from new software. It came from copying a rule that a free, volunteer-run tech event in the Sud-Ouest had been stress-testing since 2011. The tooling just made the rule cheap to follow. If you want to see how the format is documented — and why the wall matters more than the talks — the organizers' own pages are a good place to start: how the unconference format is organized.

What we're taking from it

The lesson isn't "run your project like a conference." It's narrower and more useful: publish the rule, keep one visible source of truth, and let the people closest to the work resolve anything that isn't structural. The unconference format has been iterating on that idea for over a decade with no budget and no keynote. A construction project with a real budget and a real contract can afford to steal it.