<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>User Experience on Event Modeling</title>
    <link>https://eventmodeling.org/tags/user-experience/</link>
    <description>Recent content in User Experience on Event Modeling</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 30 Apr 2020 22:01:58 -0700</lastBuildDate>
    
	<atom:link href="https://eventmodeling.org/tags/user-experience/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Great User Experience Demands Event Modeling</title>
      <link>https://eventmodeling.org/posts/user-experience-event-modeling/</link>
      <pubDate>Thu, 30 Apr 2020 22:01:58 -0700</pubDate>
      
      <guid>https://eventmodeling.org/posts/user-experience-event-modeling/</guid>
      <description>&amp;ldquo;Context Without Measures is Helplessness; Measures Without Context is Chaos&amp;rdquo;
 It is no surprise that my five-year old son thinks that Google Home is a person. He talks to it like a person; giving thanks when it does what he wanted, and gets exasperated when it doesn&amp;rsquo;t. Given this context, what would great software be like if it was a person? I would argue that a hallmark of great software is that you think of it like a servant, or better yet, a butler.</description>
    </item>
    
  </channel>
</rss>