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.

Discipline and disciplined process

A 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.

  • Working with the map
  • 7 min read

This part is about the discipline of doing the work often enough, on a rhythm, that it becomes a process you can see. It is not a matter of willpower or virtue. It is a matter of cadence, and cadence can be drawn on a map.

A process exists only when it repeats

Think of a recipe that has been cooked once. It is a story, not a process. You cannot say how long it takes, what it costs, or where it waits, because you have only one example to go on.

A process begins to exist when the work comes back. Quotes go out every Monday. Invoices go out on the first of the month. Every delivery gets the same three checks. The repetition is what makes the shape visible: the steps stop changing, the waits become familiar, and the people involved can describe it in the same words.

That is also why a process can quietly stop existing. If the Friday review is skipped three weeks in a row, it is no longer a Friday review. It is a habit that used to exist. Nobody decided to drop it; the rhythm simply lapsed.

Two things are worth separating here:

  • Repeating is doing the work again on its usual rhythm.
  • Standardizing is doing it the same way each time.

You can have the first without the second. A business often runs a weekly purchasing round that is done differently by whoever is around. The cadence is real; the method is not yet stable. Seeing which of the two you have is a useful thing to know, and neither is a failure.

Cadence as a discipline

In Part 2 we described cadence as the rhythm at which a flow runs: hourly, daily, weekly, monthly, quarterly, or once. Here the point is a little different. Cadence is also the thing that most often holds a process together.

A weekly meeting is a cadence. So is a month-end close, a morning stand-up, or the first Monday inspection of the tools. These recurring events have a quiet job: they are the moments when information gets passed from one person to the others. They are also the moments that tend to get cancelled first when a week is full.

A few lenses on cadence, offered as questions rather than rules:

  • What rhythm does this work actually run at? Not the rhythm you meant. The one you could point to in the last two months.
  • Who or what depends on it arriving on time? A late invoice run moves money later. A late stock check moves a delivery date later. Sometimes the dependency is easy to see; sometimes you only learn it when the rhythm slips.
  • Is the rhythm shared or private? If only one person knows it runs on Thursdays, the cadence belongs to a person, not to the business.
  • What does the rhythm cost? A recurring meeting is a stock of hours leaving the business on a schedule. That is neither good nor bad. It is a figure worth knowing.

Notice that none of these questions asks whether the cadence is right. The map cannot know that. You can.

A worked example

Maple Street Bakery is invented, for illustration only.

Maple Street Bakery is a neighbourhood shop with a few staff. Dana owns it, bakes and does the special orders. Léo runs the counter. Priya does the early shift in the kitchen.

Dana draws the week as three pieces of repeating work:

  • Opening and closing. Every day, Priya opens at 5:00: ovens on, dough out, trays set. Every evening, Léo closes: counter cleared, floor swept, ovens off, tills counted. Each takes about 45 minutes.
  • Weekly equipment checks. On Mondays, Priya spends 30 minutes on the ovens and the mixer: door seals, temperature against the dial, a look at the belt. Dana wrote a short checklist for it.
  • Wednesday huddle. After the lunch rush on Wednesdays, Dana, Léo and Priya spend 30 minutes on the special orders for the week and anything that went wrong at the counter.

When she gives each piece a rhythm, the map shows something she half-knew. Opening and closing run every day, because the shop cannot open without them. They are also the same two people each time, which means that when Priya is away, the opening is suddenly a question. The Monday check is a weekly rhythm, and Dana knows that in practice it sometimes slides to Tuesday. The Wednesday huddle is "weekly" on paper, and the map says nothing about whether Wednesdays have been going that way.

Illustration to come

The bakery's week as a grid: opening and closing every day, the Monday equipment check sliding to Tuesday, and the Wednesday huddle, each with its people and minutes.

There are many ways to read that. You might read the sliding check as a sign that Monday is a busy morning. You might read it as an honest picture of a shop where the rhythm bends a little. The map does not choose between these. It holds the planned rhythm. If Dana wants to compare it with what happened, she looks at her diary or her own notes, outside the map.

What she does next is hers. She may move the check to a quieter day, give it an owner, put Léo in charge of the huddle, or leave everything as is. Any of those is a legitimate answer. What changed is that she is making the choice on purpose.

On the map

On the map

Ursa Major lets you show cadence and recurring work directly.

  • A process card carries a cadence chip showing how often it runs: hourly, daily, weekly, monthly, quarterly, yearly, every N periods, one-time, or, for work triggered per client, invoice or request rather than by the calendar, a flow chip that names the work unit. You set this under Process behavior in the block's editor. A block with no schedule shows a dashed placeholder chip (its tooltip reads "Schedule not set"), which is a gentle way of saying the rhythm has not been stated.
  • A block presented as a Ceremony (chosen under Presentation in the editor) stands for a recurring gathering such as a weekly meeting; its resources tab is called People and support, and its rhythm is stated the same way as any other block's.
  • Cadence is configuration only. It records the pattern you intend. It does not schedule occurrences, and it does not change any total, resource demand or cost.
  • An optional Tint cards by schedule setting in Canvas options colours cards by their cadence, so daily, weekly and monthly work can be told apart at a glance. It is off until you turn it on.

Illustration to come

Screenshot of three process cards: one with a weekly cadence chip, one with a per-request flow chip, and one showing the placeholder for a schedule that has not been set.

None of this checks whether the work happened. The map holds the plan: what you intend to run, when, and with whom. It does not count how often it ran. Whether it ran as planned is something you observe elsewhere. Part 7 comes back to that.

Reflection questions

  1. Think of one thing in your business that "we always do". When was the last time it was done, and by whom? Is the answer the same as what you expected?
  2. If you wrote down all the recurring rhythms in your week (meetings, runs, checks), which would you be surprised to see listed together?
  3. Which of your rhythms are written down somewhere other people can see, and which are known to only one person?
Adding up: cost, working hours and elapsed time