liveBook · Manning

Review criterion

As explained in Writing for Developers: Blogs that get read

A stated standard used to assess the suitability or quality of a conference submission.

A review criterion is a stated standard for judging whether a conference submission is suitable and strong. Use published criteria to shape the proposal, bio, title, and abstract before submitting. section 16.3.2

Check the submission against four practical questions:

  • Content: Is the session coherent, relevant, high-quality, and deliverable effectively? section 16.3.2
  • Originality: Does it offer new ideas, approaches, or an original delivery? section 16.3.2
  • Relevance: Will it provide insights or information that matter to the conference audience? section 16.3.2
  • Speaker fit: Do the proposed speakers have suitable expertise aligned with the subject? section 16.3.2

A revision test

Before submitting a proposal, compare its content, originality, relevance, and speaker fit with the conference’s published criteria. Revise weak areas, then keep a copy outside the submission form. section 16.3.2

How Writing for Developers: Blogs that get read covers it

How deep it goes
Defines four judging dimensions and applies them as a revision checklist, without detailing scoring methods or reviewer calibration.
Examples
Uses KubeCon’s content, originality, relevance, and speaker criteria as a concrete evaluation example.
What it assumes
Assumes a conference proposal with a bio, title, and abstract; teaches readers to locate and use published evaluation standards.
What you can do after
Apply it via a criteria checklist to revise a proposal before submission.
How it connects
Connects proposal writing with content quality, originality, relevance, speaker expertise, and effective delivery.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Writing for Developers: Blogs that get read. The section links point to the parts of the book it draws on.