As I've written before, I think that one of the most important skills one can have is basic competence. It doesn't sound as appealing as programming, writing, or engineering, but it's a rarer skill, and thus more valuable.
Most skills are clearly defined and can be easily taught, which makes them easy to commoditize. Competence, like social skills, is something that's less easy to define and teach. It's more of a personal exploration.
I define competence at the ability to get an undefined task done in an efficient manner. The skills that go into that are primarily time management and ability to learn. Someone who is very competent can take a random task in a field in which he's not an expert, figure out how to get it done, and then complete it. He won't be able to do it as well or as quickly as an expert, but that's not the point. The point is to not be totally helpless when working outside of your comfort zone.
So what does it take to be competent?
You start with confidence. If you don't believe that you can complete the task, you'll get flustered or sabotage yourself and will either give up or do such a poor job that the task can't be considered complete. You need to get your confidence from other areas, not from the area in which you're working. Look for times that you learned how to do a new skill and were able to execute it in a passable manner. If you went from zero to something then, you can do it again.
Next you need to determine what is actually important. Last summer I led the building of a loft inside the yurt on our island. I had never built anything close to that size or level of complexity. Very quickly I determined that the most important factor was safety. If the loft could hold a lot of weight in a secure manner, it would be a success. Second most important was functionality. It had to have sufficient space on top on which to sleep, enough room behind it to store stuff, and to be an appropriate size for installing a kitchen counter on the front.
Maybe most importantly, I determined that how it looked didn't really matter, and that cost wasn't a primary concern. Because I'm not an expert, I know that I'm not going to reach perfection, so I had to decide where to allow slack. By ignoring appearance I could build it in the simplest and thus fastest and safest way, and by ignoring cost I could err on the side of bigger hardware and lumber since I didn't know exactly what would be correct.
Considering what actually matters, you come up with a plan. I called my father to ask about lumber sizes, but didn't ask him about every last detail. That was the most important part, but the rest I could figure out on my own. You want to only ask people for advice for important things in which they are an expert. This is because you don't want to burn them out and giving advice and you also want to learn how to search the internet to find your own answers and be comfortable executing even when you're not totally sure.
Once you have the confidence to start, figure out what actually matters, and have done some basic planning, you start working. The most important part of this phase is recognizing errors early. You will make some errors, as you have no experience in this field, so it's important to find them. When I was building the loft I laid everything out and realized that we didn't get enough joist hangers because I miscalculated. By figuring it out early we were able to correct the mistake before the hardware stores closed.
This is the rough plan for a single task, but the real key here is to do things like this as often as possible. The more you do tasks in subjects with which you're unfamiliar, the more you'll learn about how you learn and work. That knowledge builds your general competence.
I'm an expert in very few things, but I have a high level of general competence. With no experience and very little guidance I've bought property in foreign countries, cooked meals for people, built all sorts of things, bought art, hiked in the wilderness solo, rebuilt a moped engine, and done many other unrelated things. Some of these things were hard and probably none of them came out as well as if a real expert had done them, but that's not the point.
I meet very few people who are generally competent and it's always a little shocking to me. If you think you might be one of those people, make it a high priority to develop general competence. It's a great feeling to know that you can handle anything life throws at you, and you become very useful to other people. Among the friends I have who hire, they all prioritize general competence because it's essential to autonomy.
Photo is me driving an ROV in Hungry Valley, CA. The amazing folks at rohva.org taught me how to drive ROVs and then took me out on the trails. As someone who is sort of over the thrill of motorcycling and doesn't love going offroad in Jeeps, I couldn't believe how much fun these things are. They have crazy suspensions and can handle any sort of terrain you throw at them— I'd accidentally go flying towards a ditch and the vehicle would just sort of glide over it.
I'm in Budapest now and loving it, although it's freezing here. Mostly drinking tea, coworking with my friend Brian, and going to the occasional opera or symphony concert.
long term reader but first time posting. could you please build on this post - how would you suggest a general competence noob start? how should he/she think about it and what are the short and mid term action items we can take towards this?
Specialization is for insects!
Very longtime reader, first time poster. Thank you for a great post! My 2017 is focused on exactly this idea - acquiring new skills. Learning Italian, how to play the guitar, how to dance, massage school, etc.
Also check out Mr. Money Mustache. He was just interviewed on Tim Ferriss's podcast. Lots of juicy insights:
This is also the basis thesis of Jacob Lund Fisher's early retirement extreme book and maybe also Mr. Money Mustache.
Great post. It reminds me of Tim Ferriss's "accelerated learning" with interesting examples.
You mention in the picture caption that you were kind of over the thrill of motorcycles. Do you still ride?
Might be interesting to write a post about deciding when to move on from a passion or hobby. Most people quit when the going gets tough or a new subject distracts them, but don't consciously reason their exit strategy. Curious if you have anything to say on that topic.
The one thing I consistently fail to account for when planning trips, especially shorter ones, is the disruption it will cause to my routine. For over a hundred days in a row, I wrote a blog post every day, did a Chinese lesson, worked on SETT, and a few other things for which I hold myself accountable.
I went to Peru for ten days, and although I started off strong, jamming in the blog post and Chinese lessons on my flights and bus ride to the Andes, once I started hiking I stopped doing those things. No real foul there, because breathing and walking had become difficult first priorities. When I got back to civilization, still in Peru, I resumed working hard on SETT, but I stopped doing Chinese lessons. I was practicing Spanish every day, though, so that made it okay. I wrote a monster blog post about Peru and sort of let myself coast on that. After all, it was a lot longer than my average post.
I got back to San Francisco and had only a week before I was going to Mexico. That week was great. I felt bad about being off schedule, so I used that as motivation to get back on. I rated three of those days as As and four as Bs, which is a pretty solid week. Next there are ten days completely missing from my schedule. I remember them, though. I worked on SETT every day while I was in Mexico, at a reduced capacity, as expected. I did a couple Chinese lessons, but was speaking Spanish, and fell behind on blog posts. Maybe I wrote four during those ten days.
Again, I got back and got back on schedule, but this time with less consistency. One day I gave myself an F and didn't even write any notes on the day. A few others I got Ds. There are As and Bs, too, but not as many as there should be.
Thought of the day:
All image, accouterment, support functions, and particular tactics pale in importance to being unrelentingly competent.
--> Competence means (1) being an expert at your core skill/skillset, constantly working to maximize it, and being one of the very best at what you do.
--> Competence means (2) being able to execute and produce results in a prompt, timely, reliable way using your expertise from #1.
If you've got this competence down -- and you work relentlessly to improve it -- then you'll be cut a lot of slack on the rest of the details. If you don't have this competence down or let your skills stagnate instead of grow, all sorts of nonsense is going to weigh heavily on you -- that wouldn't weigh heavily on the more competent man.