I’m attending sdnc13 as a sort of interested and excited outsider. As an Enterprise Architect (hate the pomposity inherent in that title) I think there is a lot I can learn (and #entarch as a community can learn) from service design. I try to understand and sense check business strategy in order to plan the foundations for execution. Often this is within the context of talking the talk of customer centricity, but doesn’t consistently nail it in its design of services. It’s not baked into the process and this is where I find the promise of service design to be refreshing and exciting.
It was interesting to me that there is obviously a feeling within the service design community that there is a sense of growing up to be done, that people have got it so now we need to capitalise and be seen to deliver, that there is now ‘crossover appeal’ into the mainstream, about ‘focus on outcomes not process’ and ‘using the right vocabulary for our clients/customers’ This was interesting for me because it’s a very similar conversation that is constantly recurring within the #entarch community.
The parallel between the conversations within the two communities are interesting to me so I thought I’d share a couple of things thoughts that have been flying around my head (I haven’t unpacked these yet)
Self awareness is good
Navel gazing is bad
Avoid the ‘meta-bollocks’ conversations
The vocabulary that is used is part of the experience for your clients and will make or break it.
What is the fundamental principle (design principle, architecture principle, categorical imperative? )
Is it?
Do nothing that can’t be viscerally related to an outcome for client and customer
Really looking forward to day two of the conference and continuing to learn more seems like a really supportive and self aware community and that can only lead to good things 🙂
