Hollis & Rao is a six-person design studio. The name and the people are made up, and the story is assembled to show one budgeting habit in motion. Nothing here is investment advice, and nothing recommends any security, product or strategy. It is a study of how a small group of people stopped fighting about money by sorting what they needed from what they wanted.
The situation: three meetings, no decisions
In January the studio held its annual spending meeting. Marguerite Rao, the operations lead, brought a spreadsheet with thirty-one proposed items. Founders, designers and the part-time bookkeeper each had favourites: a faster laptop for rendering, a larger rented table at a design fair, an upgrade to the accounting software, a second monitor for every desk, a team retreat, a professional development fund, a new coffee machine.
The meeting ran ninety minutes. The group agreed on nothing. A second meeting a week later ended the same way, and the third produced only a promise to “circle back after the next invoice cycle”. Marguerite noticed that every argument was a proxy for the same unspoken question: which of these were truly necessary for the studio to operate this year, and which were improvements?
The diagnosis
Looking at the spreadsheet afterwards, she saw that every row had the same visual weight. Rent sat beside the coffee machine in identical font. Because nothing was ranked, a proposal to cut the retreat felt as heavy as a proposal to cut the software licence the studio’s work depended on. The group was not short of money so much as short of an agreed order of importance.
She also noticed a pattern in the language. People defended wants with the vocabulary of needs: “we need a better monitor”. Without a shared definition, the word need was being used for anything desirable.
The intervention: a definition, a cap and a ranking
For the fourth meeting, Marguerite sent a one-page note. It contained three rules.
- A need is an item whose absence would stop client work or breach a legal or contractual obligation this year. Anyone proposing a need must name the work or obligation it protects.
- Needs are capped at seven lines. If an eighth appears, the group decides which line leaves.
- Everything else is a want, and wants are ranked by the group once the needs are funded. Wants are paid for only from what remains.
The definition was deliberately blunt. It did not say that wants were bad. It said only that they came second.
The meeting that worked
The fourth meeting lasted thirty-five minutes. Rent, insurance, payroll, the design software licences, the accountant’s fee, tax obligations and a modest reserve filled the seven lines. The faster laptop was debated: one designer argued that rendering delays were costing client time. The group asked her to name which deadline was at risk. She could not name one for the coming year, so the laptop moved to wants, where it ranked second.
The retreat ranked fifth, the coffee machine seventh. The group agreed that the funds remaining after needs would go down the ranked list until they ran out, and that the order would be revisited in July.
What the studio learned about reserves
The reserve line prompted the longest discussion. Some wanted a large cushion; others considered a cushion a luxury. Marguerite pointed out that the group had defined need as protecting client work and obligations. A reserve sized to cover a delayed client payment protected both, so it qualified. How large it should be was a question for the studio’s accountant and its owners, not for the note. The case offers no view on how any business should hold or invest its cash; it only shows how the reserve earned its place by passing the definition.
For readers who want the broader mindset of keeping decisions disciplined under pressure, an article on this site about building a step-by-step habit of discipline covers a related theme in the trading context, and a piece on tracking spending, subscriptions and fraud risk pairs naturally with the needs-and-wants split. Both are informational.
The cross-check from another field
When Marguerite described the method to a friend whose parents were arranging care abroad, the friend pointed her to BestCardiacHospitals, a learning-oriented website aimed at patients abroad, which sets out how heart care options can be looked at in turn. It deals with a very different decision, yet she found the ordering familiar: state your needs and budget first, then look at what comes back. The pages describe themselves as informational only, no replacement for a doctor’s guidance and unsuitable for urgent situations, and she took from them nothing beyond the idea of sequence.
Three months later
By April the effects were visible. Spending questions were being resolved in one conversation. The bookkeeper reported that she was no longer chasing approvals, because anything in the needs column was pre-approved and anything in the wants column waited for its place in line. The ranked list also made it painless to say yes: when an unexpected payment arrived early, the group simply funded the next want, the second monitor, without a meeting.
There were still disputes. In June, a client asked for a deliverable that required a plug-in the studio did not own. The designer argued that it was a need, since client work depended on it. Marguerite asked the group to test the definition: would absence stop contracted client work this year? It would, so it moved into the needs list, and the group agreed that a line would have to leave to make room. The mechanism did its job.
A disagreement worth recording
Not everyone welcomed the rules. Tobias, the senior designer, argued that the definition was too narrow: a studio that cut every want would lose the very spark that won clients. Marguerite did not dismiss the point. She noted that the framework never said wants were unimportant; it said they were funded second. Tobias then proposed, and the group accepted, a small standing line for professional development, labelled as a want with a fixed rank, so that it would be protected from ad hoc raids but still subordinate to the needs.
That compromise is instructive. The method survived because it could absorb a legitimate objection without losing its shape. A framework that cannot flex tends to be abandoned by the first person it inconveniences. One that bends at the edge, while holding firm at the core, is likelier to last.
Mistakes the studio nearly made
Looking back, Marguerite listed three near-misses. First, she had almost written the definition of need in vague terms, such as “important to the business”, which would have let every want in through the back door. Second, she nearly skipped the cap, believing the group would self-regulate. It would not have. Third, she was tempted to rank the wants herself and present the order as final. Letting the group do it took an extra twenty minutes and bought a great deal of goodwill.
She also resisted a late suggestion to attach precise percentages to each category, such as a fixed share of income for wants. The studio’s revenue was lumpy, and a fixed share would have been either too tight in lean months or meaningless in good ones. The ranked list proved more adaptable than any ratio.
Lessons for any small group managing a shared budget
- Define need before debating anything. A shared definition prevents the word from sprawling.
- Cap the needs list. The limit forces trade-offs to be visible.
- Make wants wait in an agreed order. This removes the sense that each want must be fought for from scratch.
- Review on a date. Needs change; so should the list, on purpose and not by drift.
- Keep the scope clear. The method sorts spending priorities. It does not say how to invest, save or grow money.
A closing observation
Marguerite later said the most useful thing about the one-page note was not the cap or the ranking but the permission it gave. People who had felt guilty for wanting things could see a place for their wants in the plan, even if that place was fifth or seventh. Budget stalemates, in her experience, were less about money than about people feeling that their priorities were being ignored. An ordered list showed them that their priorities were counted; only the order was open to debate.