Hey — I offer hands-on AI coaching for dev teams. I spend a day or two pairing with your engineers in your codebase, teaching them Cursor, Claude, Copilot, and the workflows that actually stick. No slides, no theory — just real work on real code. Your team leaves confident and shipping faster. Let's chat
Published
3 min read

Trevor I. Lasn

Builder, founder, based in Tartu, Estonia. Been coding for over a decade, led engineering teams, writing since 2015.

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.

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?”


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.


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

Reflections
6 min read

High Performing Engineer Teams = motivation + enthusiasm + autonomy

Create the conditions where engineers want to excel and they'll surpass your expectations

Mar 7, 2025
Read article
Reflections
4 min read

A Great Product Doesn't Need Marketing

Great products speak for themselves, without the need for massive marketing campaigns

Sep 18, 2024
Read article
Reflections
7 min read

Can Scrum Be Salvaged?

Scrum is failing engineering teams and what it's actually costing us

Nov 14, 2024
Read article
Reflections
4 min read

Build Your Army

If you want to do great things, you'll need people with skills that complement yours. You can't do everything yourself. You need a team. You need an army. You need to build your army.

Oct 4, 2024
Read article
Reflections
4 min read

Users Can Be Fired

Letting go of difficult or harmful users can be the key to maintaining the health and growth of your product

Sep 19, 2024
Read article
Reflections
4 min read

Why I Value Firebreak Sprints for Managing Technical Debt

How scheduled developer freedom weeks can revolutionize your codebase and team morale

Apr 8, 2025
Read article
Reflections
3 min read

Take Your Writing Seriously

It’s not just about getting the message across; it’s about doing so in a way that’s easy for others to follow. Good writing shows respect for your team and your work.

Sep 19, 2024
Read article
Reflections
5 min read

Attracting Top Engineering Talent to Your Startup

Advice on competing for great software engineers without name recognition

Sep 21, 2024
Read article
Reflections
3 min read

The 5:1 Rule: Effective Performance Reviews For High-Performing Teams

Research reveals the ideal ratio of positive to negative feedback within high performing teams

Mar 20, 2025
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.