I got to my hotel on Monday night and found one of my favorite movies on; Ferris Bueller's Day Off. I like it in part because it was shot in my home town of Chicago, but I also think it's a pretty good movie.
One line comes up at the end of the movie that is pretty deep. After Ferris and his friends have had a great day in Chicago, the damage has been done to the Ferrari, and Ferris is back home, he says "Life moves pretty fast, if you don't stop and look around once in a while, you might miss it."
A look at how we deliver value, incorporating diverse ideas that can be applied to organizations.
Wednesday, August 06, 2008
Monday, August 04, 2008
The Zen of Getting Things Done
So I finished the book Getting Things Done by David Allen. I had two colleagues recommend it within a couple of days and took that as a sign.
An underlying theme of the book is a “mind like water.” I’ve heard this idea used a lot in meditation. Think about a pond when a pebble hits it and the ripples flow out. In meditation, you want to get rid of the ripples; clear the mind.
The same idea applies to Getting Things Done. If you can get things off your mind by capturing them in an effective system, you will be more productive with the things you are doing.
A key is to be able to decide what is the next step for any of the projects you may be working on. For example, every time I start my car, the computer reminds me that service is due. The next step has to be well-defined. It’s not get the car serviced but more precisely call the service department and make an appointment for Friday at 8:00 AM.
So in your next meeting, as your discussing a project, ask the question “So what’s the next step?” and get things done.
An underlying theme of the book is a “mind like water.” I’ve heard this idea used a lot in meditation. Think about a pond when a pebble hits it and the ripples flow out. In meditation, you want to get rid of the ripples; clear the mind.
The same idea applies to Getting Things Done. If you can get things off your mind by capturing them in an effective system, you will be more productive with the things you are doing.
A key is to be able to decide what is the next step for any of the projects you may be working on. For example, every time I start my car, the computer reminds me that service is due. The next step has to be well-defined. It’s not get the car serviced but more precisely call the service department and make an appointment for Friday at 8:00 AM.
So in your next meeting, as your discussing a project, ask the question “So what’s the next step?” and get things done.
Labels:
Getting Things Done
Tuesday, July 29, 2008
Instrumental versus Fundamental Reasons for Work
I've been reading The Adventures of Johnny Bunko and I came across a concept I thought was worth sharing. In this page, Johnny's career fairy talks about doing things for either fundamental or instrumental reasons. She explains that people do things for instrumental reasons because they think it's "going to lead to something else" such as career advancement etc, even if it's not something that's enjoyable. People do things for fundamental reasons because they think it's the right thing to do.
The idea is that we can't really plan our career out because there's to much uncertainty. We shouldn't take jobs or assignments because we think they'll get us ahead. We should do the things that provide us satisfaction, align with our inner soul, or fulfill a higher purpose.
The successful people are those that do the things they want to do, not the things they think they need to do to get ahead.
The idea is that we can't really plan our career out because there's to much uncertainty. We shouldn't take jobs or assignments because we think they'll get us ahead. We should do the things that provide us satisfaction, align with our inner soul, or fulfill a higher purpose.
The successful people are those that do the things they want to do, not the things they think they need to do to get ahead.
Labels:
The adventures of Johnny Bunko
Wednesday, July 23, 2008
A Balancing Act
Good project managers know the importance of managing scope. The customer comes along, asks for a change, you fill out your change request form and get the change scheduled, possibly in a future release or iteration.
But it's not that simple, is it? If you take a hard stand, you run the risk of creating animosity with your customer. But on the flip side, if you give in to much, your project gets out of control and nothing gets delivered.
So how do you decide where to draw the line? You want to make the customer happy by delivering what they want but the key is to deliver.
I've had this situation come up recently with my customer. My compromise was to put a couple of the higher priority requests into the current release, ones that don't have much of an impact on the schedule. The rest I have slotted for the next release. At the same time, I reinforced the idea that it's more important to get the new tool into production, even without every feature, than it is to wait and get it perfect. Once they start using the tool, they will come up with other features, and some of the ones they are thinking about now won't seem so important.
So keep thinking win-win. How you can give the customer what they want while still delivering as soon as possible.
But it's not that simple, is it? If you take a hard stand, you run the risk of creating animosity with your customer. But on the flip side, if you give in to much, your project gets out of control and nothing gets delivered.
So how do you decide where to draw the line? You want to make the customer happy by delivering what they want but the key is to deliver.
I've had this situation come up recently with my customer. My compromise was to put a couple of the higher priority requests into the current release, ones that don't have much of an impact on the schedule. The rest I have slotted for the next release. At the same time, I reinforced the idea that it's more important to get the new tool into production, even without every feature, than it is to wait and get it perfect. Once they start using the tool, they will come up with other features, and some of the ones they are thinking about now won't seem so important.
So keep thinking win-win. How you can give the customer what they want while still delivering as soon as possible.
Labels:
scope creep
Monday, July 14, 2008
The Empire State Building

On my trip to New York last week, I visited the Empire State Building. The constuction of this was an amazing accomplishment.
The entire project was done in 1 year, 45 days. At the time, it was the tallest building ever constructed. The project involved 7 million man hours and up to 4000 people a day. It came in under the $50 million budget by $9 million. The construction began in 1930, during the Great Depression in the US.
The amazing thing to me is that this was designed and constructed before the days of computers. Everything had to be done by hand. I keep a slide rule around that had belonged to my father and the other day I was trying to explain to my daughter what it was used for. No scheduling tools or CAD programs to help build this monument, and yet it was a very successful project.
Wednesday, July 02, 2008
Getting Things Done
I came across a good article yesterday about how to be more effective in getting things done, writtten by a former boss of mine, Shawn Kinkade. That article also had a link to 20 motivational tips, another article worth reading.
Interesting enough, Shawn's article mentions the book Getting Things Done by David Allen. I was talking to a friend yesterday and she also brought up this book. I don't really believe in coincidences, so there must be a reason I came across this book twice in a day.
One tip I find effective for getting things done is to identify my top three priorities at the start of each day and focus on those, avoiding distractions from other tasks and activities until they are done.
So what are your priorities for today? If you're reading this, I've already got one of mine done. Remember, it takes 21 days to adopt a new habit, so if you want to become more effective, pick a tip from one of the articles I mentioned and start today.
Interesting enough, Shawn's article mentions the book Getting Things Done by David Allen. I was talking to a friend yesterday and she also brought up this book. I don't really believe in coincidences, so there must be a reason I came across this book twice in a day.
One tip I find effective for getting things done is to identify my top three priorities at the start of each day and focus on those, avoiding distractions from other tasks and activities until they are done.
So what are your priorities for today? If you're reading this, I've already got one of mine done. Remember, it takes 21 days to adopt a new habit, so if you want to become more effective, pick a tip from one of the articles I mentioned and start today.
Labels:
effectiveness,
Getting Things Done
Monday, June 23, 2008
Setting Goals
Well I ran Grandma’s Marathon in Duluth Minnesota over the weekend. I didn’t go as fast as I wanted. I was originally thinking 3 hours 10 minutes. As I got going, I settled into a pace to get me to the finish in 3:15. However, it started warming up, I started slowing down, and I finished in just over 3:25.
It’s good to set goals to move you forward, but some times you just can’t reach your goals and you have to know when to re-adjust. If I had tried to finish in 3:10 from the start, I probably would have dropped out by around 18 miles. It happened to me once, so I know. However, by knowing when to reset my goal, I was still able to finish.
I’ve been on projects that set off with some lofty goals, but is that really good? Is it really motivating to give people an impossible target, or is it more demoralizing? As project managers, our objective is the success of the project, but we have to know how to define what that means.
I don’t consider my marathon a failure because I didn’t hit my original target goal. I still ran over 26 miles in less then three and a half hours. I finished in 472nd place out of 9800 runners, so I was in the top 5%. I know there will be other races in my life that I will exceed my goals, so I’m happy with the results.
It’s good to set goals to move you forward, but some times you just can’t reach your goals and you have to know when to re-adjust. If I had tried to finish in 3:10 from the start, I probably would have dropped out by around 18 miles. It happened to me once, so I know. However, by knowing when to reset my goal, I was still able to finish.
I’ve been on projects that set off with some lofty goals, but is that really good? Is it really motivating to give people an impossible target, or is it more demoralizing? As project managers, our objective is the success of the project, but we have to know how to define what that means.
I don’t consider my marathon a failure because I didn’t hit my original target goal. I still ran over 26 miles in less then three and a half hours. I finished in 472nd place out of 9800 runners, so I was in the top 5%. I know there will be other races in my life that I will exceed my goals, so I’m happy with the results.
Labels:
goals
Subscribe to:
Posts (Atom)