Technical practice, grounded in eighteen years of shipping.
The work of making it work. Probable is the solo engineering and product practice of Neil Littlejohns. I help organizations navigate the transition from a concept to a reliable, production-ready system.
After two decades in the tech industry, spanning the UK, Canada, and global remote teams, I'm taking what I've learned and applying it to people's ideas and problems.
A practitioner's perspective.
My career began in the UK after graduating with Master's in Computer Science from the University of Bristol. My career started in video games working as a developer support engineer on the PlayStation SDK. Through this work, I learned exactly where systems fail their users. This proximity to the work led me into product management, not as a move away from engineering, but as a way to better architect the roadmap.
Since then, I have stayed close to the tools while leading teams at scale:
- Scale-up Leadership: As the senior product lead at an early-stage startup for identity verification, I grew the team and product through its formative years toward a $400M acquisition.
- Public Service: I joined the Ontario Digital Service during the COVID-19 pandemic, navigating high-stakes technical and privacy constraints, delivering apps and services to help keep people safe.
- Global Product: I've held director and staff-level roles at major privacy-tech companies with hundreds of millions of users, delivering engineering, design and product excellence.
How I work.
I treat every project like a site survey, assessing the existing terrain before recommending a path forward.
- Focus on Constraints: We start with your business reality and technical limitations. Focusing on the problems helps keep "solutioneering" at bay.
- Functional Increments: Small, high-fidelity deployments provide immediate feedback, reduce architectural risk and deliver compounding benefits sooner.
- Capability Building: I work alongside your team to ensure they understand the how and the why, leaving your organization stronger and more self-sufficient.
- Objective Clarity: I speak plainly about trade-offs, technical debt, and uncertainty. My role is to reduce noise, not add to it.