Published on March 4, 2014
UX Methodology Design Public e-Services in Lithuania Ramune Norkute, Idea Code
Information Society Development Committee Shaping Lithuania’s state policy in the development of information and communications technologies Creation of a modern information society
Human factors framework
1 Year Ahead Vacation is nice...
6 Months Ahead Diving?...
6 Months Ahead Mountains?...
2 Weeks Ahead
What Happened Abstract, big picture, no specifics Relaxed Geek terms: Construal Level Theory Close Choices Far away Specific plans, details Panic
How is this relevant to the public sector UX?
E-Service Close Far away Functional requirements Complete actions to reach a planned result Actions Abstract requirements (law), general discussions ??? Fully operational e-service Good UX
Issues with Functional Requirements Have no idea what users need “Know” what users need Has a different vision in mind Assumes that people read minds
What happens then… Far away Abstract requirements (law), general discussions Functional requirements Actions Close ??? Completion of specific actions to reach a planned result “This is not what we meant” Bad UX
Need to 1. Make people communicate their ideas early 2. Realize the difference between yourself and the user 3. Get the users involved 4. Build a common vision 5. Translate common vision into specific actions when you are far away from the deadline
New Sounds magic Agile Too risky Legal issues
Common Principles 1. User needs in the center 2. Regular user research and involvement 3. Design and development based on user resarch findings 4. Regular measurement of user experience
High level process Define the „good“ Implement Support the „good“ the „good“
Process in more detail Define the „good“ Implement the „good“ Support the „good“ Modernize Idea Design Implement Support Liquidate
Tools Stakeholder list Customer journey Target group description Service blueprint Persona description Business process diagrams Survey Wireframes User observation Sitemap User interview Interactive UI prototype Diary study Card sorting Focus group A/B testing Usability evaluation User interface guidelines Usability testing
Idea Modernize Idea Design Implement Support Identify user needs, generate and explore e-service ideas, which match those needs. Stakeholder list Target group description Survey User observation User interview or diary study Persona description Customer journey Liquidate
Design Modernize Idea Design Implement Support Formulate specific e-service solution, which will be implemented. Value to users. Clear components. Service blueprint (draft) Business process diagrams Sitemap Wireframes Usability evaluation Usability testing Liquidate
Implement Modernize Idea Design Implement Support Liquidate Code, create, build, install, setup user centered e-service solution components. Test-improve-launch. Service blueprint (draft) Wireframes User interface guidelines Business process diagrams Interactive UI prototype Usability evaluation Usability testing
Support Modernize Idea Design Implement Support Liquidate Carry out support, solve problems, implement minor changes. Monitor results. Measurement system Initial launch targets Rolling 5 year targets after launch • • • • People Infrastructure Communication Processes
Modernize Modernize Idea Design Implement Support Implement changes due to environment , technology, process and other factors. Test-improve-launch. Liquidate
Liquidate Modernize Idea Design Implement Support Liquidate a no longer needed e-service. Inform users. Ensure transition. Liquidate
Document pack UX Methodology (Process+Tools) Tool Use Examples Procurement Guidelines Training materials Available at: http://epaslaugos.ideacode.lt/ Usability Problem Solution Guide
Timeline Methodology development 2013.03-09 Trainings 2013.10 Publication 2013.10-12 Formalization 2014
E-Service Far away Abstract requirements (law), general discussions Functional requirements Actions Close ??? Completion of specific actions to reach a planned result “This is not what we meant” Bad UX
Before… Spend more on fixing bad UX later Spend less on figuring out what to do early
New Process and Tools Define the „good“ Implement Support the „good“ the „good“
Future value Spend more on figuring out what to do early Spend less on fixing bad UX later
Thank you Methodology (in Lithuanian) available at: http://epaslaugos.ideacode.lt/
Case study: UX Methodology Design for Public E-services in Lithuania. #Case study #UX in Lithuania #E-services #Public sector
A Case Study in UX Strategy Tonya ... Mapping Business Value to UX Strategy: A Case Study. ... UX Methodology Design for Public E-services in ...
Share Fennec case study - Design for ... Initial design themes and goals• Maximize screen space ... UX Methodology Design for Public E-services in ...
UX Riga 2014 Speakers: ... UX Methodology Design for Public E-services in Lithuania. #Case study #UX in Lithuania #E-services #Public sector.
... A Case Study of ... life conditions to usage of the public e-services. ... EU countries.Design/methodology/approach—the approach is ...
... to a UX question. A/B Methodology & Case Study ... design. In either of these cases, the UX ... and improving library user experience by ...
PulseUX Blog. Theory, Analysis and ... (UX) design. For the benefit of ... A small case study was conducted in order to examine the applicability of the ...
View Marius Mocevičius’ professional profile on LinkedIn. ... UI/UX architect and designer ... Administrative and public e-services portal.