How Can a Solo Marketer Run a Weekly Operating System in 90 Minutes?

Run a 90-minute solo marketing control window with a triage board, costed agenda, capacity rules, four-week simulation and exception decisions.

Short answer: answer: Reserve one uninterrupted 90-minute block: spend 15 minutes refreshing facts, 20 triaging exceptions, 25 making at most three priority decisions, 20 scheduling capacity and 10 recording commitments. Cap active work at three outcome-bearing items and move anything without evidence, an owner or a next action out of “active.” The block controls the week; it does not produce status reports.

The obvious solo workflow is a long task list. It fails because tasks do not show which live claim is expiring, which campaign is blocked or which request has displaced planned work.

The other failure is building an enterprise ritual for one person. A solo marketer needs enough control to stop drift, not a committee’s paperwork. Ninety minutes works only if routine capture happens during the week.

The Solo Operator Triage Board

The Solo Operator Triage Board has five lanes: Signals, Decide, Active, Waiting and Parked. CDM’s position is: the weekly control window should be spent on exceptions and decisions, never narrating work to yourself. Microsoft’s 2023 Work Trend Index found the measured Microsoft 365 population spent 57% of its time communicating and 43% creating; a solo system should not manufacture more communication load.

Build the board before the meeting with yourself

Each card needs only: outcome, next decision, deadline, evidence link, risk, effort remaining, dependency and next action. Signals holds unprocessed facts such as a source change or cost spike. Decide holds items that require a choice this week. Active contains a maximum of three deliverables. Waiting requires a named external dependency and chase date. Parked means explicitly not active.

Use four admission rules:

1. A card enters Active only when its intended outcome and next action are clear.
2. A new urgent card displaces an existing one; it does not create a fourth slot.
3. Waiting work does not occupy an Active slot unless the operator still has an executable action.
4. A claim, rights or customer-harm exception outranks an optimization experiment.

Kanban guidance treats work in progress as started but unfinished work and recommends limiting it to improve flow. Three is a starting policy, not a universal scientific constant. Replace it with observed throughput after four weeks.

The costed 90-minute agenda

Do not open email during the block. Capture requests into Signals beforehand. The 15-minute refresh uses a fixed panel: customer/revenue outcome, campaign delivery, evidence/rights expiry, measurement health and available hours. Investigate anomalies later unless the decision cannot be made without them.

Make at most three decisions

A decision changes priority, allocation, risk acceptance or correction. “Continue writing article” is an action; “pause the webinar and use its 8 hours to repair broken CRM attribution” is a decision.

Record Decision ID, choice, reason, evidence, consequence, review date and what stopped. GitLab’s public DRI model emphasizes one accountable individual while still gathering relevant input. Solo work still needs named external approvers for legal, financial or product matters; “solo marketer” does not mean universal authority.

Schedule usable capacity, not nominal hours

Start with contracted hours, subtract fixed meetings, administration, support and a risk buffer. An illustrative 40-hour week might contain 6 hours meetings, 5 administration/support and 5 interruption reserve, leaving 24 planned production hours. Allocate no more than 20; hold four for exceptions.

At an illustrative fully loaded cost of $60 per hour, the 90-minute block costs $90. If it prevents three hours of abandoned production, it avoids $180 of modeled capacity cost, a net $90. This is a CDM scenario calculation—not a time study or promise of savings. Substitute the reader’s real cost and track abandoned hours.

Four-week illustrative simulation

Assumptions: one marketer, 24 usable hours weekly, three Active slots, 4-hour exception reserve, and work sized in focused hours. No interviews or observed practitioner data underpin this simulation.

Week 1: Active items are an 8-hour landing-page correction, 8-hour creator brief and 4-hour email experiment. The system leaves four hours reserved. Throughput: three items.

Week 2: A consent-sync fault arrives, estimated at six hours. It replaces the 8-hour creator brief; two hours come from reserve and four from the displaced slot. The brief moves to Parked with a new decision date. Throughput: two planned items plus incident containment.

Week 3: The creator brief returns at six hours after scope reduction. One campaign awaits product evidence and moves to Waiting, freeing a slot. Throughput: three.

Week 4: Review shows median completion near seven hours and one recurring two-hour reporting task. Automating that report is justified only after its inputs are stable. The operator sets next month’s starting WIP at three and preserves the four-hour reserve.

Across four weeks, the model offers 96 usable hours. It plans 80 production hours and reserves 16. The point is not 83% utilization; it is absorbing one real exception without silently lengthening every commitment.

Decision rules for common collisions

• Revenue request versus evidence correction: correct potentially harmful or misleading content first.
• New idea versus active experiment: require displacement and state what learning is lost.
• Executive request with no outcome: move to Decide, ask what changes if it succeeds.
• Blocked work: set a chase date; park it if no executable next step exists.
• Recurring manual task: simplify and standardize before automating.
• Deadline without reason: treat it as a preference until the consequence is stated.

GOV.UK’s service guidance recommends regular prioritization using performance analysis, user research and stakeholder input, recognizing limited time and skills. The board operationalizes that principle for one person without pretending every card can be “must have.”

Measure whether the system works

Track completed items, active-item age, unplanned hours, displaced work, decision turnaround and corrections missed. After four weeks, adjust the WIP cap or buffer from evidence. If the 90-minute block repeatedly exceeds two hours, the likely problem is too much active work, missing capture during the week or unresolved authority—not an agenda that needs more fields.

Related guides

• How Do You Build a Marketing Approval Trail With Microsoft Lists and Power Automate?
• How Do You Turn Slack Marketing Decisions Into Durable Records?

Frequently asked questions

Is 90 minutes really enough for weekly marketing planning?

Yes, if the block is for control rather than content production or reporting. Inputs must be captured during the week, the dashboard must be small and investigations must become scheduled actions. Ninety minutes is a constraint that forces choices.

A marketer facing an active crisis, quarterly planning or a major launch may need a separate working session; do not stretch the weekly ritual until it consumes the capacity it is meant to protect. Track actual start and finish times for four weeks, then remove recurring preparation that should happen during capture.

Why cap active work at three items?

Three creates a visible trade-off for one person while leaving room for an exception. It is a starting assumption, not a researched universal optimum. Track throughput, completion time and blocked work for four weeks; raise the cap only if items finish predictably without increasing age or corrections.

Very small deliverables may be batched under one outcome-bearing card, while a high-risk launch may warrant a cap of one. The unit must remain meaningful. Count a waiting item when it still needs chasing, review or deadline protection; otherwise move it out of Active.

What counts as a marketing exception?

An exception is a condition that can change priority, risk or an existing commitment: broken tracking, expired rights, unsupported claims, unusual cost, missed dependency, customer harm or a result outside a pre-agreed threshold. A new idea is not automatically an exception. Define thresholds before looking at weekly numbers, otherwise normal variation becomes urgent work.

The caveat is safety or legal risk, which should be escalated even when no numeric threshold exists. Give every accepted exception an owner, containment action and time when normal work will be reconsidered.

Should a solo marketer automate the weekly review?

Automate stable collection and reminders, not judgment. A connector can refresh metrics, flag overdue evidence and create a review card; it should not decide which customer promise to break or whether a claim is supported. Stabilize the fields and run the review manually for four weeks before automating.

If input failures are silent, automation makes the ritual faster but less reliable, so include missing-data and last-refreshed indicators. Test one expired credential, one duplicate event and one failed write before depending on the automated preparation.

How should I price the 90-minute block?

Multiply 1.5 hours by the fully loaded hourly cost or by the opportunity value your business uses for planning. CDM’s $60 example produces a $90 weekly control cost; it is illustrative and excludes overhead differences. Compare that cost with observed abandoned hours, rework or missed corrections, not imagined revenue.

Founders who do not draw a salary should still assign a shadow cost so administration is not treated as free. Finance can provide a range when one exact rate would imply precision the company does not have.

What if every request seems urgent?

Require each requester to state deadline consequence, affected customer, economic exposure and what should be displaced. If everything remains urgent, rank harm and reversibility: safety, legal, customer and irreversible commitments first; bounded experiments later. A true capacity gap then becomes visible.

The exception is an incident command situation, where normal planning pauses and one response objective governs work until stability returns; record what was deferred afterward. Publish the ranked queue weekly so urgency cannot be renegotiated privately through repeated messages.

Next decision: Design a marketing team for creator-led growth and AI discovery

Related reading: Create a practical experimentation system · Design the contemporary marketing operating system · Build a modern content supply chain

Sources and research notes

• Microsoft, 2023 Work Trend Index: Will AI Fix Work?.
• Kanban University, The Official Kanban Guide.
• GOV.UK Service Manual, Deciding on priorities.
• GitLab Handbook, Directly Responsible Individuals.

Research checked 26 September 2026. No solo-practitioner interviews or original time study were conducted. The capacity, hourly cost, avoided-cost and four-week results are transparent CDM simulations, not observed findings. Readers should replace every assumption with tracked hours and have specialists review regulated or high-risk decisions.