Understanding your Job

Back in February I wrote a post about transitioning your job effectively to a new person.  I have used the same concepts and approach when helping people be more effecient and effective at their jobs as well.  What I find is that people don’t fully grasp all of the things they really do in a given day (or week, month).  Once they write it all down and analyze what they are doing is when an increase in productivity can be seen.

The tricky part is analyzing what you do and finding areas that can be improved.  People can be so deep in their work they can’t see around it – bringing in another person, which is the role I have played, is extremely benficial.

Original Post – here

photo credit: beija-flor

Getting Things Done – Almost Done!

I am near complete with the re-reading of David Allen’s Getting Things Done .  I am at the beginning of chapter 9 “Doing: Making the Best Action Choices” and have about 65 pages remaining the book.  While reading last night, I came across this sentence – “If you have a bunch of things to do on one to-list, but you actually can’t do many of them in the same context, you force yourself to continually keep reconsidering all of them.” This really hit home for me.  I know my biggest obstacle to overcome is thinking of things in context (tasks grouped by how/when you can do them) – Calls, At Computer, Errands, At Home, Work, etc.

I am still living in the one to-do list world for the time being.  I am slowly but surely starting to incorporate GTD into my workflow… and yea, it’s a bit uncomfortable.  I relate it to golf.  In golf lots of things are “backwards” – you hit down on the ball to make it go up, you hit the ball from the left side and it goes right to left, you hit it from the right side and it goes left to right – doesn’t FEEL right.  I am figuring out, much like golf, you have to trust what you are doing is correct.

I will check back in in the next week or so, I imagine I will have the book complete by then.  I am looking forward to implementing more and more of the workflow changes to my daily life.

- Bill Weber

photo credit: sookie

“Getting Things Done”… again

If you are not familiar with “Getting Things Done” or “GTD” then click here for a little background.

I first bought “Getting Things Done” by David Allen in early 2007.  I read through about half of it and then skimmed the rest – got frustrated/overwhelmed and put it down.  Really… a 43 folder system for organizing my crazy hectic life?  I don’t need 43 more of anything – unless it’s hours of vacation time.  Wait, who really uses paper anymore?  Don’t we live in the digital age with computers, PDAs and mobile phones with email?  A series of lessons learned and a 5 minute conversation brought me back to the book.

It was early 2007 and I was nortoriously unorganized.  I would agree to small, simple, to-dos from my manager and then… forget.  It frustrated the hell out of my managers and became something that would hold me back in my career if not rectified.  I was in search for the perfect tool, yes… THAT is what I needed.  If I could just find the right tool then I will be organized and all of my problems will magically disappear and I will be organized.  So I turned to Microsoft OneNote.  What a great tool!  It was perfect – note pages, tabs, colors, free form highlighting, print to pdf – it was all there.  No.  No it wasn’t.  I found that I was glued to my PC which is just a source of distractions – meeting reminders, emails arriving, other open windows of work – all grabbing for my attention.

Scrum – a Project Management Approach

Scrum – noun

1: a rugby play in which the forwards of each side come together in a tight formation and struggle to gain possession of the ball using their feet when it is tossed in among them; also: the arrangement of players in a scrum b: a usually brief and disorderly struggle or fight.  2a: (British) madhouse.  2b: a usually tightly packed or disorderly crowd

The Scrum I am talking about is none of these.  Scrum is an iterative process of software development that is typically used with agile softward development.  Even though it was intended to be for management of software development projects, it can be used in running software maintenance teams, or as a program management approach.

I have found it to be very effective in managing ongoing projects – meaning projects that are not building something from the ground-up.  If you read my post on Context Switching, you will remember the diagram of “Total Demand” to “Completed Work” – Scrum is the way in which I manage the “Total Demand”.

Consulting Basics – Dos and Don’ts

Here is a presentation that I gave to a couple internal areas a week or so ago. The presentation is a compilation of positive and negative practices that I consistently see happening with regard to meetings, email, presentations and documentation. While some of this may seem like common sense – I see these same mistakes being made time and time again. Take a couple minutes to read through this presentation and try to internalize these “dos and don’ts”.

Consulting Basics – Dos and Don’ts

- Bill Weber

photo credit: EJP Photo