Maricopa Use Cases

Browse by Role

General guidance about AI only goes so far. What tends to actually change how someone works is hearing that a colleague two buildings over solved a problem they also have. These pages collect real examples from people across Maricopa — what they tried, what worked, and what did not.

These are accounts of practice, not endorsements. A tool that fits one department’s workflow may be wrong for yours, and some of what you will read here is someone’s first attempt rather than a settled best practice. Read them as starting points.

Share What You Are Doing

What makes a good use case

The examples here follow a consistent shape, because that is what makes them usable by someone else:

  • The actual problem — what was taking too long, what was not working, what prompted trying something new.
  • What was tried — the tool, the approach, and enough detail that a reader could reproduce it.
  • What happened — including the parts that did not work. A case study with no failures in it is not being honest about the process.
  • What the person would tell someone starting — the thing they wish they had known.

Send us yours

If you have used AI for something at Maricopa — successfully or not — it is worth writing up. The unsuccessful attempts are frequently more useful than the successes, because they save other people the same dead end.

You do not need a polished result or an impressive outcome. A paragraph about something small that saved you twenty minutes a week is genuinely valuable to someone with the same task. Get in touch with the ARC to share it.