How we think

Our Methodology

The needs-wants distinction is older than modern finance. Winega uses it in a specific way, applied to specific situations, without the assumptions that usually come attached.

The core framework

What "needs vs. wants" actually means

Needs

In the Winega framework, a need is something whose absence creates a genuine functional problem. Not discomfort. Not inconvenience. A functional problem. The category is deliberately narrow.

This narrowness is useful. When you apply a strict definition of "need," many things that feel necessary reveal themselves as wants. That's not a moral observation. It's a clarifying one.

Needs also exist on a spectrum. Shelter is a need. But the specific form of shelter that meets the need varies enormously depending on context.

Wants

Wants are not lesser than needs. This is a critical point in the Winega methodology. The framework does not imply that needs should be met before wants are considered. That would be moralizing.

Wants serve real functions. They contribute to quality of life, to identity, to social connection, to pleasure. These are not trivial. The framework identifies a purchase as a want not to diminish it but to describe it accurately.

Knowing something is a want gives you more information about the decision, not a verdict on whether to make it.

How we apply it

Methodology principles

A

Start with the situation, not the category

The framework is applied after the situation is understood, not before. We don't arrive at a case study with a predetermined category in mind. We examine the situation first and apply the framework to what we find. This order matters. Applying the category first produces confirmation, not insight.

B

Hold the framework loosely

The needs-wants distinction is a lens, not a law. Some spending decisions resist clean categorization. That resistance is informative. When the framework doesn't produce a clear answer, the interesting question is why. Sessions spend time in that ambiguity rather than forcing resolution.

C

Track the decision, not just the purchase

The methodology examines the decision process as much as the outcome. What triggered the spending? What alternatives were considered, even briefly? What would have happened if the purchase hadn't been made? These questions reveal the structure of the decision, which is often more useful than knowing the category of the purchase.

D

Treat emotional function as data

Purchases often serve emotional functions. Comfort. Status. Belonging. Reward. These functions are real. The methodology treats them as information rather than as problems to overcome. A purchase that serves an emotional function is not irrational. It may be exactly the right purchase for the situation. The framework helps you see what function is being served.

E

No universal conclusions

The same case study discussed by different groups produces different insights. Winega sessions don't aim for consensus. They aim for clarity — for each participant about their own relationship to the spending scenario being examined. Different people can reach different conclusions from the same case study and both be right.

In practice

How a case study is selected and used

Case studies for Winega sessions are chosen based on two criteria: they must be recognizable to a wide range of participants, and they must resist easy categorization.

A scenario that everyone immediately agrees is a "need" produces little discussion. A scenario that everyone immediately agrees is a "want" produces equally little. The most productive case studies are the ones where reasonable people disagree, or where the same person holds conflicting intuitions.

Selection criteria

Case studies are drawn from ordinary spending situations: food, housing, transport, clothing, entertainment, services. They involve real amounts of money, real constraints, and real competing priorities. They are not designed to be dramatic. The most useful scenarios are often mundane ones that turn out to be surprisingly complex when examined carefully.

How they're used in session

The case study is not a problem to be solved. It's a situation to be examined. The facilitator's role is to slow the examination down, to introduce questions that participants might not have thought to ask, and to surface the assumptions embedded in the initial reactions.

By the time a session closes, participants have usually moved from a quick initial categorization to a more nuanced understanding of what made the decision difficult. That movement is the output of the session.

Whiteboard showing a needs-wants decision framework diagram in a workshop environment

The methodology is designed to be used, not just understood. Every principle in it has a direct application in the session structure.

Clarifying the scope

What this methodology is not

Not financial advice

Winega webinars are educational. They examine spending decisions through a conceptual framework. They do not recommend specific financial actions, products, or strategies.

Not therapy

Sessions examine the structure of spending decisions. They are not designed to explore underlying psychological issues. Participants with specific concerns about financial anxiety or compulsive spending are encouraged to seek appropriate professional support.

Not a budgeting system

The framework does not produce a budget, a spending plan, or a savings target. It produces clarity about the nature of spending decisions. What participants do with that clarity is entirely their own business.

Not a moral framework

The methodology does not imply that needs are virtuous and wants are indulgent. It does not suggest that spending less is better than spending more. It examines the nature of spending decisions without attaching moral weight to the outcome.