Time, quality and resources: the architecture of optimisation and its limits

My professional insights · Lyudmil Karaulanov · 6 min read

Published: 3 August 2026 · Version 1.0

“Could we finish a little earlier?” The question may be entirely reasonable. The customer is waiting, the opportunity is attractive, and the budget does not allow a major expansion of the team. People agree to make an extra effort, and the project finishes on time.

That success, however, deserves another look. How was it achieved? Was unnecessary work removed, was a better method found, or were the evenings and weekends of a few conscientious people simply used up? The answer matters if the same is asked again tomorrow.

What changes when we shorten the deadline?

Time, quality, resources and the scope of the task are connected. A shorter deadline may require more capacity or a narrower task. Greater reliability may require testing and checks that cannot be accelerated by desire alone.

At the same time, improvement is possible. We can remove duplicate data entry, unnecessary approvals and waiting time between operations. That is why I do not regard every request for savings as unreasonable. The question is what specific change will produce them.

When we change only the numbers in the brief, the burden may shift onto people or onto work after delivery. On paper, the project is complete. In reality, someone is still correcting what was missed.

The cost after delivery

A low quotation has a different value if defects, additional claims and disputes follow it. The same applies to work done internally. Fatigue, mistakes and the departure of an experienced person may emerge after the period for which we report the saving.

A good team's willingness to help when there is a real need deserves recognition. But when extraordinary effort becomes a routine prerequisite for delivery, the problem lies in the planning itself. Otherwise, people may begin to protect themselves against every new initiative, knowing that success today will become an even heavier expectation tomorrow.

What quality is needed?

Not every task requires perfection in every detail. Excessive refinement can also consume resources on something that brings the customer no benefit. In my view, the standard is determined by purpose, expectations, applicable requirements and the consequences of a defect.

Safety, reliability and maintainability deserve particular attention. They may not be apparent at first inspection. A check that has been omitted to save money does not become harmless merely because the omission is not yet visible.

Small additions change the overall task

One more feature, one more version, one more report. Each request may have a reasonable explanation. Together, they create a different project.

It is therefore useful to agree how changes in scope are accepted: what is removed, how the deadline moves and what the new requirement costs. This allows us to accept useful ideas without pretending that they require no resources. The original plan can also be revisited when circumstances change.

Which reserves are worth keeping?

Once unnecessary steps have been removed, a harder judgement follows. Does the next cut remove an unnecessary expense, or take away our ability to cope with a deviation? Minimum inventory, a second check and training a substitute all have a cost. So do the consequences of their absence.

Combining teams and infrastructure also makes sense only where there is a real benefit. We can share knowledge, equipment or a recurring service. But if we add more coordination than the work we save, the combined organisation may become more cumbersome. The real test is a comparison of resources, time and quality before and after the change.

Are we still heading towards the right goal?

Sometimes we diligently improve an activity whose future is already in doubt. We cut costs, but demand keeps shrinking. We speed up the process, but the customer now wants a different solution.

Then comes the conversation about direction. It is difficult, because investment and human effort stand behind the existing model. Even so, it seems more honest to me than putting the team under further strain without a clear prospect ahead.

Where is the point of instability?

What this concept means →

I see it where the promise to the customer is fulfilled at the expense of a resource that the plan does not acknowledge. The second danger is continuing to refine work that no longer achieves the required purpose.

The people doing the work usually see both the unnecessary steps and the boundary beyond which goodwill is no longer enough better than anyone. That is why, to me, their voice is the most useful starting point for any such change, and the fairest one too.

This material is of a general analytical nature and does not constitute individual legal, tax, financial or investment advice.