I&#x27;ve been a Tech Lead for a year now. I&#x27;m still learning but some of the things I&#x27;ve done which I think will help are:<p>1. Start by setting up the development environment and getting the software you&#x27;ll be working on to run locally. Then, fix a couple of easy to medium level bug fixes as soon as possible. This is the fastest way to learn what your team is talking about.<p>1.5 If you don&#x27;t understand something that&#x27;s being said at a meeting ask, but don&#x27;t hijack the meeting, make a note and talk to someone who can explain in more detail.<p>2. Think at a high-level -- what is the product supposed to be doing, abstract away -- some engineers will talk in code -- which you may not understand early on but interpret what they&#x27;re saying at a high-level.<p>4. Be available and approachable to everyone on the team.<p>5. Understand the impact of a bug fix or a feature -- how much QA effort does it require, what is the operational impact of the work, does it break backward compatibility etc.<p>6. Participate in product meetings and consider designing any new features as homework so you can better discuss it with the engineering team  you&#x27;re leading.<p>Good luck!<p><i>Edit</i><p>Some DO NOTs:<p>1. Do not complain how bad the code base is. No one likes someone new walking in and saying that at once.<p>2. That said, understand what technical debt there is and address it incrementally. Don&#x27;t say &quot;we should re-write XYZ.&quot;<p>3. Do not suggest alternate platforms and frameworks unless is absolutely makes sense -- this is especially true if the team is big and no one knows this new framework besides you. You need your existing team to contribute to and maintain projects.