Technology & Operations Executive
My background spans software engineering, CTO leadership, and cross-functional operations. I build the ownership, portfolio, delivery, and governance mechanisms that turn priorities into more reliable execution.
01 · DIRECT SCOPE
Multi-team technology operations
Direct CTO responsibility spanning software delivery and adjacent technology operations in B2B iGaming.
02 · LEADERSHIP MODEL
Layered functional leadership
Led through functional and technical leaders as organizational complexity grew.
03 · MATRIX SCOPE
Portfolio and capacity steering
Cross-functional work connecting priorities, capacity, dependencies, delivery risk, and management visibility.
Problems I Own
Competing priorities, hidden dependencies, repeated replanning, and weak visibility from commitment to outcome.
Unclear decision rights, overloaded managers, recurring escalation, and cross-functional interfaces that depend on individuals.
Roadmaps, technical risk, operations work, and strategic bets competing for the same scarce capacity without a shared decision model.
Transformation that must improve leverage, resilience, and decision quality without introducing unnecessary platform or governance ownership.
Selected Track Record
TVBET
Direct authority · CTO · 2018–early 2023
Led a multi-team technology organization in B2B iGaming. The CTO scope extended beyond software engineering into DevOps/infrastructure, QA, Support, and cross-functional delivery governance, working through functional and technical leaders.
MSP360
Matrix influence · Portfolio execution
Worked across portfolio planning and governance to surface trade-offs, dependencies, delivery risk, and capacity constraints for clearer prioritization and executive steering.
How I Operate
01 · Execution is a system property
Demand, priorities, ownership, execution, evidence, and feedback have to work as one management system.
02 · Capacity is an investment decision
Backlog and portfolio choices allocate scarce organizational capacity across value, risk, learning, and capability.
03 · Autonomy needs explicit boundaries
Clear decision rights, operating signals, feedback, and exception paths reduce escalation without removing accountability.
Current Technical Practice
Public framework · release 1.1.0
A provider-neutral framework for making repository authority, ownership, lifecycle, provenance, compatibility, and validation boundaries explicit for humans and AI agents. It is a repository assessment and design framework — not an agent runtime or orchestration platform.
Method in practice
AIRepo applies the same disciplines of authority, evidence, proportionality, and bounded technical change to a current engineering context.
Selected Writing
Portfolio economics & capacity · EN
Why execution quality is not enough when the organization allocates scarce capacity to the wrong work.
Ownership, reliability & operating model · EN
How recurrence exposes fragmented ownership, weak cross-functional prioritization, and incomplete learning loops.
Relevant Mandates
Relevant for executive operating, transformation, and senior technology mandates where cross-functional authority and business-critical execution matter.