Ever nodded along to a proposal, only to realize later it didn't make sense? Or have you agreed to a solution that only attacked the symptoms but not the underlying problem?
Sometimes, in the moment, we fail to think critically and just agree to things that seem right superficially. I feel bad when that happens to me and worse when others find faults that I missed đ. Jokes aside, critical thinking is a disciplined approach to reasoning that anyone can learn. It simply requires diligence and practice.
Today, I am sharing steps that help me think critically most of the time.
WorkOS: start selling to enterprises with a few lines of code (Sponsor)
WorkOS is a modern identity platform for B2B SaaS. It provides flexible and easy-to-use APIs to ship user management, SSO, SCIM provisioning, and fine-grained authorization in minutes instead of months.
WorkOS powers some of the world's hottest startups, including Perplexity, Vercel, and Webflow.
To keep the article focused, I am sharing tips on thinking critically when a coworker shares a proposal (to add rate limiting to your service). However, the tips can also be used in other contexts.
đ§Â 1. Understand What is Being Proposed
First things first: get crystal clear on what the problem and the suggestion are.
Here's how:
Grasp the elevator pitch: What's the TL;DR version?
Uplevel, but get specific: Prefer using an example to validate your understanding.
Example:
â "We're adding rate limiting to protect the service."
This is too vague and doesnât help you think critically. Letâs look at a better version:
â "The service gets overloaded (CPU/memory/other metrics) by a few clients, affecting others. We propose adding rate limiting to address this."
In this refined version, you know
who is causing the issue (specific clients),
what is being affected (service performance), and
how the proposal aims to solve the problem (rate limiting).
This clarity helps you focus your critical thinking on the right aspects.
đľď¸ââď¸Â 2. Whatâs the REAL problem?
Donât take the problem at face value, even if it comes from someone you trust. Validate the issue by digging deeper into the data and the backing evidence.
For example, if the proposal suggests that the service is overloaded, you should understand:
Is the overload system-wide or isolated?
What do the metrics say? Is there a direct relationship between the rise in traffic and the overload?
Is the overload proportional to the increase in load, or do we see a very high overload with a marginal increase in traffic?
Example:
The overload issue only appears with a subset of customers using a particular feature. This may suggest that the problem isnât a general overload but a bottleneck specific to that feature. So, optimizing the feature might be a better solution than rate limiting.
Asking these questions helps you distinguish between the symptoms (overload) and the underlying causes.
đ¤Â 3. SO WHAT?
Once you validate the problem, itâs time to quantify the impact by asking, "So what?" This helps you prioritize the issue and understand its business implications.
Example:
If the proposal says, âWhen client A overloads the service, it affects other customers,â keep digging deeper by asking, âSo what?â
Many customers saw their requests fail. So what
Some key customers suffered huge revenue losses. So what
They will take their business elsewhere if this keeps happening. (Of course, this one was obvious đ)
By asking, "So what," you might discover subtle nuances: Some customers are affected more than others.
This helps you decide if: The problem is big enough to need the suggested solution.
đ 4. Does the Proposal Actually Solve it?
Now that you understand the depth of the problem statement, itâs time to evaluate whether the proposal solves all of those problems.
Ask yourself:
Does this address the root cause or just the symptoms?
For example, rate limiting isn't enough if you find inefficiencies in the service. The proposal also needs to make the service efficient.
Are there any unintended consequences?
For example, if the proposal builds a simple global throttling, it could result in starving high-priority requests from customers that send less traffic.
Is this a long-term solution or a quick fix?
For example, maybe the proposal intends to add rate limiting as a short-term fix, and in the long term, it also makes sense to partition the service for better isolation.
This step is about vetting the proposalâs effectiveness. You ensure itâs not just a band-aid but a comprehensive solution that addresses the immediate problem and potential long-term implications.
đ 5. Play Devilâs Advocate
Even if the proposal looks solid, itâs crucial to challenge your thinking and assumptions. Playing devilâs advocate pushes you to identify risks, weaknesses, and potential failures, ensuring that no blind spots remain.
Challenge your thinking even when the proposal looks sane. Think about:
What could go wrong? Consider scenarios where this proposal might fail. Are there edge cases that could break the solution?
What if this solution backfires? Think about worst-case scenarios. Could the fix introduce new problems, like performance bottlenecks or customer dissatisfaction?
Are there hidden costs? Could this proposal introduce technical debt, maintenance overhead, or unforeseen negative impacts on users?
Am I being swayed by biases? Are you too trusting of this proposal because of the presenterâs credibility, or does it align too easily with your existing beliefs?
For example, if youâve advocated rate limiting for a while, you might overlook other solutions, such as optimizing the service or partitioning traffic.
The goal is to test your reasoning and uncover any blind spots or biases. By challenging the proposal from multiple angles, you can ensure youâve considered all potential risks and havenât overlooked any critical details.
đŞÂ Parting Note
Think of critical thinking as strength training. Just as you donât build muscle overnight, sharpening your critical thinking takes time and consistent effort. The more you use this framework, the stronger your decision-making skills become. So keep practicing.
You will miss things along the way, and thatâs okay. The key is to identify what you missed using the steps above and improve next time.
If you enjoyed this article, then hit the â¤ď¸ button. It helps!
If you think someone else will benefit from this, then make sure to đ share this post.
Great piece on Critical Thinking, Raviraj!
I'd add that when faced with difficult and impactful decisions, it is really important to play devil's advocate, as you described.
Additionally, involving a trusted friend to review our assumptions can be valuable â it's important to understand others' perspectives, similar to what we do with code reviews.
I have been searching Google, chatGpt for ways to improve strategic/critical thinking. Didn't find what I was looking for. Thank you for this excellent framework. I will keep coming back to this piece. (I got here from Steve Huynh's LinkedIn post)