I define what needs to be built, structure product and system, orchestrate AI-assisted implementation, test, validate and iterate. I add 13 years of operational judgement built under pressure.I combine 13 years solving real-world operational problems with product thinking, automation, documentation, testing and AI-assisted implementation. I can understand the problem, turn it into a workable solution and see it through until it can be used, checked and improved.For 13 years I coordinated services, capacity, people and incidents in real time. Today I combine that operational judgement with documentation, automation and system design to reduce errors, protect continuity and improve execution.
13 years of operational judgement included.
AQUO is the flagship product: problem, product concept, journeys, AI-assisted implementation, testing and go-to-market. NADIE shows how I approach risk, evidence and responsible AI. STUDY_OS shows the same discipline applied to governed architecture and testing. Business LAB shows productisation from idea to live operation.Business LAB shows how I took a service line from idea to live operation: offer, funnel, payment, intake and documentation. NADIE shows how I structure evidence, controls and human review. STUDY_OS shows that same discipline applied to governed architecture and automated testing. AQUO shows the functional definition and AI-assisted implementation of a complete product.The Case Note shows how I resolved a real incident without neglecting the regular operation. Business LAB shows an operation designed from scratch. NADIE, STUDY_OS and AQUO show how I turn failures and needs into controls, processes and systems.
An extraordinary incident, limited capacity and a regular operation that had to keep running. The case shows how I coordinated service recovery and what I would systematise today to keep what was learned.
View Operations Case Note 01 →A digital wellbeing product that brings daily signals together — water, sleep, energy, cycle, nutrition, mood and routines — so users can understand patterns instead of judging isolated days.
THE CASE
A deliberate safety-layer test surfaced five silent failures and led to five mandatory release checks.
Five silent failures found · five permanent release checks
Product → Brand → Positioning → Go-to-market. Beyond the product itself, I built a coherent brand system around AQUO — positioning, visual direction and go-to-market materials including a branding deck and a pitch deck. Implementation details available in conversation.
Closed beta, pre-revenue: billing not activated.
Visit AQUO →Today is not a score. It is context.
A local-first product that analyses digital journeys to detect where people could be confused, blocked, excluded or unable to recover — before the organisation notices.
THE CASE
A release control blocks publication if the product claims anything it cannot demonstrate — the system is not allowed to assert a finding without evidence behind it.
177 automated tests passing + 7 end-to-end suites
Technical beta: no real pilots yet, synthetic scenarios only.
Visit NADIE →System built from zero to plan, execute and adapt study with continuity, traceability and recovery when a session fails.
THE CASE
Later integration introduced a Planner and Learning Engine with a HOY / LEARN / CHECK / FIN session flow.
696/696 integration tests passing · verified Phase 4B checkpoint
Principles: evidence before assumptions, adaptation without punishment, Mastery ≠ Exam Readiness.
A practical system for capturing requests, structuring information, clarifying priorities and producing reusable documentation with AI and no-code automation.
THE CASE
A pre-launch audit found a missing payment route and resulted in an eight-point corrective specification.
Eight-point corrective specification · live and operational
Live and operational · no first sale yet.
Visit Business LAB →Start from the human need, map the journey, reduce friction and turn feedback into decisions.
Create structure, ownership, documentation and follow-up so good ideas become reliable execution.
Use AI where it improves speed and clarity — never where it replaces evidence, context or accountability.
When a task starts repeating, I try to stop solving it manually and turn it into a system. This is secondary evidence of how I behave as a builder — not a catalogue of primary projects.
Analytics → diagnosis → next-post recommendation.
Brand rules → content objective → structured prompt.
Personal · AQUO · Business LAB.
Concept → script → caption → production → result.
Signals → user understanding → product decisions.
Problem · audience · proposition · assumptions · evolution.
Local presence · web · social · creative growth.
Implementation details available in conversation.
For 13 years I worked in urban mobility and service operations. I coordinated services, groups and pickups, resolved incidents in real time and reorganised operations when bookings, transport or the original plan failed. That experience is now a product advantage: I know how to prioritise, decide with incomplete information and protect continuity.
The same route through a wellbeing product, a risk analyser and a service line. Seven steps, each one leaving a documented trail.
A relevant failure does not end with a fix: it should leave behind a test, control, specification, documentation or improvement that reduces recurrence.
I add the most value at the intersection of product thinking, AI-assisted build and validated execution.
Turn needs and problems into functional products and systems.
Problem framing, structure, journeys, requirements, documentation and decisions.
Use AI as an execution layer while keeping human judgement and accountability.
Test real behaviour, detect failures and create controls against recurrence.
Documentation, feedback, prioritisation, coordination and continuous improvement.
Translate needs into workable flows and systems.
Operational judgement · Documentation · Evidence-led decisions
“My path into product is not traditional. The thread connecting it is simple: I understand the problem, build the system and take responsibility for the outcome.”
My path into product is not traditional. In 2026 I built four end-to-end digital systems across different domains and worked across product definition, functional structure, journeys, documentation, AI-assisted implementation, testing and validation.
Before that, I spent 13 years solving real problems under pressure in urban mobility and service operations. The intersection of product, execution and operational judgement is where I add the most value.
Open to opportunities across Product Engineering, AI Product, Product Operations, Implementation and selected operations leadership roles.Open to opportunities across Product Operations, Implementation, AI Operations, Business Systems, Process Improvement and Technical Project Coordination.Open to opportunities across Operations, Service Operations, Customer Operations, Process Improvement, Implementation and operations coordination or leadership roles.
