Software that understands the exceptions in a licensing workflow.
In music licensing, “no license required” does not always mean “no payment required.” Xivic worked with Trevanna Tracks to reflect that distinction in its product and improve how teams classify tracks and navigate frequently used media information.
Workflow overview
Separate the rules. Preserve the right work.
Track context
Identify the classification and requirements.
License decision
Control whether licensing documents are required.
Fee decision
Keep payment requirements independent of licensing.
Document behavior
Show the document fields appropriate to each rule.
The task behind the feature
Teams needed to record whether a track required a license, identify its type and keep the appropriate documents available. A track could still need payment records even when a license was not required.
The product needed to show those distinctions clearly in the views and data people used to manage the work.
What users can do in the released workflow
-
Keep payment records available
Mark a license as not required while retaining the payment workflow. Payment documents are disabled only when no fee is required as well.
-
Keep quotes and confirmations
The exception rules no longer disable quote and confirmation documents.
-
Explain and classify the track
Record an exception reason and show it in the track summary when no fee is required. Use track types in list management and CSV imports.
-
Put useful media information first
Favorite media-list blocks so the blocks people return to appear at the top.
The detail that made the change useful
The business rule became clearer during client review: removing the need for a license should not remove the ability to record a payment. The team worked through the combinations with Trevanna, including which documents should remain available and what the track summary should show.
The change had to fit an existing product. The work involved the interface, track data, imports and document behavior. Client feedback also shaped the usability of the media list.
From client review to a working release
- Decide the behavior together Trevanna's product lead worked directly with Xivic's engineering and QA leads.
- Make the scope visible The team reviewed the changes in staging and separated an additional change into its own approved scope.
- Verify the production behavior QA confirmed the license-exception changes and media favorites on live in August 2022.
A product that handles more of the real work.
A team could record that no license was required without losing the documents needed to arrange payment. The interface, track data and document rules changed together, while track classification and media favorites made the surrounding product easier to use.
How we engineer product rules and connected workflowsWhat does your next release need to handle?
Talk with us about the rules, exceptions and connected systems behind the work.