📝
How we work (org handbook)
  • Home
  • Onboarding
  • Code of Conduct
  • Project Management
    • Project Initiation
      • Documentation and Checklists
      • Aligning with OpenUp's Mission and Vision
      • Getting Partners and Stakeholders on Board
      • Defining Project Parameters and Limitations (scope)
      • Product Management during the Project Initiation Phase
      • DRAFT COPY
    • Project Implementation
      • Project Planning
      • Agile, Scrum, and the Lean Startup Method
      • Stakeholder Management
      • Meetings
      • Communication
      • Team Management
      • Roles and responsibilities
    • Project Close-out
      • The Close-Out Report
      • Retrospective
      • Donor thanks
      • One page write-up
      • Blog article
      • Maintenance plan (if necessary)
    • Project overviews
      • Citizen Engagement App
      • Our Project List
      • Local Gov Programme
        • Business Portal
      • Tech Infrastructure
    • Project boards
  • How we work
    • Preferred tools
      • Tool sponsorships
    • Budgets & Finance
      • Taxes
        • VAT
        • PAYE and UIF
        • Workmen's compensation
        • Annual PAYE reconciliation
      • The Types of Budgets Used By OpenUp
      • When to Start Planning a Budget
      • Planning a Budget
      • How to Create a Budget
      • How to Spend a Budget
      • How to Adjust a Budget
      • Expense claims
      • Invoicing OpenUp
      • Capturing and approving invoices for payment
      • Allocating AWS costs to a project
      • Allocating Upwork transactions to projects
      • Software, Services and Hosting
      • Downloading Webflow invoices
    • Tool Development
      • Coding Roles
      • Tools For Coding
      • DESIGN
      • The Design Process: Step-By-Step
      • Tools Used In The Design Process
      • Quality Metrics: Design
      • Webflow export rules
      • CONTENT, WRITING, AND MEDIA
      • Creating Substance: The Role of Content in Tool Development
      • Creating Content: Step-By-Step
      • What Goes In Social Media
      • TRAINING & EVENTS
      • Event Planning
      • When, Where, and How to Hold a Training Session
      • Tools Used By Training and Events
      • User testing
      • Making government accessible
    • Outsourcing & Contracting
      • Why do we contract external workers?
      • Platforms We Use To Find Contractors
      • Contracting people for work
      • UpWork Contracting
    • Monitoring & Evaluation
    • Communications & Branding
      • Resizing images
      • Creating an email newsletter
      • Posting a blog
      • Sharing a blog post
      • Marketing Q &A
      • Official communications
      • Tracking app and campaign web traffic sources
    • Human Resources
      • Recruitment
      • Recruitment template: Project lead developer
      • DRAFT Recruitment template: Product owner
      • One-on-ones (1:1s)
    • Organisational Decision Records
      • ODR1: Organisational Decision Records
      • ODR2: Building dynamic web frontends using Webflow
    • Personal Information
    • Password management
  • Tech
    • Development guidelines
    • Preferred tech stack
    • Webflow project guide
      • How to build pages in Webflow so that content can be added using Javascript
    • Setting up a new server
    • Hosting on dokku
    • CDN in front of S3
    • Setting up a new Domain
    • CKAN
  • Product management
    • Our product design process
  • Codebridge
    • Codebridge - the space
Powered by GitBook
On this page
  • People will eventually need technical terminology
  • Example
  • Break up walls of text
  • Example

Was this helpful?

  1. How we work
  2. Tool Development

Making government accessible

How we write and design to make government accessible to citizens

PreviousUser testingNextOutsourcing & Contracting

Last updated 4 years ago

Was this helpful?

People will eventually need technical terminology

  • People will need to use the correct technical terms when interacting with bureaucracy that uses a technical term

    • rather than our special "non-technical" word which might be different from someone else's special non-techical term.

  • Don't try and act like the "jargon" doesn't exist. Hiding it is harmful

  • Find a way to make the jargon accessible

    • Provide more accessible terms that can catch someone's eye and for search engines to match non-expert searches

    • Provide the technical term early on in the user's journey along with an explanation so that they can learn the term

      • This is also important for technical users of your site, who would be looking for the technical term

Example

The technical term is "Section 32" or "Section 32 reporting"

The non-expert self-explanatory term is "In-year monitoring" or "In-year reporting"

This might not be beautiful design, but it makes a lot more sense than the important destination we want to help people discover:

Break up walls of text

  • We break content up into smaller sections

    • give them headings that represent the content of the section to catch the eye

  • We break the sections up into subsections that each carry some concept, even if they end up being one sentence.

    • Give them headings that represent the content of the subsection to catch the eye

Example

We often have researchers prepare a body of content that unpacks an issue in a google doc where it's easy to comment, suggest, review, and them mark approval of a specific version.

We then figure out how to arrange that content to be easily-consumed on the web, especially on a mobile phone using the above approach.

An example of trying to bridge between words people use and technical terms government uses
Example of extremely important information that would probably not get noticed by non-experts
Super helpful but hard to read content produced by researchers
Same content broken up with headings and subheadings