rc3.org

Strong opinions, weakly held

Month: June 2014

The expense report

I really enjoyed Camille Fournier’s post about the implications of exercising authority as a manager. In short, being told you screwed up by somebody who can fire you can lead to pretty serious anxiety. She nails it when she says this about her role has the head of engineering:

In fact, it is important that I’m seen as an inspirational figure to my team, someone they look up to and look forward to interacting with, and not vice-versa.

Her post also reminded me of a powerful lesson in management I learned awhile back. I heard a story about why a developer really didn’t like our head of engineering. One time, the executive was approving expense reports, noticed an odd $30 line item on this person’s expense report, and rejected it asking for an explanation. The oddness was easy to explain, and the expense report was ultimately approved, but the fact that the executive had rejected the report rather than giving this person the benefit of the doubt permanently set in their mind that the executive was a jerk.

I took a few things away from this incident. First, you can run into problems doing the right thing. The executive was being a good steward of the company’s money, and questioning the expense wasn’t wrong. Perception was the problem, as it so often is. Secondly, this person had very few interactions with the executive, and so there was no established expectation of trust that may have made this OK. If I’m only going to talk to someone a few times a year at most, I don’t want one of those interactions to be negative, especially with so little at stake.

The third was that people should be mindful of what’s expected of people with their job. Had the executive in question forwarded the expense report to accounting and had them send it back, feelings would not have been hurt. People expect accounting to carefully review expense reports. When an executive does it, it can seem petty or vindictive.

This is one of the toughest aspects of a manager’s job. You have limited chances to communicate with people, and what matters most is the outcome of those communications. Everything you do when managing people ideally helps to do their best work, whether it’s getting them the right keyboard, insuring that they’re fairly compensated, or giving them advice on how to get unblocked when they’re trying to solve a tough technical problem.

If it seems like I’m saying that as a manager, it’s important to be almost painfully deliberate in how you approach communicating, I am.

The dangers of over-reliance on perks

My colleague Melissa Santos and I wrote a piece for Model View Culture about perks and how they can be divisive, in spite of the best intentions of the people offering them. The article really cautions companies about building their culture or even their recruiting pitch around perks, it’s a dangerous shortcut to take.

Melissa has a blog, Allowed to Apply, which encourages people to just apply for things that interest them. It’s a great message. She’s @ansate on Twitter.

How the sharing economy affects workers

The Case Against Sharing

Illustrated piece by Susie Cagle on the effect that the “sharing economy” (think Uber, Lyft, AirBnb, etc) is having on the overall economy. Here’s the bottom line:

The sharing economy has painfully noble goals. But a society and an economics that truly values civic engagement, the commons, and trust between people is one that invests in the protection of those people so they can really prosper, even when something goes wrong.

I would agree that in the presence of a strong social safety net, the sharing economy would look very different. As it is, it looks like a way for rich people to exchange the opportunity for workers to steal some crumbs from other workers in service of shrinking the overall pie.

Google’s software approach to self-driving cars

Alexis Madrigal has written an interesting look at how Google’s self-driving car really works. Google has figured out that rather than building a really smart car, they could instead build a really rich digital representation of the roads on which the car will drive. Obviously there are big questions about whether this approach can be scaled to work for a larger geographic area than Mountain View, California, but I love this approach, which only software engineer would come up with. I agree with the article that collecting and storing large amounts of this kind of data is a problem we understand better than the problem of building really intelligent machines. If this approach to controlling self-driving cars takes off, it also puts Google in a great position to make money licensing data to any company that wants to build them, rather than building cars itself.

© 2024 rc3.org

Theme by Anders NorenUp ↑