How to Decide What to Work On Next in Your Business

Run the four domains in order — Offers, Sales, Leads, Operations — and ask one pass/fail question at each. The first domain that fails is what you work on next. Everything else gets delegated to agents or parked. That's the whole method, and it beats every priority spreadsheet you've abandoned, because it encodes the one thing spreadsheets can't: sequence.

Here's the failure mode this replaces. You run a $5–50M business, which means the list of plausible next moves is effectively infinite: hire a sales lead, rebuild the website, launch the podcast, fix onboarding, raise prices, add a downsell. All of them are defensible. So the loudest one wins — the thing a client complained about this morning, or the tactic from the podcast you heard on the drive in. Six months later you've been busy every single week and the needle hasn't moved. Not because you worked on bad things. Because you worked on them in the wrong order.

Step 1: Ask the Offers question

Would a stranger who perfectly understood my offer say "that's obviously worth it"?

Not "do I have a product" — do you have a compelling offer: clear value proposition, an ideal customer you can name, pricing that reflects the value, packaging that makes the decision easy. If prospects who understand what you sell still hesitate, or if you win mostly on price, the offer fails the test. Stop here. This is your work. Fixing anything downstream of a weak offer is polishing the pipes on a dry well.

Step 2: Ask the Sales question

When a qualified prospect shows up, do we convert them at a rate we'd bet on?

You need a message and a process that reliably turns prospects into paying customers — a script that works without you delivering it, objections handled the same way every time, proposals that close. If conversion depends on the founder being in the room, the sales domain fails. Don't scale what doesn't sell. Pouring leads on an unproven sales motion doesn't test the motion; it torches the leads.

Step 3: Ask the Leads question

Is a predictable volume of qualified prospects entering the pipeline without heroics?

Only ask this after Offers and Sales pass — this ordering is the framework's sharpest edge. Most founders run to lead generation first because it feels like growth. But demand generated before offer and sales are dialed in wastes resources and burns opportunities you can't get back: a prospect who hits a weak offer doesn't return for the fixed version. If the first two domains pass and pipeline is thin or spiky, Leads is your work — content, paid media, outreach, referral systems, whatever fills the top predictably.

Step 4: Ask the Operations question

If demand doubled next quarter, would delivery hold?

When leads and sales grow to the point where delivery is strained — quality wobbles, onboarding lags, your calendar becomes the company's rate limiter — Operations is the work: SOPs, team structure, dashboards, automation. Note what this implies in the other direction: if you're systemizing before demand justifies it, you've picked comfortable work over the constraint. Ops before growth is procrastination with a Gantt chart.

Then loop — the answer keeps changing

Fix the failing domain and re-run the sequence. The bottleneck rotates: a stronger offer exposes a weak sales process; a proven sales process makes thin pipeline the constraint; a full pipeline strains delivery. That rotation is the design, not a flaw — it's why OSLO calls itself a loop. Each cycle the same four letters resolve faster, and more of your effort lands as forward momentum instead of exploration tax.

Two rules keep the loop honest:

• Ties break upstream. If two domains look broken, work the earlier one. Upstream fixes shrink downstream problems; downstream fixes can't touch upstream ones.
• One constraint at a time. The founder-architect works the bottleneck. Everything else runs on agents and team — the 285 portable skills exist precisely so non-bottleneck work doesn't need you. For tie-breaking within a domain, the Optimus Frameworks toolkit includes RICE scoring (Reach, Impact, Confidence, Effort).

What this looks like on a Monday

1. Twenty minutes: run the four questions against last week's numbers. Pass/fail, no essays.
2. Name the first failing domain out loud. That's the week's focus — yours personally.
3. Pull the relevant skills for that domain and put agents on the executable parts.
4. Refuse everything downstream. The podcast can wait if the offer is failing. It will still be a good idea in eight weeks.

The discipline isn't in finding work. It's in not doing the seductive downstream work while the upstream constraint stands. If you're not sure which question your business fails first, that's exactly what the assessment resolves.

FAQ

How do I decide what to work on next in my business?

Run the OSLO sequence in order — Offers, Sales, Leads, Operations — and ask a pass/fail question at each step. The first domain that fails is your priority. Don't skip ahead: work upstream problems before downstream ones, because each step feeds the next.

What if two areas of the business are broken at once?

Work the one that comes earlier in the OSLO sequence. A broken offer makes sales work pointless; a broken sales process makes lead generation wasteful. Upstream fixes make downstream problems smaller or make them disappear entirely.

How often should I re-run the prioritization?

Every time you complete a meaningful fix, and at minimum on a regular weekly review. OSLO is a loop, not a one-time audit — the bottleneck rotates through the four domains as the business grows, so the answer to "what next?" keeps changing.

What do I do with everything that isn't the priority?

Delegate it to agents and team, or park it. The OSLO library maps 285 portable skills to the four domains precisely so that non-bottleneck work can run on agents while the founder-architect concentrates on the constraint.