First-time users, longtime strategies: Why Parkinson’s Law is making you less effective at work – and how to design a fix (Fredrik Matheson at Enterprise UX 2016)
•
5 gefällt mir•1,813 views
Fredrik Matheson: "First-time users, longtime strategies: Why Parkinson’s Law is making you less effective at work – and how to design a fix." Enterprise UX 2016 • June 8, 2016 • San Antonio, TX, USA http://2016.enterpriseux.net
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Andere mochten auch
Andere mochten auch (20)
Ähnlich wie First-time users, longtime strategies: Why Parkinson’s Law is making you less effective at work – and how to design a fix (Fredrik Matheson at Enterprise UX 2016)
Ähnlich wie First-time users, longtime strategies: Why Parkinson’s Law is making you less effective at work – and how to design a fix (Fredrik Matheson at Enterprise UX 2016) (20)
Mehr von Rosenfeld Media
Mehr von Rosenfeld Media (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
First-time users, longtime strategies: Why Parkinson’s Law is making you less effective at work – and how to design a fix (Fredrik Matheson at Enterprise UX 2016)
- 1. Fredrik Matheson Enterprise UX 2016 8 June 2016 First-time users, longtime strategies Why Parkinson’s Law is making you less effective at work – and how to design a fix.
- 2. Figuring out available dates • Finding a time when everyone can meet • Finding the most efficient flights paths and times Booking hotels • Finding a car to take you to your destination Saving receipts • Scanning receipts • Producing expense reports Approving expense reports • Keeping your business credit card trim • Budgeting project purchases • Following up on expenditures • Ordering business cards • Onboarding new team members • Manually adding users to your shadow IT • Updating credit card details for the SaaS you use • Negotiating contracts for new tools • Following up on invoices you’ve approved Sunsetting old tools • Monitoring project progress • Listening in on the grapevine • Gathering, preparing, analyzing data
- 7. Den britiske marinen, 1914
- 8. 1914 1928 Change Capital ships in commission 62 20 – 67.74% Officers and men in Royal Navy 146 000 100 000 – 31.50% Dockyard workers 57 000 62 439 + 9.54% Dockyard officials and clerks 3 249 4 558 +40.28% Admiralty officials 2 000 3 569 +78.45% Royal British Navy ships and staff
- 9. Admiralty officials 1914 1928 1935 1954 2 000 3 569 8 118 33 788
- 10. Tittel Colonial house – færre kolonier, mer å gjøre
- 11. 1935 1939 1943 1947 1954 372 450 817 1 139 1 661 Colonial Office officials
- 13. x Everyone wants a helping hand but no one wants to surrender power
- 14. Everyone wants a helping hand but no one wants to surrender power
- 15. Everyone wants a helping hand but no one wants to surrender power
- 16. Parkinson’s law Work expands so as to fill the time available for its completion.
- 19. Ronald Reagan, 1981 – Government is not the solution to our problems; government is the problem.
- 21. MemexMemex
- 22. Mother of all demos, 1968
- 23. IBM 360IBM 360
- 27. Tesler’s Law on the Conservation of Complexity “Every application has an inherent amount of irreducible complexity.
- 28. Tesler’s Law on the Conservation of Complexity “Who will have to deal with it? the user, the application developer, or the platform developer?
- 29. Tools Users System Who shoulders the burden? Tesler’s law
- 31. Tesler’s law “One cannot reduce the complexity of a task. “One can only shift the burden. Tesler’s Law, simplified
- 32. Tools Users System Who shoulders the burden? Tesler’s law
- 36. Who shoulders the burden? Tools Users System Tesler’s law
- 40. Who shoulders the burden? Tools Users System Tesler’s law
- 42. Who shoulders the burden? Tools Users System Tesler’s law
- 43. Who shoulders the burden? Tools Users System Tesler’s law
- 45. Teslers law in practice Who shoulders the burden? Tools Users System
- 48. Who shoulders the burden? Tools Users System Tesler’s law
- 50. Teslers law in practice Who shoulders the burden? Tools Users System
- 51. Who shoulders the burden? Tools Users System Tesler’s law
- 54. GOALWHY WHO HOW WHAT SPECIFIC MEASURABLE ACTIONABLE REALISTIC TIME-BOUND RELEVANTTHEORY Model developed and visualized by Moquan Chen at Bekk Consulting
- 55. GOALWHY WHO HOW WHAT RELEVANTTHEORY Model developed and visualized by Moquan Chen at Bekk Consulting
- 56. GOAL RELEVANTTHEORY Model developed and visualized by Moquan Chen at Bekk Consulting
- 57. DRAFT GOAL CUSTOMER PROFILE HOW WHAT WHY Model developed and visualized by Moquan Chen at Bekk Consulting
- 58. RELEVANTTHEORY Jobs Pains Gains Features Pain relievers Gain creators VALUEMAP CUSTOMERPROFILE Model developed and visualized by Moquan Chen at Bekk Consulting
- 59. DRAFT GOAL HOW VALUE MAP CUSTOMER PROFILE WHY Model developed and visualized by Moquan Chen at Bekk Consulting
- 60. DRAFT GOAL CUSTOMER VALUE VALUE MAP CUSTOMER PROFILE BUSINESS VALUE Model developed and visualized by Moquan Chen at Bekk Consulting
- 61. GOAL VALUE MAP CUSTOMER PROFILE BUSINESS VALUE CUSTOMER VALUE DRAFT User Friendliness.Learn Stakeholders New customers Scale Average time to learn, how to do 10 defined tasks Past [jan. 2016] 180 min Goal [jan. 2017] 30 min Model developed and visualized by Moquan Chen at Bekk Consulting
- 62. DRAFT GOAL CUSTOMER VALUEVALUE MAP CUSTOMER PROFILE BUSINESS VALUE VISIONSTRATEGY HYPOTHESIS Model developed and visualized by Moquan Chen at Bekk Consulting
- 63. DRAFT GOAL1st PROBLEM-SOLUTION FIT CUSTOMER VALUEVALUE MAP CUSTOMER PROFILE BUSINESS VALUE 2nd PRODUCT-MARKET FIT 3rd BUSINESS MODEL FIT Model developed and visualized by Moquan Chen at Bekk Consulting