Simpler.Grants.gov Public Wiki
Grants.govSimpler.Grants.govGitHubDiscourse
  • 👋Welcome
  • GET INVOLVED
    • Why open source?
    • How to contribute code
    • How to file issues
      • Report a bug
      • Request a feature
      • Report a security vulnerability
    • Community guidelines
      • Code of Conduct
      • Reporting and removing content
      • Incident response protocol
    • Community events
      • Fall 2024 Coding Challenge
        • Event Submissions & Winners
      • Spring 2025 Collaborative Coding Challenge
        • Event Submissions & Winners
    • Communication channels
  • Product
    • Roadmap
    • Deliverables
      • 🏁Static site soft launch
      • 🏁Static site public launch
      • 🏁GET Opportunities
      • 🏁Open source onboarding
      • 🏁Co-Design Group planning
    • Decisions
      • ADR Template
      • ADRs
        • Dedicated Forum for Simpler.Grants.gov Community
        • Recording Architecture Decisions
        • Task Runner for the CI / CD Pipeline
        • API Language
        • Use Figma for design prototyping
        • ADR: Chat
        • DB Choices
        • API Framework and Libraries
        • Back-end Code Quality Tools
        • Front-end Language
        • Communications Tooling: Wiki Platform
        • Use Mural for design diagrams and whiteboarding
        • Ticket Tracking
        • Front-end Framework
        • Front-end Code Quality Tools
        • Front-end Testing & Coverage
        • Backend API Type
        • Front-end Testing & Coverage
        • Deployment Strategy
        • Use U.S. Web Design System for components and utility classes
        • FE server rendering
        • Use NPM over Yarn Architectural Decision Records
        • U.S. Web Design System in React
        • Communications Tooling: Video Conferencing
        • Back-end Production Server
        • Communications Tooling: Analytics Platform
        • Commit and Branch Conventions and Release Workflow
        • Cloud Platform to Host the Project
        • Infrastructure as Code Tool
        • Data Replication Strategy & Tool
        • HHS Communications Site
        • Communications Tooling: Email Marketing
        • Communications Tooling: Listserv
        • Use Ethnio for design research
        • Uptime Monitoring
        • Database Migrations
        • 30k ft deliverable reporting strategy
        • Public measurement dashboard architecture
        • Method and technology for "Contact Us" CTA
        • E2E / Integration Testing Framework
        • Logging and Monitoring Platform
        • Dashboard Data Storage
        • Dashboard Data Tool
        • Search Engine
        • Document Storage
        • Document Sharing
        • Internal Wiki ADR
        • Shared Team Calendar Platform
        • Cross-Program Team Health Survey Tool
        • Adding Slack Users to SimplerGrants Slack Workspace
        • Repo organization
        • Internal knowledge management
        • Migrate Existing API Consumers
      • Infra
        • Use markdown architectural decision records
        • CI/CD interface
        • Use custom implementation of GitHub OIDC
        • Manage ECR in prod account module
        • Separate terraform backend configs into separate config files
        • Database module design
        • Provision database users with serverless function
        • Database migration architecture
        • Consolidate infra config from tfvars files into config module
        • Environment use cases
        • Production networking long term state
    • Analytics
      • Open source community metrics
      • API metrics
  • DESIGN & RESEARCH
    • Brand guidelines
      • Logo
      • Colors
      • Grid and composition
      • Typography
      • Iconography
      • Photos and illustrations
    • Content guidelines
      • Voice and tone
    • User research
      • Grants.gov archetypes
  • REFERENCES
    • Glossary
  • How to edit the wiki
Powered by GitBook
On this page
  • The methodology
  • Applicant archetypes
  • General themes
  • Where can we have the most impact?
  • Change log

Was this helpful?

Edit on GitHub
  1. DESIGN & RESEARCH
  2. User research

Grants.gov archetypes

Toward the beginning of the Simpler.Grants.gov project in 2023, we conducted a research study to gather insights from applicants, potential applicants, and grantmakers. As a result, we identified four major archetypes of Grants.gov applicants and identified four themes that cover the problems our work should address. Additionally, we found the most common barriers users face when applying on Grants.gov. We’re using these findings to guide our work.

The methodology

Applicants and grantmakers were selected for user interviews to understand their experience better using Grants.gov. We recruited equitably to ensure a diverse pool of participants.

Of the interviewed applicants, 26% were first-time, 39% were occasional, and 34% were frequent applicants.

With the findings from these interviews, we defined user archetypes and general themes to guide the Simpler.Grants.gov user experience.

Research objectives:

  • Examine existing user journeys and behaviors, identifying how Grants.gov fits into their overall approach

  • Learn from user experiences, roles, challenges

  • Identify barriers and how a simpler Grants.gov can create a more intuitive user experience, especially for new users

Applicant archetypes

Archetypes are compelling summaries that highlight the types of applicants that Grants.gov serves. They’re informed by and summarize user research data and represent user behaviors, attitudes, motivations, pain points, and goals. We’ll use these archetypes to influence our design decisions, guide the product’s direction, and keep our work human-centered.

The Novice

Applicants lacking familiarity with the grant application process, including first-time or infrequent applicants and those who never apply

Novices are often new to the grants application process. They face a steep learning curve when finding and applying for funding opportunities. Solving their needs will generate a more inclusive Grants.gov experience.

The Collaborator

Applicants who've applied before. They work with colleagues or partner organizations to increase their chances of success.

Collaborators have more familiarity with Grants.gov. However, they face challenges with coordinating application materials and often resort to tools and resources outside of Grants.gov.

The Maestro

Frequent applicants familiar with Grants.gov, who are often directly responsible for managing multiple applications at once

Maestros have an established approach to applying, which may include software and tools outside of Grants.gov. Their primary concerns are determining grant feasibility and staying ahead of deadlines.

The Supervisor

Applicants who have a more senior role at organizations and have less frequent direct involvement with Grants.gov than Maestros.

Supervisors are responsible for oversight, approvals, final submissions, and keeping registrations current. Their time is limited, as they're often busy with the organization's other needs.

General themes

The existing Grants.gov website works best for those who use it regularly. Larger organizations and teams of Collaborators and Maestros are typically more familiar with the ins and outs of the system. To create a simpler Grants.gov with an intuitive user experience that addresses the needs of all archetypes, four themes were defined:

Frictionless functionality

Reduce the burden on applicants and grantmakers, from both a process and systems perspective, by addressing the pain points that negatively affect their experience

Demystify the grants process

Ensure that all users have the same easy access to instructional and educational information that empowers them to have a smoother, more informed, and more confident user experience

Sophisticated self-direction

Meet users where they are during crucial moments by providing a guided journey through opt-in contextual support that reduces their need to find help outside the system

Create an ownable identity

Create a presence that reflections our mission and supports our users through visual brand, content strategy, and user interface design systems

Where can we have the most impact?

The most significant burden is on Novice to become an expert on the grants process and system. To execute our mission, there is a need to improve awareness, access, and choice. This requires reaching out to those unfamiliar with the grant application process.

There are many common barriers that users face:

Barrier
Impact

Digital connectivity

Depending on availability and geography, a stable internet connection is not guaranteed to support a digital-only experience.

Expertise

Small organizations face higher turnover, and alumni often take their institutional knowledge and expertise with them when they leave.

Education

It often requires a high level of education to comprehend the complexity and language of funding opportunity announcements.

Confused by announcements

Novices have difficulty determining their eligibility and understanding the details of the funding opportunity announcement.

Organization size

Not all organizations have dedicated resources for seeking grant funding. Many are 1-person shops who are trying to do it all.

Cognitive load

Applicants often apply for funding through several agencies, requiring they learn multiple processes and satisfy varying requirements.

Lost at the start

Novices don’t see a clear call-to-action for getting started, and they have trouble finding the one-on-one help at the beginning of the process.

Time

Most individuals wear a lot of hats (community advocate, program lead, etc.) and "grants applicant" is only part of their responsibilities and requires efficiency.

Overworked

New organizations are often too burdened with internal paperwork and infrastructure to support external funding and reporting.

Language

Applicants are faced with a lot of jargon without context or definitions, which is especially difficult when English is not their native language.

Overwhelmed by search

New applicants misuse the keyword search function and have trouble understanding the acronyms and terminology.

Blindsided by requirements

New applicants are caught off guard by SAM.gov registration and often miss the format and file name requirements.

Change log

Major updates to the content of this page will be added here.

Date
Update
Notes

2/24/2025

Initial content

PreviousUser researchNextGlossary

Last updated 2 months ago

Was this helpful?