Manifesto
Every operation I've worked inside hit the same limit. Not capability. Articulation.
The work itself was rarely the hard part. What slowed things down was that nobody had written down how the work actually moved: who decides, what triggers what, where it hands off, what "done" means. That knowledge lived in people's heads, which meant it left the room when they did, and every exception became a conversation instead of a rule.
AI hasn't changed that. It has made it impossible to ignore. You cannot automate a process that was never defined, and a process held together by habit doesn't survive the attempt to encode it. Articulating the work is not the paperwork before the real change. It is the change. Everything after it gets easier.
The bottleneck moved.
Not "can we execute?" but "have we said clearly what we're trying to do?"
That's an articulation gap, not a capability gap.
The function
Managing the work gets it delivered. Designing the system it moves through is what makes delivery repeatable, and that is the half I keep being hired to fix.
- Function
- Systems Operator
- Scope
- Project delivery · product operations · applied AI
- Method
- Map the workflow · write it down · automate what holds
- Base
- London, Ontario · Hybrid
- Stack
- Obsidian · Claude · Cursor · n8n · Notion · WordPress · Figma
- Languages
- EN · 中文
- Aim
- Make the right outcome the easy one
Doctrine
Delivery is an architecture problem, not a people problem.
The right outcome should be the path of least resistance: built into the system, not held together by whoever happens to be paying attention that week. A process that lives only in someone's head is a liability. A workflow that depends on memory instead of design is a failure waiting for a busy Friday.
Scoping · agile planning · workflow orchestration · documentation · data structure
Built in order
Each layer only holds if the one beneath it is sound. Most automation fails because someone started at the top, automating a process nobody had defined, on data nobody trusted.
Structure
Where information lives, and how it moves between people.
Definition
The process written down, so it survives the person who ran it.
Visibility
Status legible without a meeting to establish it.
Automation
The repeatable parts stop needing a human to remember them.
Agentic
What I'm building toward: systems that adapt, not only run.
Practice
Project & Product Delivery
Scoping, quoting, and running projects end to end, with the handoffs defined before they're needed rather than after they break.
Operations & Systems Architecture
Turning how a team actually works into something written down, repeatable, and not dependent on one person being available.
Team & Client Alignment
Keeping everyone on the same priorities and definition of done, and answering "where is this?" without a meeting to find out.
Agentic Development & AI
AI-assisted planning, documentation, and prototyping inside real client delivery, where it earns its place, not where it demos well.
Roles, dates, and outcomes are in the field record.
Channel
Open channel
If you're hitting the articulation gap, the distance between what your operation is and what it needs to become, that's the conversation. Not looking to manage execution. Looking to design the conditions that make it straightforward.
Signal
- Lat · Lon
- 42.98° N 81.25° W
- TZ
- EST (UTC-5)
- Response
- ≤ 24h
- Availability
- Weekdays