When the work matters, but delivery is harder than it should be
I help organisations turn product ideas into realistic delivery, recover initiatives that have lost direction, and build work systems that support the business instead of getting in its way. I bring more than 25 years across product, delivery and business transformation—and I stay close enough to the work to help make the change real.
The problem is rarely a lack of effort
Most organisations already have capable people, useful technology and good intentions. Delivery becomes difficult when priorities, ownership, processes and systems stop lining up. That is usually where I become useful.
A product needs direction. The idea is promising, but there is no shared route from ambition to decisions, a purposeful backlog and delivery that people can trust.
An initiative is losing confidence. Plans and status reports exist, yet releases keep slipping, important questions remain unanswered and nobody has a sufficiently clear view of where the work really stands.
The system has become part of the problem. monday.com, Jira or another platform was meant to simplify the work, but people still rely on manual workarounds, information disagrees and automations have become fragile.
Sometimes the answer is new technology. Sometimes it is a better process, clearer ownership or a difficult decision that has been postponed. I start by understanding which problem we actually have.
How I help
Product and delivery leadership
I help turn a product idea, strategy or set of competing requests into decisions and a route to delivery. The work can include discovery, product vision, roadmaps, backlog ownership, requirements, release readiness or embedded leadership—always keeping delivery connected to the intended business and user outcome.
Explore product and delivery leadership →
Recovery and transformation
When work has stalled or confidence is falling, I form an independent view of where things really stand, make the risks and trade-offs visible, and help create a path people can act on. That may mean restoring releases, resetting a product, aligning a supplier or changing an operating model before the situation becomes a crisis.
Explore recovery and transformation →
Work management and intelligent automation
I design and improve work-management systems around how the organisation actually operates. I work with monday.com, Jira, Confluence, Make.com, APIs and integrations, but the tool is never the starting point. The goal is simpler work, reliable information and automation that removes real effort—with training, documentation and maintainability built in.
Evidence, not slogans
A healthcare record-tracking product supported more than 10 million patients across 15+ UK installations as part of a wider healthcare portfolio
End-to-end testing identified approximately 200 issues before a major Yara release, providing the evidence needed for a more robust launch.
A cryptocurrency exchange was delivered six weeks after project initiation in a business operating within an evolving legal and regulatory framework.
AstraZeneca / Alexion engaged me on three separate occasions: first to design a practical project approach, then to lead a marketing data warehouse and dashboards project, and later to support a marketing data and AI insights initiative in a GxP environment.
Understanding comes before solutions
Early in my career, I thought finding the solution was the difficult part. Experience taught me that understanding the problem is usually harder.
I do not arrive with a pre-packaged answer. I want to understand how the business actually works, who experiences the problem, how people are working around it and what success would look like. Only then can we judge whether the answer is a new product, a different process, clearer ownership, better use of an existing system—or something else entirely.
When I work with a client, I expect to become part of the team for as long as I am there. That means explaining my thinking, asking difficult questions when they need to be asked, being honest about uncertainty and changing direction when the evidence changes.
Technology is part of the solution
Software exists to support the business—not the other way around. Sometimes the most valuable advice is that a client does not need another system; the real work is creating the conditions in which people, processes and technology can produce the intended result.
I use AI to analyse information, explore options and accelerate delivery, but it does not replace judgement. Every recommendation and every document carrying my name remains my responsibility.
What you can expect
Understand before recommending.
Explain my thinking and challenge assumptions respectfully.
Communicate openly and document properly.
Take responsibility for my work—including work accelerated by AI.
Leave behind better systems, processes, documentation and confidence rather than dependency.
That is not a proprietary methodology. It is simply how I work.
Different situations. The same practical responsibility.
I have worked across healthcare, agriculture, pharmaceuticals, software, government, banking, payments and cryptocurrency. The industries change; the delivery conversations are often remarkably similar.
Restoring release confidence
Situation: Important software releases had not been delivered successfully for several months, and management was questioning the future of the development team.
James’s contribution: As Scrum Master across operations and software teams, I introduced clearer intake, triage, risk and product processes; connected them to Jira and Confluence; and worked with teams to reduce reporting effort rather than add to it.
What changed: Releases resumed, work became more transparent across product, development, QA, support and operations, and the development team was strengthened through recruitment rather than reduced.
Making the platform fit the business
Situation: A community-services start-up had a semi-operational monday.com environment after several unsuccessful attempts. The workflows were incomplete, and the system had to remain intuitive for non-technical users.
James’s contribution: I reviewed and stabilised what existed, consolidated fragmented requirements into a phased programme, extended the platform across core operations and used Make.com where native automation was not enough.
What changed: The client gained a more coherent operational platform, end-to-end documentation and a basis for future expansion. The client then asked to continue the relationship through a support retainer.
Building an AI-native product with human control
Situation: AudioGuide is a current B2B SaaS initiative combining a museum back office, iOS and Android apps, AI-generated routes, BLE proximity, offline behaviour and multilingual content.
James’s contribution: I use AI as a high-velocity delivery capability while retaining human review: bounded work packages, explicit constraints, physical-device testing and stronger assurance for privacy, accessibility and real-world hardware behaviour.
What changed: The work provides current, hands-on evidence of AI-native product development without treating AI output as production-ready by default.
Experience is useful. Judgement is what clients need.
I have spent more than 25 years working across software delivery, product management and business transformation. I have led products and programmes, worked as a Scrum Master, managed delivery organisations, supported regulated change and implemented the systems and processes that make the work visible.
That breadth matters because product, delivery, operations and technology rarely fail in isolation. I can move between a leadership conversation and the practical detail of a backlog, workflow, integration, test plan or handover without losing sight of why the work matters.
I am based in Malta and work remotely with clients and distributed teams. My experience includes healthcare, agritech, pharmaceuticals, software and iGaming, government, banking, payments, fintech and blockchain.
Tell me what is getting in the way
You do not need to arrive with a finished scope or a preferred methodology. A useful starting point is simply:
· What is happening now?
· What has already been tried?
· What would better look like?
From there, we can decide whether a conversation would be useful and what a sensible first step might be.
