Eye on the Workforce

• Evaluate AI changes based on their effect on workflow, dependencies, and rework.
• Push back on tools that create more confusion than value.
• Define success in delivery terms, not just adoption terms.
• Monitor risks created when partner and stakeholder processes start to shift.

• Break large tasks into smaller steps with clear outcomes.
• Identify which tasks AI can speed up, support, or complicate.
• Review ownership of upcoming tasks to confirm it still makes sense.
• Revisit task assumptions during each planning cycle, not just at kickoff.
• Map current workflows before adding AI steps so dependencies stay reliable.

• Add a skills and readiness check during planning.
• Log capability gaps as delivery risks.
• Build lightweight learning into the work itself.
• Adjust timelines when new tools or methods require a learning curve.

• Reintroduce buffers to absorb learning and coordination friction.
• Protect focus time so people can adapt and experiment without constant interruption.
• Watch for signs that short-term speed gains are creating long-term instability.

• Be explicit about what is known, assumed, and still changing.
• Do not commit projected AI gains to the plan until they show up in real work.
• Use short feedback loops to test where work is actually improving.
• ·Translate team-level realities clearly for stakeholders and leadership. Help sponsors and other leaders understand the difference between expected gains and proven gains.

• Powerful automated tools improve operations but disrupt roles and responsibilities of those partnering in projects. You may not know who to work with, or what their goals or priorities are. Maybe the stakeholders themselves are unsure and need to define their new process.  
• Marketplace disruptions change business benefits of projects and programs abruptly, causing the organization to pivot to another direction rapidly. Your team’s project efforts appear to be wasted.  

• You have connected activities to strategy or business needs and may even have been part of previous complex transformations.  
• You have interacted with teams, stakeholders, and leaders to understand a situation and determine an appropriate approach.  
• You have quickly defined and executed next steps.  
• You have utilized techniques of organizational change management to execute effectively. 

• Instead of expressing concern or dismay, ask questions like,  
• “How must we change to adapt to this?”
• “What is the next step now?” 
• “Who are best specialists for answering our questions?” 
• “What will the sponsor need to know?” 
• “What are the sponsor’s concerns now?” 
• “How do we prepare for reporting?” 

• Create a meeting agenda - before it is needed - specifically to address major disruptions in a positive and constructive manner. 
• Focus on characterizing what is known and the potential implications.  
• Use risk analysis language which will be effective later in informal and formal reporting to sponsor and other leaders. 
• Prepare team in advance with meetings to discuss the need to realize the disruptive forces on the work environment and the need to be flexible. Suggest situations you see in your organization that may impact your project to make the outcome more concrete. Use examples from the marketplace, upcoming organizational changes, or new technology deployments.  
• Enable your team to report on potential disruptions they see on the horizon.
• Create an organized process for closing out one effort within a disruption and starting another. Include ways to maintain team motivation and engagement.  

Tight budgets can present a minefield for relationships between your team, the sponsor, and stakeholders. If you are able to negotiate this situation effectively, you can be successful in managing the project and be respected enough to handle larger, more complex projects.

In the previous post, I covered how to make sure your team has a positive attitude going into budget risk analysis. Assuming that has occurred, you will be safe facilitating the next step, which is to complete the formal risk analysis. This post is not about the general process of risk analysis, but only guidance in handing the tight budget situation with your team.

Keep the end in mind: You do not want the sponsor and other leadership to see you or the team as fearful and not suited to manage the effort. Instead, you want to communicate areas of concern in a thoughtful manner, assuming all involved are looking for a successful project outcome. A preliminary risk analysis would work just fine in this situation.

Preliminary Risk Analysis:  Identify Budget Busters

Now it's time to let your team tell you what they are concerned about. Your facilitation will help put these concerns into concrete project risk language. Focus the discussion first on identifying those factors that will add more time than planned and thus cause an overrun of your project budget. It is easier to keep at least a couple of general categories in your mind to help project team members explain their concerns in more precise terms. The two used here are Complexity and Novelty.

For the risk analysis examples used below, assume that the budget is low because the durations of phases were too short in the initial budgetary estimate, created prior to the project team being assigned.

Address Complexity. Week after week, different types of delays can add time to complete activities. Complex projects mean more questions to address; more time for reviews, approvals and issue resolution. Consider:

• The number of stakeholders involved across the organization or enterprise
  Are there more than a recent project that took the same amount of time? Was there a similar project completed with a similar number of stakeholders that can serve as an example of more time needed?
• Required synchronization when stakeholders have standard periodic meetings where you must present content for approval
  Are these sessions monthly, quarterly?
• Mid-project changes to stakeholder engagement process or organizational structure
  Have future changes been communicated?

Example Reporting Component. Inability to deliver new product by deadline due to expected longer duration to complete activities in most phases. The number and breadth of stakeholders involved, and the need to commit to their respective engagement requirements will add more time than previous projects to obtain input and approvals to proceed. Impact: Medium. Likelihood: High. Response/Mitigation: Document (1) effects of engagement processes and (2) early durations of issue resolutions and of obtaining approvals in order to estimate future activity durations more accurately.

Address Novelty.  More often than ever, brand new tools and processes are brought into the work environment that are disruptive to delivery expectations but also to the organization as a whole. Consider, for example:

• New powerful automations being implemented
• Use of Artificial Intelligence, where productivity improvements may have been achieved, or not
• New roles and operational processes based on either of the above

Example Reporting Component. Inability to deliver new product by deadline due to expected longer duration to complete activities in most phases. Project team is not yet proficient in using tools recently rolled out and stakeholders have concerns over how the tools work. Issues may arise that cause delays. Impact: Medium  Likelihood: Medium Response/Mitigation: Continue team training on new tools. Support stakeholder familiarization sessions for new AI tools. Document delays due to new tools and report significant to project.

Prepare for a Compelling Presentation

The next step is to write up your team's preliminary risk analysis. Choose a format that is formal, but without full rigor of standard reporting for your organization. Treat this as a helpful communication to your sponsor to raise awareness of factors that put your deadline at risk. It is better than immediately moving to the week-to-week reporting granularity that does not really capture the work environment as a whole.

It's also important to communicate these risks early. It relieves some pressure on your team, and helps you achieve understanding and support when you need to make schedule adjustments, or when you hit previously mentioned delays. Finally, you just look like you are in control despite the chaos.

You have probably experienced the disappointment of realizing that the budget you are provided is very tight for what your team is being asked to do. You feel like you are at a disadvantage from the start. Maybe the sponsor is not fully aware of what is involved. The sponsor may have unrealistic expectations. You don't want inadequate funding to reflect badly on your team!

It's easy to become demotivated at this point - IF you are not sure how to prepare for this situation.

When you are assigned a tight budget, it's time to discuss it with your team in a positive and constructive way. Your team is a valuable asset and can help manage the situation. They can anticipate problems and help develop effective communications related to those problems.

Important Understanding of Your Project Budget

Before speaking with your team, it is useful to have some background related to your project budget. If you are involved with or receive communications about organizational strategy, you may have detailed knowledge of how the budget was generated. You may have access to a business case that clarifies background and expectations. In other situations, you may only have a brief discussion with your sponsor to learn about the budget. Either way, this is good information to have before you discuss the budget with your team.

The budget may be able to be increased with justification following an escalation process. Or it may be that the solution your team is delivering will not be worth the expense beyond your assigned budget (or something close). If this information can be shared with your team, it will serve as a basis for planning. It will also help the team feel connected to the strategy.

Address any Adversarial Attitude

Once your project team finds out about a constrained budget, they will very easily fall into a frustrated “us” against “them” attitude. This will lead to unconstructive behaviors that will reduce performance and make the workplace less enjoyable, unless you take action.

You can avoid the team getting into an adversarial attitude by facilitating conversations toward an approach that is positive and constructive. As you facilitate, maintain a positive attitude to lead by example, even if you feel the frustration strongly. Listen patiently to any complaints and redirect discussion toward these points:

• The business case for the effort, including background and whether the sponsor and stakeholders prefer to increase the budget only when more information is captured during delivery.
• A tight budget is like any project constraint.  The team will plan to meet the constraint and then monitor to confirm the plan is working. Keep it routine.
• This situation can actually be an opportunity. How the team responds will show how highly developed it is. Teams that communicate accurately and in a timely fashion about the budget risks are seen as valuable in an organization. If the team is successful at letting sponsor know quickly when there is a significant danger of running overbudget – and the reason why - it will reflect well on the team.
• Outstanding teams identify risks that will be most likely to result in the budget being exceeded. Focusing on these risks in routine work and project reports is the mark of advanced teams.

Of course, you will adjust the detail of the above points based on the experience level of your team or individual team members. You can facilitate more experienced team members to persuade less experienced team members that it is possible to succeed even under a frustratingly low budget.

Be ready to field questions or statements that are based in fear. Acknowledge that fear for the benefit of the team member and other team members. A team member may have been burned before in a project with a tight budget. Once the fear has been acknowledged, it is fine to move on to facts or possible actions.

Do not give this facilitation step a quick pass. You don’t want to leave fear or resentment simmering in your team. Take the minutes necessary to air grievances and discuss opportunities.

Once you have the team looking at the tight budget more optimistically, you can move on to the next step, identifying those factors that will tend to bust your project budget. With the team’s improved attitude, they should have energy to create a good list with the knowledge that they are promoting themselves while protecting the organizational strategy.

This step of looking at budget risks will be covered in my next post.

Don’t forget that you can also find my articles on this site.

Hybrid work is causing problems. Many employers have required workers to return in some way, and workers are not happy about it. Worse, employers know return-to-office (RTO) policies have not brought about desirable results but do not know exactly what to do next. 

So, you are stuck on the front line of a problem you have little control over - again.

There is a way to turn this difficult situation into a positive, however. If you understand certain details of the background of the situation you can use your leadership skills to help meet your team goals and your employer's goals.

First, Understand the Employers' Situation

Employers brought workers back because they wanted at least two known benefits of workplace face-to-face interaction. Simply stated, these are innovation and camaraderie. Unfortunately, they did it wrong. They assumed that just being back would create the environment necessary to meet those goals. Employers are in the unenviable situation of having to force people to maintain a failed approach which makes the work environment even worse, especially for camaraderie.

• Employers are generally not sure how to meet their goals, so are forced to extend the inadequate policies while they figure it out.
• Some, who have not previously checked whether employees are actually coming to the office, are starting routine checks with sanctions for those who refuse to follow the policies.
• Workplace consultants have summarized the inadequacy here as employers not arranging for the correct activities to foster innovation and camaraderie.

Second, Understand the Employee Position

Workers generally like the flexibility afforded by working from home. They feel that they have proven they can be productive working remotely. When they have to go to work, they do not like the commute, and once they get there, they do not see any value to it. Often, "coffee badging" results where the worker comes to work only to be seen and then leaves.

• Resentment builds in the workplace - just the opposite of what employers want

These two situations make your job more difficult, but, understanding them helps you with your intervention to make office time better.

Tactics to Make Office Time Better

"Making office time better" means that you are helping meet your employer's goals while helping workers get more value out of the in-office experience. Here are some ideas to get you started. Your situation may call for something different, but your objectives are the same.

Add activities for the team to build rapport and solve problems.

Bring everyone in at the same time, consistent with their schedule.

• Conduct team-building activities that will build on the current maturity of the team.
• Eat lunch together and talk informally about shared interests.
• Identify team problems and consider solutions.

Create opportunities for innovation.

Set up interactions with unrelated teams or specialists. While this may sound unusual, innovation has been shown to arise from interaction and coordination between disparate individuals or groups. It comes from one group utilizing learning from an unrelated group.

• This is the kind of interaction employers have been hoping would happen under their RTO policies, but the policies do not necessarily facilitate these desired interactions. You, however, can help facilitate these interactions.
• Ask team members what will work for them. They may want to have a session with an expert or meet with another team to create best practices. Suggest that they think about cross functional groups to have face to face conversations with to see how disparate groups solve similar problems or work successfully in the work environment.
• Bring experts in to talk face-to-face with your team. Help make sure there is a low-stress, positive atmosphere where sharing is low-risk. Let the experts talk about how they do things and let your team focus on anything they find useful.
• "Innovation" in this case is high levels of improvement quickly by using new tools, processes or techniques unknown previously.

An Important Next Step for Your Career

Once you understand what leaders are after and what workers are experiencing, you can intervene effectively to increase worker satisfaction and improve their ability to innovate. But don't forget a critical step: Once you do this, communicate to managers and leaders what you have done. If you have achieved positive results, communicate them.

If your organization is stuck in an RTO-resentment ditch as so many are, you will show yourself as the rare type of leader that is part of the solution. This type of opportunity does not come around often, so use these simple steps as inspiration to form your own plan.

Bonus tip: In a larger organization, work with performance improvement specialists or middle managers to determine the best activities for your team, suggested specialists to contact, and to make it easier for you to communicate your efforts in this pain point so that you can get the recognition you deserve.

Don't miss my articles, also on ProjectManagement.com.