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
  • Overview
  • Context and Problem Statement
  • Decision Drivers
  • Considered Options
  • Decision Outcome
  • Positive Consequences
  • Negative Consequences
  • Follow-up Actions

Was this helpful?

Edit on GitHub
  1. Product
  2. Decisions
  3. ADRs

Cross-Program Team Health Survey Tool

ADR for Cross-Program Team Health Survey

  • Status: Proposed

  • Last Modified: November 20, 2024

  • Deciders: P&D team

Overview

Context and Problem Statement

The SimplerGrants project requires a reliable, easy-to-use, and cost-effective tool to conduct regular team health surveys. These surveys are critical for measuring psychological safety, workload management, and overall team satisfaction. The tool must support efficient data collection, analysis, and reporting processes.

Decision Drivers

  • Cost-Effectiveness: The tool must be affordable and offer good value for money.

  • Ease of Use: It should be simple for both survey creators and respondents to use, requiring minimal training.

  • Integration: The tool needs to integrate smoothly with other Google Workspace products already in use.

  • Data Analysis: Capable of basic data analysis and reporting to aid in quick decision-making.

  • Accessibility: Must be accessible to all team members and support mobile responses.

  • Security and Compliance: Ensure data security and comply with our data protection policies.

Considered Options

  • Google Forms: Integrated with Google Workspace, known for its simplicity and integration capabilities.

  • SurveyMonkey: Offers comprehensive survey tools and advanced analytics but at a higher cost.

  • Microsoft Forms: Suitable for teams embedded within the Microsoft ecosystem, with good integration with Office 365.

  • Typeform: Provides a highly interactive and engaging survey experience but may be more expensive.

Decision Outcome

Google Forms has been selected as the preferred tool for conducting our team health surveys. Its integration with Google Workspace, ease of use, and cost-effectiveness are key factors in this decision. Google Forms provides sufficient capabilities for designing surveys, collecting responses, and performing basic analyses, which meets our project’s needs without additional financial investment.

Positive Consequences

  • Cost Savings: As part of Google Workspace, Google Forms comes at no additional cost to our team.

  • Ease of Use: Familiar interface for users already accustomed to Google products, reducing the learning curve.

  • Integration: Seamlessly integrates with other Google services like Google Sheets for data analysis and Google Drive for storing survey data.

  • Rapid Deployment: Quick to set up and deploy surveys, enabling timely feedback collection.

Negative Consequences

  • Limited Analytical Tools: While Google Forms supports basic analysis, it lacks the advanced analytical capabilities of more specialized survey tools.

  • Fewer Customization Options: The aesthetic and functional customization options are more limited compared to options like Typeform.

Follow-up Actions

  • Implementation Plan: Develop a detailed plan for survey design, distribution, and data analysis using Google Forms.

  • Training Sessions: Organize brief training sessions for team leads to familiarize them with form creation and data collection.

  • Integration Check: Ensure all team members have access to Google Workspace and understand how to access and fill out forms.

  • Pilot Survey: Conduct a pilot survey to test the effectiveness of Google Forms and adjust the survey based on feedback.

PreviousShared Team Calendar PlatformNextAdding Slack Users to SimplerGrants Slack Workspace

Last updated 5 months ago

Was this helpful?