Let’s say you’re hired to build websites. sure. You’re hired to build websites. But as Horace Dediu (podcast) points out, a lot of what we need to look at is the “Jobs to Be Done” and when you look at it in that perspective, your Job to Be Done is really to solve their communication issue.
That’s right. You’re not building a website, but communicating information. Be it “This is good” or “That is bad”, or just “Buy this widget”, the job you are doing for your employer is helping them to disseminate information.
If you get up every day, build exactly what they tell you to build, exactly the way they say, there’s two very, very real possibilities of what is happening:
- You’re viewed as nothing more than a production worker
- You’re terrible at actually solving the problems given to you, and thus become #1
Sure. You have to be able to make things pretty to be a designer, and you have to be able to code to be a programmer, but you have to be able to problem solve to be effective at either.
So, what do you do if you decide you’re terrible at your job?