The work here is meant for generating feedback, so please leave your comments at the bottom of the page to help us develop these designs further.
This storyboard shows one possible use case of a Court Messaging System. It features the two main users — the juvenile & the court staff member. The details of how the system will function are just an approximation of what the forms, scripts, interfaces, and interactions would be like.
We mocked up the scenario as a tool to present to potential users, to see if this scenario is plausible, what they would change about it to make it more true to real experiences, and what they would change about the system as it’s presented here, in order to make it more efficient, useful, and tailored to their current work practices & technology.
This system map is a first draft of how a possible system may operate. It shows how the interfaces may look to the Juvenile User and to the Court Staff User. Like with the use case scenario above, this is not a firm proposal of how the system should work. Rather it is a mock-up that can be shown to both groups of users, to see if it would have value to them, and how it could be improved.
If you have comments, edits, or feedback, please leave them below.
We have begun to make drafts of what interfaces the court administrator would use when entering data into the system. They are rough sketches — please let us know what you think!
What information should we be presenting to the end-user litigant — and how should it be staged so that it’s relevant to her in the moment when she needs it? How do we build trust, long-term engagement, and a healthy relationship between our user & the messaging product? We’ve been drawing up a communication strategy to plan for these questions.
What problem are we actually trying to solve? Where should we target our solution? Here are some of our design process deliverables, in which we explore what kind of problem space, persona, and solutions we should focus on.