Maximum size of design artifact that will be fully read and reviewed to increase reliability

Affiliated to

Location

Timing

Description

In a design process, requirements and design documents are created in a shard repository (e.g., a Wiki based environment), in an attempt to keep the design artifacts in use, relevant and up-to-date with implementation. One aspect that can be considered - is the size of the artifacts. Shortening the design artifacts have a better chance of being fully read and reviewed by relevant stakeholders. We are looking for a candidate to participate in the effort of forming a mechanism to monitor and evaluate the use of the artifacts and that will measure the time a stakeholder effectively spends reading a design artifact, and measurements on the areas read. We would like to be able to measure the use of the use of the design artifacts. Also, evaluate the behavior once the artifacts are changed - and need to be re-read - do stakeholders review the whole artifact or just the area that has changed.
From these measurements - we would like to induce a single maximal value of artifact size, so that it will be fully read by stakeholders. A mechanism that is going to be built will ensure that artifacts do not pass this size, so that they remain relevant and in-use.