I continue to see that financial firm's (ING I think) commercial with the guy walking around with "his number". The next door neighbor say's his number is a Gazillion - clearly a SWAG and without a thought of "how much is enough".
Back in 2001 my financial advisor (T.A.) helped pull together a financial forecast and we discussed "my number". Next I had the challenge of figuring out - was it enough (and endless question)?
We spend a lifetime thinking implicitly about "the number" - trying to earn it, save it, invest it, and give it away. K.C. and I talked about this yesterday. What if suddenly (like winning the lottery) the number changed significantly (we only talked about the number going up not down).
Do you calibrate "up" your number - basically saying "enough earlier was not enough"? Or do you say the surprise excess can be given away? Giving away "a big number" can be stressful. I know, I know - you are saying please let me have that problem.
Everyone has that problem today regardless of the relative certainty of your number (in actual terms or forecasted). In his book "Wealthy and Wise", Claude Rosenberg plays around with "the number" with the premise that we can give more than we think.
Remember - it's only a number.
Wednesday, October 6, 2010
Tuesday, October 5, 2010
Efficient Recession
The business cycle is essential for proper balance - it's like yin and yang. So what is the optimal recession - the most efficient recession? It takes at least two quarters of lower GDP to be even considered a recession. Since recessions are considered "bad", then we should only want two quarters -- right? I don't think so.
Attempting to define the most efficient recession assumes something can be done to "control the timing and depth" of a recession. Hence the attempt with government stimulus and Federal Reserve actions. So implicitly we are defining what we view as the most efficient recession - meaning short and thin.
However this is like "squeezing a balloon". The shorter we want it, the deeper it becomes; the thinner we want it, the longer it becomes.
An efficient recession - is exactly what it takes to eliminate the bad habits of inefficient growth during the growth phase. Habits are hard to break.
Attempting to define the most efficient recession assumes something can be done to "control the timing and depth" of a recession. Hence the attempt with government stimulus and Federal Reserve actions. So implicitly we are defining what we view as the most efficient recession - meaning short and thin.
However this is like "squeezing a balloon". The shorter we want it, the deeper it becomes; the thinner we want it, the longer it becomes.
An efficient recession - is exactly what it takes to eliminate the bad habits of inefficient growth during the growth phase. Habits are hard to break.
Thursday, September 30, 2010
Overscheduled
One of the most interesting stresses that are self imposed is the famous personal schedule - or how you manage your time. Are you a planner - "Plan the Plan, and Work the Plan" or a the opposite.
What is the opposite of plan? The dictionary says - forget, ignore, neglect. I like the term ignore - because it is the most common cause of overscheduling (second is saying yes too much).
Calendar management is a learned skill and reflects the style and personality of the individual. It also relates to promptness, meeting management, route and travel habits, telephone management etc.
In the book "History of Time", I remember the cultural differences forcing others to wait extraordinarily long times for a meeting.
One thing I am certain of - when you overschedule yourself - you will be stressful. When you are around people who are overscheduled - you will be stressful.
What is the opposite of plan? The dictionary says - forget, ignore, neglect. I like the term ignore - because it is the most common cause of overscheduling (second is saying yes too much).
Calendar management is a learned skill and reflects the style and personality of the individual. It also relates to promptness, meeting management, route and travel habits, telephone management etc.
In the book "History of Time", I remember the cultural differences forcing others to wait extraordinarily long times for a meeting.
One thing I am certain of - when you overschedule yourself - you will be stressful. When you are around people who are overscheduled - you will be stressful.
Wednesday, September 29, 2010
Body Part Failure
At the Accenture ex-partner lunch, B.W. said "We are all just awaiting the failure of different body parts - we just don't know which ones and when".
My recent "hitch in the get-a-long" was the strained calf muscle from not warming up enough prior to Monday tennis. Hoping I was still a 20 year old expecting immediate recovery, B.W. reminded me that preventative care is but a minute compared to the recovery time in your 50's.
Yes my zeal to become more healthy by exercising (e.g. Tennis) had turned into a sport injury with pain, hobbling and cries for sympathy.
Wisdom arrives in the form of pain - and advice from individuals with their own painful body part failures.
My recent "hitch in the get-a-long" was the strained calf muscle from not warming up enough prior to Monday tennis. Hoping I was still a 20 year old expecting immediate recovery, B.W. reminded me that preventative care is but a minute compared to the recovery time in your 50's.
Yes my zeal to become more healthy by exercising (e.g. Tennis) had turned into a sport injury with pain, hobbling and cries for sympathy.
Wisdom arrives in the form of pain - and advice from individuals with their own painful body part failures.
Monday, September 27, 2010
Kind vs Good
Rev. Stover's sermon mentioned that the word "kind" is never used in the Bible. Immediately a line from Sondheim's "In the Woods" popped into my head. Susan and I saw "Into the Woods" in Chicago (or I should say we saw half of it - because we walked out at intermission - that's a long story).
When the wolf first introduced himself to Little Red Riding Hood he said to her suspicious reaction - "But I am Kind". Her response was "Kind does not mean Good". Very interesting ......
It is tempting to automatically connect kindness with being good. After all why wouldn't you trust that the only reason someone is being kind is to promote goodness in the world? Unfortunately we have too many situations where kindness is a ploy for selfish manipulative reasons.
So be Good - and let Kindness follow.
When the wolf first introduced himself to Little Red Riding Hood he said to her suspicious reaction - "But I am Kind". Her response was "Kind does not mean Good". Very interesting ......
It is tempting to automatically connect kindness with being good. After all why wouldn't you trust that the only reason someone is being kind is to promote goodness in the world? Unfortunately we have too many situations where kindness is a ploy for selfish manipulative reasons.
So be Good - and let Kindness follow.
Labels:
Movies/TV/Radio,
quotes,
relationships,
religion/spiritual,
susan
Friday, September 24, 2010
Wayne's Weekend
Wayne popped into my mind as the weekend approaches. Get prepared this may be a long blog - but was an important lesson to me.
In a very emotional time of my life, Wayne asked if I wanted to regularly golf on Sunday mornings at the Neumann public course on the west side. So we started the tradition. One of the Sunday mornings I was lamenting about my work schedule and started telling Wayne that I may need to eliminate Sunday golf so that I could work. Wayne responded: "Garen, you dumb ass! there are only 52 available weekends in the year and look what you've been doing for the last 10 years with those weekends."
Wayne had a way of simplifying things. He was right and like a bolt of lighting hitting the golfer - my light bulb was now fully illuminated. I resolved at that point in time (1987) that I would re-allocate my work time. I would work 24 hours (if necessary) during the week - but I made a covenant to never work on the weekend again. If my career was going to require that - then it was a career I didn't value. It was time to draw a line in the sand.
Fast forward 9 years later- 1996. Wayne had just arrived in Cincinnati from Las Vegas (his new residence) for his brother's wedding. I was knee deep in a high pressure job at Southern New England Telephone (SNET) in Connecticut - but back in Cincinnati for the weekend. Wayne stopped by for a visit at the Brill house and had dinner with Susan, Jenna and I, on Sunday evening - I'm sure I was lamenting again about the "deadline" I was facing for the project.
After a wonderful visit with Wayne, I was back on the plane to Connecticut - Monday morning. It was a tough week - the client was nervous, we were struggling to hit the deadline, and the politics were ugly - it was clear we were not going to make the date. The only alternative was to work the weekend - the first time in 9 years I would break the covenant. I would need to call Susan to let her know the bad news.
I got on the phone to tell Susan and as I was telling her my news she interrupted saying that Wayne had died - a heart attack on the plane as he was returning to Las Vegas.
I didn't work that weekend - I was in Las Vegas at Wayne's funeral on Saturday April 27, 1996.
In a very emotional time of my life, Wayne asked if I wanted to regularly golf on Sunday mornings at the Neumann public course on the west side. So we started the tradition. One of the Sunday mornings I was lamenting about my work schedule and started telling Wayne that I may need to eliminate Sunday golf so that I could work. Wayne responded: "Garen, you dumb ass! there are only 52 available weekends in the year and look what you've been doing for the last 10 years with those weekends."
Wayne had a way of simplifying things. He was right and like a bolt of lighting hitting the golfer - my light bulb was now fully illuminated. I resolved at that point in time (1987) that I would re-allocate my work time. I would work 24 hours (if necessary) during the week - but I made a covenant to never work on the weekend again. If my career was going to require that - then it was a career I didn't value. It was time to draw a line in the sand.
Fast forward 9 years later- 1996. Wayne had just arrived in Cincinnati from Las Vegas (his new residence) for his brother's wedding. I was knee deep in a high pressure job at Southern New England Telephone (SNET) in Connecticut - but back in Cincinnati for the weekend. Wayne stopped by for a visit at the Brill house and had dinner with Susan, Jenna and I, on Sunday evening - I'm sure I was lamenting again about the "deadline" I was facing for the project.
After a wonderful visit with Wayne, I was back on the plane to Connecticut - Monday morning. It was a tough week - the client was nervous, we were struggling to hit the deadline, and the politics were ugly - it was clear we were not going to make the date. The only alternative was to work the weekend - the first time in 9 years I would break the covenant. I would need to call Susan to let her know the bad news.
I got on the phone to tell Susan and as I was telling her my news she interrupted saying that Wayne had died - a heart attack on the plane as he was returning to Las Vegas.
I didn't work that weekend - I was in Las Vegas at Wayne's funeral on Saturday April 27, 1996.
Labels:
Accenture,
friends,
memories,
relationships,
sports
Thursday, September 23, 2010
Beginning and End of File
One principle I learned at Accenture in computer programming is the importance of the logic and code necessary for the first transaction and the last transaction being processed - Beginning and End of File.
Everything else becomes routine and with logical loops. Testing the logic at the beginning and end is essential for a sound program. I remember just opening the file was non-trivial code.
In life, the mystery of birth (beginning) continues to challenge scientists and death (ending) is a mystery for both the religious and secularist. So the middle part (Middle Earth) is what we know -what we routinely experience - day, night; consume, digest; start, stop; - seemingly endless cycles since we don't remember"beginning of file" and we await/expect and "end of file".
Unlike programming - we have no choice in the beginning, and the last transaction process is unknown. What we control are the logical loops in the middle.
Is it time to reprogram?
Everything else becomes routine and with logical loops. Testing the logic at the beginning and end is essential for a sound program. I remember just opening the file was non-trivial code.
In life, the mystery of birth (beginning) continues to challenge scientists and death (ending) is a mystery for both the religious and secularist. So the middle part (Middle Earth) is what we know -what we routinely experience - day, night; consume, digest; start, stop; - seemingly endless cycles since we don't remember"beginning of file" and we await/expect and "end of file".
Unlike programming - we have no choice in the beginning, and the last transaction process is unknown. What we control are the logical loops in the middle.
Is it time to reprogram?
Subscribe to:
Posts (Atom)
