When Tasked with a Problem, Start with the Bigger Picture

When faced with a challenge, I always step back to see the whole picture first. It's like pausing a complex strategy game to study the map. You might lose a few seconds of play time, but you gain a crucial understanding of the battlefield.

Trevor I. Lasn Trevor I. Lasn
· 3 min read
Building 0xinsider.com — see who's winning across prediction markets (Polymarket, Kalshi, and more) — and what they're trading right now.

It’s tempting to jump straight into action when a problem lands on your desk. But I’ve learned that taking a step back to see the big picture isn’t just helpful—it’s essential.

When faced with a challenge, I always start by zooming out. It’s not about delaying action, it’s about understanding the terrain before we start our journey.

The Power of ‘Why’

This three-letter word is more potent than any line of code I’ve ever written. Here’s why:

What seems urgent at first glance might not be that important in the grand scheme. I once had a CEO insist we needed to rewrite our entire codebase in a trendy new language. When we dug into the ‘why,’ we realized our actual pain point was slow feature development.

We initially thought we needed to rewrite our entire payment processing system to handle increased transaction volume. But by asking “why,” we realized the real issue was database bottlenecks. We ended up optimizing our database queries and implementing caching, which boosted our capacity by 300% at a fraction of the time and cost of a full rewrite.

Understanding the “why” behind a project can ignite passion and drive in a team. I witnessed this firsthand during a hackathon where our devs were tackling a problem for a local non-profit. Once they grasped how their code could directly improve lives, the energy shifted dramatically. They weren’t just writing algorithms; they were creating real-world impact. Without any prodding from me, the team voluntarily pulled an all-nighter, fueled by the knowledge that every line of code mattered.

This shared sense of purpose became our secret weapon, transforming a routine coding sprint into a mission that the team poured their hearts into.

A seemingly small fix might actually be the key to unlocking a major company initiative. By understanding the ‘why,’ you might realize that refactoring that old authentication system isn’t just technical debt—it’s the blocker for a huge partnership deal.

When a problem lands on your desk, fight the impulse to jump straight in. Instead, pause for a moment. Step back and look at the whole landscape. Then ask yourself, “Why are we doing this?”


Trevor I. Lasn

Building 0xinsider.com — see who's winning across prediction markets (Polymarket, Kalshi, and more) — and what they're trading right now. Product engineer based in Tartu, Estonia, building and shipping for over a decade.


Found this article helpful? You might enjoy my free newsletter. I share dev tips and insights to help you grow your coding skills and advance your tech career.


Related Articles

Check out these related articles that might be useful for you. They cover similar topics and provide additional insights.

Reflections
2 min read

Don't bullshit

Be the authentic voice in a world of manufactured personas

Feb 12, 2025
Read article
Reflections
3 min read

Code Wins Arguments

How Meta and other companies use the 'code wins arguments' mindset to turn ideas into reality

Sep 19, 2024
Read article
Reflections
4 min read

It's More Fun to Be Competent

Once you're competent, everything changes. You stop second-guessing yourself. You stop panicking every time you encounter a new problem. And you start taking on bigger challenges with excitement rather than dread.

Sep 20, 2024
Read article
Reflections
4 min read

Unrealistic Deadlines In Software Engineering

Unrealistic deadlines are more than just stressful—they set engineers up for failure

Sep 7, 2024
Read article
Reflections
4 min read

Prediction Markets Broke My Brain About Probability

A year of watching people bet real money on outcomes changed how I think about everything.

Feb 27, 2026
Read article
Reflections
6 min read

The Monday Morning Test to Measure Engineering Team Health

Why the first day back can reveal everything about your engineering team's health

Nov 4, 2024
Read article
Reflections
6 min read

Software Engineer Titles Have (Almost) Lost All Their Meaning

Examining the Devaluation of Software Engineer Titles and Its Impact on Tech Industry Integrity

Oct 20, 2024
Read article
Reflections
4 min read

Make It Work First Before Optimizing

Users don't care how elegant your code is. They care if it solves their problem.

Sep 27, 2024
Read article
Reflections
5 min read

Outdated Docs Are Tech Debt

Teams often neglect to create good documentation. Code gets delivered, but updating the docs is treated as a secondary task, easily postponed—until it’s too late.

Sep 22, 2024
Read article

This article was originally published on https://www.trevorlasn.com/blog/start-with-the-bigger-picture. It was written by a human and polished using grammar tools for clarity.