Conversation not discussion

It's a while since we had a 'conferences are broken' rant on the Agile blog!

Five or six of the sessions at this year's conference were... different. I already mentioned the Value In Geophysics session, which was a cross between a regular series of talks and a panel discussion. I went to another, The modern geoscientist, which was structured the same way. A third one, Fundamentals of Professional Career Branding, was a mini workshop with Jackie Rafter of Higher Landing. There were at least a couple of other such sessions.

It's awesome to see the societies experimenting with something outside the usual plethora of talks and posters. I hope they were well received, because we need more of this in our discipline, now more than ever. If you went to one and enjoyed it, please let the organizers know.

But... the sessions — especially the panel discussion sessions — lacked something. One thing really:

The sessions we saw were nowhere near participatory enough. Not even close.

The 'expert-panel-enlightens-audience' pattern is slowing us down, perpetuating broken models of leadership and hierarchy. There isn't an expert in Calgary or the universe that knows how or when this downturn is going to end, or what we need to do to improve our chances of continuing to contribute to society and make a living in our profession. So please, stop throwing people up on a stage, making them give 5 minute presentations, and occasionally asking for questions from the audience. That is nothing like a discussion. Tune in to a political debate show to see what those look like: rapid-fire, punchy, controversial. In short: interesting. And, from an organizer's point of view, really hard, which is why we should stop.

Real conversation

What I think is really needed right now, more than half-baked expert discussion, is conversation. Conversations happen between small groups of people, all sitting on the same plane, around a table, with napkins to draw on and time to draw on them. They connect people and spread awesome ideas like viruses. What's more, great conversations have outcomes.

I don't want to claim that Agile has all this figured out, but we have demonstrated various ways of connecting scientists in meaningful ways and with lasting outcomes. We've also written extensively on the subject (e.g. here and here and here and here). Other verticals have conducted many more experiments, and documented the results. Humans know how to do this.

So there's no excuse — it's not too dramatic to call the current 'situation' a crisis in our profession in Canada — so we need to get beyond tinkering at the edges and half-hearted attempts at change. Our societies need to pay attention to what's needed, and get on with making it happen.

Still more ranting...

We talked about this topic at some length on the Undersampled Radio podcast yesterday. Here's the uncut video version:

Your next employment contract

You own your brain. The hackathon we're hosting has reminded me of this. 

More than one person has expressed difficulty with reconciling their wish to participate in the event with their employment contract, which probably says something like this:

Everything you do belongs to us.

Your family photos belong to you

Yesterday I read something about US government intellectual property. I knew that most government content is free of copyright, and what I read confirmed it. It's a sort of mirror image of the situation we have in industry (this is from ACQuipedia): 

Works created by Federal employees in the course of their official duties are automatically in the public domain and may not be copyrighted by anyone.

Interestingly, works not created in the course of their duties are their copyright as normal. So a soldier's photographs on her cellphone are her intellectual property, even if they were taken on duty (provided she's not a photographer).

Our community should stand up for something resembling this same rule in the corporate environment. Of course works created in the course of your duties as an employed geoscientist or engineer belong to your employer. But clearly your family vacation photographs do not. And just as clearly, your edits to Wikipedia articles do not (unless that's your job, you lucky thing). And neither, with certain provisos, do your contributions to a hackathon.

What provisos? Well, there are other, equally important clauses about confidentiality in your contract. You may not legally disclose the company's proprietary intellectual property. So you can't show up at a hackathon and code up your company's latest migration algorithm. But coding up a new, previously unknown algorithm would be ethically OK, but if you're a geophysical programmer I can see the potential conflict there — it's a judgment call. I hope your company trusts you to make a fair decision. If the algorithm turns out to be awesome, and had 3 collaborators from different companies, then I say they should all be glad you got together to invent it. Innovation is not a zero-sum game.

Shop rights

It turns out that there's a common law provision for the ownership of your brain. So-called shop rights are generally upheld by courts, at least in the US. According to an excellent guide to IP from the IEEE, they go like this (there are variants):

  1. confidential information and inventions or other creations made during the course of employment as a normal part of job duties belong to the employer
  2. inventions made by the employee off the job, using the employee's own time and materials, will generally belong to the employee (absent fraud, related inplant work of which the employee might be aware, or other special circumstances); and
  3. inventions not related to work duties, but created with some nontrivial use of the employer's time, funds or materials still belong to the employee, but the employer has limited rights to exploit the invention without payment of royalties or other compensation.

Awesome! This is perfectly sensible. Unfortunately, employers can write almost anything they like in their contracts, and it sounds to me like clauses that trample on these rights are fairly common. And they will continue to be common until people start refusing to sign contracts that contain them.

Demand change

In light of all this, here are 3 things to demand (yes, demand — you do actually have some bargaining power when someone tries to hire you) in your next employment contract:

  • At the very least, clauses limiting your shop rights should be removed. In their absence, conflicts will be resolved by the application of common law.
  • You may contribute to Wikipedia, SEG Wiki, PetroWiki, SubSurfWiki, and other open content projects.
  • You may contribute to OpendTect, Madagascar, and other open source software projects.
  • You may contribute to unstructured events, including but not limited to unconferences, hackathons, and idea jams. 

Bottom line: your employer owns some of your creations, specifically the ones you make for them, at work, with their data, their tools, their employees, and their ideas. But you own the rest, and you emphatically own your creativity.

Changing how we are employed is entirely up to us. Legal professionals will pin us down to the bare minimum of openness and freedom otherwise — it's their job. So push back, ask for change, and retain your brain.