Ursa Major
Menu

How to

Get startedYour first canvasFill in a blockPeople, machines and capacityCalculate and read the figuresFix a problem

Learn

Thinking in systems

A business is a systemA business is easier to read when you stop listing its tasks and start watching what builds up, what moves, and how long things take to move. This part introduces five plain ideas from systems thinking: stocks (what accumulates), flows (the rates that fill or drain them), delay (the gap between a cause and what you see), feedback loops (results that circle back and change what happens next) and cadence (the rhythm at which recurring work happens).Seeing what holds you backMost of what slows a business down is not visible on a normal day. Work waits between steps.Systems dynamics applied to businessA business changes through a few patterns: things that feed on themselves, things that push back, waits that make both overshoot, and limits that stop growth. This part applies stocks, flows, delay and feedback to two small businesses: referrals and the morning rush at a bakery, and rework, steel lead time and a bottleneck at a fabrication shop.

Working with the map

Two clocks: work and waitingEvery job in your business runs on two clocks: the hours someone works on it, and the time it takes from start to finish. The gap between them is waiting, and waiting is what customers feel and task lists hide.Ceremonies: what the rhythm costsA ceremony is a gathering that comes back on a rhythm: the morning huddle, the Wednesday order review, the month-end look at the numbers, the yearly planning day. Each one is small on the day it happens and large over a year, because the rhythm accumulates.ChunkingA chunk is a group of things you treat as one thing, so you can think about the group instead of every piece. Chess players, climbers and everyone planning a week do it all the time.Discipline and disciplined processA process written on a wall is a hope. A process that is repeated, on a rhythm, by the same people, in roughly the same way, is something you can look at, discuss and change.Adding up: cost, working hours and elapsed timeWhen you map a process you end up with figures on many blocks: hours of work, costs, durations, waits. It is natural to add them all up, but they do not all add the same way.

Stay current

What’s new

Support

Contact supportSend feedback

About

FeaturesOur approachAbout Ursa MajorTerms of ServicePrivacy PolicyConfidentiality

Draft: this text has not been reviewed by the owner and may change before publication.

Sales and marketing as flows

Selling is a chain of stages. A larger quantity goes in at the start, a smaller one comes out, and each stage costs time or money.

  • Planning ahead
  • 11 min read

That is a flow, and the chain does not stop at the sale: orders become demand on production and on people's hours. This part follows three everyday cases from outreach to the shop floor or the oven: cold calls, events and advertising. Every figure is a plan you would enter, not something measured. The tables show a way of looking. They do not say which channel is worth it, and you decide what you read in them.

Maple Street Bakery and Northline Fabrication are invented for illustration. The numbers are not data, and the currency is dollars only to keep the examples concrete.

One chain, from outreach to operations

Picture the whole thing as one line. Effort goes into outreach. Outreach produces conversations, then deals or orders. Orders land on operations as demand for production or fulfilment, which draws on people's hours and on materials. At each step a share continues and the rest drops out, or a quantity is converted into another unit, such as a deal into gates or an order into batches.

Three ideas from Part 2 apply.

  • Each stage can carry a flow figure. "1,000 calls a quarter" is a rate. So is "30 deals a quarter". The share between two stages is a ratio of two rates.
  • Stocks sit between stages. Conversations awaiting follow-up, quotes sent, orders waiting to be baked or welded. Each fills from the stage before and drains into the next.
  • Delay is part of the chain. A deal signed this month may come from a conversation last month, and its work may land the month after.

Cost works the same way. You can attach a cost to each stage and divide it by whatever you want to count: per call, per conversation, per deal. Same money, different denominators, different questions.

Illustration to come

One line from outreach to the shop floor: calls, conversations, meetings, deals, gates, each stage narrower than the last, with a stock drawn between stages and a cost written under each.

Here is the smallest possible version of the whole chain, as a process on the map, running from top to bottom like every process on the canvas: advertising (marketing), then orders (the units sold, the sales made), then production (operations). Each block is a real canvas card with invented figures: the Advertising card carries the ad spend of about 2,000 a month, the Orders card the 5,000 jars sold a month, and the Production card the 20 batches those orders turn into. Flip a card to see more of it, and drag the cards to rearrange them.

Practice process: advertising to orders to production to shipping. Drag the cards and flip them.

Invented figures. Nothing here is calculated live or saved.

Three examples

Example 1: cold calls, then the shop floor

Northline Fabrication phones property managers and contractors to open trade accounts. The plan for one quarter is about 1,000 calls.

StageCountHours eachStage hoursCost at 40/hour
Calls1,0000.11004,000
Conversations1500.2301,200
Meetings602.51506,000
Deals303903,600
Total37014,800

1,000 becomes 150, then 60, then 30. Thirty deals out of 1,000 calls is 3%. Divide the 14,800 by calls and you get about 15 each. By conversations, about 99. By meetings, about 247. By deals, about 493. All four are true of this plan. Only the denominator changed.

Illustration to come

The same 14,800 divided four ways: per call (15), per conversation (99), per meeting (247) and per deal (493), shown as one amount with four captions.

Now follow the deals into operations. Say each new account is planned to order about four gates in the quarter, so 30 deals become 120 gates.

Operations stageHours per gateHours for 120 gates
Quote1.0120
Cut1.5180
Weld4.0480
Ship0.560

Sam might state a capacity of 400 hours for the quarter. Against 480 hours of welding demand, that is a gap to look at. Whether the gap is a concern, a reason to adjust the plan, or an artefact of the estimates is for the owner to say. Note too the delay: a conversation turns into a meeting about two weeks later, so some of this quarter's welding comes from last quarter's calls.

Example 2: events, then catering orders

Maple Street Bakery takes a table at local fairs and markets, about 30 a year. Plan figures for one event:

Per eventPlan figure
Table fee300
Travel and parking100
Materials (samples, signage)120
Staff time (16 hours at 30)480
Cost per event1,000

Thirty events cost about 30,000 a year. If the plan expects about 1.5 deals per event, that is about 45 deals, and about 667 per deal. Inside one event, the chain might be 150 people at the table, 25 contact cards, 8 follow-up conversations, 1.5 deals.

The 1.5 is a point estimate for an average event. It hides spread: one event might produce nothing and another four. It also hides timing, since follow-ups from the last events of the year may close after the year ends.

Hand-off to the bakery: say each deal is a standing catering account placing about 12 orders a year. That is 540 orders. At about 1 oven hour and 1 baker hour per order, the plan carries 540 oven hours and 540 baker hours across the year, about 10 of each per week, on top of the counter and special orders already there.

Example 3: advertising, then batches

Here the unit is one jar of Maple Street Bakery's packaged granola, sold online and in a few shops, and the currency is dollars. Both are assumptions for the illustration. Over a month, the plan is about 2,000 in ad spend leading to about 5,000 jars sold.

StageCountShare of previous stageSpend per item
Ad impressions2,000,0000.001
Visits to the shop page25,000about 1.25%0.08
Orders2,0008%1.00
Jars sold5,0002.5 jars per order0.40

The 2,000 is spent once, and each row shows what it is divided over. Impressions, visits and orders are counts of events. The last row converts orders into units, because an order can hold several jars.

Then the jars reach the kitchen. If a batch makes 250 jars:

Operations stagePer batchFor 20 batches
Oven hours360
Packing hours (two people)480
Flour (bags)360

Two stocks make the picture whole. The flour shelf takes the 60 bags, so a good month draws it down faster than deliveries fill it. And cash: the ad money leaves before the sales money arrives. Spend per jar covers advertising only. Ingredients, packaging and delivery are other costs, elsewhere on the map.

Reading the tables

  • They are plans. A reader who sees "3%" may take it as a measurement. It is an estimate you typed.
  • Averages smooth things. One typical event, one average call. Real weeks vary.
  • Delay moves the credit. Spend in one period and work in another are linked only by your reading. You might read a deal as coming from last quarter's calls. A colleague might read it as a referral.
  • No table says what to do. A high cost per deal in one channel and a low one in another does not tell you which to keep. The tables give the shape of each chain so you can ask your own questions.

On the map

On the map

Plainly: Ursa Major does not ingest results and does not track leads, calls, events, ad performance or orders. It has no link to a phone system, a sign-up sheet or an ad account. Every authored plan figure on a block is something you enter, and it stays as you entered it until you change it. Calculated Output fields are the exception: they are refreshed when you calculate.

What a block can carry today:

  • A stage as a block. Draw each stage, from outreach through to cutting, welding or baking, and join them with connections that show what leads to what. A connection does not pass a quantity along. You enter each stage's figure yourself.
  • Time. Duration and Delay are separate figures, in minutes, hours, days or weeks. The two-week wait is a Delay.
  • Volume as a forecast quantity. A block can state a forecast quantity with a unit and a period, such as 1,000 calls per quarter.
  • Shares as your own figures. "15% of calls" can be a custom metric with a name, value, unit and period. The app records what you write. In advanced metric settings, a metric can combine two other figures on one block with a single add, subtract, multiply or divide, with exact units.
  • Cost you state. A direct cost contribution has an amount, a three-letter currency code and a basis: one-time, per period, or per quantity with a quantity you name (an order, a call). It may be classed as fixed or variable; an unstated class stays separate.
  • Cost from people. A person's or machine's rate times the hours you assign gives a cost for that work.
  • What the totals do. Amounts are added only when they share the same cost class, currency and basis, so fixed, variable and unclassified amounts are totalled separately. A per-quantity cost needs a stated volume in matching units to become a total. Nothing converts currencies.
  • What the totals say about gaps. When you ask the canvas to calculate, a missing amount, rate or assigned quantity counts as zero and is listed as counted as 0, while invalid or incompatible values stay unknown. Costs are directional figures for the operator.
  • People and capacity. Resources state capacity for a period, and blocks draw on it. The welding demand above would show against the welders' stated capacity as a figure to look at.
  • Child canvases. A campaign, an event or the whole call chain can open into its own canvas.
Note: Some figures can be calculated from connected blocks, with limits. Today that calculation covers Duration and Delay, published through Output fields. Conversion rates and unit volumes are figures you enter; the app does not work them out from the stages around them. Where a calculated value exists you can override it: type your own value into a mapped Output field and it takes priority, and when you calculate again, that field is left alone until you clear the override. An Input field that takes its value from another canvas's Output can likewise carry a local override. There is no override on custom metrics, forecast quantities or costs. You edit those directly.

The map is a plan of record: real call logs, receipts and ad reports belong in your other systems, and you can set them next to the plan.

Reflect

Questions to think about

  1. Pick one way you win customers. Name its stages in order, and for each say what comes in and what comes out. Which figure do you know best, and which are you guessing?
  2. Follow that chain past the sale. What does an order ask of your people, your equipment and your shelves, and how long after the outreach does it arrive?
  3. If you divided one channel's cost by calls, then meetings, then deals, which figure would you quote first? What would change if you quoted another?
Glossary