{"id":3897,"date":"2018-09-06T03:46:21","date_gmt":"2018-09-06T03:46:21","guid":{"rendered":"https:\/\/russellmoverley.com\/?p=3897"},"modified":"2021-12-01T10:40:21","modified_gmt":"2021-12-01T10:40:21","slug":"jobs-to-be-done","status":"publish","type":"post","link":"https:\/\/russellmoverley.com\/jobs-to-be-done\/","title":{"rendered":"Jobs To Be Done vs UX"},"content":{"rendered":"
In preparation for a clients new website I was conducting research around underlying frameworks. I was glad to come across the strategy<\/a> by\u00a0Tony Ulwick, (CEO of\u00a0Strategyn<\/a>) known as the Jobs-to-be-Done theory.<\/p>\n After reading more about it I quickly realised that this theory is the precursor to some parts of UX theory. Its the original way of tackling User Journeys \u2013 a process I adopt which compliments my approach to web design using the Minto Pyramid Principal<\/a>.<\/p>\n I’ll try to briefly explain how.<\/p>\n With regards to website design, I describe this method as a way of creating a logical content structure to support your company’s product or service claim.<\/p>\n This brilliantly un-inspiring diagram shows this:<\/p>\n <\/p>\nMinto Pyramid Principal<\/h2>\n