From “Be on the lookout for thoughtless acts; they are where innovation hides in the open” to “Look for the tension between business goals and user needs; that is where innovation hides in the dark” I’m going to try and share several different considerations for bringing Design to Enterprise Software Development.
There is a new provocation today, and it’s the most enjoyable one yet. Technology is necessary but not sufficient…irrespective of the vendor selection to deliver a richer experience, the delivery of a compelling experience, one that resolves the dynamic tension between the ROI the business seeks, and the tasks and goals their users wish to achieve, is not a technology problem. It is a Design problem.
I think my position of “user-centered methods belong to user-experience designers” is the crossing of the chasm, while “business analysts should embrace user-centered design methods” is a tactic to be employed while we are in the belly of the whale.
In this presentation, we showcase Project Hendrix at Adobe, we talk about the importance of Design in technology, we talk about how to build Flex experiences upon SAP implementations, and we introduce the idea of Experience Oriented Architecture.
XOA suggests that service granularity, and the services themselves, emerge from the needs of a presentation tier component, of an “experience”. Rather than hypothesize on the services we might want to expose we allow the user-experience of the application consuming the services to dictate the service
…let me share some of my own thoughts on what traits define an architecture as “Experience Oriented”
I’m often asked, “how do we train our technical team to do the design work” or “how do we teach our business analysts to do the design work” and my answer is always an initially flippant but somewhat heartfelt – 4 years of Design School
…a recording of presentation where I show Project Hendrix, allowing our customer service agents to help more customers, first time, in less time, every time.
..the contentious position I wanted to take amongst a SOA audience, was that focussing on the SOA challenges like governance, fine grained versus coarse grained services, OASIS specifications and service bus approaches was fine and well, but it was missing the most important consideration in software development — that all of our efforts are in service of an end user, and that we must put them in the center of our approach.
Come and hear us introduce “Experience Oriented Architecture” as a design and development approach to fusing Rich Internet Applications and Service Oriented Architecture. SAP development has never looked better