Evgeniia Gushchina Governance & Implementation

Independent advisory · AI · IP · Data

Make complex requirements workable inside the organisation.

I diagnose the operating problem beneath a policy, risk or technology question. Then I build the ownership, controls, documents and routines needed to put the answer into use.

Discuss a problem See the work

When the work reaches me

The visible request is often only the top layer.

A document may be needed. The underlying problem is usually ownership, decision rights, missing evidence or a process that nobody can operate.

01

AI use is expanding faster than accountability.

Tools are already inside workflows, but use cases, data boundaries, review points and human responsibility remain implicit.

02

IP exists, but the chain of title is hard to prove.

Employee work, contractor output, open-source components and AI-assisted creation sit in different systems without one ownership view.

03

Data governance lives in policy, not in operations.

The organisation cannot describe the same processing activity consistently across legal, business, procurement, security and IT.

04

A cross-functional change has stalled between teams.

The design exists, but decisions, dependencies, sign-offs and adoption routines are not moving in a controlled sequence.

Advisory scope

Three systems. One implementation discipline.

01 / AI

AI adoption governance

Governance for how AI is selected, introduced and used inside real functions.

  • use-case and workflow mapping
  • data-handling boundaries
  • human review and accountability points
  • policy, decision and exception structures
  • rollout and adoption routines

02 / IP

IP and digital assets

An operating view of what the organisation owns, uses and needs to evidence.

  • chain-of-title mapping
  • asset registers and identification rules
  • employee and contractor structures
  • open-source and AI-use boundaries
  • ownership workflows and audit trail

03 / Data

Data and operational governance

Requirements translated into roles, records, controls and repeatable processes.

  • processing and responsibility maps
  • policy and procedure architecture
  • processor and vendor interfaces
  • incident and decision routines
  • implementation coordination

Scope boundary. I work on governance architecture and implementation. Jurisdiction-specific legal opinions and regulated representation remain with appropriately qualified local counsel.

How the engagement moves

Diagnose. Architect. Operationalise.

The exact scope changes, but the sequence protects the work from becoming a folder of documents nobody uses.

  1. 01

    Diagnose the system

    Interviews, document review and workflow mapping. We separate the stated request from the operational constraint underneath it.

    Output · problem map and decision brief
  2. 02

    Design the governance spine

    Roles, decision rights, controls, registers, policies, interfaces and evidence are built as one connected architecture.

    Output · operating model and working materials
  3. 03

    Move it into practice

    Workshops, sign-off waves, guidance and implementation routines make the designed system visible in daily work.

    Output · adoption rhythm and traceable handover

Selected work · Confidential technology engagement

An operating system for IP and personal data, built from an incomplete starting point.

The starting condition

A software company had no reliable chain of title, no asset register and no shared documentation for personal-data processing. The first request was narrower than the real problem.

The architecture

Work-for-hire policies, an IP identification matrix, contractor structures, asset and decision registers, data-processing policies, incident procedures, processor agreements and practical team guidance.

The live phase

An IP Management Center covering 15 numbered operational domains is designed and visible in the client's working environment. Registries, sign-offs and daily routines are still being populated and embedded.

Saudi context

Saudi requirements need their own operating translation.

I do not treat an international framework as a substitute for Saudi primary sources, institutions or operating reality. Governance design and jurisdiction-specific legal advice remain separate responsibilities.

See the Saudi approach

Working fit

The strongest engagements have a real system to change.

Good fit

  • A cross-functional problem with a decision owner
  • Access to the people who run the current process
  • Willingness to test assumptions against evidence
  • A need for structure and implementation, not a decorative policy

Outside my scope

  • Saudi legal opinions without qualified Saudi counsel
  • Technical ML engineering or security implementation
  • A pre-written conclusion that only needs a signature
  • Work that treats Saudi requirements as a generic international checklist

Advisory enquiry

Start with the point where the system stops working.

Tell me what is changing, who owns the decision and what has already been tried. I will respond if there is a credible fit.