Your job vs. your project
Jobs are finite, specified and something we 'get'. Doing a job makes us defensive, it limits our thinking. The goal is to do just enough, not get in trouble, meet spec. When in doubt, seek deniability.
Projects are open-ended, chosen and ours. Working on a project opens the door to possibility. Projects are about better, about new frontiers, about making change happen. When in doubt, dare.
Jobs demand meetings and the key word is 'later'. Projects encourage 'now.'
You can get paid for a job (or a project). Or not. The pay isn't the point, the approach is.
Some people don't have a project, only a job. That's a choice, and it's a shame. Some people work to turn their project into a job, getting them the worst of both. If all you've ever had is jobs (a habit that's encouraged starting in first grade), it's difficult to see just how easy it is to transform your work into a project.
Welcome to projectworld.
More Recent Articles
- "Um" and "like" and being heard
- Try better
- On knowing it can be done
- A ten-year plan is absurd
- Neophilia and ennui
[You're getting this note because you subscribed to Seth Godin's blog.]
Don't want to get this email anymore? Click the link below to unsubscribe.
Click here to view mailing archives, here to change your preferences, or here to subscribe • Privacy