Companies Should Pay for Their Employees to Attend Conferences
netmeister.org
netmeister.org
There are many things that employers could provide that "can't be measured in dollars" that would result in bankruptcy. In order to back up the claim implied by the headline, this article really would need some sort of cost/benefit analysis, which is not provided.
Your employees could learn advantageous and/or competitive information from talking with people at the conference. They will bring this back to you and ask for a raise when it turns out it's a bonus for everyone, but that's what we want, right? Maybe it's important enough that you get to pitch the new thing to the CEO and you get a raise as well. Everybody wins.
My old accounting professor use to say, "You get what you measure".
You can have a great culture among people with a high propensity to want to try new and different things every few years.
Yes it could happen - but mostly it doesn't. Particularly if we're talking about engineers in tech.
Keynote is such a minor part of attending a 2 day conference that 10x is a conservative estimate.
Edit: And that's just "things learned" that doesn't even count the 20-30 conversations had that can spark collaborative efforts.
Keynote is minimal.
I don't think the OP was suggesting you hire the keynote speaker to come, deliver their keynote and leave. The point is that you could do a lot more than that.
Don't think of it as education. Think of it as spies debriefing the station crew at the embassy.
I'm not sure developers are naturally skilled at parsing presentations (done by other developers, who also often aren't fantastic presenters) into meaningful presentations to give back in the office. Not that conferences aren't worth it, I'm just not sure they're worth it for that.
Those employees are representing the company when they attend, network, and quite possibly sell the company's services or products to others that they meet.
If those employee have speaking spots (they're speaking at the conference), then the company has an even better chance at getting the company's name out there in front of a lot of people. In that case, the company can benefit even more when it comes to branding and other benefits that speakers give the company.
You also lose out on the (IMHO) most important and useful part of conferences: the hallway networking.
I'm unlikely to learn anything from the conference that I couldn't learn on the web, and almost certainly not enough to justify the expenditure of time.
Plus, a round-trip flight crossing a couple of time zones would probably double my carbon footprint for the year.
The first thing in networking is showing up. The second is following up.
Also, in context of "companies should pay for their employees", none of the experiences you note benefitted the company. If you had left the company because you met a new connection at a conference, not only would the employer be out $3K to send you to the conference, they'd be out $50K or more to hire your replacement.
Sure, except that I'm far from an extrovert and that's exactly why I like conferences: I find it incredibly difficult to network and a conference provides a nice, safe, closed environment for me to do so regardless.
Also, in context of "companies should pay for their employees", none of the experiences you note benefitted the company
Absolutely. I wasn't really relying in the context of the article but rather as a counterpoint to not finding personal value in conferences. I've went to almost all conferences I've been to on my own dime, so I obviously wasn't there to benefit my employers.
Entrepreneurs conference? Can't build that start up on your own. Sales conference? You'd be derelict in your duties if you are not networking over every possible shill you can.
But programmers? Well. We're just expected to glom into some dark corner and crank out code, right?
I genuinely think this is how many people outside dev think.
But for me, the obvious reason to attend is to network with other developers. Whether your company sees that as useful or not will probably determine if they spring for it.
So... yes even programmers need people. :)
I've found it very useful both to attend and to learn from those that attended, particularly when I can get the highlights (and potentially new ideas!) of a conference I'd never attend personally.
In my experience, this is because most conferences are actually trade shows. But they aren't called that, because organizers want to disguise the fact that they want to use the event to sell products and services, rather than to teach to and train attendees.
IMO, the value of conferences is:
- It's a work-related break from work (read; easy to justify). Most conferences are pretty fun to go to, assuming you don't just rock up for the talks and then hide in your hotel afterwards.
- Networking. If you're at a conf, go and talk to people. It's amazing what you can get done just with a few conversations.
- You WILL learn stuff, and not necessarily JUST what you came there to learn. I'm yet to come back from a conference without at least 4 or 5 new ideas.
- You'll have the chance to talk to people who know a hell of a lot more about product/tech XYZ, and there's a good chance they're being paid to stand around and answer your questions.
- If you want certs, exams are often cheaper at conferences and there's nearly always some cram/lab sessions being run beforehand.
Ultimately, the value of a conference is somewhere between buying ping pong tables and Xboxs for the break room, and hiring a guest speaker for a few days - it's as much of a hearts and minds exercise as it is a learning and development one.
EDIT: Formatting
At one small conference I attended, most companies were represented by one or two people, maybe a CXX and a bizdev guy. Our company had a couple dozen people there. The attendee list was published, and it was kind of embarrassing when they acknowledged our presence during the intro remarks because it basically told everyone what a joke of a company we were. The only reason my team was there was so that my boss could add more make-work to put in his quarterly report while earning points from his team for being that "good boss" that supports employee development. It was such a mismanaged mess at that company that they even paid for a team of contractors to take a paid week off to attend a conference, mostly so that they could pad their resumes, since none of that knowledge was actually applicable to the project they were on.
At my next job, people were too busy trying to hit their goals to pitch their boss on conferences in Vegas.
Conference attendance can provide benefits to employers under the right circumstances, but if I had my own company and an employee initiated a request to attend a conference, I'd insist that he have some skin in the game--he'd either have to take vacation days, or if it counted as work days, he'd have to pay for a significant part of the travel/registration costs himself. If he's not willing, then it probably wasn't worth much to him anyway.
you have a great contributor. someone who does a substantial amount of work and has come up with enough novel stuff to get a paper published in the field.
they go to the conference, and no you don't get their output for a few days...except some work on the plane and some nights at the hotel
but they give a great talk, and learn about a bunch of new exciting things in their field to bring back with them. every time someone talks to this person and is impressed by their work, the name of your company gets associated transitively
when the people at the conference think about a new job, or using a product in your space, they implicitly think 'foo co - thats a great place doing really cool stuff'
Obviously for any of these scenarios to work you need an employee that wants to learn, and an employer who is willing to invest in their employee's growth.
Why would you hire someone as an employee if you don't trust them not to abuse company resources like that? Their "skin in the game" is that they're your employees.
It sounds like those places with negative correlation had other problems. I'd say correlation not causation.
Someone else was saying that they are stealth trade shows but I'm not sure even that is true for a lot of conference because honestly I don't think that many of these events do either very well. There are some that still focus on quality content where the material and the attendees are much more beneficial, but the conferences with the weak speaker line ups are a waste of money and in some communities it feels like we have too many conferences, many of which are not providing real value to companies for the money and time spent.
It's one thing to have a conference with intense technical material that has some interesting hallway convos during breaks and socialization in the evening. But many of these lower quality events feel like we have a bubble in this space. I'm saying this as someone who has spoken at a decent number of conferences and as an organizer 3 community based (not for profit) conferences. Or put another way, there are some that are worth it, but a lot more that are a waste of time.
- It's a perk.
- It's a chance to clear your head.
- You get to meet a lot of interesting people, chat to them about what they're doing.
- It's not the same as watching the videos. You can interact with the presenters after their talk. You can discuss the topics with others. Your time is 100% on the topic at hand.
- It shows the company really cares about professional development. They're putting their money where their mouth is.
- It shows trust in employees not to abuse this.
- Conferences help create a sense of community in the industry.
It's not something I do often, go to conferences, but it's nice to have the company's support if you want to.
Tanstaafl...
As for events, it really depends on the event and your role. If your job in part involves working with partners, communities, etc. then F2F interactions with many of those people may be important. Many people also enjoy attending such events but they're usually not (and shouldn't be) complete boondoggles.
1. Always support your employees speaking at conferences if they've been invited/selected, and make sure they rep your company on conf materials (which is usually the norm).
2. For merely attending the conference but not speaking, make sure there's a concrete justification. Examples:
- Someone you know will be at the conference is on your med-long term recruitment list, but no one at your company knows them in person yet. An impromptu meeting at the conference or afterparty along with a discussion of (and demonstration of your appreciation of) their work gets you on their radar much more effectively than a recruiter could.
- Similar rationale for people or companies you think might be valuable to collaborate or partner with.
- The conference presentations and/or workshop sessions deep dive into some topic of direct relevance to your core business, and provide enough info that employees who attend can apply it immediately upon returning.
3. Make sure the people you send are appropriate for the conference. Send your engineers to highly technical/academic conferences but not the business-oriented ones. Send your sales people to sales conferences. Etc. Be on the lookout for conferences that look highly technical but aren't actually.
4. Consider limiting the number of non-speaking conference attendances per year per employee that the company will pay for, around 2 to 4. This forces employees to choose carefully, prioritize the most valuable ones, and get as much out of them as possible.
5. Consider requiring the attending employees to provide a post-conference writeup detailing and informing other employees what they learned. Again this keeps them focused on extracting value rather than having a mini-vacation.
Or at least I'd attend way more of them.
There's a comment here about how conferences are great to help your developers make connections in industry. That seems like a mixed bag -- why should companies help their best developers to find their next job somewhere else?
There's an interesting Econtalk episode on the book "Learning by Doing" where this came up:
http://www.econtalk.org/archives/2016/05/james_bessen_on.htm...
[To summarize: when the textile mill was invented, skilled individual labor became much more valuable (because skilled workers were much more productive), but wages didn't rise much over a period of 50 years. This finally changed with the introduction of interchangeable parts in machines, which made job skills transferable, which allowed skilled employees to demand higher wages from their employers.]
I only go to them because my company pays for them and I can find conferences in cities I want to visit. As an industry we're likely wasting billions on conferences where people just hang out and network with people who can find us better jobs.
I actually tried to stop going to them, but my boss insisted because he doesn't want the budget to get cut.