Credits
We didn't invent
any of this.
labsly's tools put a Mac-native interface on methods other people spent careers developing. This page names them. Where a method is field-standard vocabulary, we use the standard name. Where the originator's exact words are theirs to keep, we paraphrase and point back here.
Systems thinking
Systema is built on a tradition that argued, for decades, that the way to fix a complex problem is to model it rather than react to it.
- Donella Meadows — leverage points, and the discipline of asking where in a system an intervention actually lands.
- Jay Forrester — system dynamics, and the stock-and-flow modeling that underlies causal simulation.
- Stafford Beer — organizational cybernetics and the viable system model.
- Russell Ackoff — the case that dissolving a problem beats solving it, and that optimizing parts degrades wholes.
- Peter Senge — system archetypes and the iceberg model, which brought this vocabulary to a much wider practice.
Causal loop diagrams, the iceberg model, system archetypes, and leverage points are all part of this shared inheritance. None of them are labsly's.
Strategy
Simon Wardley created Wardley Mapping — the value chain on one axis, evolution on the other, moving through genesis, custom-built, product, and commodity — along with the doctrine principles and climatic patterns that go with it. He publishes the method under CC BY-SA 4.0, which is why Atlas can be built on it at all.
Atlas ships with its own original example maps. We deliberately do not reproduce Wardley's published example maps, so that nothing in the app depends on someone else's illustrations.
Service design
Lynn Shostack introduced the service blueprint in 1984 — the frontstage / backstage / line-of-visibility structure that service designers still work in. The IDEO and Live|Work tradition turned that structure into contemporary practice: journey maps, service ecosystem maps, and the idea that a service is designed rather than merely operated. This is the foundation for the Service Design app.
Product design
Witness draws on Donald Norman for affordances, signifiers, and the argument that most "user error" is design error; Marty Cagan for product discovery and the distinction between output and outcome; and Teresa Torres for continuous discovery and opportunity solution trees.
Critique and boundary questions
The harder questions — whose problem is this, who decided the boundary, who is left out of the model — come from the critical systems tradition.
- Peter Checkland — Soft Systems Methodology, and the move from "the system" to "a way of seeing the situation."
- Werner Ulrich — Critical Systems Heuristics, and the boundary questions that make an analyst's assumptions arguable.
The epistemic honesty research
labsly's position that AI-generated personas must carry confidence and provenance is not an original insight. It follows a body of work that emerged through 2025 — including The Synthetic Persona Fallacy in ACM Interactions, and CHI '25 research showing that persona prompting can degrade rather than improve fidelity. We built the substrate; the finding is theirs.
Third-party software
Each app ships its own third-party attributions, listing the open-source libraries it depends on and their licenses.
Attributions for the remaining apps are published as each one ships.
Corrections
If we have attributed something incorrectly, credited the wrong originator, or missed someone whose work belongs on this page, tell us at hello@labsly.com and we will fix it.
This page grows as the Suite ships. See the manifesto for how this lineage shapes the tools.