Please login or join to subscribe to this thread
In my opinion, leveraging the best user experience and the "value" add to customers would favor you more than the technical skill. (although technical skill helps piece it all together)
Having a deeper understanding of the customer/users pain points and articulating the problem you're trying to solve would be beneficial, then, developers/architects/solution designers etc. can figure out the technical solution.
Would suggest a few options to explore in parallel:
1. Find someone who IS a SME in these and see if they are willing to have a few lunches or coffee meetings with you to fill in some of the gaps
2. Self-study during evenings and weekends using online resources or even a course - your company may be willing to subsidize that
3. Speak to other PMs who are managing similar projects, ideally in your company, but if not, in your local area. They would be able to help you understand the domain through a PM lens.
I espouse an approach called “Architectural Awareness,” which is an approach for navigating domains through architectural knowledge; that is, non-engineering big-picture knowledge that focuses on the strategy and structure of domains.
You don’t need to be an expert in these different domains, but you do need the ability to Understand, Interpret, and Communicate within them. Having this ability will allow you to:
- Collaborate: Comprehend, keep-up-with, and materially participate in domain-specific discussions using audience vernacular.
- Moderate: Moderate discussions through acumen (i.e., keen insight) level knowledge of the subject matter.
- Challenge: Challenge-out resolutions through principled level knowledge of the subject matter.
You can view the Collaborate, Moderate, and Challenge as competency levels of Architectural Awareness. With the first step being collaboration. So, to summarize, you want to have a 30k foot view of the domains of concern on your project, understanding how they structured and their purpose, along with their relationship with each other.
Focus your first efforts on understanding, interpreting, and communicating at a level that allows collaborative efforts. Once you have this level, you can then advance to Moderate and then Challenging. Always remember, that even after obtaining “Architectural Awareness,” that you are NOT the SME, although you may become recognized as such at some point in the process.
Food for thought.
John, I think the problem lies in 'the teams seem to think I should'.
Ask yourself why this is, talk to the team individually, define your role (and theirs) and identify road-blockers of the team outside the technical area.
It is a matter of trust building, and not taking on a fight on authority in an area you will likely loose. Choose the battle field is a good strategy.
It is a typical movie plot that a leader shows his value in turbulent times but was previously rejected. Find these films and see how it works.
Hi John, I had the same issue in a former role where I was coming from infrastructure project management to enterprise applications. The key is to rely on the internal experts, but also external ones consulting with your company (i.e. vendors). PM's don't need to know everything; they just need to identify people who do.
I will ask with basement on I am living from long time ago including it my actual work place. For each initiative before I start working I perform elicitation activities to have knowledge about the components inside the enterprise architecture which will be impacted. I take that knowledge searching for internal knowledge and for external knowledge. For example, about marketing. The process I follow is the same I wrote in a paper that was published by the PMI and others like "Best Practice". Here comes the paper just in case it can help you (the paper is focused on creating a solution but is the method I took): https://www.projectmanagement.com/blog-pos...-right-solution
The same for indentify the stakeholders which are critical to engage the SMEs that will help me:
But taken knowledge, perform elicitation, comes first.
Thank you the links I will certainly check those out. appreciate your insight
Thank you for the insight. I appreciate it.
Please login or join to reply