This podcast episode is the second part of an interview with Cornelius Fichtner about his career in project and project business management. The discussion picks up where the previous episode left off, detailing Fichtner's career trajectory after being let go from an internet startup. It explores various roles, cultural differences in project management environments, and the importance of networking and personal development.
Based on the provided transcript, Cornelius Fichtner describes a situation at an internet startup where there was no formal project management governance or methodology. He and his fellow project managers responded by collaboratively developing their own methodology. This involved pooling their collective experience and best practices to create an approach that worked for their specific context and challenges. They later presented their self-developed methodology to the company, which ultimately adopted and formalized it.
The transcript offers several approaches to handling individuals who take things personally in a project setting. Cornelius Fichtner admits he personally avoids direct confrontation, preferring to build relationships and work behind the scenes with colleagues to de-escalate situations. Other participants in the discussion suggest the value of a third-party mediator to resolve conflicts, or a more direct, friendly confrontation focusing on achieving a shared goal ("completion over competition"). The best approach, they acknowledge, depends heavily on the context (internal team vs. external client) and the individual's personality.
For economic advantage, Cornelius Fichtner suggests pursuing formal business education to better understand business operations at a higher level, improving one's ability to manage and grow a company. For personal satisfaction, he advises identifying and nurturing what one truly enjoys, suggesting a process of self-reflection and potentially seeking mentorship to guide this discovery. He notes that this process may take time, as finding fulfilling work is often a journey of discovery rather than an immediate solution.
