From Great Individual Judgement to a Great Decision-Making Organization

June 2026

Matt Compton

At Oregon Venture Fund, one of the qualities we look for most in founders is good judgment. Specifically, the ability to make sound decisions with incomplete information. The best founders do this instinctively. They move fast, weigh tradeoffs quickly, and act with conviction even when the picture isn’t fully clear.

So, it’s striking how often those same founders, the ones with sharp personal judgment, struggle to translate that quality into how their company makes decisions. What works brilliantly for a founding team of three tends to quietly break down as the company scales from 10 to 50 to 200 people.

We recently had the opportunity to work with one of our portfolio companies, Source, on implementing a lightweight decision-making framework with their leadership team. The experience reinforced something we’ve observed across many of our investments: effective organizational decision-making is a distinct skill from personal judgment, and it requires intentional structure to develop.

Here are some of the key principles we think about when helping founders put the right amount of structure around decisions as their companies grow.

1. Personal judgment doesn’t automatically scale

A founder’s intuition is an asset precisely because it’s fast, context-rich, and doesn’t require explanation. But as a company grows, that same intuition applied from the top without a shared framework creates bottlenecks. Decisions pile up waiting for the founder. Teams slow down or stop moving without sign-off. And eventually, people start working around the founder instead of with them.

The goal isn’t to replace founder judgment. It’s to build an organization that can exercise good judgment even when the founder isn’t in the room.

2. Ambiguity is expensive - more expensive than most founders realize

Most companies underestimate the cost of unclear decision-making. It’s not just that decisions are slow. It’s that ambiguity creates lobbying, people spending energy trying to influence a decision rather than executing on it. Lobbying creates delays. Delays create rework. Rework consumes capacity that should be going toward the actual work.

At Source, we framed it this way in our workshop: the problem usually isn’t that decisions are hard. It’s that it’s not obvious who actually makes them. That distinction changes how you approach the fix.

3. Lightweight frameworks beat elaborate processes

There’s a real risk of overcorrecting and layering on process and structure until a company slows down for different reasons. The goal is the minimum viable structure that creates clarity without creating bureaucracy.

One framework that can be effective for scaling startups is DACI (originally developed at Intuit and well-documented by Atlassian), a simple model that assigns a clear role to every person involved in a decision:

• Driver: owns the process - gathers input, frames options, makes a recommendation, and manages the timeline. The Driver is typically not the decision-maker unless it is a smaller scale decision

• Approver: the single person with final authority. One person. One role. No committees.

• Contributors: people who provide expert input before the decision is made. Being a Contributor means shaping the decision, not just being notified about it.

• Informed: people who need to know the outcome so they can act on it. They receive the decision; they don’t make it.

The specific acronym doesn’t really matter as long as it’s memorable and contains for the four key roles: Driver or owner of the initiative or project, Approver/decider, Contributors of expertise and information, and people who need to be informed of the decision. The most common failure mode with DACI and in organizational decision-making generally, is confusing the Driver and the Approver, overcrowding the Contributor role, or skipping the Informed step entirely. Each of those missteps creates a different kind of dysfunction.

One important note: Many decisions do not need a framework approach. Every day internal calls, and routine operational choices don’t need this level of structure. Apply structure where stakes are higher, multiple functions are involved, or confusion about ownership is likely. A useful pre-filter before reaching for a structured decision framework is Jeff Bezos’s Type 1 / Type 2 framework, which asks simply whether a decision is a one-way door (consequential, hard to reverse = slow down and be deliberate) or a two-way door (reversible, lower stakes = decide fast and move). Most decisions are two-way doors and can be made quickly without much structure. For consequential decisions, DACI or something similar can be the right tool for a scaling startup.

4. One Approver. Always.

This is the discipline that matters most, and the one most companies resist.

The instinct in a growing company is to involve more people in decisions as a way of building buy-in or managing risk. In practice, decisions with multiple approvers are decisions that often don’t get made, or that get made inconsistently. When everyone is responsible, no one is.

The CEO had a simple rule in the Source workshop: every decision discussed had to have one Approver named before we left the room. If we couldn’t name one, that was the problem we were solving, not a sign that we needed more discussion.

5. Clarity relaxes teams

Here’s something counterintuitive: teams actually feel less anxious when decision rights are clear, even when that clarity means they have less authority than they thought.

When people are uncertain about who decides, they expend energy trying to be in every room. They hedge their own decisions. They escalate things they shouldn’t. Clarity cuts all of that. When someone knows their role is Contributor and not Approver on a given decision, they stop lobbying and start contributing. The quality of input goes up. The speed of the decision goes up. And people’s sense of trust in the process goes up.

6. Delegation is about the “deciding,” not just the “doing”

One of the frames that resonated most with the Source team was this: delegation is often thought of as distributing work. The harder and more important form of delegation is distributing decision authority.

As a company scales, a founder who delegates tasks but retains all major decisions is still a bottleneck. The more durable unlock is learning to delegate the deciding itself: to trust people with defined authority inside defined domains, and to build the feedback loops to catch and correct mistakes when they happen.

This is uncomfortable for most founders. It feels like a loss of control. In a meaningful way, it is. But it’s also the thing that allows a company to operate at scale without the founder being the constraint on its own growth.

7. The best decisions are often made furthest from the CEO

There’s a mental model shift that matters here. Most founders instinctively think of themselves at the top of a pyramid - information flows up, decisions flow down. But a more useful frame is to think of the CEO at the center of a set of concentric circles.

The people closest to the CEO at the center have the broadest organizational view. But the people at the outer edges (mid-level directors, individual contributors, the team members closest to the customer, the vendor, or the technical problem) often have the richest, most specific information about a given decision. The best decision-maker for any particular call isn’t necessarily the most senior person in the room. It’s the person with the fullest picture of what that decision actually involves.

Structuring decision rights around information proximity, rather than hierarchy, leads to faster and often better outcomes. It also changes how a company thinks about its individual contributors - not as executors of decisions made above them, but as genuine owners of the calls within their domain.

8. Learn to reject the ask to decide

One of the clearest signals a leader can send that they are serious about delegating decision authority, not just delegating work is to actively turn down requests to make decisions that belong to someone else.

This happens constantly in scaling companies. Someone drafts a decision, completes the analysis, and then escalates it upward for “approval”, not because they lack the authority, but because escalating feels safer. A leader who reflexively makes the decision in those moments is quietly training the team that all meaningful decisions still flow through them.

The more powerful response is to reject the decision request. “Person X has the context, the relationships, and the authority here. This is their decision.” That’s the moment the delegation becomes real.

This doesn’t mean the leader disappears from the decision. They may still want to be a Contributor and weigh in on constraints, flag considerations the team might not see, or offer their perspective when asked. But there’s a meaningful difference between being a Contributor to a decision and being its Approver. Leaders who want to scale need to get comfortable empowering others to make decisions.

The bottom line

Founders with great judgment have a real advantage, but that advantage doesn’t automatically transfer to the companies they build. The translation requires intentionality: clear frameworks, defined roles, and the discipline to name one person who ultimately decides.

The good news is that you don’t need much structure to get a lot of benefits. Start with a lightweight tool like DACI, apply it to the decisions that are substantive and where ambiguity is currently costing you the most, and build from there. The right amount of structure is probably less than you’d expect, and the payoff shows up faster than most founders anticipate.