Dispatches from an Internet Pioneer
Views on Tech, Leadership, and Society from an Internet Pioneer
Why I Write
I am a trained sociologist who has spent thirty years running IT organizations in higher education. That combination is uncommon, and it shapes everything I write.
My default move when something goes wrong is structural. I look at incentives, authority relationships, and process design and flow before I look at individual character or competence. That instinct comes from years of watching good people get blamed for problems the system itself created. It is hard to outperform a broken system, and it is unfair to keep asking people to try without fixing it first.
The thinkers who shaped that instinct have names. Max Weber on legitimate authority and bureaucracy. Clark Kerr on the impossible plurality of the modern university. David Riesman on how institutions drift and why peer pressure produces conformity among those who know better. Timur Kuran on why organizations appear stable right up until they collapse. These are not household names outside academia, but the patterns they described are visible in every budget meeting, every vendor negotiation, and every ERP implementation I have been a part of. I try to write in a way that makes those patterns accessible without losing their usefulness.
The practical counterweight to all that structural influence is negotiation. Chris Voss and Chester Karrass taught me that understanding the other party’s constraints, their internal pressures, and what they need to take back to their own organization is not a soft skill. It is a form of institutional analysis from which influence is often derived, and it determines outcomes more reliably than talent or enthusiasm does.
And underneath all of it is a moral dimension that C.S. Lewis articulated better than anyone: skepticism about the present moment is not cynicism. The assumption that newer is better, or that current consensus is reliable, is itself a form of intellectual laziness. I have lived through enough hype cycles over the years to take that seriously.
I write because the conversation in higher education IT too often defaults to endless optimism about technology and thin analysis of institutions. This is my attempt to correct that imbalance, for fellow CIOs, for curious outsiders, and for the next generation of leaders who deserve a clear picture of what they are walking into.
This work is also personal. I am now about the same age that mentors Steve Williams, Tom Putnam, and Pierce Cantrell were when they invested in me. It is my turn.
Why “Internet Pioneer”?
I started graduate school at Texas A&M in 1993, just as full Internet access was being opened to students and faculty. Email let me reach writers and thinkers I admired directly. WiFi rolled across campus. The walls between people, places, institutions, and ideas began to come down in ways that felt genuinely new.
A few years later, while finishing my dissertation, I took a job as an entry-level programmer. We were building what now seems ordinary but was then unproven: putting admissions online, enabling e-commerce, building one of the first web-based class registration systems. That early work shaped everything that came after, including my conviction that the most important technology shifts are always about more than technology. They are about access, authority, and who gets to decide.
What to expect:
The recurring themes here are institutional rather than technical. How universities actually make decisions, and why those decisions so often disappoint the people making them. How AI is changing the risk calculus for knowledge workers, not just the efficiency calculus. How leaders mistake structural problems for personnel problems and then make both worse. How negotiation, governance design, and the distribution of accountability determine outcomes that no software can fix.
Technology does not work in a vacuum. It collides with people, power, culture, and institutional history. I write about where those collisions happen, what they reveal, and what they require of the people responsible for leading through them.
About Timothy Chester
I currently serve as Vice President for IT at the University of Georgia, a role I have held since 2011, and concurrently as Vice Chancellor for Information Technology for the University System of Georgia. I teach in the MBA and graduate programs at UGA’s Terry College of Business. I hold a Ph.D. in Sociology from Texas A&M.
Over more than thirty years in higher education, I have led four major ERP implementations, built technology organizations from the ground up, and watched more hype cycles than I care to count. I write about the real lessons from that experience: not just about systems and software, but about people, trust, authority, and the unglamorous structural work that change actually requires.
https://www.linkedin.com/in/timothychester/
Why Subscribe?
Subscribe to get full access to the newsletter and publication archives.
Stay up-to-date
Never miss an update: every new post is sent directly to your email inbox. For a spam-free, plus an ad-free reading experience, get the Substack app.
Join the crew
Be part of a community of people who share your interests. Participate in the comments section, or support this work with a subscription.
To learn more about the tech platform that powers this publication, visit Substack.com.
