Axel Pond / Noosaga / product design / frontend engineering
Designing interfaces that teach.
I design and build tools for navigating complex subjects. Noosaga is the flagship: a visual atlas for seeing how fields connect, split, and evolve. This site shows more of the product thinking and interface work behind it.
Live system
Flagship product
Knowledge atlas
Field to framework to concept
1,500+
fields mapped
18
top-level categories
4
core reasoning views
Working rule
Orient the user before trying to impress them.
What ships
- Atlas routes from category to field to subfield
- Compare views for schools, frameworks, and debates
- Concept maps, timelines, guides, and reading paths
- Source labels, confidence states, and AI-assisted workflows
Axel Pond
I design and build tools for navigating complex subjects.
information architecture
interaction design
frontend systems
knowledge mapping
provenance and trust
complex subjects
Why This Site Exists
The product site stays restrained. This site shows more of the reasoning behind the work.
Noosaga keeps the atlas in front. Here I can show more of the decisions behind it.
Interactive Proof
Try the product argument instead of reading about it.
Each mode answers a different question. The point is better orientation, not more features.
Test the claim
Each view should help answer a different question.
Switch modes to see how the same field becomes easier to browse, compare, trace, and trust. This is a working proof, not a screenshot gallery.
Macroeconomics / overview / field spine
Start with the shape of the field, not a random result.
The first screen should show what the field covers, which schools matter, and where to go next.
Field spine
Route clarity
Low-friction overview
Question unlocked
What are the main schools in this field, and where should I go next?
Macroeconomics
Schools
Timelines
Concepts
Guides
Debates
Interface decision
Lead with a field map, clear routes, and one obvious branch into frameworks, concepts, or guides.
User outcome
Users get bearings early instead of committing too soon to one book or article.
Engineering implication
One shared structure has to drive every view so the hierarchy survives across cards, filters, and routes.
The point is not density. It is to make the field legible early.
Method
The work sits where research, design, and implementation shape each other.
I studied mathematics and NLP, and I keep coming back to the same problem: how interfaces change what people notice. That is why the work often starts with a model and ends in code.
Model the field
Start with what the user cannot yet see: categories, rival schools, concept clusters, or source lines.
Choose the right view
Different questions need different views: overview, comparison, maps, and guides.
Build the interface behavior
Hierarchy, motion, responsiveness, and state should help users stay oriented.
Make trust visible
If AI helps shape the content, the interface has to show what is sourced, inferred, and still uncertain.
Flagship Product
Noosaga is a good flagship because the hard parts are structural.
It forces taxonomy, views, trust cues, and frontend behavior to work as one product.
Why it matters
One product, four hard problems, one interface.
Noosaga only works if the content model, views, trust cues, and visual layer support the same outcome.
Read the case studyArchitecture
Taxonomy that stays legible
Fields, subfields, schools, and concepts need a hierarchy that stays clear across every surface.
Interaction
Different views for different questions
Timelines, framework comparisons, concept maps, and guides each teach the user something different.
Trust
Provenance has to survive the pipeline
If AI helps generate structure, the interface has to expose what is sourced, inferred, and still uncertain.
Build
Frontend craft is part of the argument
Hierarchy, motion, responsiveness, and state transitions all need to make orientation easier instead of noisier.
Continue
Continue into the product, the case study, or the lab.
Live product
Open Noosaga
See the atlas in the environment it was built for.
Case studyRead the deeper proof
See the product decisions, view logic, trust cues, and implementation implications in one place.
LabOpen the experiment room
Browse experiments, interface studies, and patterns being tested before they ship.
Connect
If the work is relevant, start with the product.
That is the clearest entry point. The case study, lab, writing, and code show how it is made.