Tech Leader’s Advice: Why Goal Focus Beats Chasing Distractions

Ten years ago the author moved from a senior engineer to a team lead and, on his first cross‑department project, spent a week tangled in product changes, low‑quality bugs, delayed designs, and administrative mishaps. After the project missed its deadline, the boss asked, "What is your goal?" This forced the author to realize that chasing minor irritations—what he calls "the rabbit"—diverts attention from the real objective.

What "the rabbit" means

The phrase "the general on the road does not chase rabbits" was heard from an older leader during a project post‑mortem. "Rabbit" refers to any issue that makes you angry or forces you to prove yourself but does not help achieve the goal, such as a demanding product manager, a colleague’s coding style, or an unnecessary meeting.

Goal vs. rabbit comparison

Typical goals include delivering a project on time, improving team capability, earning a promotion, winning a difficult client, or completing a technical roadmap. Corresponding "rabbits" are unrelated complaints, personal disagreements, or minor obstacles that consume time and emotion without advancing the goal.

Case studies

Case 1 – The nit‑picking senior

A technically excellent senior engineer constantly criticized product managers, low test coverage, and even interns’ variable names. Five years later he remained a senior developer while peers advanced to architects or tech leads, because nobody wanted to work with someone who always chased rabbits.

Case 2 – Winning the argument, losing the goal

During a core system refactor, the author spent two days blaming another team for a slow interface, while the three‑day fix could have been used to implement a fallback cache or async degradation that would have kept the project on schedule. He won the argument but missed the goal.

Goal‑oriented work process

Step 1: Write down the goal. Not just in mind—post a one‑line target on the monitor, e.g., "This week: finish order‑module refactor, deploy to pre‑prod, zero P0 bugs."

Step 2: Filter every interruption. Ask, "Is this related to my goal?" If a product change helps the goal, accept it; if it’s a random request, decline without argument. Apply the same question to uncooperative colleagues or skeptical stakeholders, acting only if the issue threatens the goal.

Step 3: Daily review before sleep. Ask three questions: (1) Which task today was closest to the goal? (2) Which rabbit consumed my time and how much? (3) How can I avoid that rabbit tomorrow?

Distinguishing rabbits from tigers

"Tiger" denotes a critical obstacle that directly blocks the goal—key technical blockers, toxic team members, or compliance issues. If it’s a tiger, act decisively and resolve it immediately. If it’s a rabbit, acknowledge it briefly and keep moving. Misidentifying tigers as rabbits (avoiding problems) or rabbits as tigers (overreacting) is the biggest pitfall.

Team habit

Each Monday, the author asks every team member to state their weekly goal in one sentence, focusing on the desired outcome rather than a to‑do list, e.g., "Get the login module through security review with zero vulnerabilities" or "Secure two development slots through cross‑department coordination." Clear goals leave no room for rabbits.

Conclusion

The author believes the gap between people is not intelligence or technical skill but the sense of goal. Strong goal orientation keeps the "general" moving forward, while weak orientation lets rabbits distract and derail progress.