Making tech-simple-for-users-wp
0 likes21 views
This document discusses making technology simpler for users. It notes that traditional IT focuses on experts solving many problems, but experts are limited in number, experience, and domain. Nonexperts are often sidelined. The document proposes a more practical approach of building web-based user interfaces that are simpler for nonexperts to use. It provides examples of both web-based and WordPress-based interface patterns that aim to reduce complexity for users. The recap emphasizes starting simply and getting small wins over existing interfaces, letting users know what is happening, and avoiding unnecessary data collection or complex tasks.
Making tech-simple-for-users-wp
- 1. Making tech simpler for users Background Source: https://pixabay.com/en/tech-circle-technology-abstract-3041437/
- 2. About Me ● I Own & run CODESIGN2 (tiny local business, focusing on technology solutions) ● I’ve been working in paid IT for >16 years (this July) ● I’m a programmer, trainer, designer*, sysadmin, digital architect (I do too much) ● I’d rather be “practical” or “pragmatic”, than “clever” ● I’ve worked in a number of industries, with a number of technologies (be thankful this isn’t 2006 & this isn’t in Flash) ● I Open Source Technologies, but should still release more Libre & open-source❤️ Connect: via https://www.lewiscowles.co.uk Buy: via https://www.codesign2.co.uk
- 3. The problem(s) ● Traditional IT focuses on a few “experts” solving a lot of problems ● “experts” take 10-20 or more years to mature ● “experts” have limited domain ● “experts” are still human ● Those not identified as “experts”, which there are more of, are often side-lined. ● It’s rare, if not improbable for an “expert” to be orders of magnitude more effective past a certain involvement. ● There can be economic barriers to access of “expertise” Image via wikimedia commons https://commons.wikimedia.org/wiki/File:Rubik%27s_cube_scrambled.svg
- 4. You have to start somewhere
- 5. Practical web-based UI example
- 6. Practical web-based UI example
- 7. Practical web-based UI example
- 8. Practical web-based UI example
- 9. Practical web-based UI example
- 10. Client project, testimonial CPT
- 11. Client project testimonial CPT
- 12. Internal web-based UI example
- 14. Prior Project – Media taxonomies
- 15. Prior Project – Media taxonomies
- 16. Practical non-expert UI issues Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse sed est at neque pulvinar tempor eget in risus. Nunc imperdiet nec eros nec interdum.Sed blandit metus in euismod sagittis. Donec rhoncus augue a turpis tempor lobortis. Morbi cursus vitae nulla ut aliquam.Praesent dui lectus, bibendum ut semper vel, semper at urna. Aenean aliquam orci quis scelerisque porttitor. Quisque eu placerat justo. Proin vestibulum congue commodo. Maecenas ut commodo lectus. Donec vehicula bibendum tellus,sed condimentum quam hendrerit sed. Nullatempor porttitor elit, eu porttitor felis ullamcorper et. Proin vel arcuvel odio varius volutpat at ut leo. Sed non placerat eros. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia Curae; Aliquam elementum nibh lorem,consectetur fermentum urna feugiat a. Praesent accumsan urnadolor,non efficitur eros suscipit eu. In feugiat purus sed ex rhoncus rhoncus.Donec quis interdum dolor. Suspendisse porttitor vel arcuat volutpat. Proin at pellentesque lorem.Nunc lacus turpis, rhoncus sit amet quam sed, laoreet feugiat felis.Pellentesque nec semper eros.
- 17. Practical non-expert UI issues
- 19. Non-WP Patterns
- 20. Non-WP Patterns
- 21. Non-WP Patterns in WP
- 22. Non-WP Patterns
- 23. Non-WP Patterns
- 24. Non-WP Patterns
- 25. WP+ACF Patterns
- 26. WP+ACF Patterns
- 27. WP+ACF Patterns
- 28. • Not everything starts simple, it’s a process. Make it simpler until it’s simple. • Try to get a series of small-wins over an existing interface than burning the village down to build a spectacle. • Let users know what you are doing, when you are doing (loaders, animations), why you need things. • Try to avoid asking for things you don’t need, like pattern matching, over- complicated cognition, or unnecessary user-data. • Where systems such as WordPress exist, use them to get more done. • Learn when it might be simpler to not-use WordPress • Learn to find resources to ensure you can focus on what matters. Recap
- 29. Thank you! Lewis Cowles – Owner, Digital Architect