About Boole
Named after a logician.
Founded on a discovery.
Boole exists because the standard assumption, that performance failure means insufficient capacity, is wrong in most of the systems that matter most.
How Boole began
Our origin was an accidental discovery while applying logic, queueing theory, and system dynamics to model operational pathways, with the goal of establishing the capacity required to meet performance standards. Testing nationally recognised, best-practice healthcare pathways, we found something unexpected: for many of them, no amount of additional capacity produced sustainable compliant performance. The constraint was not the level of resource. It was that the pathway logic itself made the required standard structurally impossible to achieve.
Most organisations, and most improvement frameworks, assume performance failure means insufficient capacity, poor management, or inadequate effort from frontline staff. What we found was that many systems are operating at or very near their mathematical limits, constrained not by what they have, but by how their rules invisibly interact. And often, small changes to those rules, ones that preserve governance and safety, are enough to make the required standard achievable using the capacity already in the system, sometimes less.
Boole is named after George Boole, the Victorian mathematician and logician born in Lincoln. Based in Lincolnshire, Boole has long been an intellectual touchstone and inspiration. The company takes his name as a commitment: that what is built here makes a meaningful difference: an honour to his legacy, not an embarrassment to it. Boole was founded to bring that lens, the translation of system policies into verifiable logic, to the organisations that need it most.
What we believe
Performance issues are often due to invisible policy interactions
In most failing systems, the binding constraint is not resource. It is the invisible complex interaction of rules that govern the system: rules that, in combination, can make performance targets structurally infeasible regardless of how much capacity is added. Whilst standard performance improvement tools and methods cannot see this. Logic based analysis can.
Proof before commitment
Leaders making decisions about complex pathways deserve proven analysis of impact before they commit. The question is not "do we have a plan?" but "can this plan work?" Trial and error with complex systems is expensive, high risk, and avoidable. Proof is a founding principle of how Boole works, and it governs how we develop our tools and engage with clients.
Scale is the obligation
The methods that make invisible constraints visible are currently intensive and expert-dependent. Boole's long-term purpose is to make them accessible, across all complex systems, not limited to academic journals and research institutions.
Founder
Thomas Ridgeway
Founder
Thomas' experience includes a decade as a senior NHS operations manager before founding Public View, an NHS benchmarking and data analysis platform that has been used by more than half of all NHS organisations.
He holds an Executive MBA with Distinction from the University of Oxford, and serves as an Adjunct Lecturer in Economics and Operations Management for George Washington University.
Team
Boole is a small team of mathematicians, developers, clinicians, and operations specialists. We are growing, and always interested in hearing from talented people who share our mission. If that is you, please get in touch.