Adam Gonnerman

The concept of Agile transformation, particularly in industries perceived as traditional, such as publishing, often comes with a heavy dose of skepticism. A pivotal moment in my career was steering such a transformation for a publishing company’s engineering team, aiming to adopt Scrum methodologies. The journey, although fraught with challenges, offers valuable insights into driving change even in the most unlikely environments. Overcoming Leadership Hesitancy Initially, the transformation encountered resistance. A new boss, with roots in a different era of publishing, held the belief that Agile frameworks, with their iterative nature and flexible deadlines, were incompatible with the rigorous deadline commitments of our industry. This underscored a common misunderstanding of Agile: it’s not a lack of structure or discipline, but a more responsive and efficient way to manage projects. Despite efforts to clarify this, my explanations met with resistance, leading to a professional parti

 As project managers, we often pride ourselves on our ability to handle complex and demanding workloads. However, there comes a point where the scales tip, and we find ourselves swamped, trying to stay afloat amid the myriad responsibilities of our role. The reality is that being overwhelmed isn’t just common; it’s a serious issue that needs addressing for the sake of our projects and our well-being. Recognizing Workload Overwhelm The signs of being overwhelmed are not always as obvious as a backlogged to-do list. They manifest in constant worry about deadlines, the feeling that you're always playing catch-up, and the inability to disconnect even after office hours. This can lead to stress, burnout, and even mental health concerns, all of which are topics that, unfortunately, carry a certain stigma in the workplace. Initiating the Conversation About Workload Admitting to yourself and to your superiors that you're at capacity is the first, often hardest, step. In an environment

The line between diligent supervision and micromanagement is often a blur in the workplace. Although well-intentioned, a boss who micromanages can create a stifling and counterproductive environment. Recognizing the signs and learning to cope with such management can make all the difference in maintaining one’s professional sanity and career trajectory. Understanding the Signs of Micromanagement Recognizing a micromanager becomes easier when you know the traits. Having endured the trials of working under such management, I can attest to these behaviors: Reluctance to Delegate: Trust is not a micromanager’s forte; they hold tasks close, even when delegation would be more efficient. Excessive Control: Over-involvement in every step and persistent check-ins disrupt workflow and autonomy. Overly Detailed Instructions: Instructions become exhaustive scripts, leaving little room for personal judgment. Constant Update Requests: Interruptions for progress checks become part of the daily routi

In the realm of project management, two contrasting sources of fulfillment often emerge: the thrill of delivering results and the enriching experience of team interactions. Both aspects carry their unique set of rewards and challenges, often acting as the dual engines that propel a project forward. The Rush of the Delivery The "dopamine of delivery" is a phrase that encapsulates the sheer exhilaration project managers and team members feel when they hit targets, meet deadlines, and deliver tangible results. It's that hit of neurotransmitter-induced happiness that comes from checking off a task on the to-do list, the pride in seeing a product or feature go live, and the satisfaction in reaching milestones. This chemical reward system is hardwired into our brains, motivating us to pursue goal-oriented behavior and giving us a sense of achievement when we complete tasks. However, it's not without its pitfalls. Overemphasizing delivery can lead to a relentless chase for t

As a seasoned project manager, you're accustomed to the hustle and bustle of juggling tasks, meeting tight deadlines, and driving teams toward project completion. But what do you do when the pace slows down and you find yourself with a surplus of time and a shortage of work? It's not an unusual scenario, and while it can lead to feelings of frustration or worry about your place in the team, this can actually be a golden opportunity to amplify your career and personal growth. Here's how to leverage those quiet periods for maximum benefit. Take Initiative and Communicate When you notice your workload becoming lighter than you can handle, the first and most crucial step is to take initiative. Reach out to your supervisor or team leader and convey your eagerness to shoulder more responsibilities. Illustrate your capabilities and articulate how you can contribute to the wider objectives of the organization. Show your passion for work and your readiness to embrace additional chal

As we wade deeper into the digital age, the role of Artificial Intelligence (AI) in our daily tasks is becoming more integral and, quite frankly, fascinating. Yet, when considering the integration of AI into our professional lives, there's a lingering question about the balance between utility and authenticity. Through my experiences, I've discovered ways to leverage AI to streamline tasks without losing the personal touch that defines my work ethic and professional output. Crafting Legal Documents with AI Assistance One of the more surprising uses I’ve found for AI is in generating formal documents such as a power of attorney. Initially, I was skeptical. Would an AI comprehend the nuances and gravity of such a document? To my astonishment, it did— with a little guidance and some meticulous proofreading on my part. The AI created a draft that served as a sturdy foundation for the final document. This experience was a revelation, illustrating that with precise instructions, AI c

Navigating different sectors has provided me with a unique perspective on Corporate Social Responsibility (CSR). Here’s a brief look into this transition. My Professional Background Starting in ministry and mission work, I understood early on the value of community impact. My career trajectory later took me to prominent corporations like AMC Networks, NBC Universal, and ViacomCBS. There, I focused on program and project management, which taught me the intricacies of team dynamics and project execution. Living in Brazil twice and gaining fluency in Portuguese gave me a broader understanding of diverse cultures. My academic background, including a Bachelor of Ministry and Master of Arts in Management, along with credentials like PMP, CSM, and ITIL Foundation, equipped me with industry-specific skills. Outside of these roles, I also engaged in volunteer initiatives, such as the Uberlândia Development Initiatives. Lately, I've been inclined towards sustainability. For me, it represents

Corporate Social Responsibility (CSR) has reshaped how companies approach their roles, emphasizing their impact beyond mere profitability. With shifting societal expectations, businesses are increasingly recognizing their broader influence on society, community, and the environment. In this exploration, we'll delve into the progression of CSR, spotlight two dominant models guiding its application, and discuss the challenges and opportunities companies face in embracing these principles. The Roots: Stakeholder Model At the heart of CSR's foundation lies the stakeholder model, which expands the scope of responsibility beyond shareholders to a more inclusive framework. This model emphasizes that corporations owe duties not just to shareholders, but to a broader spectrum of stakeholders, such as employees, suppliers, customers, and the environment. It envisions businesses as entities integrated within their communities, necessitating a consideration of the broader ramifications of

In my experience, there's a delicate balance between self-advocacy in the workplace and timing your career moves wisely. This balance becomes most critical when the question of a raise comes into play. I've seen firsthand the repercussions of ill-timed requests for salary increases and the subtleties involved in these high-stakes conversations. Understand Your Value, But Also the Company's Position Reflecting on past interactions with colleagues across different companies, it's evident that many don't fully grasp the importance of timing when it comes to asking for a raise. I recall a project manager and a developer, from separate organizations, who approached the situation without due consideration of the company's status, leading to awkward or detrimental outcomes. The Missteps Both individuals seemed unaware of the impending layoffs at their respective companies. This leads one to wonder if anyone aware of such a precarious company situation would dare to req

Decision-making at the corporate level, especially when it involves core technology that will be used internationally, is never straightforward. It's a high-stakes game where the right call can propel a company forward, and the wrong one can be a costly setback. A few years back, I was at the helm of such a decision—a pivotal project that taught me invaluable lessons about rigor, diplomacy, and the power of a structured approach. Understanding the Stakes At the outset, the challenge was clear: we had to choose between leveraging our in-house technology or adopting a solution from an external vendor. The implications of this decision were vast, affecting not only our operational efficiency but also our market competitiveness. This was not just a technical decision; it was a strategic one that demanded a methodical process. The project involved a multitude of international senior executives, each with their own set of opinions and interests. The diversity of perspectives was as much

Specialization of roles and apparent similarity of job titles can create confusion. Product Managers and Project Managers play pivotal roles, but there are often misunderstandings about their responsibilities. There was a time, early in my career, when I played each role for different companies, but that was before I settled into specializing in project management. Hopefully the following will help demystify what each does.  Product Manager: The Visionary Vision Ownership: Product Managers are the guiding force behind a product's direction. They own its vision and ensure all efforts align with it. Strategy Synthesis: They craft and convey the product's strategy, ensuring everyone works towards a cohesive goal. Feature Definition: They decide what features a product should have, ensuring they resonate with the overall strategy. Content Focus: Product Managers concentrate on content, ensuring it aligns with the audience's needs, whether it's user interface or experience.

In 2020, as part of my capstone project for my Master of Arts in Management: Project Management, I found myself facing a unique challenge. At the heart of this challenge was a community center in Uberlandia, Brazil, and the barriers they faced in receiving international support. Their website was exclusively in Portuguese, making online donations almost inaccessible for those unfamiliar with the Brazilian banking system or the intricacies of international transfers. The more I thought about it, the more a solution became evident: establishing a US-based nonprofit to bridge this gap. A Personal Connection: From Brazil to Computers My connection with Brazil runs deep. Not only have I lived there twice and visited many times, but I also speak fluent Brazilian Portuguese. My children were born in Uberlandia. During my second stay in Brazil between 2013-2015, I was approached by a local, hoping to set up some computers donated to a community center by a bank. Although they were older models

The realm of publishing, like many other industries, has not been immune to the sweeping changes brought about by technology and changing work dynamics. Among these changes is the adoption of Agile methodologies, particularly in teams that intersect with technology and project management. I'd like to share a personal anecdote that highlights the misconceptions about Agile, even within progressive industries like publishing, and why it's essential for leaders to understand its real value. A Step Back in Time Years ago, I found myself working at various publishing companies. At one such company, an opportunity arose that would have been a significant milestone in my career – leading an Agile transformation for an engineering team. They were keen to evolve into a full-fledged scrum team, and the head of engineering was supportive of the initiative. However, the journey hit an unexpected bump. One day, while discussing the transformation with the head of engineering, my then-new bo

In today's ever-evolving business landscape, the concept of Corporate Social Responsibility (CSR) is gaining increasing significance. In the book "Business Law" by J. Morgan (2019), CSR is defined as an approach where businesses consider both internal and external communities. This goes beyond merely looking out for shareholders and emphasizes the importance of considering employees, the environment, and society at large. In essence, it's about businesses recognizing their broader role in society and considering the wide-reaching impacts of their decisions. Two Dominant CSR Models: Stakeholder and Triple Bottom Line Morgan elucidates two popular approaches to CSR: Stakeholder Model: Under this model, businesses owe duties to various entities - their employees, customers, suppliers, and various communities, including the local community and industry competitors. This model encourages businesses to look beyond mere profit and consider how their decisions impact social,

In the realm of technology and business, the process of migrating from an on-premises infrastructure to the cloud is no small feat. This kind of transformation can be likened to shifting an entire organization from its long-standing roots to a completely new environment. Such an undertaking not only requires technical prowess but also a meticulous plan. Here’s a tale from the tech trenches that underscores the pivotal role of project managers. Imagine an engineering team gearing up for a cloud migration, potentially to AWS. Everything seems to be in place. They have a robust plan, thanks to their diligent project manager who delineated the entire migration process into several "waves." Each wave was strategically designed, factoring in which parts of the company would be affected, which servers would be shifted, and even the stakeholders that needed to be engaged at each phase. The beauty of this strategy was its clear communication. By dividing the migration into waves, stak