The 3 W’s: A Simple Way to Solve Problems Smarter

The 3 W’s: A Simple Way to Solve Problems Smarter

In engineering, we’re constantly tackling problems. But sometimes, what looks like a simple request actually hides a bigger challenge. That’s why we rely on something we call the "3 W’s"—three questions that help us get to the heart of what’s really going on:

  1. What problem are we trying to solve?
  2. Whose problem are we trying to solve?
  3. When are we trying to solve it?

These questions aren’t just part of our design docs—they help us think deeper, dig into what’s really needed, and find the best solution.

A Real-World Example

Imagine this: an IT helpdesk ticket comes in saying, “Can we get an FTP server to upload files?” On the surface, it sounds straightforward, right? But when we ask the 3 W’s, we start seeing things differently.

  • What problem are we trying to solve? Is this really just about file transfers, or are there other issues like security or workflow bottlenecks we should be looking at? Is there further processing needed? Is this an external or internal system?
  • Whose problem are we trying to solve? Is this for one team, or could a better solution help others across the company? Is this for a partner?
  • When are we trying to solve it? Is this something we need ASAP, or is there a chance to think about longer-term needs and build something more robust? If you are trying to solve a problem "sometime in the next quarter" or "tomorrow" it will make a big difference on the thought process behind the problem solving.

Asking these questions helps us go beyond the basic request and uncover the bigger picture. Maybe instead of just setting up an FTP server, we find that we need a more secure, scalable solution that helps multiple teams down the line.

Why the 3 W’s Work

The 3 W’s aren’t just handy for solving technical problems—they bring everyone onto the same page. When we ask these questions, we make sure we’re all aligned on what we’re really trying to do, who’s involved, and how urgent it is.

It also helps us see patterns. When you keep asking the 3 W’s, you start to notice common problems or challenges that come up again and again. This can help us create solutions that aren’t just quick fixes but ones that actually move the needle for the entire organization.

How It All Started

Major credit goes to my colleague and friend, Jesse Myers. When we first started working together, the question “What problem are you trying to solve?” was already a huge part of the company culture, and it made a big impact on how I approached my work. It was a game-changer in my career.

Over time, after years of asking that one question, we realized that there was more nuance to be uncovered, especially in the fast-paced enterprise world. That’s how the other two W’s—Whose? and When?—came to life, adding more depth to every ask.

Next time we’re tackling a problem, let’s remember to ask: What? Whose? When? It’s a quick way to make sure we’re not just solving the problem in front of us—but solving the right problem, for the right people, at the right time.

要查看或添加评论,请登录

Avi Zurel的更多文章

  • Analyzing GMail (Gsuite) with Python and Google Sheets

    Analyzing GMail (Gsuite) with Python and Google Sheets

    Earlier this week, I published this tweet: I have a Gsuite account going back a few years for `kensodev.com`.

  • Our Ephemeral dev environments -driven by Slack

    Our Ephemeral dev environments -driven by Slack

    In one of my recent posts (https://www.linkedin.

  • Investing in multi-cloud

    Investing in multi-cloud

    One of the goals for us this year is to invest in multi-cloud deployments. There are multiple reasons for this, I…

    1 条评论
  • Note I shared internally after the Twitter hack

    Note I shared internally after the Twitter hack

    If you live on earth and are in tech, you know that Twitter was hacked via social engineering and access to internal…

    1 条评论
  • How we deploy to production

    How we deploy to production

    Yesterday, I was texting with a friend that asked me a question about the load on our ops team during COVID With remote…

    5 条评论
  • Managing a flexible cluster of micro-services - HOWTO in the wild

    Managing a flexible cluster of micro-services - HOWTO in the wild

    We've been managing flexible clusters of micro-services for quite some time now. Over the years, we've learned some…

  • Dishes and Laundry

    Dishes and Laundry

    I had a conversation today with one of my project managers. It made me think about this "dishes and laundry" term in…

    1 条评论
  • Adhesion

    Adhesion

    I recently gave a short talk in our engineering all-hands. I got a ton of responses, leading me to think that this…

  • Managing CI Configurations At Scale - Globality

    Managing CI Configurations At Scale - Globality

    Intro You often hear about scale issues when discussing capacity, traffic, users and other resource related topics and…

    3 条评论
  • Chat controlled RC car using a RaspberryPi

    Chat controlled RC car using a RaspberryPi

    I've been streaming myself coding on Twitch for the last couple of months. I wanted to build something really fun and…

    1 条评论

社区洞察

其他会员也浏览了