THE MEDIASPOON MANIFESTO
Publishing is collaborative.
Its workflows should be too.
The most valuable ideas often come from outside the publication itself. We believe the people behind those ideas deserve better infrastructure.
Publishing is collaborative
The most valuable ideas in publishing often come from outside the publication itself — from researchers, experts, authors, practitioners, executives, commentators, and people with direct experience.
Publications depend on these voices. Yet the systems used to work with them are still fragmented, repetitive, and difficult to manage. We believe contributor relationships deserve better infrastructure.
The problem is not always discovery
Publishing technology often treats finding more experts, writers, and sources as the main challenge. Sometimes that is necessary. But many publications already know excellent people: past authors, trusted sources, guests, advisers, researchers, and industry contacts.
The real difficulty is turning those contacts into a reliable contributor network. MediaSpoon starts with the workflow that makes those relationships usable.
Contributors are relationships, not records
A contributor is more than a name in a spreadsheet. They have expertise, preferences, deadlines, reputations, and existing relationships. They may suit a short quote but not a full article; they may be a natural podcast guest but prefer not to write.
These details become more valuable over time. They should not disappear when an editor changes jobs or an email thread is archived.
Contributors should own their identity
A contributor should not need to rebuild the same professional profile for every organization. Their biography, expertise, headshot, attribution preferences, and published history belong to them.
One account. Multiple publications. Separate private relationships. The contributor remains in control.
Every request should be clear
Contributors should know who is inviting them, why they were selected, what is requested, when it is due, where it may appear, how it may be edited, how they will be credited, whether approval is required, and whether the contribution is paid.
A clear request respects the contributor's time. It also creates better work.
Every contribution should have a visible path
A contribution should not disappear after it is submitted. Both sides should understand what happens next: received, under review, revision requested, approved, scheduled, or published.
Visibility creates confidence. It reduces repeated follow-ups and prevents avoidable misunderstandings.
Workflow should be simple
Publishing workflows can become complicated. The product should not. MediaSpoon is built around five actions: Request. Respond. Review. Publish. Repeat.
Everything else should support those actions without getting in the way. The people should remain focused on the contribution itself.
Technology should support judgment
MediaSpoon can organize information, transcribe responses, track deadlines, and reduce repetitive work. It should not replace editorial judgment, decide what deserves to be published, or remove accountability from either side.
Technology should create more room for human thought, context, judgment, and responsibility.
Discovery should be intentional
A large directory is not automatically a valuable network. Quality matters more than volume. Relevance matters more than reach. Trust matters more than the number of profiles.
Contributors should control whether they are discoverable, what they want to contribute to, and which organizations may contact them. Discovery should create meaningful relationships, not more noise.
Published work should strengthen the relationship
Publication should not be the end of the workflow. The contributor should know what was published. The publication should remember who contributed. Both sides should be able to continue without restarting from the beginning.
A good contribution should make the next collaboration easier.
We believe
— Better publishing depends on better contributor relationships.
— Contributors should own their professional identities.
— Publications should preserve the knowledge behind their networks.
— Requests should be clear and submissions easy to track.
— Attribution and approvals should be visible.
— Discovery should be optional and controlled.
— Technology should reduce friction without removing humanity.
— Every successful contribution should make the next one easier.