View
107
Download
0
Category
Tags:
Preview:
DESCRIPTION
Think of government systems as confusing by design? Elizabeth Buie, a computer systems professional with over 35 years of experience working on government systems and websites, gives her insights on the role of usability and user experience in government systems. She discusses how applying these principles and techniques in the design of government systems can make government more effective and efficient, thereby making it more cost effective and less expensive to run. She describes how these approaches can enable government systems to give their users a satisfying and even — dare we hope? — pleasant experience, whether they are interacting with their government from the outside or working for it on the inside. In government systems, we are all stakeholders. These findings are covered in Usability in Government Systems: User Experience Design for Citizens and Public Servants, which Elizabeth co-edited with Dianne Murray. This book, the first one to address this subject, contains chapters written by more than 30 experts in the field. You can get the book from Amazon at http://is.gd/uxgov This presentation was given to the DC Web Women in the autumn of 2012.
Citation preview
We Are All Stakeholders
Elizabeth BuieLuminanze Consulting
@ebuie
Usability in GovernmentSystems
User Experience Designfor Citizens
and Public Servants
Who Am I?
• I’ve specialized in UI/usability/UX since theBeginning of Time
• I’ve worked on governmentsystems even longer
• I’ve worked in a very largefirm, a very small firm, and asolo practice (current)
1978
1975
Some Notes on Terminology
• “Usability” — effectiveness, efficiency, andsatisfaction (from ISO 9241)
• “User experience” (UX) — users’ subjectiveexperience surrounding their use of a product
• Good usability is (usually) necessary for a gooduser experience, but they are not the same thing
• We can design FOR good user experience, butwe cannot (for the most part) design theexperience itself: “UX design” is a shorthand
We Are All Stakeholders
How many lives do govt. systems affect?
Can you think of anyone whose life is NOTtouched in some way by a government system?
– Their own govt.• national• state/regional/local
– Nearbygovernments
– The USGovernment
About 6.8 billion lives
The audiences of government systems
What do you think of when you hear this phrase?
Gov 2.0?Voting?
Agency websites?
“usability in government”
It’s all of these, and more.
Two kinds of audiences
• Public: citizens andothers– citizens– non-citizen residents– visitors and potential
visitors to the area– hopeful immigrants
• Internal: public servants– employees– contractors
• At all levels: national, state/regional, local
Major goals of public-facing systems
• Provide information and services to thebroadest possible audience
• Conduct transactions with the public– Optional
• e.g., find a library book and put it on hold
– Required (but doing them on line may be optional)• e.g., pay taxes, renew vehicle registration
• Encourage citizen participation (Gov 2.0)• Protect citizen privacy
Some major goals of internal systems
• Conduct the work of the government aseffectively and efficiently as possible
• Maintain national/regional/local security
Internal systems: some examples
• Defense systems• Air traffic control, spacecraft control
– some of these are defense related
• Agency intranets• Emergency response systems• Management of critical infrastructures• Legislative drafting (lawmaking)• Internal social media applications (e.g., the US
Department of Transportation’s IdeaHub)
Public and internal share many concerns
• Content strategy• Plain language• Accessibility• Mobile access• Security• Biometrics (fingerprints,
iris recognition, etc.)
• Cross-cultural issues
Photo by NIST
Usability and UX in the process
• Getting UX work into the contract• Use of usability process standards• User-centered requirements engineering• User-centered software development• Usability evaluation
Public-facing systems are not the problem
• Government often sees the public as customers• A good experience motivates people to use the
site or system• Governments want to be responsive to their
citizens
of democracies
^
I redesigned this interaction, yay.
biggest
^
Internal systems can be a bigger challenge
• Internal users are a captive audience• Using the system is part of their jobs
*with some exceptions
**
• Systems can be very complex
Internal: Usability more sellable than UX
• Effectiveness• Efficiency• Satisfaction ?
– Not quite as easy– Can be couched in terms of employee morale
and therefore productivity– Less important than the other two, but a case
can be made
• But experience? Surely you jest.
What makes govt. projects different?
• Effect of national politics– Priorities– Direction– Funding
• Access to users in advance– Once an RFP is issued, bidders
cannot talk to users• Contract structure
– Usability and UX may not bementioned in the RFP
– Can be difficult to bid it if not
What makes govt. projects special?
• Number and diversity of usersaffected
• Potential to affect importantaspects of many people’slives
• Potential to help makegovernment itself moreeffective and efficient
Dare I say “more satisfying”too?
Challenges to UX in the govt. process
• Getting usability into the contract (or the RFP, ifyou’re on that side of the project)
• Working it into the project if it’s not in the RFP• Getting awesome UXers
– Being seen as sexy– Paying as well as commercial
I do have to confess, though,that NASA, ESA, and theInternational Space Station arepretty dadgum sexy projects.
*
*
Flexibility is essential
• Do what’s called for in each project• Pay as much attention to the users’ subjective
experience as we can, within constraints
Any improvementis good news.
• I offer my motto:
And finally, some wider issues
• Service design– Cross-channel design– Channel shifting
• Applying design to policymaking• UX designers and e-democracy
Thank you!
Elizabeth Buie
Luminanze Consultingwww.luminanze.comebuie@luminanze.com
@ebuie
Order book from Amazon at http://is.gd/uxgov
Recommended