arrley exists to make work safe, healthy and high-performing. most of that happens inside client engagements. but some questions are bigger than any one engagement, and some tools should exist whether or not anyone is paying for them that month. that is what arrley labs is for.
why a consulting partner runs a lab
consulting has a quiet problem: the incentives reward confident answers, not tested ones. frameworks get sold for years after the evidence moves on. we would rather test our ideas in the open and be corrected early than defend a slide deck past its use-by date.
the lab is where we do that testing. it is deliberately small, deliberately practical, and wired into real work: the questions come from sites, boardrooms and incident reviews, not from conference stages.
what we focus on
labs work sits in the same four areas as our practice:
- health & safety: making regulatory knowledge usable, and finding indicators that lead rather than lag.
- people & culture: measuring what people actually experience, at a cadence that matches the obligation.
- organisational performance: reporting that changes decisions instead of filling slides.
- operational excellence: closing the gap between work-as-imagined and work-as-done.
how we decide what to share
two rules. open where possible: if something can be published, licensed openly and reused, it should be. honest about what’s unproven: project pages say plainly whether something is being explored, in development, or holding up in the field. you will not find invented case studies or suspiciously round percentages here.
the first project is safetylm, an open-source AI assistant for AU/NZ WHS practice, being built entirely in public. more on that in the next post.