In my view, stakeholder engagement in long or complex projects is mostly about consistency, clarity, and trust. It is not enough to communicate only when there is a problem or when a formal update is due. Stakeholders need to understand where the project stands, what has changed, what decisions are needed, and what risks may affect the outcome.

I think one practical approach is to agree early on how different stakeholders want to be informed. Some need detailed technical updates, while others only need key decisions, risks, timelines, and business impact. If everyone receives the same level of detail, communication can either become too heavy or not useful enough.

From my experience in laboratory, manufacturing, technical documentation, and process-development environments, alignment often depends on making information simple, visible, and reliable. Clear ownership, regular short updates, issue tracking, and honest communication about delays or changes can prevent a lot…

Read more

I don’t think great leaders are only born with leadership qualities. Some people may naturally have confidence, charisma, or strong communication skills, but real leadership is developed through experience, responsibility, mistakes, feedback, and the way someone responds under pressure.

For me, technical expertise is important, but it is not enough on its own. I have seen people with strong technical knowledge struggle to lead because they could not communicate clearly, listen properly, or create trust in the team. On the other hand, some quieter people can become very strong leaders because they are consistent, fair, emotionally intelligent, and able to bring clarity when things become difficult.

A truly effective leader today needs a balance: enough expertise to understand the work, enough decisiveness to move things forward, and enough emotional intelligence to understand people. Leadership is not only about giving direction; it is also about creating an environment where…

Read more

Great question. For me, one of the biggest PMO challenges is proving that the PMO is not just an administrative layer, but something that genuinely helps teams make better decisions and deliver work with less confusion.

If teams only experience the PMO through extra templates, reports, and approval steps, it can easily be seen as bureaucracy. But when the PMO creates clarity around priorities, risks, ownership, resources, decisions, and escalation points, then it becomes much more valuable.

From my experience in laboratory, manufacturing, technical documentation, and process-development environments, the challenge is often not the lack of procedures or templates. The challenge is making sure those tools are actually useful for the people doing the work and meaningful for the people making decisions.

If I were setting up or redesigning a PMO, my priorities would be: simple governance, clear definitions, lightweight reporting, visible links to strategy, and regular feedback…

Read more

Great discussion. I have not used AI in the same type of multi-state IT delivery context, but I see a very similar value in technical documentation, SOP work, laboratory organisation, and project reporting. For me, AI works best when it helps reduce the first layer of manual work: drafting, structuring information, comparing versions, building checklists, summarising logs, or turning scattered notes into something usable.

Where I would be more careful is treating AI output as a final answer. In regulated, technical, or operational environments, the risk is not only that AI gives a wrong answer, but that the answer looks structured and confident enough for people to trust it too quickly. That is where human review is still essential.

I like Kunashe’s point about automation bias. In my view, AI should support the workflow, but not replace ownership of the decision. The person using the tool still needs to understand the process, the risks, the data source, and the consequences…

Read more

Great discussion. I agree with the idea that the goal should not be to standardise everything, but to standardise the information that actually supports decision-making.

From my experience in laboratory, manufacturing, and technical documentation environments, too much standardisation can become a burden if people are forced to fill in fields that do not help them do the work better. At the same time, too little standardisation creates confusion, especially when management needs to compare status, risks, delays, deviations, or priorities across different projects or teams.

For me, the right balance is to have a common core: the same definitions for status, risk level, milestones, ownership, escalation points, and key decisions. But the working layer should stay flexible. One team may use a spreadsheet, another may use a tracker, and another may need a more detailed log, as long as the essential information can still be compared and understood in the same way.

I also…

Read more

Interesting discussion. Coming from Croatia, I think the answer depends a lot on the industry and the type of work. For example, as a student I worked full summer seasons in restaurants, and in that kind of work you do not really have the option to stop during the hottest weeks because that is exactly when the season, customers, and income are at their peak. You work hard during summer because that income can carry you through the winter.

So for some industries, especially tourism, hospitality, agriculture, construction, or outdoor work, the question is not simply how to avoid heat, but how to organise work better around it. That can mean earlier preparation, more breaks, rotating tasks, better hydration, cooling areas, and planning the hardest work outside the worst heat where possible.

I think the real issue is that heat-wave strategy cannot be the same for every sector. In some businesses you can reschedule work, while in others the demand is highest exactly during…

Read more

Thank you, Deborah — I think that is a very clear and practical way to put it. Sustainability can drive innovation, but the trade-offs need to be made visible and managed deliberately rather than discovered too late in the project.

For me, that is where project management becomes essential: not to remove every trade-off, but to help teams understand which trade-offs are acceptable, which create long-term value, and which could become risks later.

How do you think project managers can best surface these trade-offs early — through risk registers, stakeholder workshops, decision matrices, lifecycle costing, or another approach?

Thank you, Marlene — I really appreciate the way you broadened the discussion beyond environmental impact. I agree that sustainability should also be connected to operational efficiency, reputation, risk, social value, and long-term business performance.

Your point about the business case is especially important. In many projects, the challenge is that the upfront cost is visible immediately, while the operational benefits appear later and are harder to quantify at the decision stage. That can make sustainable options look less attractive even when they create stronger long-term value.

One practical way forward could be to include lifecycle cost, waste reduction, maintenance impact, stakeholder value, and regulatory risk as part of the early business case, not as a separate sustainability add-on. In your experience, which of these arguments tends to be the most convincing when teams or sponsors are hesitant because of higher initial costs?

Thank you, Nilakantha — I agree that initiation and planning are probably the most critical stages because decisions are still flexible enough to influence materials, energy use, cost, and long-term performance.

I also like your point that the focus should not stop after planning. Early integration creates the direction, but the value is only protected if sustainability remains visible during procurement, execution, and operational handover. Otherwise, good intentions from the planning phase can easily disappear under time and cost pressure.

From a procurement perspective, what do you think is the most practical way to keep sustainability criteria active throughout the project lifecycle — supplier evaluation, lifecycle costing, technical specifications, or something else?

Thank you, Dalal — I really like how you framed sustainability as both a risk and value question, not only a compliance issue. That distinction is important because it changes how teams justify decisions that may look more expensive or slower at the beginning.

A practical example that comes to mind is material selection. If a more sustainable material is considered only near the end of a project, it can create delays, retesting, procurement challenges, or cost pressure. But if it is evaluated early together with performance, lifecycle cost, regulatory expectations, and supply risk, it can actually reduce uncertainty later.

I agree with you that the benefit is not always immediate, which makes the business case more difficult but also more important. How do you think project teams can make lifecycle value visible early enough so that sustainability is seen as a strategic decision rather than an added burden?

Thank you, Dalal — I really like how you framed this, especially the idea that the balance depends on the level of uncertainty.

One practical example that comes to mind is the early stage of a research or product development project. If the team locks the scope and method too early, they may end up optimizing the wrong idea instead of learning whether the idea itself is the right one. In that phase, lighter structure, short feedback loops, and space for experimentation can be much more valuable than detailed control.

But once the concept becomes clearer and the project moves closer to implementation, stronger governance, documentation, and risk control become essential. So maybe the real challenge is not choosing between traditional and flexible approaches, but knowing when to shift from exploration to control.

Have you seen a particular point in projects where flexibility should start turning into stronger governance?

Project management frameworks are designed to provide structure, control, and predictability. However, in environments that require innovation, this same structure can sometimes become a limitation rather than an advantage.

In many projects, strict planning, predefined scope, and rigid processes can reduce flexibility and make it harder to adapt to new ideas or changing conditions. On the other hand, without structure, projects risk losing direction, control, and accountability.

This creates a fundamental tension between control and creativity.

From my perspective, the challenge is not choosing between structure and flexibility, but understanding how much structure is actually needed to support innovation without suppressing it.

This raises a few important questions:

Do traditional project management approaches (e.g. highly structured planning and control) limit innovation in your experience?

Have you seen projects where more flexibility actually led to better outcomes?

How do…

Read more

Sustainability is increasingly positioned as a key driver of innovation and long-term value in project management, particularly through ESG principles and lifecycle thinking. In theory, integrating sustainability early in the project lifecycle should lead to more efficient use of resources, better outcomes, and more innovative solutions.

However, in practice, this integration often introduces new trade-offs. Projects are still constrained by time, cost, and scope, and adding sustainability requirements can increase complexity, require additional analysis, and sometimes slow down decision-making. In fast-paced environments, this can create tension between delivering quickly and delivering responsibly.

At the same time, sustainability can also act as a catalyst for innovation — pushing teams to rethink materials, processes, and stakeholder value. The real question, in my opinion, is not whether sustainability is important, but how it is implemented within real project…

Read more

I agree that balancing stakeholder expectations with limited resources is one of the biggest challenges today, especially in fast-paced environments.

From my experience, the most important thing is being realistic and transparent from the beginning. When expectations are not aligned early, it usually leads to pressure, rework, and dissatisfaction later.

What helped me the most was:

• clearly defining priorities at the start

• communicating trade-offs openly when resources are limited

• making sure stakeholders understand what is feasible within given constraints

I also found that simple but regular communication (short updates, check-ins) can prevent misunderstandings much more effectively than complex reporting.

Regarding stakeholder alignment, I agree that many issues are not technical but come from unclear roles and expectations. Even basic structure and clarity in responsibilities can make a big difference.

Overall, I think strong communication and realistic…

Read more

Balancing short-term delivery pressures with long-term sustainability is definitely challenging, especially when deadlines and costs are the main drivers. In my experience, the key is to make sustainability part of decision-making early, not something added later.

What helped me was defining a few sustainability-related criteria at the planning stage and then revisiting them during key project phases. This made it easier to justify decisions even when there was pressure to prioritise speed or cost.

In terms of tools, I found that simple approaches worked best, such as:

• including sustainability criteria in project requirements

• using stage reviews to reassess long-term impact

• considering stakeholder impact beyond immediate project goals

For measuring success, I think it’s important to go beyond the traditional time–cost–scope triangle. In addition to those, I looked at:

• resource efficiency

• long-term usability and value

• overall environmental impact (even at a…

Read more