Editorial Policy

This page explains how articles in the Votito knowledge base are produced, maintained and corrected, and what we explicitly do not do.

What the knowledge base covers

The knowledge base focuses on product-management methods, workshop techniques and delivery practices that help teams clarify outcomes, make evidence-led decisions and reduce waste. The articles are mostly focused on software product management, but many techniques will apply to a wider market. Each article is a reference entry on a single method, with enough detail for a reader to understand the idea, decide whether it fits their situation and start applying it. Articles are written for product managers, product owners, team leads and delivery-focused engineers.

We do not aim to cover every product-management idea in circulation. Topics are chosen for one or more of the reasons set out in the next section.

How topics are selected

A method is a candidate for inclusion when at least one of the following is true:

  • It is part of our own working practice and we can write about it from first-hand experience.
  • It is an important product management technique relevant for the wider community, and it’s described in a primary source (an academic paper, a published book, a conference talk) that we can cite
  • It is an important reference, inspiration or related technique to the above, and it’s described in a primary source (an academic paper, a published book, a conference talk) that we can cite.

We prefer methods that are outcome-driven, evidence-led and focused on impact over output. Methods that have fallen out of credible use, methods that are speculative or unproven and methods that duplicate an article already on the site are not added.

How articles are written

Every article in the knowledge base is written by a named human author. The author is shown in the byline of each article and linked to their author page, which lists credentials, published books and external profiles.

We do not publish articles generated by large language models or other automated text generators. Authors may use automated tools for copy-editing, grammar checks and formatting, but the substantive content is written by the named author.

Sources and citations

Articles cite their primary sources. Where the source is a book, the citation links to a publisher or retailer page and carries full bibliographic metadata (authors, ISBN, publisher). Where the source is a scientific paper, the citation links to the Digital Object Identifier (DOI) on the publisher’s site and carries the journal or venue, year and authors. Where the source is an article, a talk or a practitioner-written piece, the citation links directly to the primary source.

Citations appear in a “Bibliography” block at the end of each article. They are marked up with schema.org microdata so search engines and other downstream tools can resolve them to real publications. External citation links are intended to be followed (readers and crawlers should be able to follow the trail to the original work).

Publication and update dates

Every article shows a publication date and, where applicable, an update date.

  • The publication date is derived from the first commit that introduced the article to our public repository. It is fixed and does not change once an article is live.
  • The update date is shown only when the article has received a substantive content change, such as a correction to a factual error, a meaningful expansion, a revised recommendation. It is not changed for typo fixes, link repairs, formatting changes or metadata-only edits. We deliberately avoid changing dates without changing content so that readers can trust the dates they see.

Current review practice

Articles are not peer-reviewed in the academic sense. There is no independent reviewer who signs off on each piece before publication, and there is no fixed review schedule after publication.

The current practice is:

  • The named author is responsible for the accuracy of the article they publish.
  • Articles are updated when we notice a factual problem, when a cited source becomes unavailable, or when the method has evolved enough that the description is out of date.

Corrections and feedback

If you find a factual error, a broken citation, an out-of-date recommendation or a missing source, please email contact@votito.com. Corrections are applied to the source article; if the change is substantive the article’s update date is changed as described above. Please include the article URL and a brief description of the issue.

General product feedback, feature requests and support questions go through the channels listed on the contact page.

What we do not do

  • We do not run a formal peer-review process.
  • We do not accept paid placements, sponsored articles, or affiliate-driven recommendations of methods. Book citations in the “Bibliography” block may include affiliate links to retailers; the choice of which book to cite is never influenced by affiliate revenue.
  • We do not publish articles whose body text is generated by large language models.
  • We do not back-date articles, and we do not bump update dates without a matching content change.
  • We do not use anonymous or pseudonymous bylines.
  • About Votito — who we are and why the knowledge base exists.
  • Authors — the authors of the knowledge base.
  • Contact — legal publisher, registered company, general enquiries.