Skip to main content

Learning hard stuff the easy way

My 9 year old daughter told me recently that she wants to "do something." When I asked her to clarify she said, "I want to get a job." Now that was interesting. I stifled the urge to laugh (because I can hear her as an adult saying how she wishes she didn't have a job, but I digress) and discussed it with her in a serious fashion. We decided that she could put her great imagination to use and start a "clothing line" that she would sell through CafePress.com or a similar site.

I will proudly state that my 9 year old is extremely intelligent and has the vocabulary of a 15 year old, but even that doesn't mean she would automatically "get it." So, for several nights after she expressed her desire, we spent some time each night talking about concepts like product design, marketing, and sales. What I found was that I had to put an extraordinary effort into internalizing the functions of business so that I can synthesize new ways to describe them to a 9 year old.

In other words, the KISS principle applies here in spades.

Guy Kawasaki, a well-known venture capitalist, has a concept he calls the 10/20/30 Rule of Powerpoint. In short, he states that a Powerpoint presentation should be no more than 10 slides, last no longer than 20 minutes, and contain no fonts less than 30 points in size. While I won't debate the merits or flaws in the concept (I will state unequivically that I love it, however), I do want to point out that it encourages the same, simplified thinking through deconstruction of complex topics.

Can you put together a 10/20/30-compliant presentation that describes your work experience and skillset? You better turn off the Autofit feature before beginning, because I suspect you'll have trouble doing so. In fact, I'll claim that if you don't have trouble doing so then you aren't doing it correctly.

Is this just an exercise of futility? Absolutely not. By forcing yourself to distill what you do and have done into a succinct, summarized format, you really learn to throw out the irrelevant crap and polish up the stuff that helps you to shine. Extrapolate this exercise into other areas of your professional life, and you'll quickly begin to see what's important to you as a salesperson, a market strategist, a technologist, etc.

Esther Schindler
wrote in a recent article on the topic of "getting resumes past HR" (geared toward technologists), "That is, [the recruiter told me], 'Create a resume that a layperson will understand. Yes, include the technologies used and maybe a bit about your methodology, but make sure it's readable to the point that a non-techie friend can get the gist of what you've accomplished in each job. Keep that tech-oriented résumé for the hiring manager to review.' "

So if we're to boil down our backgrounds to just the bare essence, what do we do with the rest of it? It belongs in the magical circular file cabinet underneath your desk that gets emptied every night.

Popular posts from this blog

"Ni jiang yi yang de hua ma?"

Last week, I wrote about the necessity of having a clear message . Because this topic is so important I decided to follow-up with another entry on this general subject. This week we will approach it from another angle. (For the curious, the title says " Do you speak the same language? " in pinyin, which is a transliterated Mandarin Chinese.) Recently, a good friend of mine (who is Chinese, ironically) and I were playing pool. He had to bank the 8-ball in the pocket to win the game, and since it was an informal game and bank shots are my area of expertise, he asked me for advice. I told him, "you just need to strike the cue ball with medium speed so that it hits the 8-ball right in the middle." He didn't believe me so we marked the positions of the balls, and then he took his shot only to watch the 8-ball sail past the pocket. "A-ha!" he exclaimed. "I told you it wasn't that easy." But when we reset the positions and I made an attemp

It's Easier to Fail at DevOps than it is to Succeed

Slippery when wet Since the term DevOps was coined in Belgium back in 2009, it is impossible to avoid the term whether in discussions with colleagues or in professional trade magazines.  And during the years while this movement has gained momentum, many things have been written to describe what elements of a DevOps strategy are required for it to be successful. Yet in spite of this, there is an interesting data point worth noting: not many organizations feel there is a need for DevOps.  In a Gartner report entitled DevOps Adoption Survey Results (published in September 2015),  40%  of respondents said they had no plans to implement DevOps and 31% of respondents said they hadn't implemented it but planned to start in the 12 months after the survey was conducted. That left only 29% who had implemented DevOps in a pilot project or in production systems, which isn't a lot. "Maybe it's because there truly isn't a need for DevOps," you say.  While that

Is No/Low-Code the Key to IT Nirvana?

 Unless you've had your head in the sand for the past year or so, you've seen the phrases low-code  and no-code  bandied about quite frequently everywhere you look.  You've probably wondered if this is something new that's here to stay or just a "flash in the pan."  Although the terms have been in the fore of the IT trade publications recently, Low Code Development Platforms (LCDP) (and the corresponding No Code Development Platforms) have been in existence since 2011.  Their roots can be traced to the 90's with 4th generation programming languages and GUI-assisted programming paradigms, e.g. IBM VisualAge for Basic, which was discontinued in 1998. For those of you who aren't familiar with either, the premise is that these platforms allow someone to quickly build applications using a WYSIWYG interface and a "click and configure" paradigm to Isn't this the source code to Roblox? rapidly build full applications with little or no coding requ