Handoffs are where work dies
Every failure I investigated came down to a handoff: someone thought someone else owned it. A working system makes the next action and its owner explicit at every single step — never assumed.
About JFS OPS
Turn operational friction into working systems.
JFS OPS explores how practical software, automation, process intelligence, and selective use of AI can help organizations run better.
Why I started this
Built from operational experience, not software theory.
I'm John Shelly, a Toronto-based facilities and workplace operations professional. I've run a 1.5M sq ft three-site portfolio with a $6M operating budget and around 5,000 daily occupants — including saving about $200K a year renegotiating a cleaning contract, and managing coordinators across London and Paris.
What I kept seeing wasn't a lack of effort or talent. The real challenge was rarely receiving the first request — it was keeping the work visible once responsibility moved between coordinators, vendors, approvers, and landlords. In that gap, information scattered across email, work orders, spreadsheets, and service-provider threads, and follow-up depended on memory.
JFS OPS is being built around a practical response: create a reliable record for unresolved work, make the next owner and next action explicit, and use the record to improve. The company is deliberately starting narrow — one high-friction workflow at a time — rather than claiming to replace an organization's existing systems.
What the work taught me
Three lessons from the operations floor.
Running facilities and shipping operations across countries, contractors, and buildings taught me the same lesson in different uniforms: the system breaks at the handoff. Three things I learned shape everything JFS OPS does:
Invisible work is unmanaged work
If a request lives in someone's head, a chat thread, or a corridor conversation, it does not exist to the operation. The first job of any system is capture: make the work visible before trying to optimise it.
The third time is a procedure
The same failure at the third site is not bad luck — it is a missing procedure. Operations that remember what happened last time stop paying for the same lesson twice.
How we think
Practical before complicated.
The goal is not to add technology for its own sake. The goal is to understand the work, reduce avoidable friction, and create systems that teams can actually rely on.
Make the work visible
Important operational work should not disappear into email, hallway conversations, spreadsheets, or memory.
Connect the next action
A useful system makes ownership, urgency, approvals, and follow-up clear to the people responsible.
Improve what repeats
Recurring work creates patterns. Those patterns can become better procedures, reporting, and decisions.
Initial focus
Start with the work that keeps places running.
JFS OPS is initially focused on facilities, workplace, property, and business operations.
Potential applications include request intake, work routing, vendor coordination, reporting, documentation, process visibility, and human-approved automation.
The starting point is intentionally practical: one specific workflow, one team, and one measurable improvement before expanding further.
JFS OPS is currently in build: the Operations Desk is running with its first operational capabilities, and we are preparing for first pilots with facilities teams. If you are reading this early, you are seeing the product take shape — the pilot plan describes exactly what comes next.
Talk to us
Describe the friction in your operation.
A short conversation about the workflow, the information involved, and a practical next step.