Archive for August, 2013

2nd Place at Hack the Museum at The Henry Ford

Wednesday, August 28th, 2013

We won 2nd place in Hack The Museum last month. On Saturday July 27th Cody Greene, Jeff Molsen, Paul Kaiser and I competed in a Hackathon, Hack the Museum at The Henry Ford Museum in Dearborn Michigan. Below are some screen shots of the “telephone” game we made in ONE DAY! Yes, it worked, and yes we were tired.




hfm5 hfm6

 The Opportunity

You know when you are looking at a big display case in a museum and you know they have more stuff in some back room but you can’t see it. Well our hack solves that and gives digital access to those objects. In addition we wanted to make it a fun experience, making it into a game. This game could be played pre-visit before someone comes to the museum or perhaps by kids on a kiosk while their parents are waiting in line to buy tickets.

The concept

We blended the physical and the digital. We allow the visitor to reach back into the collections from an exhibit that they are looking at and interested in. Answering “What else might be in the basement or back room?” We also allowed the different sorting/arrangement of a collection be it by date which is different than how it’s ordered in the display. It is easier to resort, rearrange digital items quickly. Lastly, we made a game that flipped or pivoted how people approach the objects. Instead of the telephone first like you see in the display, we first played a sound, and then the person had to guess which telephone made that sound.

 Overall application design

We had access to many of the museum’s API, with the web API we  used java JAXB to parse and unmarshall the results from xml to java which we used in our JSPs to display the results. We  used java xjc to generate java classes that are analogs to the xml schema and when we unmarshall the results from calling the web service those java classes are what get populated. We used APACHE HTTP client API communicating with the web service.


Official Hack the Museum Site at Maker Faire Detroit

Blog Article about the Hacking The Henry Ford (The Henry Ford Official Blog)

Deadline Detroit article highlighting the 1st place winner

Cody Greene

Jeff Molsen

Paul Kaiser




The Truth About Customer Experience

Tuesday, August 27th, 2013

Here are my notes from the article “The Truth About Customer Experience”

The Truth About Customer Experience: Touchpoints matter, but it’s the full journey that really counts.By Alex Rawson, Ewan Duncan, and Conor Jones. Harvard Business Review, September 2013, pp90-98

I’ll sum it up as how important it is to move from touchpoints to journey perspective. Solely looking at touch points is in my view “sub-optimization” similar to what occurred in supply chain management in which companies made just one link very excellent but resulted in “crack-the-whip” problems farther along the chain. (Supply Chain perspective comes from my work in automotive supply chains and the work of Goldratt from The Goal.) I caution trying to assess your progress with the approach if you just do step 1 and 2. I have seen the step 1 & 2  done well but the company then says “oh yes, we know that, we just can’t do anything about it.” The step 3 and 4 with cross functional processes and creation of “chain manager” is what is most important to deliver the value this approach can drive.

p92 “A company that manages complete journeys would not only do its best with the individual transactions but also seek to understand the broader reasons for the call, address the root causes, and create feedback loops to continuously improve interactions upstream and downstream from the call.”

p92 “Most customers weren’t fed up with any one phone call, field visit, or other interaction – in fact, they didn’t care much about those singular touch points. What reduced satisfaction was something few companies manage – cumulative experiences across multiple touch points and in multiple channels over time.”

p92 “Most service encounters were positive in a narrow sense – employees resolved the issue and hand – but the underlying problems were avoidable, the fundamental causes went unaddressed, and the cumulative effect on the customer was decidedly negative.”

p92 “But even as they work hard to optimize their contributions to the customer experience, they often lose site of what customers want”

p93 Companies need to embed customer journeys into their operating models in four ways:

  1. Identifying Key Journeys: They must identify the journeys in which they need to excel
  2. Understand Current Performance: Understand how they are currently performing in each
  3. Redesigning the Experience and Engaging the Front Line: Build cross-functional processes to redesign and support these journeys, and
  4. Sustaining at Scale by Changing Mind-Sets: Institute Cultural Change and continuous improvement to sustain the initiatives at scale.

 p93 Identify Key Journeys … both top down (executive working session) and bottom up.

p94 bottom-up effort … additional research … customer and employee surveys along with operational data … regression models to understand which journeys have the greatest impact … run simulations to get potential impact.

p96 delivering at scale on customer journeys requires two high-level changes that merit mention here: (1) modifying the organization and its processes to deliver excellent journeys, and (2) adjusting metrics and incentives to support journeys, not just touch points.

p97 “new permanent role, redeploying senior people from siloed functions to become “chain manager” responsible for overseeing specific journeys …

p98… organizations must identify the appropriate metrics and create the appropriate measurement systems and incentives to support an emphasis on journeys.

p98 holding the sales agent, the technician, the call center, and the back-office agents responsible for a trouble-free install and high customer satisfaction at the end of the process, instead of simply requiring a successful handoff to the next touchpoint.

p98 And one large retail bank started requiring each executive-team and board member to call five dissatisfied customers a month – a simple but effective way of holding the leadership’s feet to the fire on customer experience issues.

p98 These efforts provided a real opportunity to differentiate not just the service experience but the brand itself.


The Goal by Eliyahu M. Goldratt

See Also

Example Customer Journey Map / Measuring Happiness in Usability Testing

Diagram of Systems to Help People Find and Manage Information

Monday, August 26th, 2013

Oldie but goodie – Here is my diagram made after reading “Information Architecture for the World Wide Web” by Louis Rosenfeld & Peter Morville. It’s a one page visual summary of the book.