The SYSTEM Framework
Six questions. One framework. Built for operators who are tired of solving the same problems twice.
Most improvement efforts fail because they skip steps. SYSTEM is a six-step framework that ensures you solve the right problem, the right way, before building anything around it. The framework works for a problem you can solve in an afternoon and for a system that takes six months to build. The questions are the same.
The Framework
The questions most operators skip — and why skipping them is expensive.
S
Start with the Decision
What are we actually trying to decide?
Every problem worth solving requires someone to make a decision. The first job is to identify exactly what that decision is before anything else happens. Most organizations skip this step because the problem feels obvious. It rarely is. Starting with the decision rather than the solution is what separates leaders who build the right things from leaders who build things well and solve the wrong problem.
2 prompts in the pack
Y
Your Reality
Where are we right now?
Before you can improve anything you have to understand where you actually are. Not where you think you are. Where the data, the people, and the daily reality of the workflow say you are. This step covers the process, the data, the human dependencies, and an honest assessment of what AI can and cannot do in this specific workflow.
2 prompts in the pack
S
Simplify
What is the one thing we are solving?
Before anything gets built, the problem has to be narrowed to one decision, one outcome, one system. Not the roadmap. Not the vision for everything that could eventually be fixed. The one thing that will be solved completely before anything else gets added. Complexity is easy. Simplifying to the one thing that matters is the hard work, and it is where the leverage lives.
2 prompts in the pack
T
Test the Idea
Who needs to believe in this?
A good idea that nobody believes in will not survive contact with a real organization. Before anything gets engineered or scaled, the idea has to be sold. That means identifying who needs to believe in this for it to work, and building a proof of concept simple enough to show real value quickly. Internal selling is not a soft skill. It is the difference between a system that gets adopted and one that gets filed.
2 prompts in the pack
E
Engineer It
How does this work, and who owns it?
Now build it. With clarity on the decision, an honest picture of current reality, a simplified and specific outcome, and the right people bought in, the actual system can be designed and built properly. This means defining the inputs, the steps, the rules, the owner, and the expected output — including an honest assessment of whether to build in-house or bring in outside help.
2 prompts in the pack
M
Multiply It
How do we scale it and reinvest the time?
A system that one person uses is useful. A system the whole team uses is leverage. The Multiply step is about taking what works and expanding its impact beyond the person who built it — through automation, delegation, documentation, or AI-assisted workflows. It is also about being intentional about where the recovered time goes. Recovered time that is not reinvested disappears back into the noise within 90 days.
2 prompts in the pack
SYSTEM is not a rigid methodology. It is a set of six questions any operator can run a real business problem through. The depth of each step scales to the size of the problem. A quick internal tool might move through all six questions in an afternoon. A custom system might spend a week in Y alone, mapping current reality across multiple people and data sources.
The Prompt Pack puts the full framework in your hands.
12 deep prompts — 2 per step — built to run any business problem through the SYSTEM from start to finish. Each prompt includes a clarification layer that has the AI ask the right questions before it starts diagnosing.
$49 — one-time purchase