Adele Kyriacou

I discuss 5 ways of adopting AI in your daily work and product development, ranked from easiest to hardest in my latest video. This might be my most useful video yet, so please repost to your networks 🙏 I look at ways to start building AI into your product development, from sprinkling it here and there, to rethinking your product and user experience with an AI at its core. I answer the following questions: - How can you start using AI tools right now? - How can you begin to add AI to your products and services? - How can you innovate new products and features with AI? - How can you reinvent your user experience with AI? - How can you gain a data advantage to train your own AI? Did I miss anything? Was it actually useful? Let me know! Did I miss anything? Was it actually useful? Let me know!

So we just shipped a new feature, and quickly made an update after realising we broke one of the content design commandments… THOU SHALT NOT USE JARGON! ⚡️ WARNING: This video contains extreme use of jargon. Including content design jargon. The irony is not lost on me… When developing features, even if you start with user needs, you can quickly fall into the trap of using language that is specific to technical details of how you are building software, rather than remaining useful to users. Jargon makes users think harder to understand what’s going on. It adds time to their day and in some cases it makes your software less accessible, especially if your users have dyslexia, or even just a child in their arms. I haven’t really got a clear fix for you. Jargon creeps in, especially if you have a small team who are balancing a lot of priorities. (We know all about that!!) The most practical thing you can do, is just make sure you use your own software, and use it like a user, even better, use it as a user! Eat your own dog food. This helps spot issues before users do. Of course, you should speak to your users too :) Thinking like, or being a user, will make jargon more apparent as you use your software. So anyway, we shipped an updated version using plainer language, check out the video for details. Hopefully that will make more sense to our users now! How often do you get confused by jargon? How often do you ship software with jargon? How do you avoid it? Let me know in the comments! P.s. Trying out vlogging this year. Let me know what you think :)

I’ve just left the best job I ever had to start my own business, OpenDigital. Let me tell you my plan.

Oooo, freebies 😁 If you work in a public sector organisation and you would like a printed copy of Modernising Legacy Applications in the Public Sector, you can order your copy here: madetech.com/resources/books… #LegacyModernisation #LegacyTech

"Failing becomes safe when failure is cheap, and you make failure cheap by seeking feedback on a daily or weekly basis which will ensure failure costs you days rather than months." lukemorton.tech/articles/def…

"What you won't get from Scrum or Kanban is how your team should work together to validate ideas, develop software or prove that your software is meeting the needs of your organisation and users." lukemorton.tech/articles/def…