1 / 28

People Centric Designs IoP - Dagstuhl October 2017

People Centric Designs IoP - Dagstuhl October 2017. Going beyond the screen. An Industry Perspective on Internet of People. WELCOME. TO THE DARK SIDE. Our toolbox. Lean Service Creation.

reneer
Download Presentation

People Centric Designs IoP - Dagstuhl October 2017

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. People Centric DesignsIoP - Dagstuhl October 2017

  2. Going beyond the screen

  3. An Industry Perspectiveon Internet of People

  4. WELCOME TO THE DARK SIDE

  5. Our toolbox

  6. LeanServiceCreation LSC is a multi-disciplinary way of working that maximizes the probability of creating successful digital services

  7. A process to replicate success

  8. http://iotservicekit.com

  9. Intelligence augmentation for designers

  10. Cool technology is not enough

  11. Embedding human behavior models in network protocols

  12. How Do We Design for IoP? • People want new tech, but don’t know how to use it • We need Designing for IoP workshop. Interactive, collaborative tools. • The details of such a kit implicitly sets the boundaries and mindset, for better and for worse

  13. IoP KISS A: Industry adoption needs simple, usable concepts they can map to ideas they already know • Not a new “opportunistic network protocol with cloud fallback”, it is a “distributed database and an easy API” B: (there is no point B)

  14. IoP: Social Variables • Pick your variable type. Use. • Thread safe (functional approach?) • With local atomic training • Locally coherent structure • Global convergence • Geographic and affinity-group variation • Trust baked in at a deep level (only trust open training data?) • Illustrate the most useful archetypes/design patterns, discard the rest • Show, don’t tell. Short examples and cheap PR rule. IoPShrödinger Cat videos • Start a foundation. Build the ecosystem with relentless, boring message repetition

  15. IoP: Tell a Story to Your Audience The Driver: Great UX“So, IoP, entertain me, tell me a story” • Designer: (blah blah here) • Developer: architecture details • Reliability • No single point of failure • Fallback models • Latency • Bandwidth • New capabilities • Contextual • Location based • Better AI integration • Explicit trust contract with the user • Business: markets and money • Increased local market access • Local competition to drive down prices • (Don’t say “commoditization”) https://www.flickr.com/photos/wonderlane/7167097899/in/photostream/lightbox/

  16. Thanks! paul.houghton@futurice.com @mobile_rat

More Related