More Related Content


Working with the web and the future

  1. Working with the web & the future Sally Jenkinson @sjenkinson .
  2. @sjenkinson
  3. @sjenkinson The internet of 2021
  4. @sjenkinson
  5. @sjenkinson
  6. @sjenkinson
  7. @sjenkinson What challenges does the future bring?
  8. @sjenkinson
  9. @sjenkinson What we plan now may not be relevant in the future
  10. @sjenkinson Our project
  11. @sjenkinson Our users Our business Technology Wildcards Our project
  12. @sjenkinson Disruption will only accelerate Our existing standards, workflows and infrastructure won’t hold up Proprietary solutions will dominate at first The standards process will be painfully slow.
  13. @sjenkinson Our choices can become white elephants
  14. Verbundnetz_13022010_1580.jpg @sjenkinson
  15. @sjenkinson Keeping up vs getting ahead
  16. “It’s all broken!”
  17. “We have to throw it out and start again!”
  18. “…be guaranteed to meet the business and customer needs for the next 5-10 years at least…”
  19. @sjenkinson Keeping up as individuals
  20. @sjenkinson@sjenkinson
  21. @sjenkinson The future is hard!
  22. @sjenkinson The future, from the past
  23. @sjenkinson
  24. @sjenkinson
  25. “Short of figuring out real teleportation, which would of course be awesome (someone please do this), the only option for super fast travel is to build a tube over or under the ground that contains a special environment. ! This is where things get tricky.”
  26. @sjenkinson Telling stories can give human context to technology
  27. @sjenkinson
  28. @sjenkinson
  29. @sjenkinson
  30. “a work kit useful for parceling ideas into their atomic elements” @sjenkinson
  31. @sjenkinson Interactions and interfaces
  32. @sjenkinson
  33. “We’ve seen repeatedly that if an interface works for an audience, there’s something there that will work for users. ! Finding what that thing is and using it for inspiration in our own work is part of how we can use these speculative interfaces.” Make It So (
  34. @sjenkinson
  35. @sjenkinson
  36. @sjenkinson Using future thinking
  37. 1. Better consider our users’ changing needs. 2. Identify opportunities. 3. Aid prioritisation. 4. Define what something is and what it will be. 5. More robust decisions - understand limitations and benefits of choices. 6. React quickly/better to change by embracing evolution. 7. Make more exciting things and shape the future of the web! Future benefits @sjenkinson
  38. @sjenkinson The future & our work
  39. @sjenkinson
  40. Half-life @sjenkinson
  41. User interfaces & interactions Features Digital platform components (CMS, etc) ‘Non-digital’ systems (accountancy, etc) Browsers Hosting environment & languages Third party integrations Deployment tools Different elements have different half-lives @sjenkinson
  42. Choose technologies and architect your developments with half-lives in mind @sjenkinson
  43. @sjenkinson Separate concerns, loosely couple Think in patterns, not pages Modular CSS Enhance!
  44. “Zero UI is … taking us away from screens to a more natural way of interacting with things” Andy Goodman @goodmania
  45. Submit doStuff()
  46. @sjenkinson A practical approach to the future
  47. Discovery & planning Work content first Separate content from display to better cater for new outputs (visual or otherwise) Where screens are involved, remember to think from very small to very large Prioritise your requirements Create a backlog and strategic roadmap & make these visible Balance problems now & of the future Consider future usage patterns, interactions, and behaviour Embrace wider trends (remote teams etc) Learn from the past Don’t be bound by form Create a set of high level principles for the future Make no assumptions about usage Stories and design thinking (workshops)
  48. Example principles
  49. @sjenkinson Frederik Pohl “A good science fiction story should be able to predict not the automobile but the traffic jam” @sjenkinson
  50. Embrace web standards, semantics, open formats Progressive enhancement Create incrementally, release often Track & manage change Think atomically Allocate time to improve the past and the future Lifespan of project components Separation, modularity, loosely-coupled architectures and services Embrace automation Document decisions (not heavily, but ensure the past is captured for future learning) Prototype & test Doing Responsive design Leave space for the future Draw a line - what do you support? Why?
  51. Share your experiences Specs & upcoming technologies Measure, & use your data Better digital preservation Play more Take inspiration from the world (watch more sci- fi!) Evolving Accept change. It doesn’t mean you failed Work to educate others, to facilitate improvements Fix problems that you can see, and those that might be Provide support (bleeding edge technology users often have it rough)
  52. @sjenkinson Cup of tea?
  53. @sjenkinson
  54. “Don’t plan for the future because there is no future - just now and a series of next nows.” Jon Gold @jongold
  55. @sjenkinson Thank you! My slides are mainly blue because according to Make It So, blue is ‘futuristic’ - it’s the most prevalent colour in sci-fi interfaces