When you join a new organization, it is quite natural to feel a strong urge to fix things. Let me ruffle some feathers here…

You will notice processes, tools, or practices that feel inefficient, outdated, or even wrong. Maybe the team uses Jira instead of Linear, Java instead of Go, MongoDB instead of MySQL (for a use case), or Tabs instead of Spaces. It will be tempting to point it all out immediately. Resist that urge.

Do not get overwhelmed by outrage. Every organization has quirks, and yours is no exception.

Complaining loudly in your early days won’t make people rally behind you. You may be right, but what you lack is context. What looks foolish from the outside might have made perfect sense at the time.

So, start by asking why. Be curious. Ask questions, and listen closely. The more context you gather, the clearer the rationale will become.

At first, focus on integrating rather than fixing. Show reliability, do good work, and build relationships. Once you have established credibility, you’ll find that people are more open to your perspective. That’s when you can choose your battles carefully.

Keep this simple framework in mind:

• Ask why before suggesting what
• Listen more than you speak
• Build trust before pushing change
• Pick one thing, not everything

Prove your ideas with small wins, and show that you understand the context. Over time, you will gain the influence to bring major changes and improvements.

You can’t fix everything on day one, but you can ruin trust in one.