Does your organization perform business process mapping? Mapping of business processes is important if you want to understand what is happening. Mapping your "as is" processes tells you a lot about what you may already know, but also a lot about what you don't know.
When you begin to map your processes, you will start to see the activities, products, information, and decisions being made that support the process.
Some reasons to map your business processes are:
Mapping the "as is" processes will assist your team when doing detailed analysis
Helps to identify process ownership, and identifies the roles that support the process
Helps to show the difference between cycle time and value-added time
Helps to measure process performance
Helps to identify problem areas to address
Establishes performance baselines when creating "to be" processes
Identifies process bottlenecks, and disconnects
Shows relationships between activities and products
NOTE: When looking at what processes to model, the processes that cross functional business areas should be addressed first.
Three principles to keep in mind when process modeling are (in this order):
Eliminate wasted time and work
Consolidate efforts where possible
Automate (where it adds value)
When process mapping we are always asking questions like "why are we doing this", "why are we not doing that", "can this step be eliminated, consolidated, automated", "can we do this step/sub-process better, faster, smarter, cheaper”? Business process mapping can help your organization to operate more efficiently and respond to change faster, which ultimately will lead to improved customer satisfaction.
For more information be sure to Google "Business Process Mapping" or "Business Process Modeling"
Tuesday, May 03, 2005
Friday, April 22, 2005
Project Management Basics
To improve your project management results you need to look back over your organization's project management successes and failures. In doing so patterns or trends will emerge that will help you pinpoint areas for improvement. Research in the area of project management has shown the following simple steps can lead to radical improvements in your project management results.
Here are some ideas:
When starting a project a core team of competent, motivated people must be assigned as early as possible to the project and kept on the project until the end.
The project manager is held responsible for managing the success of the team and for motivating and monitoring the team's performance.
The project manager position needs to be a full-time position with documented job responsibilities.
The organization must ensure that the project manager is held responsible for the success or failure of the project.
The project sponsor's organization and/or the end user group(s) are responsible for defining the specifications of the project's product. This is not a project manager's responsibility, however the project manager works to coordinate these activities.
A project plan (word document) needs to be developed with the cooperation of the core team.
Developing the project plan is the responsibility of the team, not just the project manager.
A lessons learned/project close-out meeting needs to be held at the end of every project to determine if the project objectives were met and to identify project management process improvements for future projects.
A communications plan must be developed for the project, and kept up-to-date.
There are many other items we could add to this list, but the ones listed here are vital if an organization wants to have any success at managing projects.
Here are some ideas:
When starting a project a core team of competent, motivated people must be assigned as early as possible to the project and kept on the project until the end.
The project manager is held responsible for managing the success of the team and for motivating and monitoring the team's performance.
The project manager position needs to be a full-time position with documented job responsibilities.
The organization must ensure that the project manager is held responsible for the success or failure of the project.
The project sponsor's organization and/or the end user group(s) are responsible for defining the specifications of the project's product. This is not a project manager's responsibility, however the project manager works to coordinate these activities.
A project plan (word document) needs to be developed with the cooperation of the core team.
Developing the project plan is the responsibility of the team, not just the project manager.
A lessons learned/project close-out meeting needs to be held at the end of every project to determine if the project objectives were met and to identify project management process improvements for future projects.
A communications plan must be developed for the project, and kept up-to-date.
There are many other items we could add to this list, but the ones listed here are vital if an organization wants to have any success at managing projects.
Tuesday, April 12, 2005
Communicating with Discretion and Tact
How are your project communications? How do others perceive you? How do you perceive yourself as a communicator?
Let us review some rules of communication that will help us better manage our projects.
When making presentations know your:
OBJECTIVE – Goal, Purpose, Destination
LISTENER – Know facts about the group, the group expectations, the key people
APPROACH – Premise, Strategy, Theme, Pay-off for the Listener
When speaking with others one-on-one, use statements that show you are concerned about them. Remember the three “A”s when communicating.
APPRECIATING – Show appreciation for the other person’s problem or situation
Examples: “I appreciate you bringing this to my attention”
“Thank you for letting me know that”
ACKNOWLEDGING – This lets the other person know that you hear them
Example: "I can understand…”
“I sorry to hear that..."
ASSURING – Lets the other person know that you will help
Example: “This will be taken care of…”
“I will see to that personally.”
Some thoughts to ponder…
Project Managers that do not communicate effectively at the right times are destined to fail.
Poor communication skills have derailed many a career.
More than likely you will never be told that your communications skills are lacking.
Every project needs to have a written communication plan.
In closing, there are many good resources available to help us all improve our communication skills. A couple of books you might consider are: “The Four Agreements” and the “Seven Survival Skills for a Reengineered World”.
Wednesday, April 06, 2005
Conflict in Negotiations
In the book "Field Guide to Project Management" by David I Cleland, there is a discusson on page 282 about "Conflict in Negotiations". As the book mentions, PMI (the Project Management Institute) outlines eight project management functions that can be a source of conflict.
To paraphrase from the book, the areas are:
Scope: what is to be done (results, products, services)
Quality: what measures, what steps to be taken
Cost: financial outcomes, savings, ROI
Time: deadlines, resources, when complete
Risk: what risks are accepted, avoided, deflected
Human Resources: what resources, what skills, availability, competency
Contract/Procurement: cost, requirements/specifications, when, how, what, where
Communciations: when, how, to whom, contains what
There are several ways to approach handling conflict (see the Guide to the PMBOK), however the important point to keep in mind is we must confront the issue(s)and work with the individuals or groups to come to a win/win outcome.
Unresolved conflict can often lead to bitterness and resentment, which can linger and rise up later to sabatoge your project.
To paraphrase from the book, the areas are:
Scope: what is to be done (results, products, services)
Quality: what measures, what steps to be taken
Cost: financial outcomes, savings, ROI
Time: deadlines, resources, when complete
Risk: what risks are accepted, avoided, deflected
Human Resources: what resources, what skills, availability, competency
Contract/Procurement: cost, requirements/specifications, when, how, what, where
Communciations: when, how, to whom, contains what
There are several ways to approach handling conflict (see the Guide to the PMBOK), however the important point to keep in mind is we must confront the issue(s)and work with the individuals or groups to come to a win/win outcome.
Unresolved conflict can often lead to bitterness and resentment, which can linger and rise up later to sabatoge your project.
Wednesday, March 30, 2005
When Project Managers Attack!
As a project manager I have had my share of frustrations over the course of my career. Some days while working on certain projects I feel like why bother. I get to the point of thinking, if others don't care about the project's objectives, why should I? I can only give one good reason why the project manager should care about their projects; THAT IS WHAT WE GET PAID TO DO!
Certainly there are other reasons to care: a sense of ownership, responsibility to our customers, a commitment to finish what we started, personal pride, professional integrity, because it is the right thing to do, because others are counting on us, because as leaders we must always do what is expected, etc, etc, etc...
Project managers wear many hats. We are members of teams, leaders of teams, we are followers, we are stakeholders, we are fiscal planners, we are risk managers, risk takers, planners, schedulers, mentors, quality assurance reps, writers, motivators, listeners, we are empathetic, we are sympathetic, we demonstrate common sense when others don't, we demonstrate a fair and balanced approach to problems, and lots more.... You get the idea. You can see why we are sometimes frustrated. You can see why we need to be as professional as we can all the time.
I have communicated with many people that read this blog, and there is a lot of frustration out there in the Project Management world. The consensus seems to be that yes, there are organizations that do a good job of Project Management and have a great support structure for their project managers. But, it seems that a large majority of organizations don't do a very good job implementing and/or supporting project management, and according to what I hear, quite a few do a terrible job.
In many organizations the project manager position (if one exists) isn't viewed as a profession, but a job that can be performed by virtually anyone in the organization. That can be frustrating for those of us that consider ourselves to be professionals. We all get frustrated sometimes no matter what job we have. We all feel like we aren’t being supported which can lead us to believe that we are being “setup to fail”.
You know what, we all get paid to do a job, and sometimes the job isn't easy, fun, or structured the way we would like. If our managers value us as individuals then they should be willing to hear our ideas about what we need to be successful.
Keep in mind; the project manager can’t be successful on his or her own. They need a management structure in place that is committed to seeing Project Management succeed. Management must at least agree that Project Management adds or can add Value. Management must be able to state the Value that Project Management is adding or should be adding to the organization. If management can’t do that then you probably need to find a new place to work. It is that important.
As you probably know by reading this blog I usually try to reinforce the basics of Project Management, and today won't be any different.
Rule #1 - Team Conflict hurts Projects!
Team members need to remember that they must manage their departmental responsibilities as well as their project tasks to support the project to which they are assigned. Their management needs to assist the team members in setting priorities so that the project work doesn't suffer when the departmental work becomes more important.
Rule 2 - Management Apathy Hurts Projects!
All levels of impacted management must remember that if they are not engaged and interested in a project's success then their lack of support is a major contributor to project failure.
Rule #3 - Poor Planning Hurts Projects!
Project Management can only work when the project manager is given time to plan properly. Also, the project sponsor must explain the project's objectives clearly, and most importantly, obtain the entire team's commitment to meet the all of the project's objectives (this is a critical planning component). Simple project management principle: If you Fail to Plan, then you Plan to Fail. The failure to allow enough time for proper project planning is the sponsor's fault.
Keep fighting the Good Fight!
Certainly there are other reasons to care: a sense of ownership, responsibility to our customers, a commitment to finish what we started, personal pride, professional integrity, because it is the right thing to do, because others are counting on us, because as leaders we must always do what is expected, etc, etc, etc...
Project managers wear many hats. We are members of teams, leaders of teams, we are followers, we are stakeholders, we are fiscal planners, we are risk managers, risk takers, planners, schedulers, mentors, quality assurance reps, writers, motivators, listeners, we are empathetic, we are sympathetic, we demonstrate common sense when others don't, we demonstrate a fair and balanced approach to problems, and lots more.... You get the idea. You can see why we are sometimes frustrated. You can see why we need to be as professional as we can all the time.
I have communicated with many people that read this blog, and there is a lot of frustration out there in the Project Management world. The consensus seems to be that yes, there are organizations that do a good job of Project Management and have a great support structure for their project managers. But, it seems that a large majority of organizations don't do a very good job implementing and/or supporting project management, and according to what I hear, quite a few do a terrible job.
In many organizations the project manager position (if one exists) isn't viewed as a profession, but a job that can be performed by virtually anyone in the organization. That can be frustrating for those of us that consider ourselves to be professionals. We all get frustrated sometimes no matter what job we have. We all feel like we aren’t being supported which can lead us to believe that we are being “setup to fail”.
You know what, we all get paid to do a job, and sometimes the job isn't easy, fun, or structured the way we would like. If our managers value us as individuals then they should be willing to hear our ideas about what we need to be successful.
Keep in mind; the project manager can’t be successful on his or her own. They need a management structure in place that is committed to seeing Project Management succeed. Management must at least agree that Project Management adds or can add Value. Management must be able to state the Value that Project Management is adding or should be adding to the organization. If management can’t do that then you probably need to find a new place to work. It is that important.
As you probably know by reading this blog I usually try to reinforce the basics of Project Management, and today won't be any different.
Rule #1 - Team Conflict hurts Projects!
Team members need to remember that they must manage their departmental responsibilities as well as their project tasks to support the project to which they are assigned. Their management needs to assist the team members in setting priorities so that the project work doesn't suffer when the departmental work becomes more important.
Rule 2 - Management Apathy Hurts Projects!
All levels of impacted management must remember that if they are not engaged and interested in a project's success then their lack of support is a major contributor to project failure.
Rule #3 - Poor Planning Hurts Projects!
Project Management can only work when the project manager is given time to plan properly. Also, the project sponsor must explain the project's objectives clearly, and most importantly, obtain the entire team's commitment to meet the all of the project's objectives (this is a critical planning component). Simple project management principle: If you Fail to Plan, then you Plan to Fail. The failure to allow enough time for proper project planning is the sponsor's fault.
Keep fighting the Good Fight!
Tuesday, March 22, 2005
Loose Lips Sink Ships!
Have you ever heard of the "Three Ships to Success"? The one that is considered the best to have and/or demonstrate is Kinship. Kinship requires that you take time to nurture and build your relationships to make them stronger. The second ship is Sponsorship. This requires that a senior person in your organization take a personal interest in your career and your success. The third ship is Showmanship. This ship is your ability to delight and amaze your superiors, peers, and subordinates with your abilities and talents. While the three ships are important, without ability, skill, and knowledge the three ships will not take you very far.
While you work on your "three ships", keep in mind that if you work in a highly political environment you need to work on the following:
Don't criticize others.
Use data to back up your claims and don't exaggerate your needs or your customer's requirements.
Try to understand the political process where you work no matter how hard that may be.
Understand that many rules are out of date, no longer make sense, are not enforced, and are often ignored. Use this to your advantage, but never at the expense of another person, group, or your organization's reputation.
Prove yourself through your efforts, not by talking about what you once did.
Be respectful of others. Keep in mind they determine if you are treating them with respect, not you.
Be reasonable (this can be difficult). Note - I'm not sure who determines reasonableness.
On a personal note, I have never liked or performed up to my highest potential in highly political environments. The things I have listed above are weaknesses of mine and are things I need to work on to be a better project manager.
Remember relationships based on personal preference and personal styles are often major contributors to highly political organizations. Lastly, keep in mind the perceived and demonstrated values of your organization will drive the politics.
Rule of the day, the Three Ships of Success can help you to overcome political hurdles.
Tuesday, March 15, 2005
Project Management - Don't Do These Things
Don’t believe everything you are told about a potential project’s benefits. Investigate for yourself and plan accordingly.
Don’t take on a project that doesn’t have a strong sponsor that is committed to seeing the project succeed.
Don't forget that most project assumptions should also be risks.
Don't set project expectations that are higher than reality can deliver.
Don't try to define reality too early in the project planning phase.
Don’t define solutions that do not address needs.
Don’t forget to manage customer expectations.
Don’t forget to thank your team members for the good job they are doing.
Don’t be a whiner. A leader never whines and a whiner never leads.
Don’t forget that leaders need to have credibility.
Don’t forget that credibility requires honesty, dedication, commitment, and capability.
Don’t forget that people are the number one reason for project failure.
Don’t forget that empowering teams is a management function.
Don’t allow others to influence your attitude. Be positive in the face of adversity.
Don’t forget to have fun while working on your projects.
Don’t forget that Project Management is mostly art and some science.
Don’t take on a project that doesn’t have a strong sponsor that is committed to seeing the project succeed.
Don't forget that most project assumptions should also be risks.
Don't set project expectations that are higher than reality can deliver.
Don't try to define reality too early in the project planning phase.
Don’t define solutions that do not address needs.
Don’t forget to manage customer expectations.
Don’t forget to thank your team members for the good job they are doing.
Don’t be a whiner. A leader never whines and a whiner never leads.
Don’t forget that leaders need to have credibility.
Don’t forget that credibility requires honesty, dedication, commitment, and capability.
Don’t forget that people are the number one reason for project failure.
Don’t forget that empowering teams is a management function.
Don’t allow others to influence your attitude. Be positive in the face of adversity.
Don’t forget to have fun while working on your projects.
Don’t forget that Project Management is mostly art and some science.