Samuel · Antwerp, Belgium

Find the signal.
Shape the path.
Build what lasts.

Independent perspective for leaders navigating consequential technology, organization, AI, architecture, and transformation decisions.

25+ years across enterprise engineering, platforms, architecture, operating models, and global transformation.

Independent perspective, built in operating reality

Not a playbook. A way through.

The work is to make a difficult choice clearer: what matters, what it depends on, what it will take to carry it, and what should happen next.

I bring a practitioner’s view to choices that span leadership, technology, funding, risk, and delivery—without turning a complex situation into a generic answer.

01

Built from ambiguity

Capabilities, platforms, and operating models shaped where there was no ready-made path.

02

Designed to endure

Attention to the decisions, ownership, architecture, and habits that make change stick.

03

Grounded across contexts

Direct leadership experience across the Americas, Europe, and Singapore.

Career & academic affiliations

Experience that informs the work.

Leadership and academic experience across global enterprise technology, product, consulting, and executive education.

Employment and academic affiliations only; no client, partnership, or endorsement relationship implied. Executive MBA international modules: MIT, ETH Zurich, SMU Singapore, and AUC Cairo.

What I help clarify

Judgment for consequential change.

The recurring challenge is rarely the technology alone. It is connecting people, architecture, incentives, funding, risk, and execution into a system that can actually move.

An abstract field of connected points with a blue path moving deliberately through them.
01

Teams that can move

Operating models, accountability, decision rights, and capability building that replace organizational friction with useful momentum.

People · structure · flow
02

Wicked problems, made navigable

Mapping uncertainty, exposing hidden dependencies, and turning competing truths into a decision framework leaders can use.

Systems · ambiguity · decisions
03

Technology strategy that holds up

Architecture, platforms, AI, and investment choices designed for the operating reality—not the presentation deck.

Architecture · AI · execution
Notes from the field

The thinking is part of the work.

Writing is where ideas are tested in the open: separating signal from hype and translating technical shifts into consequential choices.

AI · Developer experience · June 2026

The AI efficiency paradox

AI makes code cheaper to produce, but it does not make understanding, verification, security, integration, or operations cheaper. The constraint moves—and leadership must redesign the system around it.

Read on LinkedIn ↗
Agentic engineering · June 2026

Code is cheap. Decisions are expensive.

When AI writes syntax, architecture, boundaries, validation, and judgment become more—not less—important. A production experiment in role-based agentic delivery.

Read on LinkedIn ↗
Technology strategy · November 2025

Use trend reports without being used by them

A trend report should be an input to thinking, never the output of strategy. Start with the business problem, triangulate the signals, and test readiness against your own terrain.

Read on LinkedIn ↗
Open-source contributions

Useful ideas should travel.

I contribute in the open so ideas can be inspected, challenged, improved, and carried further by others.

Private, reviewable AI memory

PersonalOS

A contribution toward user-owned AI memory: visible files, explicit review, and context that can move with the person instead of remaining trapped inside one product.

Portable practices for better agents

MetaSkills

A contribution toward agent work that can be reused and improved: practical, installable skills that help teams turn good workflows into useful starting points—without adopting another platform.

Reviewable AI-assisted delivery

AgentFlow SDLC

A contribution toward more dependable agentic delivery: clear roles, visible handoffs, practical guardrails, and a durable record of what happened and why.

Also contributing

Active contributions to open-source projects, maintained in my forks while pull requests are under review.

Navigating a consequential decision?

Compare notes.

If technology, organization, and execution are pulling in different directions, share a little context. Samuel will respond directly.

Prefer LinkedIn? Connect there ↗

Your details are used only to respond to this message.