Indie Systems Journal: Why We Built an Open, Community-Driven Publication for Systems Thinkers

The first-ever editorial from the Indie Systems Journal — our origin story, our mission, and why the world needs a different kind of systems publication.

There is a particular frustration that every serious systems thinker knows. You find a paper that promises exactly what you need — a rigorous exploration of feedback loops in distributed infrastructure, or a deep analysis of sociotechnical failure modes — and then you hit the wall. A paywall, to be precise. $39.99 for 48 hours of access. You close the tab. The idea you were chasing disappears like smoke.

That moment is why the Indie Systems Journal exists.

We are not a hobby newsletter. We are not an academic vanity project. We are a deliberately independent, editorially rigorous publication built by practitioners and researchers who believe that systems thinking deserves a public commons — a place where ideas circulate freely, where contributors are real people with skin in the game, and where the editorial mission is defined by the community rather than by a publisher's subscription revenue targets. This founding editorial explains where we came from, what we stand for, and — crucially — what we are asking from you.

The Origin Story: A Slack Thread That Refused to Die

Every real publication starts with a conversation that outgrows its container.

Ours started in a shared Slack workspace populated by systems engineers, cybernetics enthusiasts, infrastructure architects, and a handful of academics who had grown quietly disillusioned with the mainstream publishing circuit. The thread was titled, without much ambition, "good systems papers you've actually read lately." Within two weeks it had over 400 messages. People were sharing pre-prints, dissecting methodology, arguing about definitions of emergence, and — repeatedly — expressing the same frustration: there was no single venue that covered the breadth of systems thinking without either disappearing behind a paywall or dumbing the content down to a listicle.

The mainstream options felt like a binary trap. On one side: prestigious, peer-reviewed journals like the IEEE Systems Journal or Systems Research and Behavioral Science — rigorous, important, but institutionally gated. Access required either a university affiliation or a credit card. The knowledge inside was publicly funded in many cases, yet publicly inaccessible. On the other side: the content-marketing blogosphere, which produces plenty of "systems thinking for beginners" posts but rarely advances the conversation beyond Donella Meadows 101.

The gap between those two poles is where the Indie Systems Journal was born.

Three of us — a reliability engineer, a complexity researcher, and a technical writer who had spent a decade covering infrastructure — drafted a simple one-page manifesto on a shared Google Doc at 11 p.m. on a Tuesday in late autumn. The manifesto had three lines: Open access always. Practitioner voice matters. Depth without gatekeeping. We shared it in the Slack channel the next morning and asked if anyone wanted to help build something around it. Twenty-three people said yes before lunch.

That was Run 1. This editorial is its public record.

Our Editorial Scope: What We Cover and Why It Matters

Defining scope is one of the most important — and most undervalued — acts in publishing. A publication that tries to cover everything covers nothing well.

The Indie Systems Journal has a defined editorial scope that distinguishes it sharply from both mainstream academic journals and generalist tech publications. We sit at the intersection of three domains:

Systems Engineering and Architecture

We publish rigorous, practitioner-informed analysis of how complex engineered systems are designed, fail, evolve, and recover. This includes distributed systems, resilience engineering, infrastructure architecture, and feedback-driven design patterns. Unlike the IEEE Systems Journal, which prioritizes novel theoretical contributions from credentialed academics, we actively seek field reports from engineers who have operated these systems under real-world conditions — the kind of knowledge that rarely survives the academic peer-review translation process intact.

Sociotechnical Systems and Organizational Dynamics

Technical systems do not exist in social vacuums. We cover the human dimensions of systems: how teams encode assumptions into architectures, how organizational incentives shape infrastructure decisions, how communication structures mirror (and misfire against) technical dependencies. Conway's Law is not just a design heuristic here — it is a recurring analytical lens.

Complexity Science and Applied Cybernetics

We take feedback loops, emergence, nonlinearity, and adaptive behavior seriously — not as metaphors borrowed from biology to make slide decks sound impressive, but as analytical frameworks with genuine explanatory power. We are skeptical of complexity theater and rigorous about distinguishing cases where these concepts genuinely illuminate from cases where they merely decorate.

What we do not cover is equally important. We do not publish general software development tutorials. We do not cover productivity systems or personal knowledge management, despite the semantic overlap with "systems." We do not publish content whose primary purpose is to market a product or service. Our editorial independence is structural, not aspirational.

Who We Are: The Contributors Behind Run 1

Indie publishing lives or dies by the credibility and authenticity of its contributors. A faceless editorial collective is just a content operation with better branding.

Run 1 of the Indie Systems Journal features contributions from eight writers and researchers, each of whom came to systems thinking through a distinct path — and each of whom had a specific reason for choosing to publish here rather than through conventional channels.

Maya Osei is a senior site reliability engineer who has spent twelve years operating distributed systems at scale. Her contribution to Run 1 examines how incident retrospectives systematically undercount second-order failure contributors due to the way most post-mortem templates are structured. She could have submitted this analysis to a software engineering conference. She chose us because, in her words, "I wanted to write for the people who will actually fix the next incident, not for a program committee."

Dr. Tariq Ahmadi holds a postdoctoral position in complexity science and has published in peer-reviewed venues. His Run 1 piece explores the misapplication of Ashby's Law of Requisite Variety in management consulting contexts. He is publishing with us simultaneously with an academic preprint — something our contributor agreement explicitly supports — because he wants his ideas to reach an audience that does not have JSTOR access.

Priya Sundaram built and sold a logistics technology company and now writes about supply chain systems from the perspective of someone who has watched elegant theoretical models collapse under the weight of real procurement constraints. Her Run 1 essay is the most personal piece in the issue, tracing how a single point of failure in a vendor relationship cascaded into a company-threatening event over eighteen months.

These are not manufactured personas or ghostwritten pieces. Every contributor in Run 1 submitted a bio, a motivation statement, and a conflict-of-interest disclosure. We publish those disclosures openly. Transparency is not a policy we enforce; it is a culture we are building from the first issue.

Why Indie Publishing Fills a Gap That Academic Journals Cannot

The case for open, independent publishing is not simply an ideological argument about information freedom — though that argument is valid and important. It is also a structural argument about what kinds of knowledge traditional academic publishing systematically fails to capture.

Peer-reviewed journals are optimized for novelty claims, methodological rigor, and reproducibility. These are genuine virtues. But they create systematic blind spots:

Tacit practitioner knowledge rarely survives the formalization required for academic submission. The insight that "our monitoring system always lies about latency during GC pauses" is operationally crucial and intellectually interesting — it tells you something real about how measurement systems interact with the systems they measure. But it is not publishable in IEEE Transactions.
Negative results and failure analyses are underrepresented in academic venues because they are harder to frame as novel contributions. Indie publishing has no such structural bias.
Timeliness is sacrificed to thoroughness in academic cycles. A peer-reviewed paper analyzing a major infrastructure failure pattern might appear eighteen months after the failure is common knowledge in practitioner communities.
Access economics mean that even when academic journals produce genuinely important systems work, the people who most need that work — engineers, architects, operations teams at companies without institutional library subscriptions — cannot read it without paying per-article fees that add up fast.

The open-access movement within academia has made real progress — arXiv, PLOS ONE, and mandates from funding bodies like the NIH represent genuine gains. But open access alone does not solve the formalization problem or the timeliness problem. An independent publication with different editorial values is a complementary infrastructure, not a competitor to academic rigor.

We also fill a community function that journals structurally cannot. A journal publishes issues. We are building a conversation. Our comment infrastructure, our contributor forums, and our editorial round-tables are designed to make every piece of published work the beginning of an exchange, not the end of one.

How to Participate: A Call for Contributors and Readers

A publication that calls itself community-driven has to do more than gesture at community. Here is what genuine participation looks like at the Indie Systems Journal.

For Prospective Contributors

We are actively seeking submissions for Run 2. Our editorial scope is described above, but the best way to understand what we publish is to read Run 1. Beyond scope, here is what we look for:

A specific claim or observation, not a general survey. "Systems thinking is important" is not a thesis. "The standard five-whys methodology systematically attributes failures to human error because of how the stopping condition is defined" is a thesis.
Evidence drawn from real experience or primary sources — operational data, case studies, direct observation, or rigorous engagement with existing literature.
Transparency about your perspective and its limits. We do not require false objectivity, but we require that contributors be honest about their standpoint.

We do not require academic credentials. We do not require a certain number of years of experience. We require intellectual honesty, a specific argument, and a willingness to engage with editorial feedback.

Submissions are reviewed by a rotating editorial board of three contributors, none of whom are the submitting author. Reviews are returned within three weeks. We publish a decision rationale for every submission, accepted or rejected, and we welcome resubmissions after revision.

For Readers

Subscribe to the journal at no cost — open access is not a promotion; it is permanent policy. Share pieces that deserve wider circulation. Disagree publicly in our comment threads when you think a contributor has it wrong; substantive dissent improves the work. If you are an engineer, researcher, or practitioner who has been waiting for a venue that takes systems thinking seriously without charging you for the privilege, you have found it.

The most important thing you can do right now is send us the paper you have been meaning to write for three years. The one with the real insight, the uncomfortable observation, the case study that your employer would never let you submit to a conference. We want that one.

Conclusion: This Is Run 1. The Race Is Long.

We are under no illusion that launching an independent journal in a landscape crowded with newsletters, Substacks, and declining attention spans is a straightforward proposition. We know that building editorial credibility takes time, that community trust is earned through consistency, and that the moment we compromise on access or independence is the moment we become what we set out to complement.

But we also know that the conversation that started in that Slack thread at 11 p.m. has not stopped. It has gotten louder and more specific and more technically serious with every passing month. There are thousands of people carrying around systems insights that the existing publication infrastructure will never surface. Run 1 is our bet that those people will find each other here.

Read Run 1. Submit to Run 2. Tell a colleague. The Indie Systems Journal is open — and it intends to stay that way.

The Indie Systems Journal publishes practitioner-grounded, open-access analysis of complex systems. All content is free to read, share, and cite under a Creative Commons license. Submissions for Run 2 are open now.