Starting a new role is never easy. There are a ton of ideas, new processes, people, and new technology to pick up. In addition, you may have also changed problem domains, which means you're having to learn about the problem we're trying to solve. That's a lot to take in, "drinking from the firehose", if you will. That being said, how do we control the flow? How do we optimize our learning to be effective in the short term and not need six months of ramp-up time?

In this session, I'm going to walk you through my playbook of starting a new role by exploring the four pillars of knowledge (product, people, process, and technology) and how they relate to each other. From there, we'll explore each of the pillars more in-depth, looking at what questions are urgent and important and which ones are just important. Finally, we'll wrap up on exploring timelines of what information you need to know by the end of your first week, your first sprint, first month, and first quarter.

Intended for engineers of all experience levels, you will have an example playbook that you can use when you start a new role by the end of this session.