TM1 Fanboy is built on the idea that software history should be written from evidence, not inherited mythology.
Too much writing about enterprise technology collapses into vendor timelines, origin stories, retrospective certainty, or community memory treated as settled fact. TM1 Fanboy is trying to do something stricter and more useful: to work from dated materials, name the sources being used, and stay clear about what each source can and cannot prove.
That approach is personal as well as editorial. Christoph Hein studied modern history before spending more than fifteen years working in business intelligence, TM1, enterprise planning, and related finance technologies. TM1 Fanboy grows out of both sides of that background: historical training that cares about sources, context, and uncertainty, and practical experience that recognizes why these systems mattered inside real organizations.
TM1 Fanboy treats historical sources as the foundation of interpretation, not as decoration for a predetermined story.
Why Sources Matter
TM1 matters here not only as a product, but as a lens into a larger history of enterprise decision-making.
The core question behind the publication is not simply what TM1 was or how it worked. It is why organizations repeatedly believed that new systems would help them understand the business, model uncertainty, allocate resources, and decide better. To answer that well, the publication has to stay close to the record: who said what, when, in what format, for what audience, and under what institutional conditions.
TM1 Fanboy treats historical sources as the foundation of interpretation, not as decoration for a predetermined story.
What Counts as Evidence
The strongest materials are those that anchor claims in a specific time and context:
- original manuals and technical documentation
- advertisements, brochures, packaging material, and screenshots
- trade press notices, reviews, and market comparisons
- conference slides, user-group material, and presentations
- archived websites and public product pages
- patents, filings, acquisition announcements, and legal documents
- interviews, oral histories, and firsthand recollections
- version tables, release notes, and product records
Historical artifacts are evidence, not decoration. Whenever possible, the publication prefers real material over reconstructed summaries, vague recollections, or generic illustration.
What Different Sources Can Prove
Not every source does the same kind of historical work.
- A manual can show how a product was explained to users.
- An advertisement can show what a vendor wanted the market to believe.
- A trade-press notice can establish public visibility at a particular moment.
- A review can show how the market described a product category or use case.
- An interview can preserve memory, motive, and practitioner perspective.
- A version table can support chronology while still leaving distribution details open.
Those are different kinds of proof. Good history depends on keeping them separate rather than collapsing them into one flat narrative.
Research Method
TM1 Fanboy combines AI-assisted research workflows with historical judgment.
AI can help with:
- locating and organizing material
- extracting text from difficult documents
- comparing versions and wording across sources
- identifying recurring themes, names, and dates
- preparing draft notes and structures
But AI does not decide what a source means.
Historical judgment still determines:
- whether a source is contemporary or retrospective
- whether a statement is evidence, interpretation, or marketing
- how contradictions should be handled
- what remains uncertain
- what can responsibly be published
The point is not automation for its own sake. The point is to make the research process more disciplined, more visible, and easier to challenge.
Corrections and Contributions
Readers with historical materials, corrections, contradictory evidence, or firsthand recollections related to TM1, Sinper, Applix, Cognos, IBM Planning Analytics, OLAP, planning systems, or business computing history are welcome.
The most useful contributions are specific: a dated source, a scan, a capture, a manual, a slide deck, an announcement, or a recollection that can be situated in context.