Arsenije Savić
Product and systems designer, engineer, facilitator, and artist. I make complex systems easier to see, use, and change.
I work on the structures beneath the interface.
My work sits between software, organizational design, and culture. I am drawn to systems where the visible interface is only the surface of something deeper: authority, roles, permissions, decisions, resources, relationships, and memory.
I move between product design, engineering, facilitation, and artistic practice because the problems I care about rarely stay inside one discipline. Sometimes the right artifact is an interface. Sometimes it is a protocol, a map, a piece of software, a gathering, or a sound work.
The through-line is agency: making enough of the system visible that people can understand where they are, what they can do, and how they can change the conditions around them.
Tools should extend agency, not replace it.
A principle that connects the product, organizational, and creative work.Three practices, one inquiry into how people orient, relate, and create.
Rhizome
Systems and facilitation for collective coordination: authority, decisions, responsibility, tension, memory, and distributed stewardship.
Practice →Solar
Place-based gatherings, cultural experiments, field recordings, and temporary spaces for encounter.
Practice →Tnikpu
Ritual sound, image, performance, and ancient-future transmissions exploring attention, myth, and symbolic experience.
Practice →Products and systems where structure matters as much as surface.
BOXSPOT
A two-sided booking product coordinating athlete discovery, gym capacity, waivers, payments, and operator workflow.
Case study →Hypha
Product and governance architecture for modular spaces with agreements, members, resources, and decision flows.
Case study →Rhizome
A coordination practice and emerging software system for authority, tension, responsibility, and shared organizational memory.
Case study →Start with the system. Find the smallest thing that makes it more legible.
See the relationships
Before designing screens, I map actors, authority, states, dependencies, incentives, information, and constraints.
Make the hidden explicit
I turn implicit organizational or technical logic into objects, flows, interfaces, and shared language.
Build close to reality
My engineering background keeps product decisions connected to data, backend behavior, edge cases, and implementation.
Keep people in the loop
I prefer systems that increase human judgment and shared capacity rather than hiding consequential decisions inside tools.
A path through interaction design, engineering, platforms, and collective systems.
I began in interaction design, moved deeper into full-stack product engineering, then into founding and product leadership. Work with decentralized and cooperative organizations pulled me toward governance, facilitation, and organizational design.
Today those threads meet in an independent practice: designing products, building systems, researching coordination, and making cultural work from the same underlying question — how can structure support more freedom rather than less?