Here’s another installment in my FAQ series.
I’ve always had trouble explaining what I do to non-technical people. It’s gotten better over the years, but it’s still a struggle to explain my job.
Usually, the conversation goes like this:
Q: What do you do for work?
A: I work for a big software company.
Q: Cool. What company?
Q: <Blank look>
A: Oracle sells software for businesses.
Q: <Relieved look>Oh. So you write code?
A: No, not anymore.
Or some variant of that. Depending on how much I feel like talking, I might say “I surf the Internet all day” just to bend the person’s mind a bit.
The answers get even tougher when I talk to people in tech. When you say Oracle to the average geek, the immediate assumption is database. After I explain that I work in Apps, it gets even harder to explain what I do here at the ‘Lab.
My answer when I don’t feel like explaining in this case is, “I blog”.
We here at the ‘Lab have very unique and cool jobs. If you’re new here or you’ve always wondered, here’s a brief synopsis of our charter.
We were formed back in April 2007 to explore innovation within Applications. I use the three E’s to remember our original charter:
We spent a lot of time early on explaining what 2.0 is (and is not) and why 2.0 matters. This is an activity of the past now, and everyone seems to agree that 2.0 is important. We probably had very little to do with raising the importance, but we can offer first-hand experience when people ask for further education, e.g. how do I start a blog, what if someone posts porn, how do I start a community, etc.
Again, this activity has changed since we started. Before it was about convincing people that 2.0 matters. Now, it’s more honing the message to what about 2.0 matters, e.g. you can’t always throw a blog or a wiki at a product and says it’s 2.0.
Of course, this is a subjective area where my opinion differs from others. We try to focus on the principles I list further down to keep ourselves grounded.
We always knew that talking would only get us so far. So, from the get-go, we knew we’d need to show people and let them kick the tires. We don’t have all the answers or the domain expertise to say confidently what will work for a particular group of users. Our goal was to provide a sandbox where product teams could get a feel for 2.0 and make that leap themselves.
The light goes on, and someone says, “this would be great for x problem our users face.”
This is why we built Connect. We operated initially as a skunkworks outfit, but those days are long gone.
Update: Dan’s comment points out that I did a poor job of explaining. So, I’ve added some meat to the bullets, expanding them into sections.
We’ve always followed two very simple principles.
- Web 2.0 is about people, not technology (chat, forums, search, blogs, wikis, RSS, tagging, social networks, etc.).
- Execution wins.
Following these principles, we built sites like Connect and Mix to execute on the first two E’s. An unexpected and happy side effect to our work is that people outside Apps used our stuff and got interested and involved in what we’re doing.
As the tide has risen for Web/Enterprise 2.0 over the past few months, we’ve done less innovative thinking and more maintenance and enhancement. So, what I do every day now is very different than a year or even six months ago.
Because I don’t code, which is a good thing for the team, I wear a lot of hats. In fact, my role reminds me a lot of my startup experiences from back in the Bubble.
So, lately, I’ve been saying I work in a startup within the giant behemoth that is Oracle, and in many ways, this is very true. Like a startup, we’re a very small team with many responsibilities. Also, we have to be nimble with our strategy and able to change direction depending on demand for our services.
We have very demanding jobs and work like we’re at a startup. I frequently see mail from Rich and Anthony in the wee hours. I’m actually suspicious SkyNet replaced them with cyborgs sent back through time, since they are rarely offline or not working.
Anyway, we might have the coolest jobs at Oracle, depending on whom you ask. I’ve been at Oracle for 10 years now, in several different capacities, and this is the most fun I’ve had yet, even if it’s the hardest to describe.
Which is why I tell people that I blog.