What makes an assignment complex

Difficulty does not arise from the volume of materials alone. More often, it results from uncertainty or dependency between issues: the participants describe events differently, a calculation does not reconcile with the underlying data, a contract does not reflect the actual working arrangements, or a technical specification does not make the delivered result verifiable.

Sometimes the difficulty concerns only one issue. In other cases, a decision in one field changes a decision in another: clarified facts alter the legal assessment; a calculation affects the contract price; the data scope changes the requirements for an information system; and a technical specialist’s conclusion affects the acceptance procedure.

The first task is therefore to understand precisely where the difficulty lies and which circumstances determine the answer.

First define the question that needs to be answered

The initial request does not always describe the real problem accurately. A request to prepare a response may conceal an error in a calculation or a shortage of underlying documents. A contract may be requested before the parties have defined the deliverable and the acceptance procedure. A requirement to develop an information system may arise before the processes and data it is meant to support have been described.

Vladislav begins with several questions:

  • what decision needs to be made;
  • which events led to the current situation;
  • what has already been established and what is known only from the participants’ accounts;
  • which actions have previously been taken;
  • what currently prevents the issue from being resolved;
  • what consequences would follow from each available option.

This analysis distinguishes the cause of the difficulty from its outward manifestation. The original assignment may then become narrower, with a single document sufficient to resolve it. In other cases, it becomes clear that the legal issue cannot be separated from calculations, contractual terms, technical data or the decisions of other participants.

Do not replace missing information with assumptions

A sound decision begins with facts. Vladislav Naganov compares documents, correspondence, calculations, information from digital systems and the participants’ actual conduct. For every material event, he records the date and the source; contradictions are not smoothed over to produce a convenient narrative.

If one document records performance while another shows that the result was not accepted, it is necessary to establish what was delivered, when and on which terms. If an amount in a calculation does not match the underlying data, the final figure is not enough: the basis, methodology and arithmetic must be checked. If participants describe an oral agreement differently, it cannot simply be treated as an established fact.

Missing information is not replaced by the most plausible explanation. Vladislav identifies which alternatives remain possible, how they differ and which documents or actions would test them. This is particularly important in a dispute, an audit or before a decision carrying financial or legal consequences.

Account for material connections without expanding the assignment unnecessarily

Not every matter requires a large team. If the answer can be established by checking the applicable rule, a contractual term and the relevant records, the work should not be made artificially complex.

Related issues are included only when the conclusion genuinely depends on them. A legal assessment may change after the actual volume of work is checked, and contractual terms may change after the price calculation is reviewed. System requirements depend on the scope and quality of the source data, while the acceptance of a technical result must take account of the verification method determined by the relevant specialist.

Vladislav identifies these dependencies and separates material matters from secondary ones. This keeps the work focused on the decision rather than on the quantity of documents collected or participants engaged.

Compare options by their consequences

A complex situation rarely has only one possible route. Several options may be legally permissible but differ in timing, cost, required approvals and the likelihood of a later dispute.

When comparing options, Vladislav considers:

  • whether the action complies with the applicable law and contract;
  • whether the necessary authority, documents and source data are available;
  • whether the decision can be implemented within the available time;
  • what each party would need to do;
  • how the selected option would affect the other parts of the project;
  • whether the result can be verified and evidenced;
  • which objections are most likely to arise.

Complexity is not an advantage in itself. Preference is given to an option that meets the applicable requirements, can be implemented in the circumstances and serves the purpose for which the decision is being made. If the available information is insufficient, the first decision is how to obtain it.

Check that the documents are consistent

The same issue is often reflected in several documents. Requirements are recorded in the contract and technical specification, the price is supported by a calculation, performance is evidenced by a report or acceptance certificate, and changes are documented through correspondence and amendments.

These documents serve different purposes but must not describe the same facts, obligations or deliverables differently. If a contract provides for one scope, the assignment specifies another and the acceptance certificate does not show what was actually delivered, disagreement may arise even where the participants acted in good faith.

Vladislav checks the connection between the documents and the decisions:

  • whether the contractual scope reflects the actual requirement;
  • whether compliance with the stated requirements can be verified;
  • whether the calculation supports the stated amount;
  • whether rights in the resulting materials have been defined;
  • whether agreed changes have been documented;
  • whether the records show what was completed and accepted at each stage.

For a focused assignment, this review may cover only a few documents. In a large project, it may extend to the materials of several participants. The principle remains the same: one agreement must not become several incompatible versions.

Frame precise questions for subject-matter specialists

To provide a conclusion that can be applied to the project, a specialist needs the source information relevant to their question and an understanding of which decision depends on the answer.

Vladislav Naganov identifies the issues that require specialist knowledge, frames the questions and compares the answers with the other circumstances of the project. A technical specialist may need to determine which properties of a material must be tested and by which method; a software developer may assess the data and the implementation of a requirement; a financial specialist may verify the calculation methodology.

The relevant specialists determine and substantiate specialised technical content. Vladislav aligns their conclusions with the contractual terms, the parties’ rights and obligations, deadlines, performance procedure and acceptance documents. This makes the specialist conclusion usable for the decision it was intended to support.

Check whether the decision can be implemented

A document may be legally sound and still fail to answer what should happen next. Vladislav therefore examines the practical implementation of the selected option:

  • who must make or approve the decision;
  • which documents and data are required;
  • in what sequence the actions should occur;
  • which decisions by other participants affect further work;
  • how performance will be evidenced;
  • what must change if a key assumption is not confirmed.

The conclusion must reflect actual authority, deadlines, resources and working procedures rather than remain a theoretical scheme.

Show the basis for the conclusion

In a complex matter, it is important to explain the basis for a recommendation: which documents, calculations and contractual terms support it, and which assumptions still require verification.

If the outcome depends on a court, public authority, customer, counterparty or another independent participant, that dependency is taken into account when selecting the next steps. If a definitive conclusion requires testing, expert examination or a technical calculation, it cannot be replaced by a legal or managerial assessment.

This approach does not remove uncertainty where uncertainty objectively exists. It shows what can already be decided, what requires further verification and which action should come next.

What should be clear after the analysis

Depending on the assignment, the resulting material should answer some or all of the following questions:

  • which circumstances have been established and what supports them;
  • which questions remain open;
  • which options are available and how they differ;
  • which option is recommended and why;
  • who must participate in implementing it;
  • which documents need to be prepared or amended;
  • how performance and the resulting outcome will be verified and documented.

Specific examples of materials prepared are presented on the Practical experience page.

How this approach developed

Work in electoral and public law taught Vladislav Naganov to analyse conflicting information under strict deadlines and to anticipate potential objections.

Municipal office in Khimki provided practical insight into how legal and managerial decisions are implemented in municipal services and how they are affected by the authority of public bodies, the work of contractors and the interests of residents.

Managing Effective Technology Solutions LLC from 2017 to 2026 provided experience in defining assignments for project teams, working with requirements and data, contractual structuring, testing and acceptance of software systems. Technical implementation was provided by software developers and other specialists; Vladislav was responsible for managerial and contractual matters and interaction with customers.

These stages are described in greater detail in Vladislav Naganov’s biography and on the Projects and organisations page.

Complex projects at EES

Since 2026, Vladislav Naganov has applied this approach as a Partner and Head of Complex Projects Practice at Effective Engineering Solutions LLC.

Where an assignment requires several professionals or organisations, their joint work is organised through EES. Software development, engineering calculations, testing, expert examination and other specialist work are performed by participants with the relevant qualifications and authority.

The general EES engagement process is available on the corporate website. The stages, deliverables and terms of each project are agreed separately.

Vladislav Naganov’s practical experience · Vladislav Naganov’s role at EES · Discuss a complex assignment with EES