Tech Open Day: Explaining Architecture Decisions to Customers

Technical reviews used to happen internally: architects present the solution, engineers raise questions, and conclusions are recorded. This year we tried something different — we opened an architecture review to customers and explained every trade-off in language they could understand.

What we covered

• Technology choice: why we chose a mature approach for this project instead of the newest technology;
• Data: which data must be real-time, which can be delayed, and where the cost difference comes from;
• Performance: how the system stays available for the first screen, concurrency and weak network scenarios.

The questions customers asked most

Unexpectedly, customers cared less about technical terms and more about three practical questions: can the system still be changed in three years, can the data be taken back, and who is responsible when something goes wrong. These are exactly the parts we weigh most in architecture design.

What comes next

We plan to turn the tech open day into a series, each session around one topic with customers invited to join the discussion. The value of technology ultimately returns to whether the business is better supported, and helping customers understand trade-offs is part of building long-term trust.

Explaining complexity clearly is itself an engineering capability.

Thank you to every customer who joined. The topic and date of the next open day will be announced on our website and blog.