Invisible front doors
The requirements are pretty clear: an obsessive attention to the detail of how your service works, and the ability to fix glitches quickly and easily. It really shouldn’t be hard, but far too often it clearly is.
The requirements are pretty clear: an obsessive attention to the detail of how your service works, and the ability to fix glitches quickly and easily. It really shouldn’t be hard, but far too often it clearly is.
Back in February, I wrote about the battle between the big endians and the little endians, between those who see service design as an engineering problem and those who see it as a customer agility problem. Like most battles, it should be an unnecessary one.
The Oxford Internet Institute organised an intriguing sounding seminar under the title of Gov 2.0, or Truly Transformative Government. The implied raspberry in the subtitle was itself a promise of some entertainment while the main title implied radical realignment of boring government with the hyper trendy of Web 2.0. The combination made it unmissable.