Consulting
Designing the measurement, not just taking it. For organisations whose numbers have to hold up in front of a regulator, a funder or a reviewer.
The four blocks below are draft wording, written from the spec's own list. Change any of it. The block that matters most is the one nobody can write for you: three to five past projects, one line each, naming the outcome. That list is what a reader checks before deciding whether the rest of the site is worth their time.
-
Program design
Working out what to measure, how often, at how many places, and what the result will be able to support once it exists.
For: anyone standing up monitoring from nothing, or inheriting a program that is collecting data nobody can use.
-
Protocol development
Turning a method into something a field crew can follow the same way twice, and writing down the reasoning so it survives being questioned.
For: teams whose results change depending on who took the readings.
-
Custom tool development
Building the small piece of software a specific measurement needs, when nothing off the shelf fits and a spreadsheet has stopped coping.
For: programs where data collection is the bottleneck rather than the analysis.
-
Advisory
Reviewing a design, a dataset or a submission before it goes out, and saying plainly where it will be challenged.
For: anyone about to defend a number and wanting to know the weak points first.
Past work
Not written yet.
Three to five projects, one line each, each naming what changed as a result.
Starting a conversation
Describe the measurement and what it has to support. If it is not something I should take on, I will say so and point you at whoever should.