- An important question to answer first: Are you trying to find fulfilling work, or are you trying to have work that supports a fulfilling life?
- There are a couple of exercises worth doing as you start your discovery of fulfilling work, they are
- Map of Choices - Map out your career thus far and note the primary motivations for each transition, your motivation list: Status, Respect, Talent, Making a Difference, Passions, Money. Then stack rank your motivations based on what you want going forward.
- Imaginary lives - Imagine you have 5 parallel lives, what career does each of your 5-selves have?
- Reverse JD - If newspapers do not have job descriptions but instead of people looking for jobs, what does yours look like? Share this with 10 friends from diverse work backgrounds and see what they’ll hire you for.
- Fulfillment is derived from 1) meaning 2) flow and 3) freedom (or autonomy). This is very similar to the Dan Pink TED talk.
- Now that you have some idea of what careers you might want to try, do these to fast-prototype your ideas:
- Discovery Conversations - talk to people who do the work, learn about it.
- Branching projects - Take a few hours, a day or weeks to try projects in the careers you desire. Do internships, volunteer, or contract for someone.
- Radical sabbatical - Take months to a year off from your current work and do short stints at potential work you want.
- Do the 5 Whys. This wasn’t mentioned in the book, but is an exercise inspired from my Six Sigma quality management training that I found applicable in conjunction with the Map of Choices and the stack rank of Motivations. For each motivation, ask the 5 whys. You might not get 5 answers but go as deep as you can. For example here is my 5-whys map for Talent. Talent —> Feel Useful —> Be included —> Social safety, relevance, camaraderie and friendship. Social safety and relevance had further whys —> survival —> shelter, food, clothes. Turns out the reason I wanted my talent used is because I wanted 1) a sense of camaraderie and friendship, and 2) I tied it to my basic survival. This help me eventually breakdown into source-needs that were more important than the motivations given in the book. Your 5-whys map will be different, but I encourage you to try it.
I greatly enjoyed Ricardo's talk. It was both entertaining and informative. It will change the way you look at life, rules and business.
- "Everyone wants to leave a legacy. But why do you want to be remembered?"
- "If you are giving back you took too much."
- Have a terminal day a week, or two. Imagine if your doctor told you that you had 6 months to live, you'd make a bucket list right? Use Terminal days to strike down that list before the doctor ever gave you the news.
- The opposite of work is not leisure, but idleness.
- Free yourself from the anchor of past achievements so you can start something new. Ricardo burned his life's achievements in a bonfire so that 1) his kids won't have the shadow of his footsteps to haunt them, and 2) he can start anew.
Da Link: http://go.ted.com/QGR
This is a great blog post for Product Manager everywhere written by my colleague Sam. Here are the 5 lessons I learned from it:
- Adding analytics generally involves adding a line of code here and there to fire an event when a user performs an action in your product. Some frameworks for adding analytics events and tracking them include Google Analytics and KISSmetrics.
- Empathy Debt = lack of information about the state of your customer's love (or hate) for your features
- "There’s nothing worse than getting to the end of an experiment and realizing you don’t have all the events you need. Try to do your analysis before you run the experiment using some dummy data so you can see any gaps in what you’re capturing."
- Create 2-3 very different versions of the feature you're trying to test. The key is to keep them very different. Deploy all of them and track results.
- It’s great to be data-informed, but being entirely data-driven can sometimes leave you blind to the overall experience. The data tells you how they are behaving but not why, so talk to the users as well to get a rounded picture.
As a Product Manager, a common challenge I come across is helping people see the big picture. It is common for someone to be so close to the detail that it becomes unnatural to step back and see the point of it all. This HBR article explains some useful techniques to help someone see the forest for the trees.
- Imagine physical distance
- Imagine separation in time
- Imagine it is not you involved, but a stranger
- Imagine the outcome is uncertain.
Ability to see the big picture is a valuable skill. Not only does it make what one does everyday become more meaningful, it also helps with communication since stepping back requires one to take in other points of views.