Indie Systems Journal Editorial Run 1: What It Is, Who's Behind It, and Why It Matters

The independent publishing landscape for systems thinking has been quietly expanding, and Indie Systems Journal is one of the more deliberate entries into that space. Its first editorial run — what the team calls "run 1" — represents not just a debut issue but a stake in the ground about how systems-oriented writing should be selected, presented, and circulated outside of academic gatekeeping. This post breaks down what editorial run 1 actually means in practice, profiles the editorial philosophy driving it, situates the journal within the broader indie publishing ecosystem, and documents how the curation process for run 1 selections worked. Because very little has been written about this publication yet, this piece aims to be a useful primary reference for writers, readers, and practitioners trying to understand where Indie Systems Journal fits in their reading diet.

What "Editorial Run 1" Actually Means in Indie Systems Publishing

The term "run" rather than "issue" or "volume" is a deliberate choice that signals something about how Indie Systems Journal operates. In traditional academic publishing, issues are tied to calendar schedules and volume numbers — artifacts of print logistics that persist even in digital-only journals. A "run," by contrast, borrows language from limited-edition print culture (think risograph zines and numbered letterpress chapbooks), where a run defines a finite, coherent production batch rather than a recurring slot on a calendar.

For Indie Systems Journal, editorial run 1 is the founding cohort of content: a bounded set of pieces that were solicited, reviewed, and shaped together as a unit. The editorial team treated run 1 as both a proof of concept and a position statement. Every piece accepted needed to justify its place not just individually but in relation to the whole — a curatorial logic more common in art catalogs or curated essay collections than in periodical publishing.

This matters practically for contributors and readers alike. It means:

No filler content to meet a page count or word quota
Thematic coherence across pieces, even when topics vary
A defined close — run 1 is complete; it doesn't roll into run 2 seamlessly
Archival stability — what's in run 1 stays in run 1, without post-publication additions

The implication for writers considering submitting to future runs is significant: Indie Systems Journal is not looking for a stream of content. It is looking for pieces that fit a specific editorial moment.

The Editorial Team, Vision, and Submission Philosophy

Who Is Steering This

Indie Systems Journal is structured around a small editorial core rather than a large editorial board. This is intentional. Smaller editorial teams make faster, more consistent decisions and are better positioned to maintain a coherent voice across a run — a trade-off that sacrifices breadth of editorial perspective in exchange for thematic tightness. The team includes editors with backgrounds spanning complexity science, organizational design, and independent content creation, which is reflected in the kinds of questions the journal takes seriously: How do systems behave at scale? What does a feedback loop look like when it's embedded in human institutions rather than computational models? Where does theory fail in practice?

The journal does not publish purely academic work, nor is it a practitioner blog. It occupies a middle register — rigorous enough to make falsifiable or at least testable claims, accessible enough that someone without a PhD in systems dynamics can follow the argument without a glossary.

The Submission Philosophy

Submissions to run 1 were handled through direct invitation and open call simultaneously — a hybrid approach that allowed the editors to seed the run with anchor pieces while leaving room for unexpected voices. The open call was not heavily publicized on mainstream channels, which means run 1 reflects a relatively tight community of writers who were already paying attention to systems-adjacent publishing.

The journal's stated submission philosophy emphasizes three things:

Specificity over generality — "Systems thinking" as a category is broad enough to be almost meaningless. The editors asked contributors to ground their work in a specific system, failure mode, or case rather than writing at the level of abstraction where everything is a system and nothing is a system.
Honest uncertainty — Pieces that admitted the limits of their analysis were preferred over pieces that overstated conclusions. This is a harder editorial standard than it sounds; most writers default to confidence as a rhetorical device.
Writing that stands on its own — The journal does not publish work that requires a companion presentation, a data appendix, or a tweet thread to be comprehensible. Each piece must be complete.

The practical implication: if you are a systems practitioner whose best work lives in slide decks and workshop facilitation, Indie Systems Journal may not be the right venue — at least not without a significant translation effort into prose.

The Curation and Peer Review Process for Run 1 Selections

How Pieces Were Evaluated

The review process for run 1 did not follow traditional double-blind peer review. That is worth being direct about, because it affects how you should read and cite the work. Instead, the editorial team used what might be called editorial peer review: each submission was read by at least two members of the core team, with disagreements resolved through discussion rather than voting. External readers were consulted for pieces that required domain-specific knowledge the editorial team didn't have in-house.

This approach has real advantages and real limitations. On the advantage side, editorial peer review is faster, allows for stylistic coherence, and tends to produce better-written final pieces because the editorial feedback is integrated rather than fragmented across multiple reviewers with different priorities. The limitation is that it is more susceptible to editorial taste functioning as an unacknowledged filter — if the editorial team has a blind spot about a particular approach to systems analysis, that blind spot will show up in run 1.

The editors acknowledged this trade-off in their framing of the run. They are not positioning Indie Systems Journal as a substitute for peer-reviewed academic publication. They are positioning it as a complement: a place where ideas can be developed, tested against a thoughtful readership, and iterated before (or instead of) the academic publication track.

What Got Cut and Why

Understanding what didn't make it into run 1 is as informative as knowing what did. Pieces were declined for the following reasons, according to the editorial process documentation:

Over-reliance on established frameworks without extension — Citing Donella Meadows or Peter Senge without adding anything to the conversation was not sufficient. The editors wanted to see what the writer brought, not just which canonical texts they had read.
Abstraction without anchor — Pieces that stayed at the level of "systems thinking helps organizations adapt" without a concrete case or mechanism were returned for revision or declined.
Length without density — Long submissions were not penalized, but length had to be earned. A 4,000-word piece needed to be doing 4,000 words of work.

These criteria are worth internalizing if you plan to submit to future runs, because they reveal the editors' underlying epistemology: they are skeptical of credentialism, skeptical of abstraction, and skeptical of writing that performs rigor without delivering it.

Contextualizing the Journal Within Indie and Zine Publishing

Where Indie Systems Journal Sits in the Landscape

The past decade has seen a meaningful proliferation of independent publishing outlets for serious nonfiction, particularly in areas that don't fit neatly into academic disciplines. On one end of the spectrum, you have peer-reviewed open-access journals trying to democratize academic publishing (PLOS ONE, arXiv preprints). On the other end, you have Substack newsletters and Notion-hosted blogs where individual practitioners share work informally. Indie Systems Journal is trying to occupy a distinct position between those poles.

The closest analogues are publications like The Prepared (focused on engineering and manufacturing practice), or essay collections published by independent presses like Stripe Press — publications that take ideas seriously without requiring institutional affiliation as a credential for the writer. The zine tradition is also relevant: zines have always been about creating distribution outside of gatekept channels, and Indie Systems Journal inherits that ethos even if its production values are more polished than a stapled-and-photocopied zine.

What "Indie" Signals in This Context

"Indie" in this context means three specific things:

No institutional parent — The journal is not affiliated with a university, think tank, or professional association. This means it is not constrained by the politics or publication norms of those institutions, but it also means it doesn't carry their credentialing weight.
No advertising model — The journal is not optimizing for clicks, shares, or advertiser-friendly content. This frees up editorial space for pieces that are genuinely difficult or that challenge comfortable assumptions.
Small-batch production — Like a small-batch spirit or a limited-edition print run, each run is finite and complete. There is no pressure to produce content continuously to maintain an algorithm's favor.

The trade-off is reach. Independent publications without institutional backing or algorithmic distribution have to build their audience through quality and word-of-mouth, which is slow. Run 1 is a bet that the systems-thinking community is large enough and underserved enough that a rigorous, independent venue will find its readers.

The Broader Indie Systems Publishing Landscape

Indie Systems Journal is not the only outlet trying to serve readers interested in systems thinking outside of academia. Practitioner communities around Wardley Mapping, Cynefin, and complexity science have their own informal publishing infrastructure — conference proceedings, community wikis, and curated reading lists. What distinguishes Indie Systems Journal is its commitment to edited, completed prose as the unit of publication. It is not a forum, not a wiki, and not a repository. It is a journal in the older sense of the word: a place where considered thought gets a stable, citable home.

Why Run 1 Matters Beyond Its Contents

The significance of editorial run 1 is partly about what's in it and partly about what it establishes. First runs set precedents. They define what a publication is willing to publish, how it treats contributors, and what its editorial standards actually look like in practice (as opposed to what they look like in a submission guidelines document). For Indie Systems Journal, run 1 is the record against which future runs will be judged.

For writers in the systems thinking space, run 1 is worth reading not just for the ideas in it but as a benchmark for what the editors value. If you find yourself disagreeing with their selections — thinking certain pieces are too abstract, or not abstract enough, or too practically focused — that's useful information about whether future runs are the right venue for your work.

For readers, run 1 offers something increasingly rare: a small, coherent body of writing that has been shaped by a consistent editorial sensibility. In a content environment where most "curation" is algorithmic, there is genuine value in a human editorial team saying "these pieces belong together, and here's why."

Conclusion

Indie Systems Journal's editorial run 1 is a first-mover publication in a space — serious, independent, systems-oriented writing — that has been underserved by both academic journals and informal practitioner blogs. The editorial team's decision to use a run-based rather than issue-based structure, to deploy hybrid open-call and invited-submission processes, and to apply editorial rather than traditional peer review reflects a set of deliberate trade-offs that prioritize thematic coherence and writing quality over credentialing and volume. Whether those trade-offs pay off will depend on whether the publication can build sustained readership and attract strong submissions across future runs. Run 1 is the evidence to evaluate those questions against. Read it, submit to future runs if the philosophy resonates, and watch how the editorial choices evolve over time.