The industry is connected by value. Its intelligence is still fragmented.
Value moves through this ecosystem constantly — money, rights, talent, attention, work. What does not move is understanding. The information needed to improve the system exists, but it is distributed in a way that prevents it from being assembled, compared, or acted on.
- Structural categories
- 9
- Evidence state
- Hypothesis
- Validation status
- Not yet established
Nine problems that reinforce each other
These categories are not a list of complaints. They are a working model of why a large, capable, cash-generating ecosystem repeatedly encounters problems it already knows how to solve — and why the same failure tends to return after it is fixed.
A hypothesis is not a finding
Every category on this page is a structured hypothesis about how the ecosystem's problems interact. Each states what would support it, what would weaken it, and how it could be investigated. None has been validated, and none should be read as a description of how widespread a problem is.
We do not sell identifiable complaints
SolutionSynq will not build a commercial product out of named individuals' grievances. Categories describe structural conditions, not accused parties, and the research model behind them is designed to separate pattern from allegation.
Numbers are not added without a source
No prevalence estimate, market size, or industry statistic appears on this site without a reliable source, a publication date, the context it was produced in, and a link to the original. Where such a source does not exist, the site states the gap rather than filling it. Every source is published in full, with its limits attached, in the evidence review.
What each one is, how it would be tested, and what it would point toward
Select a category to read the full structure: who it affects, how it could be investigated, what would strengthen the hypothesis, what would weaken it, and the intervention it points toward.
Searches the name, summary, explanation, the people affected, the investigation, and the evidence that would support or weaken it.
Showing 9 of 9 problems
The people who experience a problem rarely share a language with the people who understand it, and the people who could solve it are usually not introduced to either. The information exists — it is simply distributed in a way that prevents it from being assembled.
Who it affects
- Everyone in the ecosystem, unevenly
- Most acutely: small independents, freelancers, regional producers
How it could be investigated
- Map where an equivalent problem gets recorded differently across professions
- Compare how five different roles describe the same underlying constraint
- Trace where a known solution fails to reach an adjacent sector
What would support the hypothesis
- Stakeholders independently describing the same constraint in incompatible terms
- Adoption of workarounds that duplicate existing capability
- Repeated requests for guidance that already exists somewhere in the ecosystem
What would weaken it
- Structured channels already connecting the relevant parties
- A shared vocabulary that turns out to exist and be in use
- A single settlement that demonstrably changed practice
The intervention this points to
A shared, neutral structure for describing problems, causes, and capabilities — with enough rigour to compare them and enough accessibility that it does not exclude the people who need it most.
What the published evidence says
These are the published, dated sources that bear on this problem. Each one is stated with its own limits — none of them establishes the whole hypothesis, and the hypothesis stands or falls on the investigation above.
Contexts this is implicated in
A context is listed where the problem is materially present, not because the sector exists nationally.
Connects to
Each problem is also a cause of another
The nine categories are not independent. Fragmentation causes repeated failures because lessons cannot travel; weak institutional memory causes fragmentation because knowledge leaves with people; root-cause invisibility causes repeated failures because remedies target symptoms. Treating them as a connected system — rather than nine separate complaints — is the difference between addressing causes and processing symptoms.
A note on scope
These categories describe conditions across the ecosystem as a whole. They are not a claim about any specific company, platform, studio, individual, or city, and nothing on this page should be read as identifying a specific organisation's practice.
Where the ecosystem genuinely differs — by language, region, scale, or structure — that difference is preserved in the research rather than smoothed away. See the ecosystem explorer for the sector-level view, and our approach for the method that would test these hypotheses.