Capability over technology.
Start with what the organisation must reliably do. Select technology only after that capability is explicit.
Zürich · CTO · Systems builder
Build the system.
Skip the theatre.
I am Andy Edmonds, a CTO and systems architect. I turn complex technology into repeatable business capability, especially where trust, governance and messy reality matter.
Technically serious. Culturally open. Lightly irreverent.
Personal operating system
Online
Systems conscience
Evidence before opinion
Capability over technologySystems over symptomsEvidence over egoOwnership before permissionAlignment before motion
00 / Position
Technology is only useful when the organisation can reliably wield it.
I work where engineering, product, research and commercial strategy meet. The useful question is rarely “Which technology?” It is “What capability?”
02 / Principles
A few rules that carry actual weight.
Useful principles constrain decisions. Decorative ones merely improve the wall.
Systems over symptoms.
Repeated outcomes are usually produced by structures, incentives and information flows, not isolated personalities.
Evidence over ego.
Claims should be testable. Decisions should remain revisable. Reality gets the deciding vote.
Ownership before permission.
Clear authority and responsibility beat queues of ceremonial approval. Give people a boundary, then let them move.
Alignment before execution.
Speed without shared intent creates expensive turbulence. Align the model, then accelerate the work.
03 / Work
What I build.
Not isolated deliverables. Operating capability that can survive handover, scale and inconvenient questions.
Autonomous engineering systems
Agentic software delivery with deterministic workflow, bounded agents, durable memory, evidence and human authority at the right gates.
Product operating systems
Turn feature intent into traceable decisions, delivery contracts, feedback loops and deployed outcomes.
Commercial operating systems
Translate market evidence into a defensible customer profile, disciplined discovery, pilots and repeatable revenue motion.
Architecture and due diligence
Test technical claims, expose hidden dependencies and design for portability, sovereignty, recovery and sensible governance.
Organisation design
Decision rights, standards, team structures and operating cadence that outperform without requiring permanent heroics.
04 / Personality
Technically serious. Never self-serious.
Swiss-anchored, not Swiss-stiff. Direct, curious, practical and comfortable with difference.
Rigour with warmth
Clear standards, precise claims and direct feedback, delivered without turning the room into a tribunal.
Directness without theatre
Say the useful thing early. Avoid performance, jargon fog and the strange corporate ritual of pretending nobody noticed.
Scepticism with curiosity
Challenge weak assumptions without becoming allergic to possibility. A good question can be both sharp and generous.
Precision with play
Serious work benefits from energy, humour and a little oxygen. Solemnity is not a quality standard.
MultilingualPluralTolerantPracticalWarmly scepticalPlayful when usefulComfortable with difference
05 / Signatures
How I tend to show up.
Systems conscience
Evidence before opinion. Name the mechanism, not merely the discomfort.
Standards as manners
Good boundaries are respect made executable. They help independent people work together.
Protective bluntness
Say the difficult thing while it can still help, not after it becomes an incident report.
Client as peer
No guru theatre. Think together, expose trade-offs and leave capability behind.
Load-bearing minimalism
Remove until what remains is clear, durable and still able to carry the weight.
Sovereignty by design
Portability, privacy, accessibility and recovery are architecture, not clean-up work.
06 / Culture
Serious about the mission. Never solemn about ourselves.
The culture I trust has energy, initiative, honest early communication and room for people to grow.
Trust is built through communication.
Unused capability is a greater loss than lack of capability.
Energy is contagious.
Trajectory matters more than polish.
I can work with mistakes, inexperience, failed experiments and changing minds.
I struggle to build around silence, excuses, disengagement and capability left idle.
Selected evidence
Not a trophy cabinet.
A few signals that explain the range: distributed systems, standards, research programmes, startups and operational technology.
Co-founder and CTO, Aerial Grid
Building trustworthy aerial intelligence infrastructure and the organisational systems required to deliver it.
Co-author, OGF OCCI standard
Experience turning distributed-systems complexity into interoperable contracts that independent organisations can use.
Siemens and Intel background
Large-company engineering context combined with startup and research environments.
Multi-million Euro technical programmes
Cloud robotics, data-centre automation and large-scale test infrastructures across distributed teams.
Terraview, later acquired by Gamaya
Experience carrying technical systems through venture reality, operational constraints and ownership transition.
Start with the system
Bring me the problem that keeps changing names.
That is often where the hidden system is. We can make it explicit, give it an owner and turn it into capability.