AI use is expanding faster than accountability.
Tools are already inside workflows, but use cases, data boundaries, review points and human responsibility remain implicit.
International advisory · Technology governance readiness
Make governance work inside your organisation.
I help technology companies connect requirements with clear responsibilities, practical processes and usable records. The work can begin with a focused diagnosis and continue through design and implementation.
When the work reaches me
Where the work begins.
A document may be needed. The underlying problem is usually ownership, decision rights, missing evidence or a process that nobody can operate.
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.
Data governance lives in policy, not in operations.
The organisation cannot describe the same processing activity consistently across legal, business, procurement, security and IT.
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.
Ways to work together
Start with a clear scope. Build from there.
AI, IP and data are modules of one governance practice. The entry point is the business decision that makes evidence and ownership urgent.
01 / START
Technology Governance Readiness Diagnostic
A focused 2 to 3 week engagement that shows where external scrutiny will expose the operating system and what to fix first.
- AI, IP and data baseline
- one agreed deep-dive module
- ownership and evidence gaps
- executive decision brief
- 90-day roadmap
02 / BUILD
Governance System Build
One priority module is turned into a connected operating structure after the Diagnostic shows where the work belongs.
- roles and decision rights
- controls and approval points
- policies and working records
- registers and evidence architecture
- interfaces with local specialists
03 / OPERATE
Implementation Sprint
The designed system is put through real work so ownership, records, approvals and review routines become visible in practice.
- populate priority registers
- move decisions and sign-offs
- run working sessions
- establish review cadence
- handover an operating backlog
Scope boundary. I work on governance architecture and implementation. Jurisdiction-specific legal opinions, certification, formal assurance and regulated representation remain with appropriately qualified specialists.
Current project · Software company · Ongoing
IP and personal-data governance for a software company.
The project
I am working on an IP and personal-data governance system for a software company. The project connects software and digital assets, the rights and records behind them, and the responsibilities and processes through which the organisation manages them.
My work
My work includes the governance structure and supporting policies, agreements, registers and practical guidance. Implementation is ongoing and forms part of the work with the team.
Working fit
Is this the right fit?
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 practical structure and implementation
Outside my scope
- Jurisdiction-specific legal opinions without qualified local counsel
- Certification, formal assurance or regulated representation
- Technical ML engineering or security implementation
- A predetermined conclusion or signature-only assignment
Before we speak
A closer look at the work.
Use these public materials to understand the advisory scope, see the reasoning and prepare a safe first conversation.
01PDF · 2 pages
Orientation
Technology Governance Advisory Overview
A concise view of the problems I work on, the ways an engagement can begin and what happens after the first conversation.
Open resource02PDF · 3 pages
Demonstration
From Trigger to Governance Decision
A synthetic example showing how a customer request can be translated into management decisions, ownership and a practical 30-day route.
Open resource03PDF · 1 page
Preparation
Before Our First Conversation
Five questions that are enough for an initial fit conversation, plus a clear boundary around confidential and restricted information.
Open resourceView all advisory resources
No documents or confidential material are needed for an initial fit conversation.
Where I work
Confidentiality & information handling
Confidentiality & information handling
The first conversation stays high-level.
An initial enquiry only needs public or sanitised context: the decision, timing and what is at stake. If non-public information becomes necessary, I first confirm fit and conflicts, agree confidentiality terms and an appropriate exchange route, then request only what the defined engagement requires.
- 01Minimum necessaryOnly information required for the defined work.
- 02AI boundaryNo client-confidential material in consumer AI tools.
- 03Separate permissionNo substantive disclosure or public case use without prior written agreement.
Advisory enquiry
Start with a short introduction.
At this stage, the decision, deadline, owner and high-level context are enough. We can then clarify whether the work fits and what the next step should be.