What won't change?

I was having a conversation with Dad the other day about Amazon and why they had been such a successful company (more) recently. Our conversation stemmed from a conversation about companies investing in the right things for future growth, which is why Amazon was brought up – because they were famously unprofitable for many years. Now, however, they continue to be one of largest and profitable companies in the world and have some impact on many people’s lives every day. Why is that?

One answer might lie in this interview with Jeff Bezos. In it, he talks about how the main strategic imperitive at Amazon has always been to focus on what won’t change in their business. I thought that was a little counter-intuitive at first, but now think it’s a fairly salient piece of advice for many of us and the problems we’ll face this year. Here’s a good paragraph from the article which articulates it well.

“…I can’t imagine that ten years from now they (customers) are going to say, “I love Amazon, but if only they could deliver my products a little more slowly.” And they’re not going to, ten years from now, say, “I really love Amazon, but I wish their prices were a little higher.” So we know that when we put energy into defect reduction, which reduces our cost structure and thereby allows lower prices, that will be paying us dividends ten years from now. If we keep putting energy into that flywheel, ten years from now it’ll be spinning faster and faster.”

I love the last sentence especially. Just like solving the little problems and moving to the mobile web, it’s continuing to push at the flywheel of change that makes success truly happen in an organisation. And having knowledge about the things that won’t change for your customers is a great place to start pushing.

Robots will do your job. Soon.

Yesterday’s post talked about solving the little problems you might have in an organisation at the beginning of the work you’d really like to do. It referenced a great thread on Hacker News, which had a huge conversation on it that stretched from how people bill for their services to what the difference is between a contractor and a freelancer. I’d like to talk today about what happens when robots can do your job, and what that means for the future of work.

Tim Hwang is the founder of The Awesome Foundation and also the founder of a legal firm called Robot, Robot and Hwang. The two senior partners at RR&H are robots and Tim jokes he’s the junior partner. Tim is experimenting with replacing law work with robots trained to respond and deal with the various issues that a lawyer may face.

This comes out of an experiment Tim and his colleagues have been playing out through the Web Ecology Project. In their main experiment, they randomly select 500 (real) twitter users and then had three teams build three bots to engage with those users. The winning bot would be the one that formed the most real relationships with the human twitter users. Check out this YouTube video interview with Tim to hear more about it.

Talking to Tim about this, it blew my mind. What does the future of the workplace look like when robots can do many of the lower value social things we currently do…not just the lower value physical things which led to the replacement of humans in the manufacturing industry? Steve Sammartino asked a related question in a post recently, with regards to what happens if you don’t radically reinvent yourself and what you’re doing.

To bring this all back to yesterday’s post, it would seem evident that this is only further encouragement to provide extreme value to the people you’re working with. Robot’s can’t, and probably won’t, be able to use intuition and reasoning to help move people towards a more successful strategy or business plan. Humans can. It all comes back to being strategic and providing value, and if you can do this then you probably won’t be replaced by a robot.

Solve the little problems first

There’s an interesting thread going on over at Hackernews at the moment. It’s titled, ‘As a freelancer, how much do you bill per hour?’ What’s great about Hacker News threads like this one, though, is that it has +190 comments on it with lots to take away from people who are experienced and good at what they do. If you’ve ever struggled with the question ‘how much am I worth?’ then check it out. I especially liked this, from j45:

“High Impact Consulting – This book taught me to only do tiny but really painful items for new customers to build momentum. By getting short term, high impact/pain point items out of the way, it clears the table to say “This consultant has learnt my business and why we do things the way we do”. Big projects land themselves. I call it dating before I get married.”

Working on solving ‘little’ problems internally first can be a great way to prove out the value of your approach. Often, the ‘little’ problems once solved are often the ones that create the most positive change in a companies culture. It’s something I hadn’t heard put so well before and something i’ll mull over for the next few weeks or so.

Do your people lobby for what is right?

There’s a great piece on Google Think Quaterly; an interview with Oxfam CEO Barbara Stocking. This paragraph stood out for me.

“…everybody is very committed to the cause. That makes them quite an interesting bunch to manage, particularly in Oxfam where we don’t pay much; people are here because they want to do something about poverty. They have quite specific ideas and corralling them so they work to corporate objectives is an interesting challenge. Quite often people don’t come to me to discuss the pros and cons; they come to lobby me heavily about what they think is right.”

I quite love the idea that people don’t go to her to discuss the simple pro’s and con’s – they go to her to lobby for what is right. It’s a positive form of dissent, which Yammer CEO David Sacks also discusses in this great article in the New York Times. Brilliant.

Learn to code

Learning to write code is fast becoming an important skill for the average knowledge worker. Most people working in communications teams now need to have some ability to translate what they want as close to machine language as they can. That might present itself as simple Markup or HTML, or be more significant languages such as Javascript or understanding how CSS works. As the title of Douglas Rushkoffs book suggests, we will either program or be programed. Today, I’ve noticed some buzz around the new service being offered by Code Academy, called Code Year.

The premise behind Code Year is simple. You subscribe via email and receive a weekly lesson with tasks you can participate in. Fred Wilson is taking it up. Buster Benson is tweeting about it. Paul Graham has invested in it. It’s a brilliant initiative and something I think would be great to take part in.

I begun trying to learn Ruby On Rails last year. It’s something I’ve let lapse a little bit since starting at Yammer as that became my core focus, but I’m excited to be heading to Rails Camp in 2 weeks to scratch up on the skills I learnt at the last camp in June 2011. Learning to code is hard for me. It’s not something that will be on my habit calendar for a little while yet, but a skill I still want to invest in learning more at some point this year.

If 2012 is the year you want to learn how to code, Code Year looks like a great place to start.