A quite pretentious title, but a relevant topic for Itera today, as we are moving towards being a system supplier, delivering full-picture deliveries. Continuing from my presentation at last year's Itera Conference, where I tried to identify the role of a functional architect and its relation to other roles, in this year's presentation I want to look more specifically at the relation between service designer and architect, the overlaps, similarities and differences. How do we start speaking the same language, how do we avoid bottlenecks and "handovers", and how do we assure a flow from context to details throughout the system life cycle, from sale, concept and development to operation and maintenance.