Here are some tips I would give, as an individual contributor: * Minimize the number of simultaneous projects. Having more on your plate than you can imagine g

Here are some tips I would give, as an individual contributor: * Minimize the number of simultaneous projects. Having more on your plate than you can imagine getting done is a huge cause of stress and burnout. * Avoid switching priorities frequently. Shield the team from too many external requests. * Avoid making "small" requests (e.g. a random data pull). Handling your request is probably not as small an amount of work as you think. This is especially a problem when for people with a lot of meetings - they may not have that many hours left in the day for their "real" work, and your "small" request might take up all those hours for today (which is really stressful when you badly needed those hours for something else!). * Avoid interrupting developers / making them feel like you could demand something at any time. * Clarify priorities, and don't bug people about lower priority things. * Don't schedule too many meetings. Developers work on a Maker's schedule, and ideally would have at least half of each day completely free of meetings. Meetings are more draining for ICs than they are for you. * Don't argue with time estimates given by developers. (Though looking for ways to reduce the scope of a project is valid) * Give developers time to pay down tech debt. * Listen to and act on issues people raise. * Let people know what is going to happen well in advance. Give people time to gear up for changes. Don't make people feel like things could suddenly change at any time with no warning.