Stay Constructive When Work Gets Messy

Why a good professional attitude means staying realistic, taking initiative, and finding a useful way forward

Oct 13, 2026

In expert work, things rarely go exactly as planned. Priorities change, projects run into unexpected difficulties, decisions get delayed, and carefully prepared recommendations end up being rejected. Sometimes months of work become irrelevant because the organization has decided to go in another direction.

You may also find yourself dealing with problems that have very little to do with your own work. Another team fails to deliver something you depend on. A key person leaves the organization. Someone tries to undermine you through office politics. Management makes yet another poorly thought-out decision that makes it harder to do your work. The budget gets cut halfway through a project. Or someone suddenly demands an urgent solution to a problem that has been building up for months—but nobody bothered to tell you about it until yesterday.

These situations are familiar to anyone who has spent enough time working in organizations. You can plan carefully, communicate clearly, and do excellent work, but there will always be factors outside your control. The more complicated the work and the more people involved, the more opportunities there are for something unexpected to happen.

How you respond to these situations matters. Your expertise may help identify the problem, but your professional attitude often determines whether you make the situation better or worse.

Complex work will generate problems. Your reaction should not become an additional one.

A Positive Attitude Is Not the Same as Positive Thinking

A positive professional attitude is often associated with optimism, enthusiasm, and being pleasant to work with. These are certainly useful qualities. But I think the most important part of a positive attitude becomes visible when something goes wrong.

I am not particularly interested in the kind of positive thinking where every problem is an opportunity, every setback is a learning experience, and everything will always somehow work out in the end. Sometimes a project really is in trouble. A decision may be poorly justified, a proposed solution may be technically unfeasible, or an organization may be heading in a direction that makes little sense. Pretending otherwise would hardly be professional.

In fact, I would expect a good expert to be critical. If you recognize a serious risk, you should point it out. If a proposed approach seems unlikely to succeed, you should say so. Agreeing with everything may make you pleasant company, but it is a rather questionable way of applying your expertise.

The difference is in what comes after the criticism. Consider two ways of responding to a proposed solution that you believe will fail. You could simply explain why it is a bad idea and leave everyone feeling a little more miserable. Or you could explain the problem, its likely consequences, and the realistic alternatives available.

Both responses may be technically correct. Only the second one helps people move forward.

This is how I prefer to think about a constructive attitude. You recognize the situation for what it is, including its unpleasant aspects, and try to find a useful way forward. Sometimes this means proposing a different solution. Sometimes it means recommending that the entire initiative should be stopped. Being constructive does not require you to believe that every problem can be solved to everyone’s satisfaction. It just means approaching the situation with the intention of improving it.

Complain Less, Describe Problems Better

I complain remarkably little at work. Still, that does not mean I like everything that happens. Quite the opposite: my initial reaction to many things is critical, sometimes even negative. I can get irritated by poor decisions, inefficient ways of working, and problems that could have been avoided with a little more planning.

Complaining just rarely improves the situation. Of course, there is nothing terribly wrong with occasionally expressing frustration to a colleague. We are humans, after all. And sometimes discussing a frustrating situation with someone else can help us understand it better. The problem begins when complaining becomes our usual way of dealing with difficulties, especially in meetings where people are supposed to make decisions and get things done.

Imagine working in a project where decisions take forever, responsibilities are unclear, and different managers keep giving conflicting instructions. You might conclude that the whole project is a mess. And you might be absolutely right.

However, telling everyone that the project is a mess is unlikely to make much difference. A more useful observation would be that three managers are giving conflicting instructions, nobody has clear authority to make the final decision, and the project is therefore unable to proceed as planned.

Now we have something to work with. The problem can be discussed with the relevant people, decision-making responsibilities can be clarified, and the project may finally move forward.

The underlying principle is to translate complaints into problems that can be acted on.

This also changes how you communicate criticism. Instead of merely pointing out that there are insufficient resources, you can explain what can realistically be delivered with the available people and time. If expectations are contradictory, you can make the conflict visible and ask which objective should take priority.

A useful expert helps people understand what is wrong and what could be done about it. Repeatedly reminding everyone how badly things are going adds relatively little value, even when the observations are perfectly accurate.

A Can-Do Attitude Does Not Mean Saying Yes to Everything

People often praise colleagues for having a can-do attitude. I generally think that is a good thing. Expert work comes with unclear requirements, shifting priorities, and plenty of situations where the obvious answer seems to be that something cannot be done. It helps to work with people who are willing to explore possibilities instead of giving up at the first obstacle.

However, the concept can be interpreted in a rather strange way. In some organizations, having a can-do attitude seems to mean accepting every request, agreeing to unrealistic deadlines, and somehow delivering whatever management has come up with this time. The person who points out an obvious problem may be seen as difficult, while the one who promises to make it happen is considered wonderfully positive. At least until the deadline arrives.

I see it somewhat differently. One of the reasons organizations employ experts is their ability to assess what is realistic and sensible. If a proposed plan requires twice as much work as the available time allows, saying yes will hardly solve the problem. Neither will regularly working late to compensate for poor planning. Being flexible and willing to make an extra effort is valuable, but professional judgment is equally important.

Imagine being asked to deliver a comprehensive analysis in a week, although the work would normally take a month. You could simply explain why the request is unrealistic. Or you could promise to do your best and hope that things somehow work out. A more useful approach would be to understand what the analysis is actually needed for. Perhaps a focused review of the most important alternatives would be sufficient for now, with the remaining work completed later. Or perhaps the deadline really needs to change.

This is where I think a can-do attitude becomes valuable. Even when the original request is unrealistic, there may be other ways to achieve the underlying objective. You can suggest a different approach, reduce the scope, adjust priorities, or find a simpler solution. Sometimes the most sensible recommendation is to abandon the idea altogether and spend the time and resources on something more useful.

Of course, this also requires a willingness to take initiative and occasionally step outside your usual responsibilities. Being constructive is more than identifying problems and waiting for somebody else to solve them. When you have the opportunity to help move things forward, it makes sense to do so.

For me, a can-do attitude means being willing to look for a workable way forward, even when the initial plan falls apart. It combines initiative and flexibility with a realistic understanding of what can and should be done. After all, there is little value in promising the impossible, however positive that may sound.

Understand Broadly, Own Selectively

One challenge in expert work is deciding what to care about and what to take responsibility for. That is particularly relevant when working in large organizations, complicated projects, or roles where you need to cooperate with people from different functions and teams.

In my own work as an enterprise architect and consultant, I am used to looking at the big picture. Understanding how processes, applications, organizational responsibilities, and development initiatives depend on each other is an important part of the job. Often the most valuable observations come from recognizing connections that people working within individual teams or projects have overlooked.

However, seeing a problem does not automatically make it your responsibility to solve it. Let’s say your work depends on another team delivering something, and that team is seriously behind schedule. You should certainly understand the situation, assess its impact on your own work, and make the dependency visible to the people responsible for managing it. Perhaps you can also suggest alternatives or help coordinate a solution.

But this does not mean you should personally take over the troubled team’s responsibilities, start managing their work, or spend your days worrying about every problem they have.

This may sound obvious, but in practice the boundaries can become blurry. Particularly conscientious experts sometimes end up taking responsibility for problems simply because they are the ones who understand them. Before long, they are trying to compensate for unclear ownership, poor management, and weaknesses elsewhere in the organization.

Being helpful is generally a good thing. Taking unlimited responsibility for everything around you is a rather exhausting way of working.

Understand broadly. Own selectively.

There is an important distinction between being aware of an issue, taking appropriate action within your role, and becoming responsible for the entire outcome. You can raise concerns, communicate dependencies, propose solutions, and follow up when necessary. Other people still need to carry their own responsibilities.

A constructive attitude also means recognizing where your contribution is most useful. Sometimes the best thing you can do is make a problem visible to the right person and then return to your own work.

Stay Calm When Everything Is Suddenly Urgent

Another useful professional habit is staying reasonably calm when things start getting hectic.

Most expert jobs have their share of urgent requests. A deadline is suddenly approaching, a senior manager wants an answer immediately, or a problem appears that supposedly requires everyone’s attention. Sometimes these situations really are urgent. Other times, the urgency has more to do with somebody’s expectations or a lack of planning than with the actual consequences of waiting.

In either case, immediately adopting the same level of stress as everyone else rarely helps.

When an urgent request arrives, I think it is worth first understanding what has actually happened. What changed? What is the real deadline? What happens if the issue is addressed tomorrow rather than today? Is there something that genuinely requires immediate action, or is somebody mainly looking for reassurance that the problem is being handled?

These questions may seem rather basic, but they can quickly change how the situation looks. What initially appeared to require several people working late into the evening might turn out to be a decision that can be made in a short meeting the next morning. Or perhaps the situation really is critical, in which case understanding the problem helps focus the effort where it matters.

Calmness should not be confused with indifference or slow decision-making. When something requires urgent action, a good expert should be able to act quickly. However, acting quickly and reacting emotionally are two different things.

There is also a social aspect to this. Stress spreads easily within teams. When one person starts panicking, others may become nervous as well, and soon a significant amount of time is being spent discussing how terrible the situation is instead of addressing the actual problem.

An experienced expert can provide value simply by helping others regain a sense of proportion. Ask the relevant questions, clarify what needs to happen, and get people working on the right things.

Calm is not slowness. In complex work, it is often a way of avoiding unnecessary work.

Try Not to Take Everything Personally

Expert work can become surprisingly personal. We invest time and effort in understanding complicated problems, developing solutions, and producing recommendations. Our work often requires judgment, creativity, and years of accumulated experience. Naturally, we tend to care about the results.

This makes it frustrating when somebody rejects a recommendation, criticizes our work, or decides that a carefully prepared deliverable will never be used. The first reaction may be disappointment or even a feeling that our professional competence has been questioned.

Sometimes that interpretation is justified. Perhaps the recommendation really was poor, the analysis missed something important, or the work failed to address the actual needs. Constructive criticism deserves attention, particularly when it reveals something we could do better.

But there are plenty of other possible explanations. A decision-maker may reject an otherwise reasonable recommendation because the timing is wrong, the budget is insufficient, or the organization is unwilling to accept the associated risks. There may be competing priorities, internal politics, historical decisions, or dependencies that were never particularly visible to you.

In complex organizations, outcomes rarely depend on one person or one piece of work. This is worth remembering before concluding that an unfavorable outcome is a personal failure.

I find it useful to approach these situations with a broader question: What else could explain this outcome besides me?

The question works in both directions. It helps avoid unnecessary self-blame, but it also makes it harder to automatically blame other people. Perhaps there are legitimate reasons behind a decision that initially seems unreasonable. Understanding those reasons may be more useful than defending your original recommendation.

At the same time, professional maturity includes accepting that your work may have contributed to the problem. The point is to understand what happened and learn from it, rather than turning every setback into a judgment about yourself or someone else.

Five Habits for Staying Constructive

So, how can you maintain a constructive attitude when work gets messy? I think much of it comes down to a few practical habits rather than any fundamental change in personality.

Pause before transmitting your first reaction. Your initial thoughts about a situation may be critical, irritated, or pessimistic. That is perfectly normal. But you have some control over what you communicate to others. Before responding to a frustrating message or an unexpected change, consider what the other person actually needs from you. Your first reaction does not have to become your professional response.
Separate events from your interpretation. Somebody asking for changes to your work is an event. Concluding that your work was useless is an interpretation. Similarly, a delayed decision does not necessarily mean the decision-makers are incompetent. Distinguishing what happened from what you think it means helps you understand the situation more accurately and choose a sensible response.
Turn complaints into decisions. When something is wrong, try to identify what needs to change and who can make it happen. If there is too much work and too little time, the useful discussion concerns priorities, scope, and resources. If responsibilities are unclear, identify the decisions that need an owner. You may not always have the authority to make these decisions yourself, but you can often help others make them.
Understand broadly, own selectively. Keep yourself informed about the wider context and dependencies affecting your work. Recognize where you can contribute and where responsibility belongs elsewhere. Help others when it makes sense, but remember that being a good expert does not require personally fixing every problem you encounter.
Look for the next useful move. When things go wrong, it is tempting to spend time analyzing who made the mistake, why nobody anticipated it, and how the situation could have been avoided. These questions can be valuable, particularly when learning from what happened. But the immediate priority is often to find a workable way forward. Could you approach the problem differently, reduce the scope, adjust the timeline, or change the priorities? Sometimes the best option is to abandon the original idea altogether. A can-do attitude means being willing to explore alternatives and help move things forward, while remaining realistic about what can and should be done.

None of these habits is especially complicated. They are also easier to describe than to follow consistently, particularly when you are tired, under pressure, or dealing with the same frustrating problem for the fifth time. Still, they provide a practical way to improve how you respond to everyday difficulties.

Your Attitude Is Part of What You Deliver

I have written before about resilience, which is closely related to this topic. However, I think there is a useful distinction between the two. Resilience is partly about our capacity to absorb setbacks and recover from them. A constructive professional attitude is what other people experience from us when those setbacks happen.

This matters in expert work because our colleagues, managers, clients, and other stakeholders experience much more than the technical quality of our work. They also see how we handle uncertainty, react to criticism, deal with disagreements, and behave when plans fall apart.

You may be an excellent expert in your field, but if every unexpected problem leads to complaints, frustration, or unnecessary drama, working with you can become surprisingly difficult. On the other hand, an expert who remains calm, raises concerns clearly, and helps people find a way forward can make difficult situations considerably easier for everyone involved.

Of course, this does not mean suppressing your emotions or accepting every unreasonable demand. Sometimes the constructive response is to disagree firmly, establish boundaries, or explain that something simply cannot be delivered under the proposed conditions. Being pleasant and being professionally useful are related, but they are not quite the same thing.

I am certainly not naturally positive about everything. My first reaction is often skeptical, and sometimes even quite negative. Over the years, however, I have learned that this first reaction matters much less than what I do with it.

You can dislike a situation without adding drama to it. You can be critical without becoming cynical. And you can point out problems while still being someone who helps solve them. That, to me, is what a good attitude in expert work is largely about.