ENEste artigo encontra-se publicado em inglês.
• 11 min read •By Tiago Marques

The Thinking Trap

Recently, I wrote a cost analysis for a data platform migration. The original proposal moved compute from one cloud paradigm to another. My counter-proposal scaled the existing solution vertically instead. The original had a 33-year payback period. Mine would have cut costs dramatically. Nobody asked me to do the analysis. I did it to reason through the problem and prove a point to myself. The math seemed correct. The architectural conclusion was wrong.

I couldn’t see the event-driven microservices context that made the proposed architecture sound. My reasoning was sound. The information I had was incomplete.

I should have talked to the architect before doing any analysis. That’s on me. Sometimes you just want to challenge yourself and see how far you can get. But the deeper questions stuck with me: at what point do you start thinking at the wrong level, expanding into other people’s territory? When are you stepping outside your lane? Will it bite you later?

I like to think at the “why” level. Architecture, strategy, trade-offs, system design. But currently, I’m positioned at the “how” level. Implementation, tickets, sprints, pull requests. This isn’t just a personal failing. It’s a structural misalignment that affects every senior individual contributor (IC) whose natural mode is architectural thinking.

I call it the Thinking Trap.

The Four Misalignments

I’ve identified four misalignments that create structural frustration.

1. Thinking vs. Information Access

You’re expected to reason about systems you don’t have full visibility into, or haven’t come across yet.

You see patterns. You ask questions. You draw conclusions. But the conclusions are only as good as the data you have access to. A senior engineer isn’t always invited to the rooms where long-term strategy is mapped out. When you opine without that context, you’re reasoning from partial data. Sometimes the data you need lies in plain sight. Tribal knowledge that gives you important cues. Blind spots exist everywhere, at every level.

Learning to navigate an organization for context is itself a skill, one I’m still developing. It’s not just about hunting down documents. It’s about building relationships so that people proactively share context with you. Treating that friction as an excuse for producing a flawed analysis is a trap of its own. When you’re wrong because of missing data, it looks like overstepping. When you’re right, it looks like you got lucky.

If you’re asked to think critically about a system, produce a decision record, and take ownership of the outcome, you need this skill sharpened. The stakeholders who read your document won’t care about your skill issues.

If you’re doing it for your own learning, asking “what if I were the one designing this system?”, take the opportunity to sharpen your ability to find context, observe how the process flows in real life, and do a postmortem after the fact. Compare the solutions. Learn from the outcomes.

2. Thinking vs. Output Capacity

Architectural thinking produces insights, decision records, and strategic recommendations. But your role is primarily measured in PRs, story points, and delivered features.

The thing you’re trying to get better at isn’t what you’re explicitly evaluated on. Your performance review rarely has a line item for “produced an Architecture Decision Record (ADR) that prevented a six-figure mistake.” It has a line item for “delivered X features on time.”

If I can’t explain why a decision record mattered in terms my manager or the business cares about, that’s my failure, not the review system’s. The tension is real. Architectural work doesn’t fit neatly into sprint metrics. But the responsibility to translate its value into business outcomes is just as real. Otherwise, you feel like you’re doing two jobs: the “how” job you’re paid for, and the invisible “why” job you can’t stop doing. You may also start feeling impostor syndrome.

Doing invisible work carries a heavy context-switching cost. It takes a toll on your mental energy and decision quality. The secret is calibration. Don’t underdeliver, don’t overpromise. Keep commitments. Learn and experiment only when you have enough time.

Sometimes “stay in your lane” is code for “you haven’t delivered enough trust yet to earn a voice in this conversation.” Other times it’s genuine structural rigidity. Learning to tell the difference is part of the growth. And the only reliable way to earn that trust is to execute flawlessly at your current scope first.

3. The Idea Graveyard

I’ve contributed to multiple “idea graveyards.” Those backlog buckets where proposals go to wait for later refinement and discussion. Confluence pages, JIRA tickets, MkDocs repositories. I’ve done them all. I generated prototypes, worked on them in great detail, only to watch them be completely ignored. I thought the content would speak for itself. I thought people would recognize the necessity of what I’d written with such care. And because most people in teams don’t step out of their comfort zone, I’d gladly share my thoughts just to avoid keeping the room silent.

In reality, I probably think I’m smarter than I really am. Coupled with occasional team dynamics, this led to a distorted view of myself as the only person capable of solving all the problems.

My biggest recurring mistake was letting ideas sit and rot instead of actively discussing them. One at a time, aligned with what the team, the manager, or the stakeholders already consider the next priority. Reading the room is a skill. Humans are political. Pre-wire the key people before the meeting. Frame the proposal in terms the decision-maker cares about — cost for the CFO, risk for the CTO, velocity for the VP of Engineering. Producing too much, too fast is just noise. It wastes time and energy.

4. Thinking vs. Career Trajectory

The skills that make you valuable at the “how” level are not the exact skills that get you promoted to the “why” level.

Speed, volume, reliability. Those get you to senior. Judgment, systemic influence, and architectural vision. Those get you beyond it. You have to demonstrate competence at a level you’re not yet positioned to operate at, while still delivering at your current level. It’s the career equivalent of needing experience to get the job, but needing the job to get experience.

Doing this from the “how” position means doing it without structural authority. It’s the hardest possible way to build the evidence you need for promotion, which is why thinking strategically about your career path matters early, not after two years of friction.

I’ve produced Architecture Decision Records on FinOps, compliance, and ingestion architecture. All Staff-level artifacts, all from a Senior role. None of them moved the needle on my title. They built the case, but the case lives in documents, not in how the organization sees me. That’s the trap: the evidence is real, but it’s invisible unless you actively surface it. And surfacing it takes time; titles move on years, not documents.

Recognizing Which One Has You

Not all four hit at once. At any given moment, one is the primary source of frustration. The first step is diagnosing which one.

If you’re drawing conclusions but feel unsure because you know you’re missing context, it’s Information Access. Ask for architectural briefings. Request access to upstream design docs. Frame it directly: “I want to make better implementation decisions today so we don’t rewrite this tomorrow.”

If you’re producing analyses but feeling invisible, it’s Output Capacity. Don’t let your architectural work stay in a private scratchpad. Share design docs with your tech lead and engineering manager. Quantify the risk mitigated. Build the paper trail.

If you’re generating proposals that vanish into a backlog never to be seen again, it’s the Idea Graveyard. Stop producing in bulk. Pick one idea, discuss it actively, and align it with what the team or stakeholders already care about. Reading the room matters more than writing the perfect document.

If you’re doing the work but not getting the title, it’s Career Trajectory. Build an internal evidence portfolio. Document the decisions you influenced, the mentorship you provided, and the architectural landmines you helped the team avoid.

What to Do About It

If you recognize yourself in this pattern, these six principles are crucial:

Master your current scope first. None of this matters if you’re dropping tickets. An architect who can’t ship is just a commentator. The fastest way to earn a seat at the architectural table is to be so ruthlessly reliable at the “how” level that people actively want your brain on harder problems.

Make the invisible visible. Every analysis, every design doc, every governance assessment. Document it, share it, and include it in your evidence file. The “why” work you are doing out of necessity is your promotion case. Tie it directly to team velocity or cost savings.

Talk to your manager. Frequently. Don’t assume they see the invisible work. Don’t assume they know you want to grow toward architecture. Have the explicit conversation. Ask what the bar looks like for the next level and where you stand against it. And when you’re unsure whether your “why” work is valued or seen as a distraction, ask directly: do you want me to keep doing this, or is it against what you want from my role and expertise? Clarity is cheaper than resentment.

If your manager can’t or won’t have this conversation, find someone who will. A skip-level leader, a mentor in another team, a senior architect who’s walked the path. Career growth shouldn’t depend on a single relationship. Build a small circle of people who see your work and can advocate for it.

Build external clarity in parallel. Write articles and give talks, but do it to clarify your own thinking. If that builds a reputation outside your company, it’s a valuable side effect, not the primary goal. Your promotion case must live on internal impact; external writing simply helps you articulate that impact more clearly.

Champion one idea at a time. The Idea Graveyard fills up when you produce faster than you advocate. Pick one proposal. Discuss it actively. Align it with what the team or stakeholders already care about. A single idea that ships is worth more than ten that sit in a backlog forever.

Pay attention as the years go by. I’ve watched this pattern play out across multiple organizations. Early on, the friction is motivating — you’re learning, producing, proving yourself. As time passes, the same friction can become draining. The analyses get harder to produce without the right context. The stakeholder tension compounds. The career trajectory stalls. There’s no fixed deadline, but there is a point where the cost of staying starts to outweigh the cost of leaving. Don’t set it in stone. Just check in with yourself honestly, year by year. Is the gap closing, or is it widening?

For Managers Reading This

If you manage a senior IC who thinks like this, the cheapest retention move you can make is simple: give them access to the architectural picture.

Not a promotion. Not an immediate title change. Just the information.

Invite them to the design reviews. Share the long-term roadmap. Let them see the full context. The cost to you is zero. The alternative is losing a high-performer who is already doing Staff-level thinking on a Senior-level salary. They will eventually notice the disparity.

What This Costs the Organization

The Thinking Trap isn’t just a career problem for individuals. It’s a quiet tax on the business.

When senior ICs can’t access the architectural picture, decisions get made without their input. The same mistakes repeat. The same shortcuts accumulate. The same technical debt compounds. The people who could have flagged it early weren’t in the room.

When their “why” work goes unrecognized, they stop producing it. Not because they stop caring, but because the system trained them that it doesn’t count. The ADRs dry up. The FinOps analyses stop. The governance assessments disappear. The organization loses a layer of strategic thinking it never knew it had.

When they burn out and leave, the cost is concrete: recruitment, onboarding, lost context, delayed projects. But the deeper cost is the signal it sends to everyone who stays. Strategic thinking isn’t rewarded here. Stay in your lane. Keep your head down. That’s how organizations that were once fast become slow.

The cheapest fix is the one already described: give them access. The second cheapest is recognizing the work they’re already doing. Both cost nothing. Both prevent a loss that’s expensive to replace.

Closing the Gap

I am highly aware this perspective can risk sounding entitled. Like the classic “the organization doesn’t recognize my genius” complaint.

Much of this frustration is self-inflicted. It comes from a communication gap we, as engineers, have to learn to close. It requires learning the business metrics that matter and earning the political capital required to influence systems larger than our immediate sprint.

But some of the friction is structural.

Companies frequently hire senior engineers for their judgment and experience, then position them in execution frameworks that isolate them from the context needed to apply that judgment effectively. The result is a quiet pipeline of burned-out senior talent. Naming this pattern isn’t about demanding a free pass to the strategy table; it’s about figuring out whether the friction you feel today is a gap in your own execution, or a structural boundary you need to learn to break through.