[[Notes]] - Topics: [[Teamwork]], [[Productivity]] - People: Eric Kimberling - Source: https://www.youtube.com/watch?v=E2TloG0LR8I --- ## Summary - Have strong communication and leadership skills above all else. Followed by having strong business process and operational understanding, then technical expertise. - [[We manage people, not things]]. - [[Technology is a marvellous potential, but we are the ones that give it meaning]]. - [[A vision without resonance is one that will be forgotten]]. - [[Project management is change management]]. - [[You cannot stop change. You can only manage your perception of it.]] - [[You don't need to be the best at everything, but it helps to be good at a lot of things.]] ## Notes - There are more skills and competencies needed beyond technical expertise and experience via context. - **Technical knowledge**. Don't just look at the technical solution, but also look at the solution architecture. How does it all tie together? - Understand secondary factors beyond the technical implementation, such as database insecurity. - In other words, have a good understanding of the solution both in [[Depth]] and in [[Breadth]]. Technical expertise is important, but it's probably the least important amongst the key skill sets. - [[We manage people, not things]]. - [[Technology is a marvellous potential, but we are the ones that give it meaning]]. - Business Process and operational understanding. The ability to dive into, understand, and adapt to how business functions work (at different parts of the business). - Understand the many flavours of the collective [[Philosophy of work]]. To be effective is to adapt it as if it was your own. - [[To change a philosophy of work, you must first understand it]]. - [[Meet them where they're at]]. Live it. It is only then that you can meaningfully steer it. - Understand people over software. Understand people over things. [[Understand how the business works to discover how the business could work better]]. - [[Manage the top line your strategy, your people, and your products and the bottom line will follow]]. - [[Don't be afraid to give up the good to go for the great]]. - [[People don't buy goods and services. They buy relations, stories, and magic.]] - Know the numbers - even for that which are unmeasurable. Have a good feel for strengths and weaknesses in order to support the project as it moves forward. - **Have strong communication and leadership**. This is the most important skill set. - Understand the needs and effective communication styles of those involved, and be proactive in communicating vision and updates. - Take ownership over a project. Lead. - It's not enough to have a vision. You must effectively communicate it. - [[A vision without resonance is one that will be forgotten]]. - [[Technology is easy. People is hard.]] - The better you are at leadership and communication, the stronger and more effective you're going to be. - **Experience with broad change transformation**. - Project management is change management. - To manage change, or rather to manage your perception of change, is to manage people. - Change happens. [[You cannot stop change. You can only manage your perception of it.]] - [[It is not a problem to solve. It is a process to manage.]] - To be a good project manager, you need a wide variety of skill sets. - [[You don't need to be the best at everything, but it helps to be good at a lot of things.]] ## Original ![[What makes a good project manager?-1.jpg]] ![[What makes a good project manager?-2.jpg]] ![[What makes a good project manager?-3.jpg]]