Adam Gonnerman

When I was young, meeting someone new was uncomplicated. You saw another kid, asked if they wanted to play, and a friendship began. Growing up in a pre-internet world, the people you knew were largely the people you saw regularly. You had each other's phone numbers, and that was enough. Connection happened through proximity. There was a time, further back in history, when formal letters of introduction served as the mechanism for entering new social and professional circles, but that practice faded long ago. Today, the introduction happens online, often before any in-person meeting ever takes place. About twenty-one years ago I made a trip to New Hampshire. I was a full-time minister at the time and was exploring the possibility of becoming a bivocational minister in that state, with the goal of finding steady work while using my remaining time to plant a Brazilian congregation. When I arrived, I already had a contact: a Brazilian man I had connected with online. He and his Americ...

A little over a month ago we heard about someone at Meta losing a good portion of her email to an AI that went off course. She managed to stop it before it finished, and it apologized, but the damage was done. I was surprised that she posted about it publicly. In any case, it demonstrates the danger presented by giving AI complete control over one's desktop and work.  This situation was presaged humorously by the series Silicon Valley. See below and enjoy!  

More than a decade ago, sitting across from a Brazilian consultant who was reviewing my resume for a potential project management opportunity, I received a verdict I was not expecting. He looked up from the page and said, matter-of-factly: "You're a theologian." He was not wrong about my degree. I hold a Bachelor of Ministry, earned through an accelerated program at Harding University that covered nearly four years of biblical, counseling, and ministry education in two. But in the standard Brazilian professional framework, you are what your degree says you are. My PMP certification, my years of project management experience, my track record of delivering complex initiatives meant very little in that moment. I had graduated into theology. Therefore I was a theologian. I thought about that conversation years later when I enrolled in a Master of Arts program in management with a concentration in project management, made possible through Viacom's employee education bene...

Nobody puts missionary experience on a project management resume. I did not either, at least not explicitly. But after fifteen years delivering complex technology programs, I am convinced that two years of mission service in Brazil shaped my professional instincts more than any methodology certification ever has. Let me explain why. After a mission internship in Brazil in 1997, I committed to returning as a full-time missionary. That meant getting the right education first. I enrolled in Harding University's School of Biblical Studies, an accelerated program that compressed nearly four years of education into two. The pace was relentless. I studied beginning through advanced biblical Greek in 24 weeks. Along the way I went deep not just into Scripture but into counseling, fundraising, cross-cultural communication, and the practical realities of sustaining a mission. I was trained to enter unfamiliar territory and figure it out. That turns out to be an extraordinarily useful profess...

“The purpose of a system is what it does.” — Stafford Beer A team drowning in slow approvals decides the problem is speed, so they add AI. Leadership announces a new assistant to unlock productivity. A chatbot is rolled out to close knowledge gaps and reduce internal friction. Demos look promising. Early outputs feel impressive. But weeks later, nothing fundamental has changed. Decisions are still unclear. Ownership is still fuzzy. Data is still inconsistent. If anything, the noise level has increased. You can't use AI to repair broken systems. What it does in reality is accelerate their weaknesses. You see, AI multiplies what already exists. Unclear decision rights leads directly to faster confusion. If no one knows who owns decisions, AI generates more options. Further, more stakeholders weigh in, and decision latency increases. Think about it like this: AI increases surface area of disagreement. Poor data result in confidently wrong outputs. If your data are incomplete, incons...

"The leader must own everything in his world. There is no one else to blame." — Jocko Willink, Extreme Ownership Having just been assigned to a cloud migration team, I was trying to get the lay of the land and understand where project work stood. What I gathered wasn't good. They hadn't had a project manager for about a year, and work had started to drift badly. That first week was when their manager called me into his office. He laid into me about how far behind everything was. His frustration directed at me felt like an accusation, as if I'd personally caused the delays. I could hardly get a word in edgewise as he vented. It became very clear to me that although I had no hand in creating the mess, it was mine now anyway.  This is part of inherited debt. When you step into a team, you don't just inherit a role. You inherit the technical shortcuts nobody documented, the cultural habits that formed before you arrived, and the strained relationships with stakeh...

“The essence of strategy is choosing what not to do.” - Michael Porter It's a familiar event to anyone who has worked with a tech team. You have work well along on a project when a stakeholder comes along asking for "just one more feature." If you are the project manager or product manager, people will look to you for guidance. You know that capacity is full, tradeoffs are real, the roadmap will bend, and something inevitably will break. Yet, the pressure is subtle (or non-so-subtle, depending on the stakeholder). There's an expectation, perhaps, that you'll say that the team can make it work, suggest that all are aligned, and acknowledge that this is an important feature. So, you say "yes." Six weeks or less later, you find that delivery slips, quality drops, morale dips, and trust is now eroded. Leadership is not only about what you drive forward. It’s about what you refuse to absorb. We need to be clear that saying "no" is not obstruction....

“By failing to prepare, you are preparing to fail.” - Benjamin Franklin In startup and tech culture, we celebrate the last-minute save. But heroics are often symptoms of earlier neglect. Hero Culture thrives on moments like this: it's Friday at 4:47pm, a ticket has been sitting in review for two weeks, the stakeholder is impatient, and the engineer has a flight to catch, so someone pushes the deployment button because it's a small change and it's always fine. By 9pm there's a Slack thread, by 10pm it's a call, the engineer is somewhere over Ohio in airplane mode, and the one person who knows that part of the codebase is stepping outside a birthday dinner every fifteen minutes to check their phone. The fix takes forty minutes, the post-mortem takes two weeks, and the person who stayed up to save the night gets praised on Monday morning while the person who warned against Friday deployments three sprints ago is quietly forgotten. That's the thing about Hero Cult...

“Only when the tide goes out do you discover who’s been swimming naked.” -  Warren Buffett One consistent truth I have observed in business is that leaders tend to reward what is visible, while some of the most essential work within organizations remains unseen. Consider a product launch. Slack channels fill with celebration, leadership offers public praise, and performance metrics are widely shared. Now contrast that with months of refactoring, quiet mentoring, and diligent risk mitigation that largely go unnoticed. Visibility distorts perception. This is visibility bias in action. It appears as: Shipping rewarded more than stabilizing. Roadmaps praised more than operational rigor. Deck-building valued over difficult conversations. Activity mistaken for impact. This connects directly to a post I previously wrote on shipping versus advancing , where I argued that organizations often conflate visible activity with meaningful progress. Shipping, with releases, tickets, a...

“You can't build a reputation on what you are going to do.” - Henry Ford Many years ago I told someone that my wife at the time and I were planning on adopting a child at some point in the future. To my dismay, the response was “congratulations!” As if I had already adopted a child. The person went on to say what good people we were. Receiving such praise did not feel gratifying. It felt misplaced. Almost like a “stolen valor” situation. After that I kept to myself our plans to adopt, and as it turned out the only child I ever adopted was my beloved step-daughter. The other day I wrote a blog post that I’d hesitated about quite a bit. It was regarding the DBA program at Edgewood University. On the one hand, I was excited to share a program that I’d found to be so affordable and complete, and from a good (albeit small) university. On the other, I dreaded the possibility of giving the appearance of one trying to take credit for what he has not yet done. There is an emotional tensio...

“ All change is not growth, as all movement is not forward .” — Ellen Glasgow One day I was at the neighbor's house, hanging out with friends, when I noticed a calendar with a quote for each month. Paging through it, I came across the one above. It impacted me deeply at the time, as it aligned with what I often felt I saw in the world. Movement without progress. As the years have passed the quote has stayed with me, and its meaning to me has evolved as I've progressed through my career. I can see that in today's business culture, we often confuse activity with achievement. Let's consider the differences between shipping and advancing. "Shipping" means delivering something, releasing a feature, completing a sprint, publishing a post, or closing a ticket. Shipping is visible. It feels productive. It checks a box. Advancing, on the other hand, means moving closer to a meaningful objective. It's creating durable value. Improving systems and not just outputs....

There we were, on a Zoom call, sharing our quarterly roadmap with leadership. The visuals were clean with dates, themes, milestones, and color coding. I think it's safe to say that the emotional effect of such a roadmap is a sense of alignment, clarity, and reduced anxiety. That's where there may be a problem. Roadmaps create psychological safety, but that safety can become an illusion of control.  Visual order reduces anxiety. We humans are social beings, and stories are core to our way of thinking about life. We prefer structured narratives over ambiguity. A roadmap, high level though it may be compared to a detailed project plan, turns uncertainty into a sequence. Having dates implies predictability, and sequencing implies causality.  Executives, for their part, want forward visibility. They want to see into the near- and mid-term future to the extent possible. Sales wants commitments that can be communicated and kept. Finance wants forecasting. Engineers look at the roadma...

Early in my career, I worked as a web producer at a startup, an experience I have written about before. It was a formative role that required wearing multiple hats and operating with a high degree of ownership. One of my primary responsibilities was receiving content from publishers and converting it into a format compatible with our online reader. The inputs varied widely. Investment newsletters arrived as emails, Word documents, PDFs, and in one case even by postal mail. Each format required a different workflow, and transforming them into publish-ready content demanded both technical adaptability and careful attention to detail. Although I could have managed most of the process from memory with minimal notes, I made a deliberate decision to fully document my work. I created step by step guides, including screenshots, and stored everything in Confluence. I also made sure my colleagues knew where to find it. My thinking was simple: if something unexpected happened, the business should...

For some time I've been thinking about my next academic move. While I have two Masters degrees, at some point in the future I'm going to want to complete a Doctorate in Business Administration. I've looked into a few options, but one from Edgewood University has stood out from the rest . Although it seems this program might be relatively new to the university, they have a great lineup of courses . And they are affordable, compared to other schools. You can complete your DBA for well under $25,000 according to what I've read.   Here are some quick facts about the school, via Wikipedia : Established: September 4, 1927 Religious affiliation: Catholic (Dominican) Endowment: $50 million President: Andrew P. Manion Academic staff: 150 Students: 2,469 (fall 2024) Undergraduates: 1,236 (fall 2024) Postgraduates : 1,233 (fall 2024) Location: Madison, Wisconsin Check out the video below and have a look at their website, if you're interested. I'm not saying this would d...

This video explores a provocative critique of Bitcoin, challenging common narratives about its independence and long term viability. It examines claims that Bitcoin’s price is deeply tied to government spending dynamics, questions whether its massive energy consumption poses an existential threat in a climate constrained world, and probes the sustainability of its speculative valuation structure. The discussion also raises concerns about regulation, financialization, and whether Bitcoin represents a true alternative to the traditional system or simply another chapter in the history of speculative bubbles.

Startups in their early days can be quite small. Just a handful of people wearing multiple hats, trying to reach a goal. That was the case in one startup I worked for very early in my career in business and technology. I had been hired to be customer service, but quickly found myself in the role of web producer. I was preparing and uploading content for the users, which was more complex that it sounds given the various formats that were delivered to me, and I was reporting bugs. Oddly enough, something we didn't have even post launch were "offline temporarily" and 404 pages, but no one on the team had time to create them. To be clear, as customer service, this shouldn't have been my responsibility.  The CEO noticed this gap, with the missing error pages, and pointed out that visitors hitting missing pages would encounter a confusing dead end. The urgency was clear, that these pages needed to be addressed immediately to maintain credibility and ensure a smooth experien...

My title right now, were I employed, could be "program manager," "project manager," "technical program manager," or technical project manager. Fundamentally, a project manager thinks about planning, organizing, and guiding work so that a specific goal is achieved on time, within scope, and within budget. Unlike operations work, projects have a beginning, middle, and an end. They come and go. Now, I have held other titles. Once, at Scholastic, I held the title of Senior Technical Product Manager. This was a role that blended the fields of project and product management. Despite this experience, there came a time that I wanted a clearer and more current understanding of how strong product managers operate day to day. For this, I arranged to shadow a product manager where I worked. At the time, this was more about curiosity and personal growth, rather than role transition. Now, though, I could see a time coming in which I would want to transition into product...

Early in my career, I was invited to sit in on a meeting with enterprise architects and senior engineers to discuss an integration between a legacy content management system and a new distribution platform. I was there as the (fairly junior) project manager, not the technical authority in the room. The conversation quickly became highly specialized: API contracts, data schemas, caching layers, and system latency thresholds. It was clear I wasn’t the deepest technical expert at the table, and for the first part of the discussion, I mostly listened and felt a little lost. What I began to notice, however, was that while the technical details were sound, the group was implicitly optimizing for architectural elegance rather than delivery timing. No one was explicitly mapping the proposed solution against the external deadline tied to a partner launch. I asked a clarifying question that went something like this (I may have actually rambled a bit): “If we implemented the simpler, interim int...

In a few blog posts here recently I've attempted to share what we can expect with the coming burst of the AI bubble . I think it's a matter of "when," not "if." The clip below explains the consequences of the end of the AI bubble in simple and direct terms. What bothers me about it, besides its inevitability, is that I can't think of what to do to protect myself from the aftermath.   

The most interesting concept I’ve learned about in the past month is “enshittification,” a term coined by Cory Doctorow . He uses it to describe the predictable decline of digital platforms: first they are great to users, then they shift to favor business customers and advertisers, and finally they extract maximum value for shareholders, often degrading the experience for everyone else in the process. The term is blunt, but the framework is sharp. It gave language to something I’ve observed repeatedly in media and technology organizations: product decisions that begin as user-centered gradually become revenue-optimized, and eventually erode trust, quality, and long-term viability. Related to that, I’ve been following Doctorow’s arguments about a potential AI bubble, his view that massive capital is flowing into AI in ways that may not be sustainable relative to real, durable value creation. That perspective helped me separate two things that are often conflated: genuine technological...

 About eleven years ago, I read a book on Positive Psychology that, at the time, had nothing to do with program management or technology delivery. One idea in particular stayed with me: the notion that some people are simply born more prone to depression, that they “did not win the cerebral cortex lottery.” The framing was direct and compassionate. It suggested that for many individuals, depression is not a failure of discipline, mindset, or effort, but a biological predisposition shaped by genetics and brain chemistry. That insight fundamentally changed how I viewed both mental health and human performance. Professionally, it shifted how I interpreted behavior on teams. Before that, I might have unconsciously attributed low energy, pessimism, or withdrawal to disengagement or attitude. Afterward, I became far more careful about separating observable outcomes from assumed intent. I learned to ask more questions, create psychological safety in one-on-ones, and normalize conversatio...

In May 2020, I founded Uberlândia Development Initiatives (UDI) to support the community of Shopping Park in Uberlândia, Brazil—an under-resourced neighborhood of roughly 40,000 residents in a city of more than 680,000. While Uberlândia is a regional hub with a strong university system, public transportation, and economic opportunity, Shopping Park developed for decades without consistent access to basic infrastructure such as sanitation, asphalt, and nearby services. I was particularly moved by the work of Centro de Formação Comunitário São Francisco de Assis (Estação Vida), a community center serving more than 150 children daily with meals, tutoring, sports, music, and life-enriching programming. I established UDI to raise the center’s profile internationally and create a secure, structured way for supporters in the United States and beyond to contribute. I dedicated significant time to forming the nonprofit, navigating the legal process to obtain 501(c)(3) tax-exempt status in Dece...