Principles of Quality at Mighty Acorn Digital
Mighty Acorn Digital's principles of quality for building reliable digital services for state and local governments.
Overview
At Mighty Acorn, we build digital services that enhance public trust and satisfaction. A critical part of building those services is a robust quality assurance (QA) process that ensures its functionality, reliability, and usability. Our process is guided by the following principles:
Human-centered
We prioritize building things that are easy and intuitive for end users, so testing is always done from an end user’s perspective, replicating real journeys that actual users need to follow from start to finish (for example, each step from applying for a fishing license to submitting a payment and finally receiving the license). We focus on end-to-end testing, such as following a person who just lost their job step by step, from the moment they start an application for unemployment to the moment a deposit is made to their bank account. (See: Human Centered Testing.)
Shift left
Our approach to QA is rooted in the principle of “shifting left,” meaning QA begins in the earliest stages of a project. QA team members are involved in every phase of the project lifecycle, starting before development even begins by reviewing requirements and designs. This practice aims to identify potential issues as early as possible, which lets us avoid and prevent future flaws before they become more time-consuming and expensive to fix.
Everyone contributes to quality
Team members with quality in their title are advocates for a process that is owned by the whole team. “QA” or “testing” is not a separate phase conducted in isolation: product, design, and engineering don’t work in siloed specialties, considering work done once it’s handed to QA, but stay accountable to their work by actively monitoring and engaging with it until it is delivering value to end users. Final testing is not about catching bugs: it is where QA applies a user-centered lens to completed work. If a bug reaches production, we ask “Where did our process fail to catch this?” not “Why did QA miss this?”
Working in partnership
We bring a curious mindset, questioning instead of assuming. We seek out subject matter experts to make sure we understand the ultimate goal and can shape testing efforts around verifying that goal has been achieved. To build trust, we plan, write, and execute tests in partnership with our clients. All stakeholders and team members should know what we’re doing, why we’re doing it, and participate in conversations about what and how we’re testing. We anchor that transparency in processes that are maintainable and documented so that ownership transfers seamlessly to stakeholders when a project ends.
Evaluate project context to pick the right tool for the job
Every project has a unique budget, timeline, and risk profile. We deliberately choose the right toolset for the job: deploying automated testing where it yields the highest value, manual testing to ensure functionality meets real-world expectations, and AI when it meaningfully can reduce time and effort.
Help us improve
Your feedback helps us create better resources for teams like yours.
Last updated on