Keeping the reasoning outside the tools that produced it

← Architectures

Reference structure · Knowledge structure · Organisations × Psychology

One arrangement for holding an organisation's current model of itself where it survives tool changes and staff changes.

This is one possible structure, not a target state and not a record of a system observed in a specific environment. It is useful while its assumptions hold, and it says where a different arrangement would fit better.

The structural question

Where should an organisation's working understanding live, when the systems that generated it are replaced every few years?

Components

Each part is here for a reason: what it owns, and what it depends on.

• Durable written record

  Owns: Source of record for the current understanding and how it changed.

  Depends on: Depends on plain formats and on someone maintaining it; tolerates no tooling lock-in.

• Project and delivery inputs

  Owns: Their own artefacts; they contribute, they do not hold the record.

  Depends on: Depends on a convention for what gets promoted out of a project into the record.

• Decision references

  Owns: The link between an understanding and a decision taken on it.

  Depends on: Depends on decisions being recorded at all.

• Revision trail

  Owns: What changed, when, and what made it change.

  Depends on: Depends on people editing the record rather than adding a new document beside it.

Ownership and source of record

The record needs a named owner or it silently degrades. Ownership of the record is not ownership of the conclusion — the boundary between 'who maintains this' and 'who can change what it says' is worth making explicit.

Movement through the structure

1. 01

   Project inputs

2. 02

   Synthesis

3. 03

   Durable written record

4. 04

   Decision references

5. 05

   Revision trail

Synthesis is the step organisations skip. Without it the structure becomes an archive: complete, searchable, and not consulted.

Dependencies

The question is whether the dependency matches what the organisation needs.

Intentional coupling

Understanding and revision trail belong together. A current view without its history cannot be argued with.

Costly coupling

Holding the record inside a wiki, CRM or delivery suite couples institutional understanding to a licence renewal and to that tool's structure.

What is hard to reverse

Deliberately high: plain text, plain links, exportable. The irreversible move is adopting a proprietary knowledge product whose model becomes the organisation's model.

When something fails

If the record is not maintained it becomes stale rather than absent, which is the more dangerous failure — it looks authoritative while being wrong. Staleness needs a visible date, not an assumption of freshness.

Assumptions

A reference structure is only reusable when its assumptions travel with it.

What must hold

If these are not true in a given environment, the structure is the wrong starting point.

• Staff turnover or tool replacement is expected on a horizon that makes portability matter.
• Someone will maintain the record; the structure does not supply that person.
• Synthesis is valued over accumulation.
• The organisation is willing to record being wrong, not only being right.

Trade-offs

Each improves something and costs something. Neither side is universally preferable.

• Portability against the convenience of the tools people already use daily.
• A maintained smaller record against a complete unmaintained archive.
• Shared understanding against slower local movement.

What this makes possible

Prior reasoning becomes recoverable, and onboarding can start from what is currently believed rather than from folklore.

What it constrains

It creates maintenance work with no immediate delivery output, which is the first thing dropped under pressure.

How you would know whether it helped

Whether anyone reads the record before re-deciding something, and whether the revision trail shows genuine revision rather than only additions.

What informed this

Technical reasoning about format durability, and repeated practice in organisations where understanding left with individuals.

Another structure may fit when

Another structure may fit when the domain changes faster than any record can track; then a short, dated decision log alone is more honest than a maintained model.

Where this stops fitting

Stops fitting where the organisation is small and stable enough for understanding to be genuinely shared, or where the domain changes faster than any record can track.

Related

Related reading

Industry

• Enterprise SaaS
• BFSI
• Healthcare
• Government
• Pharma

Knowledge · Playbook

• When What the Organisation Learned Leaves With People
• When the Organisation Waits on One Person

Evidence · Observed Situation

• When unrelated frustrations turned out to share one structural cause
• When routine decisions were being escalated because no system carried the context

The situations linked above informed this representation. They do not establish that this structure is right for another environment — that remains a question about the specific organisation, its ownership and its constraints.

Architecture, as a question →Work with Cralgo →