SYSTEM FIRST — TASK SECOND
Most task and project apps have it backwards: they optimize finishing singular tasks, with the totality of the work second. The Marduk Method reverses the paradigm — the priority is accomplishing the business's objectives through your tasks. It is a system to create the systems in your business.
Slice the Chaos into Pieces
The Method treats tasks as the unordered chaos the hero faces. First you cut the chaos into pieces — tasks — and every task falls into one of three categories: Projects, Chores and Responsibilities. Then you weave those pieces into a tapestry: your business system. List them, quantify them, give each an SOP and completion criteria, and put a management process over the whole — and you'll sleep soundly knowing the business is running as well as it can.
Projects, Chores & Responsibilities
The task taxonomy — three kinds of pieces, three different disciplines.
Projects
Tasks with a start and a clear end. When you're done, you're done — move the office, launch the website, sell the company vehicle. Big or small, what they have in common is that they never repeat.
Chores
The lifeblood of any established business: tasks that repeat on a predictable cadence, with the most consequence when they're missed. Pay rent. Run payroll. Send the investor update. Frequency is negotiated with the team — and can extend as competence grows: weekly becomes monthly becomes quarterly.
Responsibilities
Tasks that repeat — unpredictably. Onboarding a new employee. Who administers each software account. Who do you call when the lights go out at the front of the building? The disregarded details that become very important the day you sell.
As Infrequently as Possible, Yet as Often as Necessary
That is the whole doctrine of chore frequency. Only experience and your team can negotiate how often a chore truly needs doing. When you're unsure, err on the side of a higher frequency — then extend it as the team gets more competent. In this way a chore is dynamic, and every extension hands you back time.
Negotiated, Opt-In Agreements
The assessment is a negotiation because every expectation gets explicit opt-in from the whole team. When everyone agrees payroll is completed every two weeks, a payroll that hasn't been issued by the 20th day is a fact to address — not an argument about whether it's late. Precise language turns conflict into administration. Use your words: they are magic.
Management by Exception
Marduk has eyes all around his head — it is impossible for him to miss something. Codify when everything is due, and when it's all on time, don't manage. A late task is an exception, surfaced immediately. Think of it like an appliance starting to spark: identified quickly, it's a simple fix. Ignored, the sparks become a flame — and left unattended, the flame becomes an inferno that consumes the whole building. Management by exception means the sparks never get that far.
SOP-First, In-Flow Documentation
Most people avoid creating standard operating procedures because they don't know how, they don't prioritize it, or they harbor a subconscious fear of eliminating that which gives them meaning. The Method makes documentation in-flow: every time a task is completed, its SOP and completion criteria accrete — until the task could be handed to a third party. That documentation is the ultimate value: it is the IP a buyer actually wants, in a system instead of your brain.
Every SOP Is Written Toward Three Handoffs
- Cover — a colleague can take the task while you're sick or on holiday
- Scale — your replacement hits the ground running
- Sale — the operational knowledge transfers to the buyer, not with you
The Daily Practice
Marduk keeps you accountable to the things you know you should be doing.
Bounded Days
Know when you're done before you start. Each day is a strategically constructed, finite scope of work with a clear and definitive end — the antidote to always-on burnout, and the source of the sense of accomplishment that drives motivation.
30-Day Streaks
Complete everything you commit to, every day. Breaking daily commitments erodes your team's trust and your own self-esteem; keeping them — and stacking a 30-day streak — rebuilds both. Accountability starts with yourself.
Batch Your Work
Tasks come at us fast, and it's easy to get stuck putting out fire after fire. Visibility into your workflows uncovers similar tasks so you can batch them — a proven way to work smarter, not harder.
Work ON, Not IN
Too often we get stuck working in the business and neglect to work on it. The core of the method is constantly evaluating what you're working on and optimizing your effort for maximum result — carved-out strategic time, not fire-fighting.
READY TO PLAY A LARGER GAME?
The world's highest performers have a coach. Do you? Building a business system requires seeing the forest for the trees.