Resonance
Resonance is a system for planning a symphonic orchestra season. It connects departments in a shared environment, allowing the season to be built and evaluated from multiple perspectives, revealing conflicts early and enabling informed adjustments
Developed as a school project guided by Amir Neiman and Dolly Alaluf.
Overview
A symphonic season is the structured plan of an orchestra’s yearly activity - covering concerts, repertoire, artists, venues, scheduling, and budget.
Planning begins with defining seasonal strategic goals, from which repertoire is developed and evaluated against logistical and budgetary constraints, before moving into detailed scheduling and execution.
The Problems
Making goals actionable
Strategic goals are abstract and hard to translate into artistic decisions.
Insights
The season takes shape through iteration, as decisions continuously reshape one another.
Both strategic goals and musical content can be translated into a shared set of content attributes
The Solution
One System, Multiple Perspectives
Planning is grounded in a shared dataset, where stakeholders view the same information through different perspectives, using a common language that links goals and repertoire.
Setting Goals
Goals are translated into content attributes, which determine the season’s intended stylistic balance.
Concert Assembly
Concert elements (works, composers, conductors) are combined to form concerts.
Each element carries attributes that influence the season’s balance, bringing it closer to or further from its desired state.
Series Assignment
The assembled concerts are grouped into curated series
across the season structure.
Scheduling
Concerts are assigned to the venue schedule while
operational conflicts become immediately visible.
Shared Visibility
Cross-department conflicts are directly accessible through a shared dashboard.
Main Screens
Process
Wireframes
