Part 12 · How do you interpret the results?
Module 28 · From Formula to Program Language
Translate the symbols back into the field
By the end of this module you will be able to
- Translate a formula into program language.
- Write a finding a non-analyst can act on.
- Avoid leaving results as code fragments.
A formula is the start of the work, not the end. Nobody ever approved a budget because a slide said NoCold + NoSuper. Decision-makers need plain language, so compare these two ways of saying the exact same thing:
| Please don't write this | Write this instead |
|---|---|
| "NoCold + NoSuper explains LowCov." | "Coverage fell below target wherever the cold chain was broken or monthly supervision was missing. Fix either gap and the outcome changes." |
Same finding, two very different audiences. The first is a code fragment only you understand. The second is something a state immunization officer can read once, repeat in a meeting, and act on by Friday. Always carry the result that last mile into program language.
Reflect
Rewrite one finding for a real audience.
- Would a state immunization officer understand your sentence on first read?
- Have you said what to do, not just what the symbols are?