Category Archives: writing

Growing authority

It’s good to think about the kind of life you want to grow so that when everything comes together – knowledge, skills, character – you can make the most of it. image I recently turned thirty. This is great. Being a thirty-something carries a little more gravitas than being a twenty-something. It’s not a magic bullet, but I think it will help. Maybe in my thirties, I’ll get better at using the Voice of Authority. Maybe I’ll figure out how to stop sounding like I’m five years old. Maybe I’ll stop hedging my blog posts and conversations with maybes and probablys. I checked the mirror the other day. Still no crow’s feet. Gotta work on those. Every so often, I think about the way I want my face to wrinkle and age. Smile lines, yes. Frown lines, anger lines, not so much. Do you think it would be weird to find someone who can retouch one of my photos so that I’m more crinkly? Usually people want to go the other way around. Anyway. Growing older has its perks. While I wait for the aura of respectability to settle in, I’m working on accumulating knowledge and skills. They’ll come in handy someday.

I was going to say, this girl looks like she's 16, what does she know? ... but she says she's 29. A little better. :)

from a forum post I think it’s about deliberately growing my circles of authority: understanding my limits and then gradually expanding them. Here’s a snippet from a recent HackerNews article that made me think about this concept of “authority”:

3. I built a bigger product than I had authority for I started up Happy Bootstrapper in April with no followers or authority. I planned to write a book about metrics first. The reason is simple – I know my metrics, but I’m not a growth consultant or a SaaS owner. Starting with simple info-products would have bought me time to grow my authority at the same speed with my products. Then I just happened to stumble into a problem/pain that I knew I could help people with. I didn’t stop to think if I had the authority to actually sell the product. And if you aren’t selling something trivial then you’d better have something to prove people that you know your topic. Teaching people about the topic does the job, but it requires time.

3 Lessons From My Almost Failed Launch Authority isn’t just for selling things. It can help when asking questions or sharing thoughts. It’s like the way open source mailing lists strongly encourage people to show their work when asking a question. Don’t just ask a question out of the blue, show how you’ve tried to find an answer on your own. Experience (even a little bit) earns you conversation. It’s also about making it easier for people to identify with you, which is essential if they’re going to listen. I did a lot of technology evangelism as a consultant, coaching teams and communities on social business and internal collaboration platforms. It was always about finding a few people within the group or in a similar group with whom people could identify. Few people were going to listen to me say that something was easy to learn. In many cases, I was the same age as their sons or daughters, and they were used to being confused by stuff that their kids found easy. If the advocate was someone in their group – especially someone who’s not always the first adopter of new things – it was much more effective. One of the most useful techniques for influencing people is Feel, felt, found: I know how you feel. I felt that way when… I found that… You can tell it with other people’s stories, but it’s more effective with your own. As I go through life, I’ll probably collect more experiences that can help me identify with people and vice versa. I’ll probably also diverge (like with this semi-retirement experiment thing!), but with experience, I can get better at emphasizing similarities. It’s the ethos of rhetoric’s logos, pathos, and ethos: character is part of persuasion. And I’ll learn more, too. I’ll learn things worth sharing. I’ll learn things that can save other people time or money, make ideas easier to explore, and so on. Here’s what I’m a semi-authority on (based on what people have asked me about) and my current limits:

  • Emacs: getting started, playing around with it, some coding – but not yet working with Emacs core or doing lots of Emacs Lisp wizardry
  • Sketchnotes: getting started, working digitally, publishing, learning from others, using in presentations and blog posts – but not paper, and not graphic recording/facilitation
  • Quantified Self: tracking time, analyzing data, working with Excel, basic stats – but not R, and only a few types of measures
  • Blogging: learning through writing, blogging about tech and life, working with a large archive, adding sketches – but not yet e-books or other information products
  • Bulk cooking: filling the freezer with individual meals (with an Asian slant), cooking frugally – but not vegetarian and not large-scale
  • Hacking around introversion: connecting, taking notes, following up, speaking in public – but not networking events

I don’t want to turn into the “I know what’s best for you” sort of authority. I think good authority is more along the lines of being able to:

  • empathize with people because you’ve been through something similar, and make it easier for them to understand where you’re coming from
  • ask the right questions to help people think through things, share their experiences, and come to their own conclusions
  • share experiences and pitfalls so that other people can avoid your mistakes or explore the secret bonus levels you’ve discovered
  • enrich the conversation

What kinds of authority do I want to build? I want to get really good at learning and sharing. I want to grok things and share what I understand. I want to inspire and help lots of people learn and share more effectively. I want to get really good at working around my limits. That’s where Emacs, sketchnotes, Quantified Self, blogging, cooking, and introversion all fit in, I think. Emacs gets around the limitations of the tools I use. Sketchnotes and blogging help me get around the limitations of memory and introversion. Bulk cooking helps me get around the limitations of time. Quantified Self helps me get around the limitations of irrationality and forgetfulness. Not perfect, but useful. I want to get really good at living life with equanimity. I want to weather the ups and downs and sidewayses of life. Frugality is a subset of this, I think – the ability to resist the temptations of consumption and desire. So how can I build that kind of authority over the next few decades? shutterstock_111523355Primary insights come from doing things. As Washington Irving said: “One of the greatest and simplest tools for learning more and growing is doing more.” Secondary insights come from reading, talking to people, and learning from other people’s lives. I can make the most of being close to a library and speed-reading like crazy. Decent fill-in while I don’t have much experience. At some point in time, maybe everything will come together. I wrote once:

If I can get a decade or two of great writing out right around the time I should have tons of experiences to write about, that should be fine.

Quantified Awesome: Time and building mastery Let’s see how this works out. =) Image credits: Brain tree: Christos Georghiou (Shutterstock), Book tree: Cienpies Design (Shutterstock)

What kind of authority are you building? How are you going about it?

Quantified Awesome: Time and building mastery

image There’s an often-repeated number in studies on expertise: it takes 10,000 hours of deliberate practice in order to build a skill to mastery. Last year, I logged 265 hours writing, or around 45 minutes a day. Don’t be scared off by that. If you’re repurposing something you’ve already done, blogging takes maybe 5-10 minutes. It takes an astonishingly long time to think through new things. I can type at 90-110 words per minute, but my brain chugs along at 16 words per minute when reflecting, and I haven’t quite gotten the hang of using speech recognition or dictation to get past that barrier. I suspect I won’t be significantly faster. Thinking takes time. That 265.5 hours is butt-in-seat time. Yes, that’s the professional term for it. I have surprisingly little of it, considering how much I perceive writing to be a part of my life. (Really? Just 45 minutes a day? What would happen if I doubled that?) Generously including quick blog posts as part of this practice, assuming that I’ve maintained a similar pace since around 2003, neglecting the fact that real writing involves a whole lot more rewriting (which I tend to do out of forgetfulness rather than deliberate improvement), and ignoring the assigned writing I slogged through in school (or the countless e-mails I dash off), the calculations show that I’ll probably be inching closer to awesomeness… oh… when I’m 57 or so. I know life doesn’t quite work out like that, but let’s pretend for the sake of calculation. It doesn’t actually look half-bad, you know. If I can get a decade or two of great writing out right around the time I should have tons of experiences to write about, that should be fine. Of course, with the unreliability of memory (both mine and the computer’s), I’ll just have to hope my blog will survive the years. And if I turn out to be a passably good writer who can package up what I’ve learned and turn it over to the next generation of young whippersnappers, then that’s great. Don’t need to win any awards. On a similar note, I logged 198 hours drawing last year. This does not include the times that I filed drawing under “Business – Plan” or “Personal – Plan” instead. Even less revision going on over here, but I’m working on ways to improve that, and other ways to increase the proportion of writing and drawing in my life. Malcolm Gladwell’s Outliers: The Story of Success broke down that 10,000 hours into around 10 years of daily 3-hour practices. I have spent a ton of time coding. I’ve been coding since I was six or so, and I worked on quite a few web development engagements at IBM. I’m still nowhere near “master” level. I can point to lots and lots and lots of people who are way better than I am. I have fun with it, though. I can make stuff happen. It’s good to remember that invisibly sunk time, the accumulation of experience over years. That way, I don’t get frustrated about drawing if it feels less natural than coding, and I can see all this writing as building a skill step by step. Thank goodness for visible progress. Hooray for a blog that lets me go back in time! Compared to a year ago, I draw so much more than I used to. I feel a little more organized and coherent as a writer – headings for my paragraphs, an index for my posts. I still don’t have the deft interweaving of personal story and insight I envy in Penelope Trunk’s blog or the lyrical geekiness of Mel Chua (no relation), but I’m growing into my own style. I think it would be fascinating to have 10+ years of time data. It’ll be interesting to see how I change things along the way. Not that quantity of time controls everything, but it’s fun to ask questions and realize that the composition of your time doesn’t always match up to what you think it is. Then you can tweak it. Other 2012 numbers to put this into perspective, because I have the data anyway: image
  • 3024 hours of sleep – 8.3 hours per night and I’m still fidgety when I go to bed; I wonder how one deliberately practises sleeping
  • 729 hours socializing (in person, answering e-mail, etc.) – not much deliberate practice going on there, but good to spend that time
  • 411 hours connecting with people for business (in person, answering e-mail, etc.) – a little bit of systematization and experimentation
  • 102 hours reading fiction, 88 hours reading nonfiction – funny, I thought it would be the other way around, although some of it did get classified as “Business – Drawing” instead
  • ~75 hours playing LEGO video games
More time analysis looking at percentages So that's where all the time went!

Sketchnotes: Designing content so that it works – Carl Friesen (#torontob2b)

UPDATE 2012-11-15: Here's the video recap! Designing Content So It Works Carl Friesen, Global Reach Communications Like these? Check out my other sketchnotes, visual book notes/reviews, and visual metaphors. Here's the text from the sketchnotes to improve people's ability to search for it: Designing content so that it works Designing content so that it works Carl Friesen, Global Reach Communications Website for e-book on content design 1 2 3 4 5 stories The Trend Client wants customized solution Show that you understand their world 1. Trend & historic causes 2. current situation 3. Thoughts on developments, reasons 4. Recommendations The How-To 1. 2. 3. Example: trustees, communication process must be: Relevant + Realistic not necessarily what you do, but what clients will find helpful Helpful! - process with steps or - a list of success factors 1. outcome 2. supplies/equipment 3. steps 4. avoiding pitfalls/problems The How-to-Work-With How to get good results from working with you cannot be self-serving include info on saving money 1. wild success experience 2. factors 3. advice   The Case Study Leading-edge thought & sound implementation Trans-Canada highway story Wildlife protection Not about showing how clever you are! Must have learning points THEY can use Must be a story Tell with the client credibility 1. Initial situation 2. Steps 3. Problems & solutions 4. Lessons learned   The Survey Shows that you stay in touch must be what your audience cares about More useful with a trend Distribute appropriately Level of detail Consider limited distribution The Opinion informed opinion, thought leadership at no charge Long form -situation -views on good & bad aspects -recommendations The Review -New product/service -What's different -Discuss good/bad The Comment Notes by Sacha Chua, @sachac,