Today I learned:
1. The Best Laid Plans…often go awry. In an earlier post on preparation to work from home post-ACL reconstruction, I subtly (?) bragged about how well prepared I was to remain effective during time out of the office. By day 2 it became clear, despite IT support and “successful” testing, all tools are not equally reliable. The IP phone on my PC is a bust – it keeps cutting out.
Can you hear me now? Nope.
The good news is today I learned many of the free tools available are more reliable than those we pay for. Google Talk and Skype have saved the day, and not added any cost to me or the company. No IT support either – plug and play, just like things should be.
2. Why I wouldn’t succeed as a drug addict: It’s plain and simple. I just don’t have the stomach for it. For 2 1/2 days following surgery I was nauseous and dizzy. I felt weak and couldn’t stand to be on my feet for long. Using the crutches to cross my house made me feel like vomiting. My mind was foggy and I couldn’t concentrate. I was feeling as though the recovery period was going to be much worse than I thought.
Today it finally occurred to me that maybe it was the pain medication, not the surgery, that was the problem. I decided to go cold turkey and kick the drugs to test the theory out.
It was a good decision.
Within 2-3 hours the fog lifted. I was immediately more functional, both physically and mentally. The knee pain, despite no pain medications, is exactly the same if not better, too. It was an interesting lesson. It turns out the surgery wasn’t as bad as I thought. I am just not very good at doing drugs.
Today I learned:
1. Bed Rest in a Digital Age: Prior to yesterday’s ACL reconstruction, I had two previous arthroscopies on the same knee in the early-1990’s. It was almost 20 years ago but I have two vivid recollections:
- Dialling my own home phone number from downstairs to make it ring upstairs so I could ask my mom to bring down some ice cream, without getting off my lazy butt. I remember this, partially, because she reminds me of it every chance she gets.
- Watching ALOT of crappy TV.
As a high-school student who actually attended all my classes, this was my first exposure to the Soap Opera genre. Try as I might I never took to Days of Our Lives and General Hospital, but there just weren’t many other options in those days.
The world is different this time.
I stacked months of reading by my bed in preparation for the down-time but one day out of a general anesthetic and still hooped up on pain meds, my head is not so much into books. Instead I have watched a few shows recommended by friends on Netflix – The Hour and Justified are favourites so far – and watched a work-related webinar.
As I look at myself now, surrounded by my iPhone, iPad, and macBook Pro, as well as my work laptop and blackberry, I have a sense this round of bed rest will be very plugged in. This blog may in fact prove to be therapeutic as it forces some form of daily creation, rather than consumption.
All the technology comes in handy too – this time I have 4 separate devices that I can use to Skype my mom to see if she can drop by with a bowl if Ice Cream.
2. Over-prescribing Meds: On discharge from hospital I assumed I would be sent off with a small script for T3’s, but in fact I was given a prescription for a fairly heavy narcotic. Interestingly, I was prescribed 60 tablets which my close friend (a pharmacist) described as “an awful lot for knee surgery.”
Taken at the recommended dosage of 1-2 tablets every 4-6 hours, the 60 tablets would be depleted at a rate of between 4 and 12 per day. Essentially, worst case I have 5 days of meds, but best case I have 15 days (or more if I don’t need them frequently).
This made me wonder: Why prescribe so many tablets?
Surely if I am in so much pain that I run through these meds at the fastest pace then someone should see me before 5 days to assess the problem. Alternatively it could be that I will have so many tablets leftover when I am done that they end up sitting around in my medicine cabinet long after I need them. This invites abuse by me or someone else.
I trust my doctor – I think he’s great and I am sure he did a good job on my knee – but I wonder how much thought went into the follow-up medications. It may be that he assessed me and felt a large prescription was safe and low risk. I hope that is the case.
It seems to me though that it is more likely the script size was just a convenience factor for both him and me – an attempt to reduce follow-up visits just to write a new script. If that is the case then I am not too impressed. A smaller prescription would potentially catch and save problems at both ends of the spectrum.
My quest to learn two things a day, and to blog about it for the first 66 straight days, has moved on the road for a short period. Expect a few travel and/or Disney related posts over the coming days. I apologize upfront as the already scattered theme to this blog could get even less obvious in the coming days.
Today I learned:
1. Leapfrogging technology: We headed south this morning to visit with Mickey & friends in Anaheim. On the flight I was immediately pleased to see personal seat-back TV’s on what I assumed was a bare-bones carrier. The novelty wore off quickly though when I realized it didn’t matter for my family. With a laptop, iPad and smartphone (along with a few old school colouring books, newspapers and magazines) we brought enough entertainment for the whole family. And we were not alone.
I took a walk up and down the aisle halfway through the flight and noticed two things:
- Everyone was awake
- No one was watching the TV. Not one person in the 15 rows (with 5-6 people in each row) all the way to the back.
From this you should take-away two things:
- There were only 15 rows to the back. I clearly fly coach.
- The seat-back TV, a relative youngster, has already been rendered virtually useless.
In my quick little survey of about 80 people I counted 12 tablets, 17 laptops and 2 smartphones being used, and keep in mind many of those devices were being shared. Several were being watched by 3 children at once. The rest of the people were reading, eating or sitting quietly. No one was plugged in to the seat-back entertainment system.
What should this tell us?
At least for short-haul flights – ours was 2 hours 40 minutes – it would be smarter for airlines to focus on services that supplement the devices people want to use. Wifi, for example, would probably have had takers. It would have added value to me. A Netflix-like service that allowed a pay-per-view option on my device might even get a bit of uptake.
My take way is clear. Adding more seat-back TV’s is like stringing telephone wire in China. There is no point. Airlines need to find a way to monetize the technology we already bring in our carry-ons, rather than trying to provide their own hardware. Without any real analysis I have to assume this approach would be cheaper and offer better margins. If they aren’t installed already I would leapfrog the seat-back TV and move on to the next wave.
2. It’s (not) a small world after all: Every time I travel to America I need to fight the holier than though attitude that seems to kick in. Obviously I keep travelling here because there are so many cool things to see and do. Now, disclaimer aside…
Just about every Canadian will tell you that as soon as you cross the border the world just seems bigger in every dimension. Particulalry in waistline. I came across one tidbit today that seems timely and hits the point home. One of Disneyland’s most famous attractions, It’s a Small World, was renovated in 2009. According to “The Unofficial Guide to Disneyland, 2012 Edition” p. 240, one of the reasons for this is the waterway needed to be dug deeper to “accomodate today’s heavier guests.”
There is something oddly appropriate about people today being too big for It’s a Small World. How far we’ve come in 50 years.
Today I learned:
1. Competence: The other day I took part in a leadership training seminar where we discussed the concept of competance. The facilitator showed a great video clip of a labourer carrying bricks off a boat:
This man is clearly good at his job, and he has spent whatever time was required to develop a true competence in the task at hand.
Reflecting back on the discussion today, this clip raises two questions:
a. Will his employer (apparently in Bangladesh) pay for the treatment of his future neck and/or back injuries?
b. How do you help your team members achieve this level of competence – or mastery really – in their jobs?
The second question is tougher.
The basic method proposed in my session was to “show them what to do, how to do it ,and why.”
No question it is good, clear advice. But a video like this suggests to me that is really part of step two in this problem. From my perspective the video tells as much a story about hiring practice as it does about competence and eventually mastery. I do believe there is some form of greatness or calling in everyone, but I don’t believe everyone is suited to do anything. To me this video is more about Jim Collin’s famous statement that you need to “get the right people on the bus,” or in this case the boat. Not every person is going to balance 20 bricks on their head. Most are going to fail miserably at this task. To me this is more a lesson in finding and then nurturing the development of the right people, than it is about taking who you have and helping them master the task at hand.
Am I right or have I had one too many bricks fall on my head on this on?
2. Preparation, Take 2: After yesterday’s post on presentation preparation and my perception that people are too often inclined to blame their lack of preparation on a technology fail, today I found myself involved in a 2 hour preparation session with representatives from my company and one of our vendors aimed at planning a series of three webinars for a customer group. Two hours, about 10 people online, bouncing ideas and working on a very rough run through. We had technology problems, poor narative, and incomplete explanations. At the start we weren’t on the same page with the message and we had differing views on the key issues to address. It was generally a weak product.
Is this a problem?
It was the first of 3 sessions, over which I expect we will iterate the presentation to a final product that I am sure will be polished and, most importantly, valuable to the customer. It certainly feels good to have a take away from personal involvement in a good process, just one day after learning a similar lesson while observing a bad one.