Make device thinking critical in our approach – focuses us on what we really need in terms of: Performance Interactions Accessibility Content centricity User journeys and ability to perform tasks Readability
we get the fundamentals of the service working on small screens and slow network speeds, it can work on more capable devices.” Gov.uk ‘Register’ to vote design https://designnotes.blog.gov.uk/2014/07/14/things-we-learnt-designing-register-to-vote/
start to shape the design patterns and styles we need. For an existing project, lofi prototypes could utilise the building blocks provided by an existing style guide
approach Collaborative and emergent design – talk with users/clients/customers Define a design language – style guides and beyond Interface design Interaction design IA
improve Stay agile Keep UX a goal at all stages Allow an emergent, iterative, solution that really can deliver working software early on Focus on making the smallest step for the biggest value Focus on adding incremental enhancements Focus on testing the hypothesis as we go
quality Proven solution Focus on experience esp. across devices Unified design language aligned with the business vocabulary Collaboration – maintain the conversation
there is a balance – pick what works for you We still need to be able to communicate our ideas with clients and sometimes this will need a fairly high def vision. Progressive enhancement and mobile first can both be hampered by some js frameworks Ways of working – moving to a more collaborative approach whilst maintaining value – UX team critical to this