Smartstaff, administrator
3,320
edits
Changes
→Determining the organization and layout of questions
Will you be using features like invitations, annotations, and group email? Consider the full application lifecycle including how outcomes will be reported and how you will demonstrate the outcome of the funding such as who benefited. Also consider what types of communication you will have with the applicant. Will you use notes, annotations, emails, a separate UTA to manage these communications? Can applicants upload an audio/video application or explanation using the media library or will all communication be text based? How can your users get help along the way if things don’t go as planned or something unexpected happens? Will you use the +AI integration as part of the pre-screening process and allow other roles to get help from the artificial intelligence as part of their processes. Will you use the e-signature integration for digital signing documents or some other integration, if so, which vendor?
==Determining the organization structure and layout of questions==
Now that you have determined the structure of the data so you can output the data your community needs in the ways they need it, consider the surface of the form.
'''How will you logically group content?'''
What groupings will make sense to your community's mental model? For example, will you put all the questions related to applicant outcomes under the same title bar, will you place related content on the same tab, if so what logic will you use for grouping like content? Grouping similar content under a title bar makes it easier for users to jump to the desired content. Will you use the title bar navigation pane to jump to parts of your application. Will you favor vertical scrolling for an improved mobile experience or go with a horizontal tabbed layout. Exercises such as card sorting can help with designing the information architecture of your form.
'''How will you present the content?'''