Tag: Skills

Best of PMTimes – The Faux Thinking: “I Know It All”

Written by Divya Kishore on September 8, 2022. Posted in Articles.

Often, I feel I am living under a delusion that I know the answers to all the questions when it relates to me.

Fair enough, right? Each of us knows ourselves the best. However, a self-assessment check is not only a healthy habit but also aids in taking corrective actions based on the results. How do I perform a self-assessment? Here’s an idea to conduct this evaluation test: Ask questions by playing the role of a stakeholder (describing your needs) and a business analyst (eliciting requirements) at the same time. I know what you are thinking, “How is interviewing myself going to add any value?” This simple yet powerful technique forces us to reflect and come up with honest responses. You will be surprised to see how much of a gap is there between what we are thinking vs what responses we give when questioned.

Imagine you are considering pursuing a certification. Here are a few questions you can ask yourself:

Interviewer (You): Why do you want to become certified?

Response from stakeholder (You): I want to enhance my professional credibility. Also, the sense of accomplishment that I met a professional goal will be satisfying.

Interviewer (You): What specific problems are you facing in your progress towards achieving this certification?

Response from stakeholder (You): I am unable to take out time to prepare for certification and tend to procrastinate.

Interviewer (You): What are you going to do to stop procrastinating?

Response from stakeholder (You): By scheduling the exam date and then backtracking to prepare based on this date.

Interviewer (You): What are the risks associated with this certification?

Response from stakeholder (You): Time and opportunity cost.

Interviewer (You): How would you measure success?

Response from stakeholder (You): Passing the certification exam on the first attempt.

Interviewer (You): What if you don’t pass in your first attempt?

Advertisement
[widget id=”custom_html-68″]

Stakeholder (You): I will focus on the topics I didn’t score well and schedule my next exam date so that I don’t procrastinate (again!)

Interviewer (You): How will this certification add value to your career?

Response from stakeholder (You): I can apply what I have learned to my daily work and it gives the external world a chance to interpret my level of knowledge in my domain.

Interviewer (You): What would you do differently from what you have done in the past?

Response from stakeholder (You): I will allocate dedicated study time and follow a schedule diligently.

A few recommendations relating to the self-assessment check:

Tailor the interview questions to whatever you would like to achieve (personally or professionally). Tip: Find sample questions online.
Questions and responses can be short or extensive.
Skip the typical questions that you would ask in a requirements elicitation session. Example: You don’t have to ask who is going to benefit from this initiative since this is an exercise for yourself.
You must be self-disciplined to conduct this interview at least once a year. Tip: Schedule a meeting on your calendar for a self-assessment check.
You must be honest when responding to questions.
You must take time to evaluate your interview results and analyze areas of improvement.

What next after this interview? Create a “to-do” list based on the interview results and post it in a place where you can see it. At a minimum, it will be a reminder to work on those action items before it goes off your radar. I hope you can follow the interview style (or come up with a style of your own) to help you to track progress towards your goals.

“My goal is not to be better than anyone else but better than I used to be” (tinybuddha.com)

Best of PMTimes: Managing Fear and Anger in Projects

Written by George Pitagorsky on August 31, 2022. Posted in Articles.

Published on: Mar 19, 2020

Fear, including anxiety, and anger are realities. They are normal. They appear in all situations, including projects.

There is a challenge – to not suppress or ignore these emotions AND to not to act out in emotionally driven behavior. Finding the place between suppression and acting out takes wisdom and skillful effort.

What are the causes of fear and anger? How can we minimize the causes? What are the side effects of being driven by them? How can the power of these emotions be channeled for productive use?

The answers to those questions require mindful introspection. It requires a process among the people involved to explore and resolve, or at least understand, the dynamics of people working together. Emotional and social intelligences along the willingness to forgive and work on oneself are used to avoid the lashing out, withdrawal, blaming, irrational expectations and the other side effects of reacting to emotions.

Causes: Uncertainty and Lack of Control

A predominant cause of fear in projects is lack of control. Uncertainty makes people feel that because they cannot predict the future they are at risk. For example, not knowing if one is safe blossoms into worry about negative outcomes. Thinking that one might not get one’s way creates anxiety that can transform itself into overly aggressive behavior.

Uncertainty and the lack of control it elicits leave many people feeling uneasy and helpless. Uneasiness and helplessness are experienced physically as unpleasant sensations in the belly, chest or throat. Thoughts and worries run rampant. We label the sensations and thoughts as the emotion fear. Similarly, we label the burning in our chest or gut and accompanying thoughts as anger.

Relationship Between Fear and Anger

Fear and anger are closely related to one another. They are both unpleasant and, may range from subtle anxiety and annoyance to terror and rage. Fear and anger occur during stressful or otherwise challenging events. People who evoke fear or anger are seen as hostile. Hostility elicits anger and conflict.

Anger can be a symptom of fear. Fear is perceived as weakness, anger as strength. When one is feeling fearful and weak, anger comes up to create a sense of strength. It is the fight part of the fight or flight response to threats. Fear is transformed into anger and directed at the someone (including oneself) or something perceived as the cause. Anger becomes a means for regaining control and a mask for the “weakness” of fear. For example, when in conflict, say, over a design alternative or a plan, the other party becomes the target of anger because there is uncertainty and the fear of a negative outcome.

Anger can be directed at an inanimate object, like a computer. This happens because one cannot control the device’s operation. Frustration arises. There is worry about not being able to get required work done on time.

A project manager might become angry at an administrative department or vendor responsible for a delay. The anger arises out of the lack of control over that department’s response or the vendor’s delivery. There is the fear that the delay will result in schedule slippage and the slippage will be blamed on the project manager.

It doesn’t matter that neither the department head nor the vendor has control. It doesn’t matter that they would like to avoid angering their client or that they have no control themselves. Nor does it matter that they are as fearful as the project manager. Fear and anger are emotions and emotions are not rational. When rationality is brought into play, the emotions can be managed effectively, without suppressing them.

What’s Wrong with Fear or Anger?

There is nothing wrong with anger or fear. Fear is a signal that triggers heightened awareness. Anger brings up lots of energy and clears the way for action. However, being driven by either of them is counterproductive.

Freezing in fear or avoiding conflict is unproductive.

In the moment, acting out in anger, might feel better than experiencing fear. However, reactively acting out in anger is unproductive and destructive. It does not lead to a positive outcome. Breaking the computer or yelling at the department head is not likely to put one in control or make things more certain. In fact, it is likely that acting out in anger will make things worse. Uncertainty increases because it is impossible to know how the other party will react to being the target of anger. A punched-out computer screen will not improve productivity. Not only that, it will only feel good for a moment. Then, there will be embarrassment, guilt and remorse followed by an expense to replace the computer.

Advertisement
[widget id=”custom_html-68″]

Neither Suppression nor Acting Out

Suppressing fear or anger is as unskillful as reactively acting out. The middle ground between acting out and suppression is recognition, acceptance and transformation.

Recognize

First, recognize the “afflictive” emotion (fear or anger afflicts one as unpleasant, painful sensations and often lead to behavior that afflicts others) as soon as possible.

This is an aspect of emotional intelligence – awareness of one’s own emotions early in the emotion’s life. Emotions grab hold in tenths of a second and then increase in intensity, taking over the mind with the need to somehow relieve the pain, or, if the emotion is a pleasant one, to keep it going. The earlier one recognizes the symptoms of an emotion the easier it is to moderate behavior.

Part of the recognition is to be aware that the emotion is not you. Saying “I am angry” or “I am afraid” sends the wrong message. It is more effective to say, “I am feeling anger.” That reinforces the reality that the emotion is a feeling and that, like all feelings, it is a temporary complex of thoughts and physical sensations.

Step back from the feeling, observe it and do not be identified with it.

Acceptance and Transformation

Once the emotion is recognized, it can be accepted. One accepts that there is anger instead of denying or suppressing it. Acceptance enables transformation.

Let’s be clear, acceptance a situation does not mean perpetuating it. No one can change existing conditions. However, one can, to a degree, influence the future. Acceptance creates the solid platform needed for effective behavior. It enables transformation.

Transformation takes the emotion’s energy and uses it to fuel skillful behavior. The emotion represents energy. Energy is neither good nor bad, it is just energy. How it is used is critical.

For example, let’s look at the situation of the vendor that realizes that there will be a delay in its delivery of a necessary product. The delay will have a ripple effect in the project. The vendor rep experiences anxiety. She fears that the project manager, who has a history of volatile behavior, will freak out. She recognizes her anxiety and can let it cause her to hold back on the truth or use it as a signal that she’d better be careful to craft a communication that while it gives the PM the truth earlier rather than later, also helps to avoid an outburst.

As for the project manager. If he recognizes and is motivated, he can catch his anger before he starts yelling at the vendor rep and instead channels his energy into assessing the impact and changing the plan to minimize disruption. He must recognize his anxiety and be candid with his stakeholders. If he is emotionally intelligent and empathetic, he will realize that the vendor rep is anxious.

The bottom line is that it is skillful to manage fear and anger without suppressing them. Doing so requires the cultivation of mindful awareness to enable recognition, acceptance and transformation.

Best of PMTimes: Project Management Strategies for Succeeding in the Fashion Industry

Written by Jennifer Hahn Masterson on August 30, 2022. Posted in Articles.

Published on: Jan 21, 2020

The fashion industry is one of the fastest-growing ones and it’s probably more unpredictable than any other.

What is “hot” today may easily not be popular tomorrow, which makes it very difficult to plan for very long periods in the future. Still, this industry needs people who know how to manage all its aspects and we can only admire them for their skills.

What people see are models showing the latest fashion trends on the runway. Some are relatively conventional, while others are quite eccentric and we enjoy looking at these works of art, but we probably don’t know what is going on behind the scenes of a fashion show. Instead, we simply admire the final result. For this result to be achieved, teams of people have worked tirelessly for months to prepare such an event and they had to be managed properly. To help you understand what happens behind the scenes, we’re prepared this list of the crucial project management strategies for succeeding in the fashion industry.

Stakeholder management

This refers to your knowledge of the market and customers, as well as your ability to successfully deal with a number of stakeholders who have an impact on your company. The list is quite long and includes, among others, trade organizations, suppliers, sponsors, partners, buyers ad distributors. If you want your company to grow and be successful, you have to establish a transparent collaboration, which facilitates excellent communication with all of them.

Planning

There are many different types of projects in fashion. They range from opening a shop (physical and/or online) to product launch, organizing a fashion show or entering a new market. Each project requires a plan that will turn your vision into reality. You need to have a plan that factors in all the vital steps to reach your goals. This is one of the trickiest things, since the fashion industry is moving fast, but that doesn’t mean you can’t plan. Actually, it means you have to devote more attention to planning, because you want your company to produce new fashion items as successfully as possible. With the fierce competition in the industry, this task is harder than ever, which only makes it more important.

KPIs

Each process needs to be analyzed to ensure the project is efficient. However, knowing what, when and how to analyze is quite a challenge. The key is analyzing relevant aspects, eliminating human bias and producing actionable data that can be used for preparing, planning and managing projects. Choose the minimum of indicators that reflect crucial parameters and trends, such as time, cost & revenue, work efficiency and work quality to get a clear picture of the direction your project is heading. Forward-thinking companies are now using a digital marketing dashboard to automate the process of data collection and processing, thus saving a lot of time.

Advertisement
[widget id=”custom_html-68″]

Risks and changes

With changes happening constantly in the business, it’s vital you stay on top of your game at all times. No matter how long your company has been successful, it you fail to anticipate future trends and identify challenges, you won’t stand very good chances of surviving. That’s why fashion companies have to identify possible risks (production failures, supply chain errors, etc.) and be prepared for sudden changes (demand change, regulatory changes etc.). Also, they should be aware that customers are much more conscious of the social impact of fashion’s pursuit of producing clothes as fast as possible. It’s true that producing cost-efficient items is important, but negative media coverage can have a devastating impact on any business and ruin a brand’s image. Hence, you need to wage the risks and benefits carefully and balance them out.

Agility

It’s very important that a fashion company and its management are agile and flexible. This means that processes, such as sales, customer management or supply chain management will be more efficient, i.e. lead to higher and faster turnover of products and better position on the market. Agility also encompasses the notion that project teams work and collaborate more efficiently. All this is eventually translated in boosted reputation and improved business results, which are the goals of every company in the world. Going by what a new Bachelor of Arts in fashion design at Raffles Milan teaches its students, the fashion system is a huge, articulated, often unpredictable territory, where a sense for the classics manages to find common ground with the extremes of experimentation.

Teamwork

A lot has been said about the importance of teamwork, and fashion companies should know it better than most other businesses. Any misunderstanding or problem in communication can have detrimental effects on the outcome. That’s why it’s important to have regular review meetings to discuss decisions and analyze processes. Every team member needs to know exactly what their responsibilities are. We can’t stress enough how crucial communication and collaboration are in the fashion industry. The ultimate goal of producing a clothing line as efficiently and quickly as possible can’t be reached unless everyone involved works together effectively.

These strategies are very important for most industries, but when it comes to the fashion industry their role simple gets more important. That’s why every project manager should be aware of them and apply them in such a way that they help the company reach its goals.

When is a Decision Final?

Written by George Pitagorsky on August 3, 2022. Posted in Articles.

This article addresses the question, when can a decision no longer be changed?

Everything we do results from a conscious or unconscious decision. When it comes to anything important, it is better to make firm conscious decisions.

In projects, changing decisions about objectives, requirements, designs, staffing, and vendor selection is disruptive and costly. Not changing them may also be disruptive and costly.

When is a Decision Final?

A decision is final when it can no longer be changed. It can no longer be changed when the decision has been completely implemented or when authority, rules, and regulations say the decision cannot be changed.

We can’t revoke a decision to build a house once the house is built. It is physically impossible (in the absence of time travel) to go back and not build it. While it is physically possible to change a decision that has been deemed final by authority, there are political ramifications.

Models, Beliefs, and Relationships

Models and beliefs about sticking to decisions influence the decision-making process. Relationships among stakeholders are affected. Some expect that once a decision has been made the decision-making ends. They believe that going back to reassess a decision is a sign of poor decision making – being sloppy, wishy-washy or indecisive.

Consider the relationship between executives, clients, requirements analysts, and implementers.

Clients and executives love decisiveness and hate ‘analysis paralysis’ – they want to ‘get on with the work’
Clients often change their minds
Requirements analysts are charged with avoiding the need for changes and communicating changes to the implementers
Implementers are often ‘annoyed’ by the changes, thinking that the clients are indecisive and oblivious of the impact of their changes and the analysts are not doing a good enough job when eliciting requirements
Analysts feel that they are not given sufficient time and do not have sufficient access to decision makers.

We value both firm decisions and the flexibility to change them.

Expect Change

Change is inevitable. Consider a conscious decision-making process:

“1) Define values, goals, objectives and specifications underlying the issue or question

2) Define the decision making and target environments

3) Agree upon decision criteria

4) Identify solution options

5) Analyze and compare solution options vis-à-vis the decision criteria

6) Decide

7) Implement the decision

8) Monitor and adjust

9) Reflect on the process for lessons learned.”[1]

We see that step seven, Implement the decision, is not the finish line. We acknowledge the need for adjusting decisions whenever conditions change.

Advertisement
[widget id=”custom_html-68″]

Decision Making and Change Management

This question of when a decision is final links decision making and project change management.

The heart of change management is deciding whether to change previously made decisions.

A change management process decides whether to allow change to earlier, frozen, decisions. Changes are costly. Changing a requirements or design decision before it is implemented costs far less than changing it afterwards. Changing a decision that has been baked into a contract can require legal proceedings. Changing a screen design in a website less costly than changing the design of a physical product, like a bridge or building once construction is started.

A Middle Way

Enable and minimize change.

We want to be flexible, open to changing our minds, and we want to avoid wasting time and effort caused by having to unnecessarily revisit decisions.

Let’s look at a case. A design team decided on the use of a certain type of handheld device. Based on that decision a procurement process was started. A couple of weeks into the procurement process for the devices, the design team changed its mind. They decided that a handheld device would not work. They changed the design to use work stations instead. This wasted the time and effort of the procurement team and the vendors they reached out to for bids.

Was the change warranted? Yes, it was recognized that use of handheld devices made operational costs excessive.

Could the design change have been avoided? Maybe. If the team avoided unnecessary changes by spending more time and effective effort to better understand the decision factors – objectives, work environment, criteria – using checklists, and making sure people speak up with ideas, comments and criticisms.

Causes

In this case, the design team became aware that they had not consider the operational issue of the loss, damage, and ‘shrinkage’ of the devices when a member spoke up to bring the operational issue to light.

Why hadn’t he/she/they spoken up earlier? Maybe the idea just dawned, or out of fear to speak up during the design sessions. Either way, it was a good thing the issue was raised and that the design team and leadership accepted the change, even though it disrupted schedules and wasted effort. The up front loss was miniscule compared to the expenses saved.

Imagine if design team leadership didn’t support the change, saying that it was too late or too politically dangerous to question the earlier decision. Not only would there have been an inferior outcome, but some members of the design team would also be demotivated, thinking that their leadership was unprofessional and cowardly.

If this kind of thing happened frequently it would be a sign that the design team’s process needed some improvement.

Action

Adapt an approach that dynamically balances enabling and avoiding changes.

Any project decision can be changed until the decision has been completely implemented. Minds change when information regarding decision factors change. While you may never be perfect, make sure your decision-making process addresses all the factors that influence the decision. Take the time to get it as right as possible the first time.

Consider how often stakeholders change their mind after having decided, and how many decisions end up being poor ones.

Do you need to devote more time and focused effort to the decision process? Do you need more formal facilitation, brainstorming, checklists, and input from experts regarding objectives, decision criteria, environmental considerations, and options?

[1] https://www.projecttimes.com/articles/the-power-of-decision-criteria/

The Courage to Try Something Old – Part 1: Facilitation

Written by Elizabeth Larson on July 13, 2022. Posted in Articles.

We know that it often takes courage to try something new. But what about trying something old? Sometimes it takes courage to do the basics, things that we know work, but for a variety of reasons are deemed to take too long or seem too “old school.” Often the old ways are not welcome. To be sure, the old ways do not always add value. But when they do, it can take courage to convince the organization that it’s worth spending the time. The first one of these oldies but goodies that I will address is about facilitating requirements meetings. Even the concept of a meeting seems a bit old school, and when you add on the discipline needed to successfully facilitate, it can seem insurmountable.

The glorious thing about requirement meetings is that rather than interviewing many stakeholders separately, which is time-consuming, we can get the stakeholders together. It’s a chance to get issues discussed, questions answered, and direction set. But stakeholders may come unprepared or with hidden agendas. There are usually different personalities and communication styles which cause different types of disruption. And it takes courage to take the time to successfully facilitate. It takes courage to keep the meeting focused. Here are three tips that will provide you courage and increase the likelihood of success.

Preparation. No matter how experienced we are, no matter how many meetings we’ve facilitated, no matter how many disruptive stakeholders we’ve encountered, we face new challenges each time we facilitate a requirements session. We can’t eliminate the disruptions, but we can minimize their effect. Thoughtful preparation with the appropriate stakeholders will help us go into each requirements event with confidence. Minimally, we need enough preparation to communicate the following before the meeting:

• Objective. This is an action, stated as a verb. Examples include: to resolve issue(s), develop a process describing a current or future state, review the results of an iteration/phase, or project.
• Desired outcome. This is a thing, stated as a noun. Examples include: decisions, issues, parking lot topics, requirement models and lists, story maps, flows and other diagrams, user stories, action items, follow-up items, and responsibilities, to name a few.
• Attendees, prep work needed of each, and expectations for their contributions during the meeting.
• Topics to be covered, who owns the topic, and approximate time to be spent on each.
• Tools and techniques to be used and how, when, and by whom.

Advertisement
[widget id=”custom_html-68″]

Meeting agreements (ground rules, protocols). The ability to keep focus during the session requires the use of meeting agreements, or ground rules. Throughout the years we have tried to soften the use of the term “ground rule,” maybe because “rule” seems so inflexible. Regardless, these agreements help keep us grounded. Getting participants to establish and then follow them, though, is tricky but necessary—necessary because disruptive participants can make everyone miserable. If we call out the disruptor, we risk breaking the safe environment and having the other participants shut down. If we do nothing, we will not successfully meet our objectives. There is no one right way to handle disruption. What has worked best for me is to anticipate disruption, include it in the prep work, and hold pre-meetings with those most likely to be disruptive. And the use of a parking lot can be one of the many agreements established.

Quick decision are not decisions. The final thought is that decisions cannot always be made during the meeting. There are a myriad of reasons why trying to curtail discussions and move forward will result in frustration and future changes. We can’t demand that decisions be during the meeting. But we can have a tentative agreement, and then it’s up to us to check in with reluctant participants as needed.
Sound a bit old school? Yes, of course. These are techniques that have been around a very long time. But they work.

We tried getting rid of meetings, and that didn’t work. We tried getting rid of meeting agreements. Chaos. We tried getting quick decisions, only to be blindsided and saddled with rework later. Sometimes the old is not the most popular, but it is the best approach, even if it takes courage to get people on board.

[i] I use the terms requirements meetings, sessions, events, and workshops synonymously.

[ii] I once suggested the use of a parking lot and some of the attendees didn’t know that it was a list of tangential topics that would be handled outside of the meeting or at a future one. They thought that we were actually going to meet in the company’s parking lot!