Skip to main content

Tag: Planning

Management Skills: Understanding What Makes Delegation Effective

What should managers know about delegation? Understanding the key elements of delegation is the key to using this management skill effectively.

Delegation is a management concept that is frequently misunderstood and misused. It is entrusting an activity and its results to another person. The Merriam-Webster Dictionary defines delegation as ‘the act of empowering to act for another. In effect, this means that one person gives another the right to make decisions for him. It is this idea that underlies many managers’ reluctance to delegate.

The following information about delegation might help a manager overcome his concern about delegating that kind of decision-making power.

 

What Can and Cannot Be Delegated?

There are three terms about delegation that are often used interchangeably but they are quite different.

  • Accountability: the main feature of the manager’s job is that he is held accountable for the results of the work being done. It is a feature that is attached to that position. The manager cannot delegate accountability. No matter what work he gives over to a subordinate, he alone is accountable for the final results.
  • Responsibility: an employee might have certain responsibilities concerning the work. These are usually identified in the job description. Whether or not the employee wholeheartedly accepts those responsibilities and fulfills them is his choice. All the manager can do is offer the responsibilities of some of his work. The employee might or might not want to accept them.
  • Authority: by definition, authority is the ‘power to influence the behavior of others. A manager cannot delegate responsibility or accountability, but he can delegate authority. He can make it known that an employee is acting in his place for that particular work; that the employee has the power to influence the work being done by other staff.

 

Why Is Effective Delegation an Important Management Skill?

One function of a manager can be defined as achieving work objectives by coordinating the efforts of other people. Effective delegation has two benefits that are relevant to this.

  • A manager who delegates is practicing good time management He has more time to spend on other major areas of his job for which he is accountable. He has time to look for efficiencies in the overall work process.
  • A manager who delegates authority for certain tasks creates a working environment in which staff can learn from their successes and failures.
  • As staff assumes more responsibility under the guidance of the manager who is ultimately accountable, the entire organization grows and matures.

 

When Is Delegation Appropriate?

Here are some of the primary factors for the manager to consider when deciding whether or not to delegate.

  • Organization objectives: do not delegate amid a crisis that requires rapid, informed, decisive responses to restore the organization’s normal operations.
  • Availability of staff: it’s not just a question of how many people are available, but also, who are they, and what is their experience and competency? It might be better for the manager to do the job himself, rather than delegate to the wrong person.
  • Location: where are the employees located? If the manager works in a head office and his employees are scattered across branch offices, he should be delegating. In the interest of efficient operations, considerable authority simply has to be delegated to those people who are in the field where the actual work is happening. The scope of the delegation depends on how fast, efficient decision-making is balanced with the consistency of policy and procedures across the entire organization.
  • Culture of the organization: what is the current culture? Do managers still make all the decisions? Even if that kind of environment is already changing, employees will need a period of adjustment until they can fully accept that they are being trusted with the authority and decision-making that has been delegated.

The manager might find it easiest to look carefully at his job and identify what absolutely cannot be delegated. Then, consider everything else, perhaps a specific project at a time, or a time-limited process. There are many options. For example, an administrative assistant can answer routine letters and e-mails. Jobs that require specialized skills can be delegated to employees with those skills. The manager has to see only the results. Activities that lead to the professional development of employees and test their ability can and should be delegated.

 

Advertisement
[widget id=”custom_html-68″]

 

How to Delegate and Manage Efficiently

Business owners who are effective managers practice time management. They also have strong skills in negotiation, supervisory, and leadership. After all, “managing” equates to “achieving objectives through others.” Technically, any manager who cannot successfully delegate cannot manage, by definition. Therefore, business success depends on their willingness to motivate, trust, and reliance on their employees to produce results.

To delegate is not that simple, and when done in the wrong way, it can backfire. But when used effectively, it greatly benefits the business. Delegation is an art in business and a skill that can be learned. There’s popular workplace advice: “delegate when possible.”

 

One of the most famous and often quoted on delegation comes from an equally famous Scottish industrialist and philanthropist Andrew Carnegie who said, “The secret of success is not in doing your work but in recognizing the right man to do it.”

Here are ways business owners use to delegate successfully.

 

Match the Right Employee with the Tasks to be Delegated

Delegation takes careful thinking. The staff’s expertise, strengths, and interests are highly considered. For example, for a staff dealing directly with customer service, the role is delegated to an employee who enjoys serving customers, possesses great people skills, and knows how to investigate and solve problems.

 

Define Clear Goals and Expectations for the Assigned Tasks

Defining clear objectives eliminates the ambiguity in the process as the staff discovers for himself or themselves how to follow through. It also enhances the probability of achieving desired results.

 

Clarify Assigned Tasks

Once the right match is identified and goals clearly defined, the manager confirms that the staff understands the purpose and the goal. It is important that the manager sets clear deadlines and removes ambiguities.

 

Set-up Controls and Checkpoints

Controls and checkpoints monitor the employee’s progress. The manager or business owner discusses how progress and performance measures are evaluated as a yardstick for success.

 

More Insights on Delegation

  • Delegation is not the same as routine work assignments that fall within the normal job role of the staff. They should be identified and explained to the staff. True delegation involves giving the staff the responsibility and authority to do something that’s normally part of a manager’s job and not theirs.
  • Delegation is not “dumping” tasks either. It is not an abdication of responsibility. If employees think that the least desirable tasks are being tossed on their lap in the name of “delegation,” they will resent it.
  • New managers may tend to assume that once they delegate, they are no longer accountable for the task outcome. Handing over responsibility and authority to employees has its limits, however, ultimate accountability remains with the business owner or the manager.
  • Some managers may fall into the trap of taking an assignment back unwittingly. They might say, “Here, let me show you,” and end up doing the whole assigned task themselves. A competent manager avoids this by letting employees solve problems for themselves.

Delegating greatly improves efficiency through proper planning and communication. Business owners and managers can focus on high-priority issues and not get bogged down in work that depletes their time and energy. At the same time, they can develop their employees and make them more valuable to the business.

There is a certain amount of risk-taking inherent in the delegation. The manager must be willing to accept the results of the delegated work and be willing to be held accountable for them. But, if he is delegating effectively, monitoring, coaching, and supporting, the organization as a whole will benefit.

Best of PMTimes: Performance Review – Don’t Hide From Project Failure, Respond To It

Published on August 14, 2019

When you start a project you want it to succeed. But, projects fail.

 

Unless we learn from past mistakes we are destined to repeat them. To learn from the past, take a hard, unbiased and candid look at performance to discover the causes and conditions of both success and failure, document them and use them to refine your process.

I wrote about performance reviews back in 2016. Recent experience has highlighted the reality that as much as performance reviews are acknowledged to be the best way to learn from collective experience they are not always performed. This article explores the relationship between project failure and why reviews are not held and how to make them effective when they are.

Projects Fail

The article Project Management Statistics: 45 Stats You Can’t Ignore has a recent compilation of statistics regarding project performance. The article reports that project success has been rising, according to PMI and other survey sources. But, cost and schedule overruns and benefits shortfalls are still significant. For example, a “A PWC study of over 10,640 projects found that a tiny, tiny portion of companies – 2.5% – completed 100% of their projects successfully. The rest either failed to meet some of their original targets or missed the original budget or deadlines. These failures extract a heavy cost – failed IT projects alone cost the United States $50-$150B in lost revenue and productivity. (Gallup).” [2 IBID]

Responding To Failure

How do you and your organization respond to failures, or do you react? Do you make use of failures to promote ever greater probabilities of success? Or, is there fear, blaming and punishment and sweeping failures under the rug?

Some of the most successful people have said the following about failure
“There are no secrets to success. It is the result of preparation, hard work, and learning from failure.” Colin Powell

“Anyone who has never made a mistake has never tried anything new.” “Failure is success in progress” Albert Einstein

“I have not failed. I’ve just found 10,000 ways that won’t work.” Thomas A. Edison

The common theme is the recognition that highly intelligent and successful people accept failure and do not let it get them down. They learn from failure.

Performance Reviews

Surveys point to causes of failure and to correlations between project success and process maturity, among other factors. The surveys are useful starting points for learning. Survey data is based on a looking back at project performance to identify general tendencies.

However, to succeed, go beyond generalities. In project management, the performance review is the primary forum for learning from past performance by reflecting on how successful a project has been and the specific causes and conditions that influence success and failure. Therefore, it is a best practice to make sure project performance reviews are held and that they are effective vehicles for learning and continuous improvement.

 

Advertisement
[widget id=”custom_html-68″]

 

The Goal

The goal of a performance review is to identify practices that will inform future behavior. There is a commitment to continuously improve the process. Improvement comes out of the exploration of the things that have led to success and those that have contributed to failure. The focus is on the process. Lessons learned are transformed into proposed process changes.

Who doesn’t want to improve performance? Yet, there is resistance to doing the work to achieve it.

Step Back To Objectively Observe

It is highly effective to step back and objectively observe what you are doing and have done. There are two kinds of stepping back. One is so subtle and natural that you can be observing what you are doing while you are doing it. The other requires that you stop, observe and reflect.

Ideally, you as an individual are doing the subtle kind as you go through life – mindfully aware of what you are doing and adjusting your behavior as you go. The other kind of stepping back – to stop, observe and reflect – is equally important. The performance review is just that – a stepping back. Reflecting on whether what you are doing is what you think you should be doing, enables you to find the best way to proceed.

Stepping back allows you to choose and respond rather than react. When you document your observations and reflections during project life, you set yourself and your team up for a successful project performance review. When you do reflect on the current state of your project, go beyond the typical focus on deliverables, schedule and budget to include a sense of the health of relationships and levels of stress. Add questions like, Are there unproductive arguments? Are stakeholders enthusiastic? Are people happy?

Why Reviews Are Not Held

Project reviews are widely supported as the best way to learn from past performance. Yet, they are not always held and sometimes, when they are, they can be useless and boring. Why are project reviews not held? There are a number of causes interacting with one another – fear and blame, a history of useless reviews, poor facilitation, and not recognizing the value of performance review and improvement.

In one organization, a product development project’s review was held after the project was deemed a failure. The event was videotaped to make sure lessons learned were captured. Many months later, a consultant was called in to help the organization develop effective project management and performance methodologies. He discovered that the video was “lost”. It had been deemed too contentious and embarrassing.

The organization wanted to investigate how to avoid failure of future reviews and the video would have been a great starting point for that investigation. As the team remembered the event, they found that fear of confronting failure, blaming, lack of facilitation which led to the review devolving into a shouting match among a few assertive participants, and a lack of concrete factual material captured during the project were the primary factors that led to the review fiasco.

Summary

Some projects will fail. When they do, you can make the best of the situation by learning from the experience. Avoid a reaction that views failure as something to hide.

Instead, candidly review the experience, identify the causes of failure (and success) and use the lessons learned to refine procedures and guidelines for use in future projects. Remember, if you don’t learn from failure, you are likely going to repeat it.

Change the culture from one characterized by fear, blame and punishment, to one that values an open-minded view of failure and uses effective reviews and retrospectives to continuously improve. Establish an effective review process – the subject of the next article in this series.

Know Your Project’s Setting for Realistic Planning

In any project, your mindset and setting influence your experience. To plan realistically you must know the mindset of the players and the setting, the project’s environment. This article focuses on the setting, and what you can do you identify and consider environmental factors in planning.

Previous articles have addressed environmental factors from different perspectives[1]. Here we use PESTLE Analysis to identify environmental factors to better enable risk management and performance.

 

Identify the Factors

To be realistic, a plan must consider the project’s environment. For example without knowing the technology to be used and the nature of the relationships among major stakeholders, planners may be overly optimistic or pessimistic because they make unfounded assumptions; overlooking a legal requirement can have far reaching effects.

Performance can be improved in two ways, 1) by changing environmental conditions (if possible and practical) and 2) by accepting what cannot be changed and baking the impact into the plan. Both ways require that the conditions are identified. That is where environmental analysis comes in.

PESTLE Analysis is one of many models that help you to understand your project environment. Other models, for example SWOT Analysis, can be used instead of or with PESTLE analysis.

PESTLE Analysis assesses the Political, Economic, Sociological, Technological, Legal and Environmental factors that affect project performance. The model is usually applied on the organizational level for strategic planning. Here the focus is closer to the project itself.

 

Tacit vs. Explicit

Often, there is a tacit understanding about environmental factors. With tacit understanding, there is the risk that stakeholders do not share a common perspective of the situation. Some may be unaware of some factors; others may have different views and values. Changes may have been made or are planned that make experience less useful as an anchor for predicting the future.

Explicitly identifying and analyzing the factors helps to make sure they are meaningfully addressed. This means spending time and effort on the analysis, deciding which factors are actionable, and planning accordingly.

 

Resistance

As sensible as explicitly assessing environmental factors seems, there is resistance to it. Possible causes are, the team and its leadership may not recognize the benefits, they may believe that everyone knows how things are,  and  they may take the attitude that “we can’t do anything about the environment, so why bother talking about it.” Leadership must be willing to confront the realities of their environment, including its flaws.

 

If powerful stakeholders are eager to have realistic plans, then resistance is overcome by recognizing that one of the primary reasons for chronic late and over budget projects is not taking the project environment into account. For example, a plan will be unrealistic if it is based on the assumption that a decision will be made in a month when it always takes three because there are multiple levels of decision makers, many of whom are very busy with other priorities.

 

Advertisement
[widget id=”custom_html-68″]

 

The Factors

The environmental factors in a PASTLE analysis are described below. The purpose of the model is to raise questions that enable project managers, and planners to identify any hidden obstacles and to consider as many factors as possible. How will these issues effect the project? Do they effect multiple projects? What can be done about them to make plans more realistic and to streamline the process?

  • P – Political:

Politics is the process of making group decisions. On a macro level, there are governmental influences in the form of regulations, taxation, international and other issues. Internal politics also have an impact on the project. Is project governance effective? Is there a political issue about the way the PMO, project managers, and functional managers perceive roles and authority? Do differences in political beliefs and allegiances cause conflict among stakeholders? Is the project goal a political issue among organizational leadership? What “old grudges” and beliefs get in the way of effective collaboration?

Political issues along with the social factors are among the most difficult to address. There is a tendency to make believe they don’t exist. There may be “hot” buttons and fear of poking a hornet’s nest.

  • E – Economic

Economic factors are both internal and external. The internal ones include the perceived cost and value of the project outcome, volatility in resource costs, budget adequacy, the project budget as a proportion of the organization’s budget. How flexible is the budget? Is there a clear expectation of financial gain? External economic factors include interest rates, volatility in the cost of resources. credit availability, and market behavior.

  • S – Social

Social factors relate to stakeholder cultural norms, values, and demographics. For example, if the team includes members from different generations or cultural groups, is there potential conflict? What is the expectation and tolerance for the “Storming” stage of team development? What is the organization’s culture? Are there multiple organizations involved? Are their cultures compatible? Explicitly the way to facilitate communication, manage conflict, and make decisions can avoid unnecessary stress and conflict.

  • Technology

On the project level technology has two dimensions: the technology used to manage the project and the technology that is part of the project deliverable. Is the technology stable? Is the technology new to users and providers? What learning curves are involved? Is there adequate support? For project management is there a platform of PM software and related productivity tools? Is the platform adding value, is it well managed and supported? How is the data managed and used? What options do you have and how will each impact performance, cost, and risk? How aligned with other projects is the technology?

  • Legal

What are the contracts, rules and regulations that effect the project? How are contracts managed? Are project staff and management subject to legal liabilities? Are there audit requirements? Are there ethical issues? Common legal issues are, copyright, patents, and intellectual property, fraud, non-disclosure, consumer protection, environmental protection, data security, health and safety, discrimination and abuse.

  • Environmental

From a project manager’s perspective project performance is effected by the project environment, the environment into which the product will go, and the broader environment with its weather, climate, geographical, factors. Project and product environmental factors overlap with the other PESTLE categories.

 

Moving Forward

Using an analytical model to assess environmental factors enhances risk management and leads to better plans and improved performance. Is your approach to identifying the factors that influence your project as good as it could be? How can it be even better?

[1] Consider the Project Environment, https://www.projecttimes.com/articles/consider-the-project-environment/  by George Pitagorsky and Understanding Enterprise Environmental Factors, https://www.projecttimes.com/articles/understanding-enterprise-environmental-factors/ by Mark Romanelli

 

5 Reasons Why TeamHeadquarters Will Organize and Simplify Your Project Delivery Service

In this next instalment of my exclusive “5 Reasons Why…: series I am doing an overview of 5 reasons why you should be looking over Entry’s TeamHeadquarters platform to organize your project delivery process. Let’s examine what you can do for your project teams and organization…

Plan, execute, and monitor projects from anywhere

Simply create and manage full scale IT projects with the TeamHeadquarters project management system. Monitor task delivery results in real time and effectively communicate important updates with the project team, sponsors, and senior management. Visual dashboards provide the insight required to identify what tasks impede the project timeline.  Always have up-to-date information at your fingertips to help with timely decision making.

 

Manage project requests using the customer portal

IT departments often don’t have a formal process to receive, analyze, and approve project requests. Using the TeamHeadquarters project request forms provides a simple and effective way to manage the project request lifecycle from inception to delivery utilizing the service ticketing feature. Effectively communicate your customer’s project needs with your required decision makers.

Project forms also help the guide your customers to assist them when determining what project information they are required to submit in order to process a project request and ensure the project analysists have the ability to deliver quicker turn-around times.

 

Understand what IT support requests are causing project delays

Project resources are often called upon to support the IT team. It’s inevitable that support will be required during and after the project rollout phase. These interruptions often create delays to project task timelines. The TeamHeadquarters integrated help desk ticketing system enables the resources to provide support and report activity to better understand and communicate project delays.

 

Advertisement
[widget id=”custom_html-68″]

 

Historical reports identify what support items and project tasks were worked on, how many hours were consumed including specific dates, and comments made by the support personnel and customers. This provides the evidence for the project managers to defend project timeline delays. Project managers will have the confidence to properly communicate project delays and reference specific documents events within a single system.

 

Deliver repeatable service projects with the ticketing system and project task import

Repeatable service projects often consume considerable IT resource capacity. These service projects typically have a handful of predictable tasks and can be templated to streamline the projects. TeamHeadquarters ticket templates provides a simple way to initiate and deliver small service projects.

TeamHeadquarters also provides the ability to import a Microsoft Project plan and include the resources assigned to the tasks. This provides our customers the flexibility to create an unlimited list of task templates for multiple project types. As simple file import sets up your project in seconds. Once imported you can begin adjusting or adding tasks at will and monitor the progress in real-time.

 

Manage project and task calendar availability

Tasks are traditionally assigned with hour estimates, start and due dates, and assigned resources. Project systems often lack the ability to add these assignments to a calendar. TeamHeadquarters provides simple task calendaring and seamless synchronization with your Outlook calendar.

Team Members will now have a complete view of all calendar events including tasks and support ticket when viewing the TeamHeadquarters calendar or their Outlook calendar. To make things easier, project tasks, service tickets, and projects can be edited directly from the TeamHeadquarters calendar. No more double booking.

 

Get a complete overview of TeamHeadquarters here.

Best of PMTimes: How To Be A Better Project Manager – Advice From PM Experts

Efficiency, quality, and stability are the core values of every well-devised project.

However, these features depend on the knowledge and experience of the person behind the entire enterprise. What makes a PM’s job even more difficult is the fact that often the teams and individuals that participate in the development of a certain business project are hired and picked by the business owner.

It takes a series of personality traits, as well as a profound understanding of the task to be a good project manager, however, to get even better you should read these several pieces of advice we gathered from some of the best people in the business.

 

Keep Project Stakeholders In The Loop

The people that hired you for a certain project are not into surprises, especially if those surprises carry bad news. It might sound like a good idea to keep a setback under the radar and try to fix the problem on your own, but what if things get out of hand and there’s nowhere else to go but straight to your boss?

It’s best if you organize a talk with the stakeholders and explain the situation at hand as soon as there’s an indication things might go sideways and present your plan of action to deal with the issue. This way you’ll have the consent of the board and you might even receive help to speed up the process.

Ben Snyder, the CEO of Systemation, advises timely updates of senior management and stakeholders before doing anything beyond the previously determined course of action.

 

Keep Constant Communication With Your Team

No matter how well we plan a certain project, it’s virtually not possible to develop a plan that’s not going to hit a bump on the road. A member of the team could quit when you need all hands on deck, a social or political event might cause a setback, suppliers could run late, and there’s nothing we could do to stop these kinds of things from happening.

According to Liz Helbock, a senior director at Events.com, it’s imperative to understand that project plans and priorities could, would, and should change, which means you have to be prepared to deal with these situations. Her advice is to learn how to keep uninterrupted communication with your team so these changes won’t catch anyone unprepared.

Liz argues that the best method is to keep all team members up to date with any changes though regular meetings, emailing, and team status reports. This way, no matter which aspect of the project gets changed, the entire team would be aware of the situation and capable to respond properly.

 

Advertisement
[widget id=”custom_html-68″]

 

Keep Action Items Under Control

Cindy Calvin, an experienced marketing project manager, believes that controlling action items gives you the ability to stay in control of your project. This way you’ll always know which activities are taking place and who’s accountable for their progress.

In Cindy’s experience, it’s never a good practice to leave a team meeting without a set of action items, teams accountable for every item of each project task, as well as their specifics. It’s also important to plan actions according to priorities of the business owner, so make sure you plan deadlines for each action item so that project milestones are not endangered.

However, you should know how to filter out what’s irrelevant for the success of your project or its current status. No matter if the information comes from your boss or a member of your team, there’s bound to be a set of requests and inputs that simply have no immediate value to your project goals.

 

Win The Support Of Senior Management

Without strong support from “upstairs” projects often crash and burn or simply don’t come out as well as planned. This is why Paul Naybour from Parallel Project Training suggests that a good PM should know how to communicate with senior management and gain their support.

More experienced project managers know that executives don’t care much about your struggle to reach a certain milestone, especially if your issue demands more funds or any change that influences their plans. To win these people over, you should present your demands supported by benefits for the company such as profit grows, market positioning, and opportunities. You should make your demands about the company, not about your project.

 

Conclusion

Being a better project manager means learning from your and other people’s experience every day. It’s also a path that leads to personal and professional setbacks from which you should absorb and generate practical value. These pieces of advice are just a few road signs that you should be aware of, however, it’s up to you to improve and become the best version of yourself. So take notes, and meet every curve prepared and ready to face whatever comes after.