Technology Strategy
Direction, capability and architecture roadmaps.
Start a conversation
Good technology conversations often start with a hard problem.
The best starting point is a problem with both technology and organizational consequences. A short email covering the four points below is enough.
A useful start
We do not need a ready-made solution. Good context is enough.
When a conversation starts with context, constraints and the actual decision, it quickly becomes clear whether the problem is architectural, organizational or both.
- ContextWhat organizational and operational context surrounds the problem?
- ConstraintWhich constraint is genuinely non-negotiable?
- DecisionWhat decision actually needs to be made?
- ConsequenceWhat happens if the decision is wrong?
Conversation domains
Topics that tend to lead to deeper, useful conversations.
AI & Automation
Operational AI, RCA, governance and durable execution.
Cloud & Platforms
Control planes, lifecycle, self-service and modernization.
Infrastructure & Network
Systems, topology, service boundaries and productization.
Reliability
Failure, recovery, observability and runtime truth.
Infrastructure Productization
Turning technical capability into operable, usable services.