How We Know It Works

The software is now organized into clear parts. The next question is how we know it actually does what people need.

Why This Matters

If you do not check the software, you may only find problems after people start using it. That makes mistakes more expensive and harder to fix.

When you know how to check the work, you can catch problems earlier and trust the result more.

Core Idea

Good software should be checked in a way that matches the risk.

Simple tasks need simple checks. Important behavior needs stronger checks. The goal is not to test everything equally, but to test the right things well.

Comparison

Weak checking	Strong checking
Hope it works	Verify important behavior
Check only at the end	Check throughout the work
Focus on happy paths only	Look for mistakes too
Hard to trust changes	Safer to change over time

Worked Example

Imagine the clinic booking system from earlier.

If a reminder message is sent, the team should check that the message is correct, sent to the right person, and triggered at the right time. If the booking time changes, the system should also confirm the reminder changes with it.

The same idea applies to a store checkout, a support ticket system, or any workflow where a small mistake can cause confusion.

Common Mistakes

Relying only on manual checking.
Testing things that are easy instead of things that matter.
Waiting until the end to find obvious problems.
Assuming one good check is enough for every kind of risk.
Forgetting to check failure cases.

Checklist

Do you know what must be checked?
Do you know what would be risky if it failed?
Are the important cases covered?
Can mistakes be found before release?

Small Exercise

Pick one software idea and ask:

What is the most important behavior to check?
What could go wrong if it fails?
How would you know the software is still working later?

Summary and Next Step

Knowing how to check software makes it easier to trust and safer to change. The right checks depend on the risk and the kind of behavior you care about.

Next, learn how changes reach users.

How Changes Reach Users