The document discusses management without authority and provides tips for leading effectively without a formal leadership title. It suggests building relationships, earning trust through domain expertise, rolling up your sleeves to help, communicating frequently, and focusing on incremental improvements rather than trying to change too many things at once. The document also lists sources of unofficial power for managers like networks, communication skills, and helping remove obstacles.

1. Management without
Authority
Why you should practice it as a leader
Valeriy Zamarayev

2. How do I even approach these
Senior Software Engineers?

3. People management
with junior Engineers?

4. Cross Functional
Projects?

5. Horizontal
Projects?

6. Decision Making

7. How?

8. Does the team need you?

9. Sources of (unofficial) Power
❏ Network and relationships
❏ Domain expertise
❏ Communication
❏ Taking responsibility
❏ Process
❏ Metrics and Data Analysis
❏ Strategy
❏ Project initiation / closure
❏ Planning
❏ Status
❏ Removing obstacles, facilitating
❏ Helping manage up

10. DO
❏ Build relationship
❏ Earn trust
❏ Develop expertize
❏ Roll up the sleeve

11. DON’T
❏ Be afraid to ask questions
❏ Use project management jargon
❏ Expect to find the “One True Way”
❏ Try to boil the ocean, chane too many
things at one.

12. Over-Communicate