Make Hard Choices Easy to Understand

Clarify tradeoffs with one simple trick

Welcome back to Path to Staff! This week, we’re continuing our series on Mastering Communication. This post will cover how to communicate tradeoffs and simplify hard choices so everyone can understand.

---

Making a decision when there’s a fork in the road at work is hard. How do you choose a path to take when there’s so many tradeoffs? Even more so, how do you communicate your recommendation to those around you? And make it easy to understand?

Take an example: Your project can either launch today with several minor bugs, or you can ship it in a month and knock it down to two bugs, or ship it in three months completely bug-free. You already lean towards the middle option, because of reasons A, B, and C. But the question is: how do you reason this clearly on paper so others can understand it?

Here’s one simple technique: use a stoplight table.

Stoplight Table

This is how a good stoplight table looks like.

Stoplight table that captures multiple launch options (today, 1 month, 3 months)

Stoplight tables help you and your team reason decisions quickly. They do this by focusing discussion on concrete points.

Best of all, as decisions grow more complex, they force you to prioritize the key factors in your decision.

Let’s dive into how to construct one.

Step 1: Identify the key decision factors (rows)

First, start by identifying the factors that directly influence the decision. These become the rows of your stoplight table. Each factor should meaningfully differentiate options from each other.

It’s important to keep this list short. Limit yourself to six factors or fewer. This constraint forces clarity for both yourself and others.

In the example above, we’ve chosen four factors: UX Polish & Bugs, Engineering Capacity, Developer Reception, and Marketing.

Step 2: Order factors by importance

Once you’ve chosen the factors, order them by importance. TThis ordering establishes which tradeoffs carry the most weight and how readers should interpret the table.

Readers naturally focus on the top first, so placing the most important factors there provides immediate context. Lower-priority concerns still matter, but they should not overshadow the core drivers.

In our example, placing “UX Polish” above “Engineering Capacity” makes it clear that your customer is the ultimate priority. This should be the driving factor in your decision.

Step 3: Define clear, concrete options (columns)

The columns of the table represent the options under consideration. Each option should be concrete, distinct, and easy to understand without additional explanations.

Strong options describe real choices someone might advocate for, such as different launch timelines or implementation approaches. They should be mutually exclusive so readers can clearly compare outcomes.

If it feels like two options have a lot of overlap, revisit their definitions. You don’t want to confuse your readers with conflicting options.

Step 4: Apply stoplight colors

Your readers should be able to scan the table and immediately see where each option performs well or struggles. This is where you combine your reasoning with colors.

Use these three colors:

• Green for strong alignment

• Yellow for notable concerns

• Red for serious risk or blocking issues

I personally like to use these colors in Google Docs. They’re not too dark, and not too light either. And having three keeps the table simple and focused.

Pick these three colors (muted green, yellow, red). Skip the orange color.

Step 5: Maintain objectivity

To gain the trust of your readers, you need to make an objective recommendation within your stoplight table.

This means that you need to fairly assess and score each row (factor) based on your best judgment, not what your manager or other teams are telling you to do.

This applies even for preferred options, you have to honestly acknowledge the downsides.

For me, a good check is to imagine a skeptical reviewer reading the table. Try to criticize your own table and point out flaws in your reasoning. You should try to view your own argument from multiple angles.

Step 6: State your recommended option

At the very end of the table, explicitly state your recommendation. Tie the recommendation back to the highest-priority factors so readers can follow your reasoning. This also sets up a productive discussion.

Pick one option and set it as your recommendation

Leverage this recommendation to frame your entire discussion. I place the recommendation at the end so that readers don’t jump to your conclusion right away, and have enough mental space to think about how to arrive at their own conclusion.

TLDR:

That’s it. You now have a stoplight table that breaks a complex decision into clear, understandable tradeoffs. Stay tuned for the next part in this Mastering Communication series.

• Use stoplight tables to make tradeoffs visible

• Limit factors to what drives the decision

• Order factors by importance

• Score options with green, yellow, and red

• Be objective to build trust

• End with a clear recommendation