Enterprise UX: What, How & Why in 20 short minutes

  • 1,193 views
Uploaded on

In this short talk given at UX Australia, August 2014, in Sydney, Dave talks about his evolving perspective on what is Enterprise UX, why it is distinct and important talk about separate from general …

In this short talk given at UX Australia, August 2014, in Sydney, Dave talks about his evolving perspective on what is Enterprise UX, why it is distinct and important talk about separate from general UX, and why it is important for more practitioners to be involved.

More in: Design
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,193
On Slideshare
0
From Embeds
0
Number of Embeds
3

Actions

Shares
Downloads
57
Comments
0
Likes
17

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Enterprise User Experience ~ Dave Malouf Head of Interaction Design @Rackspace @daveixd // dave.ixd@gmail.com http://about.me/daveixd 28 August, 2014 // @uxaustralia
  • 2. Enterprise User Experience? • Is there such a thing? • What changes as a designer if it is a thing? • Why you should consider doing it?
  • 3. What does enterprise mean?
  • 4. Simply put A really large monolithic organization. Where things happen really slowly, if they happen at all.
  • 5. CLUSTERFμ¢K
  • 6. Two major properties 1. Decision makers (customers) are not the end users or problem owners 2. 90% of users use 10% of your features. They each use a different 10%
  • 7. Types of Enterprise Design • In the enterprise • For the enterprise
  • 8. Poll: Is "Enterprise User Experience" a distinct practice of UX?
  • 9. A question asked of me recently • "Isn't what makes Enterprise context unique less about doing design differently and more about the context of the actions." • "Isn't it all still users with problems we are solving on their behalf?"
  • 10. Yes, AND ...
  • 11. 1.SCALE • Variation and quantity of personas • Research • Stakeholders • Complexity
  • 12. 2.Wickedness • The level of "influence" over control of the ecosystem
  • 13. 3.PACE • Funding/Sales cycles • Public quarterly reporting
  • 14. 4.Proximity • The abstracted distance between the customer and the problem owner
  • 15. Do these things change the way you need to do design?
  • 16. Here's what changes for me
  • 17. New tools • To manage scale (depth & breath) of data • Collaboration tools that connect not just people, but artifact relationships • Connect touch points & communicate the value stream
  • 18. Stories These are even more important • To connect stakeholders to problem space • Validate within contexts without building • To coalesce a shared vision • To evaluate the value stream
  • 19. Why do I do this?
  • 20. But really ...
  • 21. If the people buying & using these can do their job, ...
  • 22. ... maybe, we can make sure these people get better lives.
  • 23. Questions Dave Malouf @daveixd // dave.ixd@gmail.com http://about.me/daveixd