<aside> 💡 Confusion disclaimer

The subject of this page is „Reference“, which is a „Knowledge Category“. This mean that this page contains the concept of „Reference“.

At the same time this page itself is of the Category Reference.

This might be confusing for readers.

This page should help you to know how to read other References better. And more importantly, write better References yourself.

</aside>

A Reference is a Knowledge Category that provides the reader with concrete information or context on a single subject that enables them to progress autonomously.

Its main purpose is to prevent colleagues from reinventing the wheel by providing the what and the why of a subject in the context of the company using the Ñimbl Knowledge Hub.

A Reference should be an easy and fairly quick read as it’s very focused and only covers a single subject (Principle of Atomicity).

The update frequency varies and depends on new insights in the business or occurs as the result of change processes.

Everybody in the Organisation should be empowered to edit this page and decide when it needs to be sent through the editorial process.

Sometimes a Reference exists to provide one or more links to another resource in- or outside the Ñimbl Knowledge Hub - just like a bookmark.

WhichKnowledge Category to document business processes is often a source for confusion. Clearly, Reference is the right one. A Guide rather gives a rough overview and a Procedure states exact steps that one individual can take in a single session to achieve a goal. A business process might span multiple days and across multiple functions.