Getting your dream job

How do you go about getting your dream job? Do you even know what your dream job would be?

Well, here’s something that may help. There’s a great comment thread (both good and bad) on Lifehacker in response to their query on tips for getting your dream job.

Maybe you can find something there that helps get you on your way? You need to find something that makes you happy. Even if it’s simply the pursuit of the dream.

Posted in Career, Tips | Leave a comment

How valuable is talent? More valuable than experience?

I’ll keep this short, because there is plenty to read after the jump. Enjoy.

Talent vs. experience?

And, if you like, c’mon back and share your views.

Posted in Experience, Talent | 2 Comments

Are you asking why or are you asking when?

Most of us get into a groove. And we think we know what we’re doing. We think the people around us know what they’re doing. And we begin to trust in the greater good. We begin to get ever so lazy. We think that people have out best interests at heart.

But you see, that’s not always the case.

I’m a big fan of arguing “can versus should.”

That argument? Just because you can do something doesn’t necessarily mean you should do something. Or as the quintessential parents always say, “If Billy jumped off a bridge, would you?”

Well, I’ve now happened upon yet another testing phrase: Why versus When.

You see, urgency is a huge driver in business. Huge.

We live in a fire drill existence.

Do this. Get it done. We need it by the end of the day. The people are coming in next week. The client wants it now. The CEO has to present this to the board. The event is going to be here before you know it. We need to report to the Street. Get the early-bird discount. Book early. The Web site needs to be updated. The code has to ship.

Now. Yesterday. Get it done. Now. Did I mention we need it now?

Here’s the thing: If you’re always asking “when” something needs to be done, you’re not asking “why” it needs to be done.

And that can be scary. It takes guts to tell everyone to stop and think. Especially when it’s your superiors. The people you trust. But you have to work to do it.

Why? (I’m so glad you asked!)

If you spend more time asking “why” something needs to be done, then you may discover:

  1. It doesn’t actually need to be done, at all.
  2. It isn’t as urgent as everyone thought.
  3. It is actually counterproductive to another–more critical–effort.
  4. It would be more powerful if combined with another activity.
  5. It hasn’t been well designed, thought through, or planned.
  6. The urgency is misplaced.
  7. The urgency is a symptom of a larger problem.
  8. Your boss is telling you its urgent because s/he asked “When?” instead of “Why?”
  9. It would be better to take a different tact.
  10. No one knows why it is urgent.

And here’s another tip: “Because [name] said so!” isn’t a valid answer.

I’m willing to bet that 90% of the fire drills you’re currently chasing don’t need to be fire drills. And I know you know that.

But start asking “Why?” It may not resolve the problem, but it will start illuminating the environment in which you work. And it will give you a better understanding of what drives the business.

And it will give you more context as to whether the urgency is moving in the right direction or is misplaced.

Or if you’re misplaced.

Because when it comes right down to it, the half-ass work that gets cranked out under duress is going to be your work. Not the people pushing you to do the work. Your work. And the urgency is never a decent recursive excuse.

“But don’t you remember we were in a big hurry?”

Nope. That becomes “No, I don’t remember that, but I do see that this reads like crap,” or worse yet, “Well, why didn’t you plan ahead?”

And that’s the one “Why?” you don’t want to get.

Posted in Can vs. Should, Corporate Culture, Fear, Uncategorized | 1 Comment

I have a strange feeling that this game just might appeal to you

There’s just something about this plucky little asteroid taking on the more powerful ships that I thought would appeal to you.

You plucky little rock you.

(Nod to Plastic Bag for both the link and the “plucky.”)

Posted in Fun | Leave a comment

Job hunting sucks

And according to Techcrunch, the job-hunting sites are keeping true to the effort by sucking, as well.

Okay, the fact that job sites are largely ineffective isn’t really news. But the head-scratcher here was that these things have been around for 10 years.

10 years!

Doing exactly the same thing–by and large–that newspapers have been doing for decades and decades. Today’s job hunting sites have been trading dead trees for pixels, but not really improving the process.

Do you have an idea for improving online job searches?

Let’s hear it.

Posted in Career, Employment, Online | 6 Comments

Product management is everything and everything is product management

Now, I’m no expert in product management. But let’s be honest, if we sat around and waited for me to write only on things at which I am expert, we’d all be in for a long, cold wait. So, all of that aside, I do know a number of good product managers. I’m even luckier to know a couple of exemplary product managers.

And because of that, I’ve gleaned–at a very high level–some insight on product management. I mean, I’ve spent a lot (a lot) of time sitting in product management meetings and listening. My primary contribution to product management meetings?

  • Meeting #1: “When are we scheduled to launch? What’s the date?”
  • Meeting #2-#999999: “Does that affect the launch date? Is the launch date slipping?”

Yes, vital component. That’s me.

But it’s good. Because when I keep my trap shut, I actually listen, so I’ve managed to pick up a few things here and there.

And here’s where the worm begins to turn.

So, the other day, I’m staring off into space, thinking about product management, and this occurs to me: Everything is a product management problem.

Let me outline some of the high points:

  • Time line / Road map / Life cycle. Every product has one. The really good ones detail the life of the product, from conception through demise. On it, you can see every upgrade, every feature, every release, every date. Everything that will happen to that product. This is the plan. For the entire product. Everything that happens occurs here so that it can be seen in the context of the product life.
  • Trade offs. This is the product manager’s preeminent skill. Everything in product management is a series of trade offs. When is that resource available to build that functionality? Regardless of when that functionality is built, when do we release it? What does the market want? What does the company want? What do we do to incorporate this last minute requirement? How do we retool based on the usability tests? Everything is a balancing act for the product manager. You can’t do everything at once. And you can’t do everything before launch. It’s a constant game of ready, fire, aim. What is attainable versus what is necessary.
  • Resource management. Once locked, loaded, and focused on target, how do we manage the resources at our disposal? Are we going to wedge in some additional functionality while we have engineering cycles? Are we going to bring in outside help to get us through this rough patch? Can we rely on a single engineer to bring everything to fruition? What if that person falls ill during QA? How much do I have to spend to get this done? Can I buy time?
  • Translation. The product manager is a Rosetta stone of sorts. Sitting somewhere between the business aspects of having a product and the labor required to bring that product to fruition. In high-tech, as an example, engineers don’t generally want to hear about the business reasons behind feature #479. They want to know the spec and they want to know what technology is at their disposal to create the feature to spec. Conversely, the CEO generally couldn’t really care less if you’ve created an AJAX implementation or used C#. S/he wants to know if the customer will be jumping for joy or throwing up all over it.

So taking those high-level points, shouldn’t we all be product managers?

I mean, couldn’t your career use some product management? A time line? A life cycle? An attainable list of features and functions to be launched at specific intervals? What does version 3.5 of your career include? Is it Windows and MacOS compatible? Where are your feature/function gaps that could move your career forward or doom it to inadequacy? What features do you want versus what functions does the business want? What happens when a competitor enters the market?

How’s your usability?

Think about it.

Posted in Career, Goals, Growth, Product management | 4 Comments

Coming out of the garage

And apparently into the cafe.

Web Worker Daily points us to a growing trend for startups.

For those of you with that entrepreneurial bent, rejoice! You are no longer relegated to the garage. No more secret startup. Now, you can be out in the open in your favorite Starbucks, rattling off your overly-caffeinated ideas among the seething mass of work-a-day types.

Cafe’s are a great place to not only work comfortably, and a little cheaper, but a place to strike up conversations with individuals that could quite potentially have complementing products or services, or lead you in the right directions to improve, or sell your offerings.

Posted in Autonomy, Culture, Entrepreneur, Productivity | Leave a comment

Why should this outlook be particular to startups?

Happened upon Andy Monfried’s You ain’t gonna learn what you don’t want to know when I was pointed to the post Value creation in a startup.

Two things occur to me:

  1. Andy can craft a meandering rant that rivals even my best attempts, and for that, I have nothing but the deepest respect. Especially because he seems to do it out of excitement, where I seem to do it out of anger. To each his own.
  2. His views can be–and probably should be–applied to any company.

This little passage is what sparked point 2, above:

That’s not life in a start-up internet company.

No matter how hard you work, there is no guarantee of anything. There is no guarantee of a job in the months ahead, no firm placement of a where your office may be, and certainly no perks that established companies have.

Shouldn’t that be life in any company?

Posted in Accountability, Corporate Culture, Value | Leave a comment

Media Temple experiencing some technical glitches

Apologies for the outage(s). Media Temple is working to rectify the problem.

Posted in Online | Leave a comment

Job titles should define the problem not the solution

Cameron Moll of Authentic Boredom was taking a look at the recent job listings on his site. And he’s provided some analysis of his review.

My favorite? The second bullet under the analysis. Specifically:

In today’s job market, I question the usefulness of such vague titles as “Web Designer” and “Web Developer”. While that may be the official nomenclature supplied by the HR department, it doesn’t seem to facilitate job seeking, especially on targeted job boards.

This is right in line with a point Toby made, earlier: Job postings should be solving a problem, not filling a position.

Filling a position is not solving a problem. Telegraphing the specific position is treating people like parts. Treating people like parts will never get your business where you want it to be.

Again, (not to continually thump the Jim Collins theory but…) get the right people on the bus and then figure out where they sit.

Posted in Bus, Communication, Employment, Recruiting | 3 Comments