CTO Nordic 2026

• What changes when architecture decisions define business outcomes
• When technology becomes the product—not just the enabler
• Where CTO ownership begins—and where it still breaks down
• What separates companies that build from those that react

• The decisions to keep systems—and why they seemed right at the time
• Where legacy quietly blocked speed, integration, and product development
• The real cost of waiting too long to rebuild

• What changes when AI moves from feature to core product capability
• Where AI systems fail in production—and why

• Why rebuilding takes longer than expected
• When small fixes no longer solve the underlying problem
• What makes rebuilding succeed—or stall

• When cloud strategy becomes a sovereignty decision
• Owning your data vs depending on your vendors
• Designing architecture under regulatory constraints

• Where fragmented data limits product capabilities, not just reporting
• Why real-time is harder and when it actually unlocks new products
• How your data architecture constrains what you can build with AI

• Complexity vs speed in distributed systems
• Coordination overhead in microservices and platforms
• Where bottlenecks emerge in modern stacks

The reality of leading technology today

• What turned out to matter—and what didn’t
• Where we underestimated complexity and paid for it
• What we would do differently if we started today
• What will matter next—and what is not worth your time