Consulting Lessons Learned

2 May 2012
Lessons learned

1. Start at the top. This introduces clarity and simplicity, or at least it should. If the top objectives are unclear then they need to be clarified and simplified.
2. Create a goal tree. Include the goal, owner, and deadline. Be MECE.
3. Establish a reporting method for each goal. What metric will be used, how often, how (email, in-person, etc.), and to whom (this should be pretty clear after creating the goal tree).
4. Step 2 is an alignment mechanism. It should help all projects and processes in the company contribute to the major company goal.
5. Projects vs. processes. They are different, but as far as I can see right now, all things in the company should be designated as either a project or a process. Projects have clear end dates, processes are ongoing. Projects may include process elements, however, for example, a task which requires multiple iterations to be completed is a process inside a project. But I don’t have that one totally flushed out yet.
6. I haven’t done it yet, but I think the real power will come in regular reporting. Accountability, baby. Make it regular, get into a rhythm and hold owners stringently accountable. Don’t let people skip out on reporting no matter what. Seriously. It must happen every period. Hunt them down.
7. Being a bit of a dictator is a good thing, because it offers clarity and focus. People don’t like constraints... but then again people love constraints. I think it’s a situation where on the surface they typically don’t like the pressure or work required, but deep down they really want someone to push them to their potential.
8. Logic trees ROCK. They help to break things down clearly. Be MECE in your trees, of course.

Also, setting up meetings with people takes FOREVER. Don't let that happen anymore, just show up and ask for a few minutes right then in person. They're not doing anything super important.